MOAC for Order Management
Overview
Multi org access control is implemented in R12 to allow the users to submit requests and
access data of different operating units in a single responsibility.
All Forms that support OU dependent data (setup, transactions) have been changed to
support MOAC functionality.
Operating Unit field is added in the Setup, Find, Summary and Transaction windows for nonfolder forms. For folder-enabled forms, Operating Unit is added as a hidden field and user
can enable it if required.
Profile Options Used in Multi-Org Access Control
The Operating Unit will be defaulted in all OU enabled windows as follows:
If the profile MO: Security Profile is set then

If the Security Profile gives you access to just one Operating Unit, then that will be
the default Operating Unit.

If the Security Profile gives you access to multiple Operating Units, then the value set
for the profile MO: Default Operating Unit is the default Operating Unit.
If the profile MO: Security Profile is NOT set then

The value set for the profile MO: Operating Unit is the default Operating Unit.
MOAC can be achieved by setting the security profile in HRMS. There are 2 security
profiles:

SECURITY PROFILE: is used for the selection of operating units from the same
business group

GLOBAL SECURITY PROFILE: is used for the selection of operating units from the
different business group
General MOAC Setup
1. Define the Security Profile in HRMS:
a. Using HRMS Management responsibility
b. Navigate to: HRMS Manager > Security > Profile
c. Verify that the Security Profile is defined (for the OM responsibility or site level)
d. If it is not yet setup, enter it and attach the Operating Units
e. SAVE
2. Setup MO Profile Options:
a. MO: Security Profile - Setting this profile enables MOAC functionality
b. MO: Default Operating Unit - This Operating Unit will default into OM forms and
reports. You can use the LOV to clear it or change it.
Keep the MO profiles in sync:
MO: Security Profile is set at both the site and responsibility level.
MO: Default Operating Unit is set at the site, responsibility and user level. This profile
determines the operating unit the transaction gets created in. If you enable Multi-Org Access
Control, then you can specify the Operating Unit (from those that are accessible to you via
your MO: Security Profile) in the various transaction forms. Verify the settings of these
profiles if you find the application not behaving as expected.
3. OM Setup:
Review new OM System Parameters migrated from OM Profiles with R12 upgrade:
Order Management Super User > Setup > System Parameters > Values, see NOTE
393646.1-R12 Readiness Cheat Sheet: Migrated OM Profile Options.
4.&clickstream=no"/epmos/main/downloadattachmentprocessor?parent=DOCUMENT&sour
ceId=393634.1&attachid=393634.1:OU_FIELD&clickstream=yes" border="0" alt="Operating
Unit Field" title="Operating Unit Field" hspace="0" vspace="0" />
When you click on the Operating Unit LOV, you will see the list of the Operating Units that
are assigned to the security profile:
Note: lf fields in the Sales Agreement form and Sales Order form are greyed out, then the
profile 'MO: Security Profile' is set but the profile 'MO: Default Operating Unit' is not set and
the Operating Unit field is not enabled to be visible in the folder. The Operating Unit is a key
piece of information and needs to be specified before entering the transaction.
If you are using MOAC then:
1. Enable the Operating Unit field to be visible in the form using the Folder Options.
2. Set MO: Default Operating Unit.
If you do are not using MOAC then unset MO: Security Profile. The Operating Unit will
default from MO: Operating Unit and the application will behave as before.