Multi-Org Access Control (MOAC) enables companies that have implemented a Shared Services operating model to efficiently process business transactions by allowing them to access, process and report on data for an unlimited number of operating units within a single applications responsibility.

Features of MOAC

• Access multiple operating units within a single application responsibility.
• Perform following tasks for and across multiple operating units with out changing responsibility.

Set-up controls, Negotiate sales agreements

Enter quotes, orders and returns

Schedule orders, Apply and Release holds

Run reports and concurrent programs

Setup Transaction Type, apply and release holds

This increases the productivity of Shared Service Centers, as users no longer have to switch application responsibilities when processing transactions for multiple operating units at a time.

Ability to view data from multiple operating units from a single responsibility, gives users more information. This enables them to make better decisions. For example when performing scheduling actions, users can now look at orders across multiple operating units and make more informed decisions on inventory allocation.

To support Multi-Org Access Control the Operating Unit has been has added as a hidden folder field in the following forms:

• Sales Order Form
• Find window (All tabs)
• Quote window, Find Customer window
• Sales Agreement Form
• Scheduling Organizer
• Pricing and Availability
• Order Import.

Since operating unit is a hidden field we can made it visible (using folder tools).

Setup required for MOAC

At a high level we need to set-up security profiles that allow access to multiple Operating Units. We also need to set the following MO profile options, in order to enable Multi-Org Access Control:

MO: Security Profile

MO: Default Operating Unit.

Note that if you do not set these profiles the application will behave as it does now

• We need to set the Security Profile at MO: Security Profile – This is Mandatory step to accessing multiple operating units from single responsibility but optional for cases where only one Operating Unit is accessed.
• We can default the Operating Unit, which is frequently used on your forms, pages or Concurrent programs.

Setup Details

Go to Responsibility –> Human Resource

Navigation: Security –> Global Profile

Select Global Profile

• Enter a Name for Profile.
• Select security type as “Secure Organizations by Organization Hierarchy and/or organization list”. Select the classification as Operating unit and the Organization name as the Name of all operating units that you want to provide to responsibility or user.

• All operating units that are to be associated to this security profile should be added in the Classification/Organization Name section. In a consistent example this would have been Denmark, Germany and Austria.
• Save and Exit from Global Security Profile

Run Security List Maintenance

Responsibility: US Super HRMS manager

Navigation: Navigate to View –> Requests –> Submit a new request –> Single Request

The Security List Maintenance concurrent program has to be run. This has to be run each time a new security access profile has been created or updates have been made.

Set Profile Options

The security Access Profile is to be associated to the user/responsibility which is done via the profile option “MO: Security Profile”

Responsibility: System Administrator

Navigation: Profile –>System.

Query for the Profile: %Security Profile%

In the System profile Form, assign the Responsibility /User to the Profile MO: Security Profile.

For more details on setup, implementation steps of MOAC, reach us at support@ibizsoftinc.com