What are Profile Options in Oracle Apps ?

Profile Options give adaptability to Oracle Apps. They are a key segment of Oracle Applications, consequently these much be seen legitimately. I will be taking numerous samples here to clarify what profile alternatives mean. I will likewise attempt to clarify by going into Oracle shoes "By what means will you outline a program that is adaptable", by utilizing Profile Options.



Taking after that, on the off chance that in any case you have inquiries with respect to profile choices, then leave a remark and I guarantee to react. For the learners of Oracle Apps, comprehension profile alternatives is required. 

What is profile alternative? 

The profile alternative acts like a Global Variable in Oracle. 

Why does Oracle give profile alternatives? 

These are given to keep the application adaptable. The business governs in different nations and different organizations can be diverse. Consequently the profile alternatives are conveyed by Oracle in such a way to stay away from hard-coding of rationale, and to let the execution group at site choose the estimations of those variables. 

Profile Options Examples 

Firstly, lets characterize the obligation regarding Clerk, as we talked about in Article.



Next, lets define the sales manager responsibility, as we discussed in Article.




Lets define user JOHN, that is Clerk




And also, lets define user SMITH ( Sales manager )





Now, we need to define the profile option for discount, hence go to responsibility "Application Developer"





When you click on menu "Profile" above, you will then see below screen for defining profile option. Please note that the "Name" field is the short name of profile option, and it is this name used in API call to FND_PROFILE.value






Now, after having defined a profile option, its time to assign these to JOHN & SMITH.
Hence go to responsibility "System Administrator"





Click on Menu Profile/System, as below




The profile option assignment screen looks like below. Enter JOHN in USER, OEPASSI% in Profile, to select profile named "OEPASSI Maximum Discount Allowed"




Assign a value of 5 to the user.





Click on torch, to return to search screen as below




and this time we will assign value of 15 against user SMITH.




OK, what if we have too many clerks, we can also simply assign profile value to Responsibility of Clerk. Doing so, all the users that use this responsibility, will inherit profile option value against Responsibility.








Assign 5% max discount for Clerks




Now, lets select Sales Manager responsibility in profile screen



Search on this...as below......




Assign value 15% to Sales Manager responsibility.
That's it for setup.



Enough definitions, provide for me a few situations where profile alternatives are utilized by Oracle.... 

1. There are profile alternatives which can turn the debugging on, to create debug messages. Say one of 1000 clients reports an issue, and henceforth you wish to empower debugging against simply that particular client. For this situation you can "Turn On" the debugging profile choice "again that particular client". 

2. There are profile alternatives that control which client can offer markdown to their clients at the time of information entrance. You can set profile alternative "Rebate Allowed" to an estimation of either Yes or No against each one Order Entry client. 

3. Lets accept an Organization has office D1 and D2. Directors of both the Departments have "HRMS Employee View" obligation. Be that as it may you don't need Manager of D2 to have the capacity to see the rundown of Employees in Organization D1. Subsequently you can set a profile choice against the username of each of these clients. The worth alloted to such profile alternative will be "Name of the Organization" for which they can see the workers. Obviously, the SQL in screen that shows rundown of workers will channel off the information focused around "logged in clients profile choice worth". 

How about we take a case. How about we expect you are an engineer in Oracle Corporation assembling a screen in ERP. Give us a chance to further accept that you are creating an Order Entry screen. 

Expect that business necessities for your improvement work is:- 

1. Screen ought to be adaptable to guarantee that diverse clients of the screen can give distinctive levels of rebates. For instance, an agent Order Entry User can give close to 5% rebate. However Sales Manager can enter an Order with 15% markdown. 

2. There ought not be any hard-coding in regards to the most extreme reasonable rebate. 

3. In the screen there will be a rebate field. 

4. At the point when the rebate quality is entered in markdown field, a blunder will be raised if client damages the greatest admissible markdown. 

Here is the way Oracle will code this screen 

1. They will characterize a profile choice named "OEPASSI Maximum Discount Allowed". 

2. The short name of this profile choice is "Oepassi_max_discount" 

2. In the when-approve thing of the rebate field(assuming Oracle Forms), after code will be composed 

On the off chance that :oe_line_block.discount_value > fnd_profile.value('oepassi_max_discount') 

At that point 

message( 

'You can't give rebate more than " 

|| fnd_profile.value('oepassi_max_discount') || "%" ) ; 

raise form_trigger_failure ;- - I mean raise lapse in the wake of appearing 

END IF ; 

Here is the way, the customer executing Oracle Order Entry will design their framework. 

1. Explore to System organization and click on framework profile menu. 

2. For Clerk User(john), set estimation of profile "OEPASSI Maximum Discount Allowed" to 5 

For Sales Manager User(smith), set estimation of profile "OEPASSI Maximum Discount Allowed" to 15 

Question: This sounds great, however imagine a scenario where you have 500 Order Entry Clerks and 100 Order Entry Sales Managers. Do we need to allocate profile alternative qualities to every 600 clients? 

Answer : Well, for this situation, each one Clerk will be alloted Responsibility named say "XX Order Entry Clerk Responsibility" 

Every Sales Manager will be doled out Responsibility named say "XX Order Entry Sales Manager Responsibility" 

For this situation, you can relegate a profile choice quality to both these obligations. 

"XX Order Entry Clerk Responsibility" will have an esteem 5% doled out against it. On the other hand, "XX Order Entry Sales Manager Responsibility" will have a profile choice estimation of 15% relegated. 

In the when-approve thing of the rebate field, after code will then be composed 

On the off chance that :oe_line_block.discount_value > fnd_profile.value('oepassi_max_discount') 

At that point 

message( 

'You can't give rebate more than " 

|| fnd_profile.value('oepassi_max_discount') || "%" ) ; 

raise form_trigger_failure ;- - I mean raise slip in the wake of appearing 

END IF ; 

If you don't mind note that our coding style does not change despite the fact that the profile choice is currently being doled out against obligation. The reason is that API fnd_profile.value will take after rationale like underneath. 

Does Profile choice quality exist against User? 

-Yes: Use the profile choice quality characterized against the client. 

-No: Does Profile choice quality exist against Responsibility 

-Yes: Use the profile choice quality characterized against the current obligation in which client has logged into. 

-No: Use the profile choice quality characterized against Site level.