The multiple organization access control (MOAC) feature enables users to enter and process transactions in two or more operating units without switching responsibilities.
You must define a security profile in Oracle HRMS and assign it to the profile option MO: Security Profile at the responsibility level to provide multiple operating unit access to a responsibility. You can use individual operating units and/or organization hierarchies with organizations classified as operating units while defining the security profile. Users associated with responsibilities that have been set up in this manner can enter and process transactions in multiple operating units without changing their responsibility.
If the MO: Security Profile option grants a responsibility access to an operating unit that does not have Oracle Projects implemented, then that operating unit will not be displayed in the operating unit list of values on the Projects windows or pages. However, the operating unit list of values in the Implementation Options window will display all the operating units that the user has access to. You can implement Oracle Projects for that operating unit here.
Whenever you make changes to the security profile in use, including the addition or deletion of operating units, you must subsequently run the Security List Maintenance process (PERSELM) in Oracle Human Resources.
The MO: Operating Unit or the MO: Security Profile profile options determine the list of operating units the user has access to for a responsibility.
When you have access to more than one operating unit based on the operating units assigned to the MO: Security Profile profile option, you can define the MO: Default Operating Unit profile option. This profile option determines the default operating unit that will be displayed in the Operating Unit field.
If the MO: Security Profile profile option is not defined, then the operating unit assigned to the MO: Operating Unit profile option is used as the default operating unit.
If the MO: Security Profile profile option is defined, and a responsibility has access to only one operating unit through this profile option, users with that responsibility will see that operating unit as the default operating unit.
Note: The MO: Operating Unit profile option was used in earlier versions of Oracle Projects that did not include Multiple Organization Access Control. When you set the MO: Security Profile option for a responsibility, it overrides the MO: Operating Unit value. But if you do not set any value for MO: Security Profile option, you still need to define MO: Operating Unit profile option.
The following table shows examples of how the operating unit field will be populated if the MO: Operating Unit, MO: Security Profile, and MO: Default Operating Unit profile options are either set with values or left blank.
| MO: Operating Unit | MO: Security Profile | MO: Default Operating Unit | Operating Units Displayed |
|---|---|---|---|
| No | Yes (Vision Services, Vision Services R&D, Vision Project Manufacturing) | Yes (Vision Services) | Default OU =Vision Services. Other OUs = Vision Services R&D, Vision Project Manfacturing |
| No | Yes (Vision Services) | No | Default OU = Vision Services |
| Yes (Vision Services) | No | No | Default OU = Vision Services |
| Yes (Vision Services R&D) | Yes (Vision Services, Vision Services R&D, Vision Project Manufacturing) | Yes (Vision Project Manufacturing) | Default OU = Vision Project Manufacturing, Other OUs = Vision Services, Vision Services R&D |
| No | Yes (Vision Services, Vision Services R&D, Vision Project Manufacturing) | No (not present in security profile. For example in Progress S&L) | No Default OU. All OUs = Vision Services, Vision Services R&D, Vision Project Manufacturing |
The first row in the table can be explained as follows. The MO: Operating Unit profile option is not set, but the MO: Security Profile profile option is set for the operating units, Vision Services, Vision Services R&D, and Vision Project Manufacturing. Similarly the MO: Default Operating Unit profile option is set for the operating unit Vision Services. In this example, the operating unit field will be populated with Vision Services as the default value. However, you will also find Vision Services R&D, and Vision Project Manufacturing operating units in the list of values.