Friday, 13 September 2013

Multi Org Access Control (MOAC)

Multi Org Access Control (MOAC)

MOAC is a new feature introduced by oracle in R12. MOAC is of 2 types

1.)   Local MOAC: It is used to access the data of Multiple Operating Units from a single responsibility of the same Business Group.
2.)   Global MOAC: It is used to access the data of Multiple Operating Units from a single responsibility of Multiple Business Groups


Create LOCAL MOAC:


Navigate to HRMS Responsibility > Security > Profile & Give details as shown below


Create Global MOAC:

Navigate to Security > Global Profile & give details as shown below


In the above shown form, we have added the operating units of VS Business Group as well as that of Vision India Business Group so the user can access any of these operating units from a single responsibility.

Once done run the concurrent program “Security List Maintenance” with the parameters as shown below



Creating Responsibilities for Purchasing & Receivables

Navigate to Sys Admin Responsibility > Security > Responsibility > Define




Assign these responsibilities to the user

Setting up profile options for the responsibilities in context of MOAC

We need to set the values for following profile options

1.)   MO: Operating Unit – When ever we define “MO: Operating unit” profile option for a particular responsibility (say purchasing) with a particular operating unit then that operating unit will be used for all the transactions which we do from that responsibility.
2.)   MO: Security Profile – When ever we define “MO: Security Profile” profile for a particular responsibility then that responsibility can be used for doing transactions for any of the operating unit defined in that security profile
3.)   MO: Default Operating Unit – Generally “MO: Default Operating Unit” will be used in conjunction with “MO: Security Profile”. It will decide that out of all operating units defined within a security profile, which will be getting defaulted.





Similarly do the setups for other responsibility

No comments:

Post a Comment