About Us Competencies Services Downloads
Whitepapers Featured Business Issue Newsletters


Oracle EBS - Education Series 1
Multi-Org Access Control (MOAC)

What is Multi Org Access Control?

The current design of Oracle EBS (Release 11i) ties user responsibilities to an Operating Unit (OU). This design was cumbersome for users who worked across operating units to perform their basic functions, since they had to change responsibilities based on the OU for which they were recording transactions.
With MOAC, Users can

“Perform multiple tasks across Operating Units without changing responsibilities”

A single application responsibility can now access, process and report on multiple operating units. The new responsibility definition can cut across multiple operating units and multiple legal entities.


Is it mandatory to implement MOAC if we upgrade to R12?

Oracle has kept this functionality as optional in R12. Companies can choose to continue with their current OU based responsibility set up. There could be arguments against opening up multiple OUs to a single responsibility which may lead to erroneous recording of transactions in wrong OUs and subsequent reconciliation issues. Further, if a lot of customizations have been built using the 11i user access model then one may choose to maintain the same set up in R12 too. Keeping this in mind MOAC has been maintained as an optional feature and can be implemented later after a thorough risk analysis.

As part of this feature Oracle R12 provides options to set default operating unit which is specific to a user and also add a list of user specific preferred operating units. It also allows the user to change his “default” OU without navigating to Profile options.

A peep into the Technical Side of MOAC:

MOAC is initialized when you open a Form, Oracle EBS page or a Report. The first MOAC call checks if the profile “MO: Security Profile” has a value. If Yes, then the list of operating units to which access is allowed is fetched and the list of values (LOV) is populated (User specific preferred OUs). Then, default value of the
LOV is set to the operating unit specified in “MO: Default Operating Unit”.

When the profile “MO: Security Profile” does not have a value MOAC switches to the 11i single organization mode. As in 11i, the profile “MO: Operating Unit” is checked and the operating unit is initialized to the one defined in it.

The important point to note here is that the profile “MO: Operating Unit” is ignored when the profile “MO: Security Profile” is set. This enables to use both Release 12 MOAC behavior and 11i behavior simultaneously in Release 12. You can also choose to completely use one of them.

Benefits of MOAC:

MOAC as a feature would benefit Companies that are using Oracle EBS in a Shared Service Environment significantly. Their back office operations are significantly centralized and require one group to perform the same function across different legal entities and operating units. Some of the key benefits of MOAC are:

  • Quicker transaction processing – process data across multiple OUs from one responsibility. For example reduce processing cost with the ability to pay invoices for multiple OUs in a single pay run
  • Obtain a global consolidated view of information across OUs and legal entities. For example Supplier sites, Customer sites across OUs
  • Easier user maintenance and better control – User responsibility set ups are significantly reduced and better compliance in terms of access control

How do we migrate to this feature?

Thirdware has developed a utility to help companies migrate to MOAC in R12 which would reduce the time and cost of implementation/upgrade significantly. Additionally, Thirdware specializes in the implementation of Role Based Access Control in Oracle using core Oracle functionalities to achieve SOX compliance.

Find a Thirdware location nearest to you
Locate Us

Disclaimer    |    Site Map    |    Bookmark and Share
2015 Thirdware Solution Ltd. All Rights Reserved.