Introduction to MOAC: For a brief introduction of what MOAC is and stands for refer to MOAC article.

Introduction to Multiple Organization Access Control (MOAC) in Oracle Apps R12

Leave a reply

Multiple Organization Access Control (also referred to as MOAC) in Oracle Apps R12 is an enhancement from the earlier version of Oracle Apps viz. version 11i. This allows multiple organizations to be defined in a single instance of Oracle Apps and allow users to transact across multiple Operating Units without changing responsibilities. In more simpler terms, what this means is that a business conglomerate like Tata Group which has businesses spread across various verticals like Energy, Appliances, Heavy Machinery etc. can be defined and setup in Oracle Apps R12 in a single instance. The data related to each of the businesses can be kept separate and secure by allowing users to only access to Operating Units to which they are granted access to.
Application of MOAC for creating invoices across multiple Operating Units

To get a better understanding of the rationale for implementing MOAC in R12, consider the scenario where a Business Group has multiple Operating Units defined in a given Legal Entity. To enter an invoice for a given Operating Unit in 11i, the user would have had to switch responsibility to create invoice for another Operating Unit. However, in R12, due to MOAC, the user is given access to a specific set of Operating Units for a given responsibility so that the user can directly create invoices for different Operating Units simply by selecting the required Operating Unit from the list of values (LOV) on the Invoice window. MOAC Tutorial Step 1: Create a Responsibility and assign to an existing user

MOAC Tutorial Step 1: Create a Responsibility and assign to a User

Leave a reply

Define a Responsibility to which you wish to restrict access to specific Operating Units. Note: For easy understanding, this tutorial is based on the Vanilla installation of Oracle Apps R12. For the purpose of this tutorial, the user name is Operations. For the purpose of this tutorial, name it as Payables, Vision Operations (USA). To know more on how to assign a Responsibility to a given user, refer to the article on Assign a Responsibility to a user We are going to assign the Operating Units to the responsibility specified above by associating with a Security Profile.

How to define a responsibility in Oracle Apps R12

Leave a reply

A responsibility is an important configuration which allows the user to navigate to the various menus and form functions within that responsibility. For example, to create a new journal, the user should be provided access to the responsibility titled GL User or GL Super User. To define a new responsibility, launch the form by navigating as follows: System Administrator >> Security >> Responsibility >> Define The following form is launched.

Define Responsibility Enter the following details to define a new responsibility. 1. 2. 3. 4. 1. 2. 3. 4. Responsibility Name: the name of the responsibility Application: the name of the application to which this responsibility is being given access Responsibility Key: internal key for the responsibility that is used by loader programs Data Group Name: Standard Application: General Ledger Menu: GL_SUPERUSER Request Group: GL Concurrent Program Group

The purpose of this article is to define and configure a basic responsibility. Menu Exclusions, Excluded Items and Securing Attributes would be covered as part of another article. On entering the above information, the form would look like below:

Define responsibility data Save the form to create the new responsibility. To navigate to the new responsibility, add that responsibility to a user using System Administrator. Then try to navigate to the new responsibility. If the responsibility is not getting reflected in the list of responsibilities, then logout and login again to find the new responsibility. The form below displays after the user navigates to the test responsibility created by the user.

Responsibility Login

MOAC Tutorial Step 2. Define Security Profile in HRMS Responsibility

MOAC Tutorial Step 2: Define Security Profile in HRMS in Oracle Apps R12
Leave a reply

Defining a Security Profile in HRMS Responsibility is an important part of configuring MOAC in Oracle Apps R12. The Security Profile is associated with a list of Organizations (which includes Operating Units). On assigning a Security Profile to a given Responsibility (e.g. Payables Visio n Operations USA) using the Profile Option MO: Security Profile, the user who is assigned to that Responsibility Payables Vision Operations USA is allowed access only those Organizations associated with the Security Profile. To define a Security Profile in Oracle Apps R12, navigate to the following location: Responsibility: Human Resources, Vision Enterprises Navigate to Menu: Security -> Profile (to associate Organizations within one Business Group)

Or Security -> Global Profile (to associate Organizations across more than one Business Group) In this example, we will only cover Profile for the Business Group Vision Corporation. In the form shown below, enter the following values for the parameters.

Define Security Profileal

1. Name: Give a name for the new Security Profile 2. Business Group: Select the business group within which we need to assign the Operating Units 3. Under Organization Security, for Security Type: Select Secure organizations by organization hierarcy and/or organization list 4. Classification: Select Operating Unit 5. Organization Name : Select Vision Communications (USA) 6. Add one more Operating Unit called Vision Services After filling out the details, the form would like below:

Security Profile Details Entered Save the form. A new security profile called Testing new Security Profile has been created and saved. MOAC Tutorial Step 3. Run the concurrent request Security List Maintenance

MOAC Tutorial Step 3: Run the concurrent program Security List Maintenance
Leave a reply

After configuring the Security Profile in HRMS Responsibility, run the concurrent program Security List Maintenance to update the Security Profile. The following parameters are requested by this concurrent program. Generate Lists for: One Name Security Profile Security Profile: Testing new Security Profile

Security List Maintenance Program Run this concurrent request and submit. Ensure that this concurrent program completes normally.

MOAC Tutorial Step 4. Assign the Security Profile created above to the profile option MO: Security Profile

MOAC Tutorial Step 4: Assign the Security Profile to Profile Option of Responsibility
Leave a reply

After the Security Profile is created and the concurrent program Security List Maintenance is run, assign the Security Profile to a profile option called MO: Security Profile to a given Responsibility. To assign the Security Profile to a Profile Option in Oracle Apps R12, navigate to the following location: Responsibility: System Administrator Navigate to Menu: Profile-> System In the following form, enter the following values

1. Responsibility: Payables, Vision Operations (USA) 2. Profile: MO: Security Profile 3. Under responsibility, assign the Security Profile Testing new Security Profile and save the form.

Associate Security Profile to Profile Option MOAC Tutorial Step 5. Test the MOAC

MOAC Tutorial Step 5: Testing if the MOAC is working fine.

Leave a reply

To test if the MOAC is working fine, navigate to the Invoice entry form in the responsibilityPayables, Vision Operations (USA) and view the list of Operating Units that are displayed. The list of Operating Units should be listed as follows: 1. Vision Services 2. Vision Communications (USA)

Invoice Workbench