The following is the brief about the Multi-Org.

Multi-Org is a server side enhancement, which enables the Multiple Organizations in an enterprise to use a single installation of Oracle Applications products while keeping transacting data separate and secure In 11i the Multi-Org Structure Business Group -> Set of Books -> Legal Entity -> Operating Unit -> Inventory Organization In R12 the Multi-Org Structure Business Group -> Ledgers -> Legal Entity -> Operating unit -> Inventory Organization The difference in 11i and R12 is : Set of Books are replaced by ledgers in R12. Ledgers are created using Accounting Setup Manager. Further Operating Unit can also be created in Accounting Setup Manager itself.

Business Group - It represents the highest level in the organization structure, such as the major division. Multiple ledgers can share the same Business Group if they share the same Business Group attributes, including HR Flexfield structures. Ledgers - Ledgers may be Primary or Secondary. It determines the Currency, Chart of Accounts, Calendar, Ledger processing Options and Subledger Accounting method. Legal Entity - A Legal company for which you prepare Fiscal or Tax Reports Operating Unit - An Organization that uses Oracle Subledger's and releated products Inventory Organization - An Organization for which you track Inventory transactions and balances

Pre-requisites: Define Organization, Define Legal Entity, Access to Responsibilities HRMS, GL, Purchasing, System Administrator, Inventory etc Steps: 1. Design a Structure 2. Define a Location 3. Define Business Group

4. Define or Use existing Accounting Flexfield 5. Create Legal Entity 6. Create Ledgers 7. Create and Assign Operating Unit and Legal entity 8. Create Inventory Organization 9. Run Reports - Replicate Seed Data, Multi-Org setup Validation Report

In R12 we have a feature call MOAC(Multi-Org Access Control) which allows the user to submit requests, enter, view and access data of different Operating Unit without having to switch between responsibilities. Profile Options: MO: Operating Unit - It will restrict the access through responsibility to only one Operating Unit MO: Security Profile - It enables the user to get access on more than one Operating Unit by defining a security profile with Multiple Operating Unit and assigning it to the responsibility (If MO: Security Profile is set, then MO: Operating Unit is ignored by the system) MO: Default Operating Unit - It is used when we have more than one OU attached to a responsibility through security profile, among whihc you want a particular OU to be defaulted during transaction entry stages. When the responsibility is assigned with only one OU then that will become the default OU, without setting the profile option MO: Default Operating Unit HR: User Type - It limits the access on windows shared Oracle Human Resources and Other Applications HR: Business Group - We associate a Business Group with a responsibility using this profile option. It should be done for all responsibilities HR: Security Profile - When we define a new Business Group instead of modifying the predefined setup Business Group, you need to set the HR: Security Profile option to point the Security profile for the new Business Group. Oracle HRMS automatically creates a security profile with the Business Group name when you define a new Business Group