Multi-Org Access Control’ (also known as ‘MOAC’ in short form) is an enhanced feature of Release 12. MOAC enables users to access secured data in multiple operating units from a single responsibility. End-Users can access/transact data within several operating units based on a Security Profile attached to the responsibility.   

                                                            MOAC Setups
1. Define Responsibilities for GL, AP,AR,FA,CM.

2. Define Business Group.
3.Define Ledger.
4.Define Operating Unit.
5. Define Security Profile.
6. Run Security List Maintenance Program.
7. Assign Security Profile to Responsibilities.  
8. Run Replicate Seed Data Program. 

 1. Define Responsibilities for GL, AP,AR,FA,CM.

Navigation: System Administrator –> Security –> Responsibility –> Define.

Responsibility for GL.

 Responsibility for HRMS.


   Responsibility for AP.

    
  Responsibility for AR.


Responsibility for FA.

                                                     

Responsibility for CM.


Setup 2: Define Business Group
Navigation: HRMS –> Work Structures –> Oraniazation –> Description.
Click on New button.


 Click on Others.
Select Business Group information.

  
Click on Ok and Save.

Once we created the business group system default assigned the business group to your HRMS Responsibility.

 Assign Business group to your HRMS Responsibility.
Navigation System Administrator –> Profile –> Systems.

Setup 3: Define Ledger.

Setup 4: Define Operating Unit.

Setup 5: Define Security Profile.
The security profile determines which applicant, employee, contingent worker and other person type records are available to holders of the responsibility the profile is linked to.
You can define security profiles in the Security Profile window to give access to a single business group or the Global Security Profile window (to allow users to access records from more than one business group).
Using the Global Security Profile window does not give Oracle HRMS users access to records from multiple business groups within the same responsibility; users must still switch responsibilities to see records from different business groups. However, HRMS users can see a restricted set of information in records from more than one business group within a single responsibility if the HR:Cross Business Profile profile option is set to Yes. In addition, you can use people management templates to query and update worker information across business groups using a single responsibility.
Navigation: HRMS –> Security –> Profile.
Click on Save.
NoteThe above security profile will access only single business group information.

 6. Run Security List Maintenance Program.

Navigation: HRMS –> Processes and Reports –> Submit Processes and Reports —> Single Request
Click on Ok and click on Submit.
Global Security Profile:
  
By using Global security Profile we can access one or more business group at a time under single Responsibility.
Navigation: HRMS –> Security –> Global.
 Click On save.
 Run Security List Maintenance Program.
Navigation: HRMS –> Processes and Reports –> Submit Processes and Reports —> Single Request

Click ok and then submit.

7. Assign Security Profile to Responsibilities.
Navigation: System Administrator –> Profile –> System
Click on Find.
  Save.
8. Run Replicate Seed Data Program.
Navigation: System Administrator –> Request –> Run –> Single Request
 Click ok and submit.


2.1. Intercompany Invoicing Cycle

When a sales order is entered in an operating unit, and if the shipping warehouse is part of a separate operating unit (may also belong to another SOB), then the goods can be shipped from the said shipping organization and the selling organization generates a customer invoice. Also the system automatically records an intercompany sale between the shipping organization and the selling organization by generating intercompany invoices. This is called Intercompany invoicing.

After entering the order in Selling operating unit, you can pick release and ship confirm the order from Shipping Operating unit. Then the following programs need to be run to ensure necessary Intercompany invoices are created ..

  1. Launch the Cost Manager in Inventory > Setup > Transactions > Interface Managers. If it is not active then go to Tools  and Launch Manager. Intercompany Invoices will not be generated unless this manager is active.
  2. In Shipping OU run ‘Create Intercompany AR Invoices’. Ensure that the items shipped have a price for ‘Internal Price List’.
  3. In Shipping OU run ‘Receivables AutoInvoice Program’
  4. In Selling OU run ‘Create Intercompany AP Invoices’. Ensure that the conversion rates between the functional currencies of above SOBs exist for the current date and GL period is open in both OUs.
  5. In selling OU run ‘Expense Report Import’ (Payables)

2.1.1. Transaction Steps

Create an Order in ‘Vision Operations’ OU and schedule it from D1 warehouse under ‘Singapore Distribution Centre’ OU as ..


After Pick release and shipconfirm the order, the delivery associated with the line is closed as ..

  • The Create Intercompany AR Invoices process creates invoice lines for order shipment transactions in Oracle Inventory where the shipping warehouse does not belong to the order entry operating unit.
  • The Oracle Receivables AutoInvoice program processes the records inserted into the interface tables by the Create Intercompany AR Invoices process.
  • Find the AR Invoice that has been generated in Shipping OU by querying for source ‘Intercompany’ and optionally by the Sales Order.

  • Create Intercompany AP Invoices process creates records in Payable invoices interface tables.
  • The Oracle Payables ‘Expense Report Import’ program processes the records inserted into the interface tables by the Create Intercompany AP Invoices process. All invoices created by the Create Intercompany AP Invoices program have Intercompany as their source.
  • Find the Payables Invoice that has been generated in Selling OU by querying for supplier and today’s date.

  • The customer invoice automatically gets created if the ‘Workflow background process’ is running. Find it in Selling OU by querying for the transaction source as ‘ORDER ENTRY’ and with a date range.

2.2. Set up steps

The below set-up steps are necessary for proper functioning of Intercompany invoicing cycle ..

  1. Define a customer and customer site in the selling operating unit.
  2. Define a supplier and supplier site in the shipping operating unit.
  3. Define Intercompany Relations
  4. Define price for the items in  ‘Internal Price list’

The organization itself is defined as a customer ‘Vision’, having a customer site in the selling operating unit as ..

The organization itself is defined as a supplier ‘Vision’, with a supplier site in the shipping operating unit as ..

Define Intercompany Relations as ..

Define price for the items in  ‘Internal Price list’ ..

Item Organization Assignment setup…
  1. Create Organization Hierarchy
    Nav: Inventory → Setup → Organization → Hierarchy
  2. Organization Name is Source Organization
  3. Subordinates is Destination Organization
    Note: You can add more than one subordinates(Destination Organization)
     
    Run Request : Item Organization Assignment
    Nav: View → Requests → Submit New Requests → Single Requests → Item Organization Assignment
Enter the Parameter
  1. Source Organization = From Organization
  2. Hierarchy Origin = Destination Organization
  3. Hierarchy = Which you created Organization Hierarchy name
  4. Category set Name = At least one Category set name required.
  5. Request Count = 1
Click (B) ok
 
After Completing the Request 
You can run the Item Status report and view the output which is assigned the against the Organization.
 
Run the Request Item Status Report and View Output

View Output Item