Oracle-R-12 MOAC-Concept
Multi-Org or multiple organization access (MOAC) is basically the ability to access multiple operating units from a single application responsibility. In Release 11i, when one had to enter or process data for multiple operating units, one had to login to different responsibilities because each responsibility could only access one operating unit. If one was managing Payables for Sweden, Norway and Finland one needed to define three different responsibilities. In Release 12, one would create a Security Profile and assign as many operating units as you required. One can tie that security profile to a single responsibility using a profile option called
“MO: Security Profile”.
For example, you could assign the security profile to the ZZ_PAYABLES.. Responsibility to allow that responsibility to process invoices across all (specified as per user need) operating units.
In Release 12, 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 profiles available and allow one to assign them to a responsibility via a profile option called MO: Security Profile.
One can define an operating unit using the Accounting Setup Manager in Oracle General Ledger or Organization Definition form in Oracle HRMS or Inventory. An operating unit is then attached to a default legal context (as compared to Legal Entity in Release 11i)
Define a security profile using either of the two forms: Security Profile form or the Global Security Profile Form that is shown below. Both forms look almost identical where Security Profile Form allows one to select operating units from only one Business Group where as Global Security profile Form allows one to select operating units from multiple Business Groups.
Global 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 subledger application forms. For eg in payables while entering invoices we get LOV of different Operating units to chose from, as shown in demo below.
Business Reason for this change:
If a task was assigned to design a Payables Invoice scanning process that had following requirements:-
- A client had 100s of legal entities and organization units
- They wanted to receive all paper payables invoices at a central location. Effectively, they would have a single Address where invoices for all the Legal Entities/Operating Units were received.
- All the invoices would be scanned at that central location.
- The scanned images were then placed in a queue that were then keyed (typed) into the system by a Team (their shared service Centre)
- This Scenario is possible if Multi Org Access Control is setup at the Specified Responsibility Level. If not, then its not feasible for the concerned team to type each invoice for various Operating unit by switching to different responsibilities.
