Multi-Org 101

Multi-Org Architecture:
1. Before Multi-Org – Need one server for every set of Books implemented
2. With Multi-Org – One server, multiple sets of Books
3. The multiple organization structure simply partitions key tables to allow for an ORD_ID number per row
3.1 Used to provide security and data segregation.
4. Criteria used to partition tables includes:
4.1 The table contains a GL Account Code (code combination ID).
4.2 There is a business reason for the table to be partitioned (for example, the entity should not be shared).
4.3 The table contains transaction data.
4.4 The table is an interface table where data being loaded is partitioned.
4.5 The table includes a foreign key to a partitioned table and is accessed independently (in other words, not just as a child of a partitioned table).

Centralized Processing:
1. Centralized GL, AP, AR, PO, OE, and PA
1.1 Clients can use your balancing segment within your Chart of Accounts to segregate legal entity data
2. Decentralized GL, AP, AR, PO, OE, and PA
2.1 Client must have an Operating Unit for each group

Multi-Org Relationships:
1. Business Group, Legal Entity and Master Inventory Organization are all separate structures
2. Business Group and Legal Entity are linked through Responsibilities using the System Profile Options
3. Legal Entities and Inventory Organizations are linked by Set of Books

Why do you need Multi_org?
1. We only have one Set of Books, Business Group, Legal Entity and Operating Unit. Why Run Multi-Org?
1.1 Future growth and acquisitions
1.2 Change in company directions
1.3 Conversion from single org to multi-org is
1.3.1 Difficult in Release 10
1.3.2 Required in Release 11i and 12i

High Level Multi-Org Setup Steps:
1. Develop the organization structure
2. Define sets of books
3. Define organizations (Business Group, Legal Entity, Operating Unit, Inventory Orgs)
4. Define organization relationships
5. Define responsibilities
6. Update Profile Options Specific to Operating Units
7. Run the Setup Validation Report (recommended)

Multi-Org model as it relates to organizations:
· A ‘Business Group’ is the highest level of the structure and has no accounting impact. The ‘Business Group’ determines which employees will be available to ‘Sets of Books’ and ‘Operating Units’ related to that ‘Business Group’
· ‘Set of Books’ is the highest level which impacts the accounting side of the business
· ‘Set of Books’ is associated with a single ‘Business Group’, multiple ‘Sets of Books’ may be associated with a single ‘Business Group’
· Each ‘Set of Books’ may have a different chart of accounts structure, calendar or functional currency
· Each ‘Legal Entity’ is associated to a single ‘Set of Books’, multiple ‘Legal Entities’ may be associated with the a single ‘Set of Books’
· Each ‘Operating Unit’ is associated with a single ‘Legal Entity’, multiple ‘Operating Units’ may be associated with a single ‘Legal Entity’
· An ‘Inventory Organization’ may be associated with any ‘Operating Unit within the same ‘Set of Books’

New Operating Units - Critical Steps:
1. Oracle provides the seed data replication program as a concurrent program
2. May need to run the Replicate Seed Data process if seeded data does not replicate correctly
3. Remember to set up Responsibilities and System Profile Options (GL: Sets of Books and MO: Operating Unit) for each new OU defined