In this post I will explain the MOAC feature offered in Oracle Apps R12
MOAC – Multi Operating Unit Access control is a major Feature that Oracle has introduced in R12.
In this post I will explain in brief, impact of MOAC in Order Management.
With the MOAC in place, now user can access to multiple operating units without changing the responsibility. This will be of great help to organizations where user need to change responsibilities to access different operating units
Like Shared Services.
To Implement MOAC, Oracle has introduced new field “Operating unit” in almost all UO like Sales Order, Quick Sales Order, Find Windows (Please refer the user guides for complete list).
Now whenever user Navigate to Transaction related forms like Sales Orders, it is mandatory to enter an OU first to create an order. The moment user select the Operating unit, all the fields that are depend on Operating Units like Ship To, Order Type etc will display data that is relevant for the OU.
Apart from the UI’s like Orders Summary, Book Order, Hold will display Orders across all accessible Operating Units. As explained above whenever user change the Operating Unit, system will clear all the operating units sensitive fields.
In Order management LOV’s for all OU dependent fields have been enhanced to display the Operating unit name along with values.
Let’s take the example of item LOV. As we know in OM item LOV will display all the items based on the Item Validation Organization. Item validation org is depending on the Operating Unit. When Operating Unit field has a value (derived or default) the item LOV will display data based on the Item Validation Org for that Operating Unit. If the Operating Unit is cleared or changed the Item field will be cleared. When the Operating Unit field is null, the item LOV will display data for the Item Validation Org setup for the default OU.
Reports
In almost all the reports a new parameter Operating Unit has been added. If user provides the value for this parameter then Report will be executed for that parameter only, but in case user left that blank report will execute for all the operating units (Accessible to user). Not only that once we select the Operating Units all the OU depend parameter reset, so that they will reflect the value for the selected Operating Unit.
Few of OM reports have made Global, i.e. they will execute and display the data for all the operating units (Accessible to user).
Before we start wring sql/plsql etc we have to keep in mind that in R12 all the operating Unit sensitive view has been replaced with the secured synonyms.
So to set the context they need to execute
MO_GLOBAL.Set_Policy_Context
This API has 2 parameters
Context
Org_id
When policy context is set to ‘M’, data from all accessible Operating Units will be returned.
When policy context is set to ‘S’, then only data from the specified Org_Id will be returned.
NOTE – if user don’t set this context all the secured synonym will not return any data.
SETUP – For complete info, please refer my earlier post.
Set the Global Profile
Set MO: Security Profile
Set MO: Default Operating Unit