​@AELDENISE if you’re in IFS CLoud, the solution to your scenario would be to create a different context for users that shouldn’t see price fields as editable.

Then you can leave the global context for your people that need to full access to update prices and map the 2nd context to people that should only see the data.

Thanks, when we go to Cloud we can look at that, but right now we are on Apps 10 and prefer to fix via permission sets (if it were possible, but not able to as it is not that granular).

​@AELDENISE, you can make Price/Currency field Read only with a separate profile and later on you can share the profile desired business users.

Long back have handled such requirement through Profile.

​@Marcel.Ausan correct me if I am wrong.

Hi ​@Abdul 

We didn’t want to have more than one base profile per country but instead to refine the access via permission sets.  However, as you say, the only option is probably via a base profile.

Many thanks,

Denise