Oracle R12 : Multi-Org Access Control (MOAC)

Release 12 sub-ledgers can process transactions for multiple operating units from a single responsibility (without changing responsibilities). Using Multi Org Access Control security features we can control responsibilities access to operating units in a shared services environment. These operating units can span across Business Groups.

For demo purpose let’s use vision instance, in the screen shot below you can see multiple operating units in the List of Values before setting up the security. In this demo we will setup to show only 2 operating units Vision Operations and Vision Construction in the List of Value for Payables,Vision Operations (USA) responibility.

Users need to plan the responsibilities as needed and setup security profiles.

AP Invoice Entry Screen:

To setup this access control three steps were involved:
1. Define Global Security Profile
2. Run Security List Maintenance Program
3. Assign the new security profile to MO: Security Profile
Let’s check the setup in detail:

Step 1: Define Global Security Profile
Responsibility : Human Resources
Navigation : Security–>Global Profile

Step2: Run the Security List Maintenance Program
Responsibility : Human Resources
Navigation : View–>Request–>Submit New Request

Step3: Assign the Security Profile to the MO: Security Profile
Responsibility : System Administrator
Navigation : Profile->System
Note: We use Payables, Vision Operations (USA) for this demo

Note: Check the AP Invoice Entry Screen after assigning the MO: Security Profile

-------------------------------------------------------------------------------------------------------------------
The Security Profiles form allows you to group together Operating Units

Define the security profile for the order management responsibility:

Navigate: HRMS Management responsibility:

1. HRMS Manager > Security > Profile
2. Verify that the security profile is defined for the OM responsibility.
3. If the security profile is not yet setup, enter it and attach the operating units
4. SAVE

The Security List Maintenance concurrent program must be run each time you add or change Security Profiles.

There are three Profile Options you need to be aware of related to Multi-Org that should be set at the Responsibility Level.

•         The R12 profile option ‘MO: Security Profile’ is always evaluated first.

•         The pre-R12 profile option ‘MO: Operating Unit’ still works in R12.  It is just a secondary priority being evaluated after ‘MO: Security Profile’.

•         The R12 profile option ‘MO: Default Operating Unit’ sets the default Operating Unit for transactions when running under a Security Profile.

Many R12 applications modules do not work with ‘MO: Security Profile’ set for a given responsibility. 

•         They must only use ‘MO: Operating Unit’.

•         Some even require all three Profile Options set.

Examples:

–         CRM Modules

–         Certain GL Drill Down Functions

(Trial and error determination of setups, no clear direction)

Now check the operating unit field in the order’s screen

Vision Operations defaults as the operating unit in the form per profile option setting for ‘OM: Default Operating Unit’ at responsibility level