System Profile values in oracle apps

Hi friends, we are going to discuss about the System Profile values in oracle apps. We will share the detail steps to set the system profile values. System profile is the option provided by oracle to view and set the profile values to control the oracle application behavior. In system profile window , we do set the profile option values and based on that application behavior got changed. If we want to control the application behavior based on some users or on some responsibility , then we do use profile values for that requirement. Profile options helps to drive the run time application values which helps to control and working of the application. If we want drive run time values from application then profile option is the best way. Please find below the complete detail about System Profile values in oracle apps.

Two types of System Profiles in Oracle apps

1.Standard System Profile.

2.Customer System Profile.

Standard System Profile: -

Oracle apps has already provided the many standard profile which we can use and set the values to control the application behavior. For example 'MO: Operating Unit' is the standard profile which we set to control the application user access in the application. whats ever the operating unit value we will mentioned for this profile , we can access the operating unit only in the application. We cannot access the other operating unit after setting this Profile option. So we can understand that how the profile options helps to put control the in the application. If we want to change the Application color or want to set some default printer in application we can all control with the help of standard system profiles.

Customer System Profile:-

For example , We have two Oracle responsibilities Payable Inquiry & Payables Manager. We want to make the AP Invoice Description field required through Oracle form Professionalization but these is one catch in this. We want that AP Invoice Description field will be required only for Payables Manages responsibility but not for 'Payable Inquiry' responsibility. In this case , We will create the custom profile and provide the option of 'Yes' or 'No' for this profile option.

Then we will set this custom profile option to 'No' for 'Payable Inquiry' but 'Yes' for 'Payables Manager' responsibility.

In AP Invoice oracle form Professionalization , we will refer this custom profile as an condition to make the Invoice description field required. Based on this custom Profile Option value , Invoice description field will be required for 'Payables Manager' responsibility but Not required for 'Payables Inquiry' Responsibility.

Oracle System Level to set System Profile values

We can set the system profile option values on these three levels.

1.Site Level

2. Responsibility Level.

3.User Level.

Site Level:-

If we will set any profile at site level then this will apply to all oracle responsibility and all oracle users.

Responsibility Level :-

If we will set any profile at responsibility level then this will apply to that oracle responsibility only.

User Level :-

If we will set any profile at User level then this will apply to that oracle User only.

Usually , we set the system profile values at Responsibility Level & User Level .

Steps to set the system profile values in oracle apps

Here below we will share the steps to set the system profile values in oracle apps.

In this case , we are taking an example of 'MO: Operating Unit' system profile. We will set this profile to 'Payables Manager'. We will set the value of 'Vision Operating Unit' for this responsibility so that this responsibility can only have the permission to access the data of Vision Operating Unit in oracle application. This 'Payables Manager' responsibility will not be able to access the data of other Operating unit except 'Vision Operating Unit'

Step 1:-

To set the value to custom profile , we need to go to the system administrator responsibility.

Profile ==> System.

How to create custom profile in oracle apps r12

Step 2:-

Here below , we are going to set the 'MO: Operating Unit' for responsibility 'Payables Manger'

System Profile values in oracle apps

Step 3: -

Here below , we are going to set the system profile 'MO: Operating Unit' value ' Vision Operating Unit' .

It will control to access the oracle application for responsibility 'Payables Manager' to ' Vision Operating Unit' only.

System Profile values in oracle apps

How to create the System Profile and set the System Profile values in oracle apps

Step 1:- Go to Application Developer Responsibility.

Profiles:- Setting System Profile values in oracle apps

System Profile values in oracle apps

Step 2:- Here below , We have created the Custom Profile.

Name: XX_DESC_REQUIRED_PROFILE

Application: Payables

User Profile Name: Invoice Desc: Required

System Profile values in oracle apps

Step 3:- Now we want to provide the LOV to our custom profile. To create the LOV for Yes and No , we need to create the Lookup and then write the sql query to refer that lookup to show the LOV in this custom profile.

System Profile values in oracle apps

Step 4:- Here below , we have create the Custom Lookup to show the lov in the custom profile.

Type: XX_DESC_REQUIRED_Y_N

System Profile values in oracle apps

Step 5:-

Now , here below we have write the sql query which is referring the custom lookup 'XX_DESC_REQUIRED_Y_N'

SQL Query : SQL="SELECT MEANING \"Run in Debug Mode\",LOOKUP_CODE

INTO :visible_option_value,

:profile_option_value

from FND_LOOKUP_VALUES_VL

where lookup_type='XX_DESC_REQUIRED_Y_N'

COLUMN="\"Run in Debug Mode\"(10)"

System Profile values in oracle apps

Step 6:- Now our custom profile has been created. We are now using this Custom profile to set the system profile value for this custom profile in Payables responsibilities and to refer in the form personalization.

System Profile values in oracle apps

Step 7:-

To set the value to custom profile , we need to go to the system administrator responsibility.

Profile ==> System.

System Profile values in oracle apps

Step 8:- Here below , We have two Oracle responsibilities Payable Inquiry & Payables Manager. We want to make the AP Invoice Description field required through Oracle form Professionalization but these is one catch in this. We want that AP Invoice Description field will be required only for Payables Manages responsibility but not for 'Payable Inquiry' responsibility. In this case , We will create the custom profile and provide the option of 'Yes' or 'No' for this profile option.