Mandatory Profile Options in oracle apps

Hi Friends , we are going to discuss about the Mandatory profile options in oracle apps. We will share the detail list of Mandatory profile options which we need to setup in oracle apps. We will share the list of those profile options , which is mandatory in oracle apps setups. These profile options we do set at User , responsibility and Site level in oracle apps. There are some set of profile options which we need to set before using the oracle application. To access the oracle apps , we should have the user access and the required responsibilities but we cannot access the application as it is. We need to set the values for some of the mandatory profiles at responsibility level to access the oracle apps application. These profiles should be set at responsibility level to use or work in oracle apps application. Please find below the complete detail about Mandatory profile options in oracle apps.

List of Mandatory profile options in oracle apps

MO: Operating Unit

We need to Assign this profile option to an application responsibility after this user with this responsibility can access one operating unit. This profile helps to set the Operating Unit for the responsibility. If we want to control, for which Operating unit , the desired responsibility should have the access then we do set this MO: Operating Unit profile for that responsibility. Given Responsibility will only have the access to that operating unit which will be set in the MO: Operating Unit profile.

MO: Default Operating Unit

Use this profile option to specify a default operating unit from the list of operating units assigned to your responsibility through the MO: Operating Unit or MO: Security Profile.

Important Point: If the MO: Operating Unit is set or you have assigned only one operating unit in the MO: Security Profile option, then that single operating unit will be your default operating unit

HR:Business Group

Using this profile option we do link the business group to a responsibility. We do Setup Business Group profile at Site level.

If you use Standard HRMS security this option is automatically set up when you enter the HR: Security Profile option, except in cases where you are using a global security profile (that is, a security profile that does not specify a business group). In this case, you must specifically set up this option for each responsibility.

MO: Security Profile

In Oracle apps r12, define a security profile in HR using the Security profile form or the Global Security profile form, and assign all of the operating units that one would want a responsibility to access. The one needs to run a concurrent request called “Run Security List Maintenance” from HR which will make those security profile available and allow one to assign them to a responsibility via a profile option called MO: Security Profile.

One can define another profile option called MO: Default Operating Unit which is optional and allows one to specify a default operating unit that will be the default when you open different sub ledger application forms.

After you define your security profiles and run the Security List Maintenance program, you can assign them to responsibilities or users using the MO: Security Profile profile option. If you set the MO: Security Profile profile option, you can also set the MO: Default Operating Unit profile option to specify a default operating unit.

If the MO: Security Profile is set, then the MO: Operating Unit profile is ignored.

GL: Data Access Set

Oracle General Ledger uses the GL: Data Access Set profile option to determine the ledgers you have access to. If you want users to access different ledgers for different operating units from the same responsibility, you should define a data access set and then assign it to the GL: Data Access Set profile option for each General Ledger responsibility. You can group multiple ledgers that share the same chart of accounts, calendar, and period type in a data access set or a ledger set

GL Ledger Name & GL Ledger ID

We do set this profile for General Ledger responsibility in oracle apps. We cannot access the GL responsibility without setting these profiles for GL responsibility.This profile option controls the ledger that each sub ledger will use for transaction processing.The ledger assigned to the GL Ledger Name profile option will automatically be assigned to the GL: Data Access Set profile option.

We do set the Ledger to responsibility using this GL Ledger Name & GL Ledger ID profile in oracle apps.

GL Set of Books Name & GL Set of Books ID

This profile we do use to assign the set of books to a responsibility. We do set this profile for General Ledger responsibility in oracle apps. We cannot access the GL responsibility without setting these profiles for GL responsibility.