A comprehensive guide to configuring MOAC Profile Options and Security in Oracle R12 & Fusion.
Multi-Org Access Control (MOAC) enables users to access, process, and report on data across multiple Operating Units from a single responsibility. This eliminates the need to switch responsibilities to perform tasks across different business units, drastically improving efficiency.
You must have at least one Legal Entity defined in the system.
Create the Operating Units that you want to group together under MOAC.
Ensure the "Replicate Seed Data" concurrent program has been run for new OUs.
Identify which responsibilities (R12) or Roles (Fusion) will require cross-OU access.
System Administrator / HRMS Super User
System Administrator
System Administrator
System Administrator
Actor: System Administrator / HRMS Super User | Module: Human Resources / Core HR
A Security Profile is a container that defines exactly which Operating Units a user is allowed to see. In MOAC, you create a security profile of type "Operating Unit" and attach the relevant OUs to it.
Example: Create a Security Profile named "North America OUs" and attach the "US Operating Unit" and "Canada Operating Unit" to it.
Navigation Path:
Setup and Maintenance > Manage Data Access for Users
Key Actions:
In Fusion, MOAC is handled via "Data Access for Users" where you assign Business Units to specific roles directly, bypassing the traditional HR security profile method.
Actor: System Administrator | Module: System Administration
Whenever you create or update a Security Profile in R12, you must run the "Security List Maintenance" concurrent program to compile the changes and make them active in the system.
Example: Submit the "Security List Maintenance" program from the Submit Requests window and wait for it to complete normally.
Navigation Path:
N/A (Real-time in Fusion)
Key Actions:
Not required in Fusion. Role provisioning processes handle access instantly.
Actor: System Administrator | Module: System Administration
This is the most critical step. You assign the Security Profile you created to the desired Responsibility or User via the "MO: Security Profile" system profile option.
Example: Set "MO: Security Profile" = "North America OUs" at the Responsibility level for "Payables Super User".
Navigation Path:
Setup and Maintenance > Manage Administrator Profile Values
Key Actions:
In Fusion, this is replaced by "Manage Data Access for Users" (Security context = Business Unit).
Actor: System Administrator | Module: System Administration
When a user opens a form (like AP Invoices), they will have access to multiple OUs. This profile option determines which OU defaults in the "Operating Unit" dropdown field.
Example: Set "MO: Default Operating Unit" = "US Operating Unit". When entering an invoice, "US Operating Unit" will be pre-filled, but the user can change it to "Canada".
Navigation Path:
Setup and Maintenance > Manage Default Business Unit
Key Actions:
Use the "Default Business Unit" profile option or user preferences.
Understand the complete procurement process from requisition to payment.
Read GuideTop SQL queries and interview questions for Oracle Apps technical consultants.
Read Guide