Setting up Multi-Org
Setup Steps [21]
1. Develop the Organization Structure
2. Define Set of Books
3.1 Define Locations for the Legal Entity, Operating Unit and Inventory Organization
3.2 Define Locations for Bill-To Sites
4. Define Business Groups
5. Assign Responsibilities with Business Groups
6. Define Legal Entities
7. Define Operating Units
8. Define Inventory Organization
9. Define Auditable Units
10. Set MO: Operating Unit & GL Set of Books Name Profile Option
11. Conversion to Multi-Org
12. Define Responsibilities
13.1 Set Profile Options for Operating Unit Responsibilities
13.2 Set Profile Options for Operating Unit Responsibilities
14. Define Inventory Organization Security
15. Implement the Applications Products
16. Assign Key Flexfield Security Rule and Assign Security Rule
17. Run the Multi-Org Setup Validation Report
18. Implement Document Sequencing
19. Define Intercompany Relations
20. Set Top Reporting Level Profile Options
21. Set Up Conflicts Domains
Step 1 [Oracle Required/ ERP Required]
Develop the Organization Structure
Level: Enterprise
Navigator: None
Purpose: A successful implementation of Multiple Organization support in Oracle Applications depends primarily on defining your organizational structure in the multi-level hierarchy used by Oracle Applications.
Step 2 [Oracle Required/ ERP Required]
Define Set of Books
Level: Enterprise
Navigator: Setup > Financial> Books> Define
Purpose: Use the Define Set of Books window to enter your sets of books
Step 3.1 [Oracle Required/ ERP Required]
Define Locations for the Legal Entity, Operating Unit and Inventory Organization
Change Responsibility to Inventory
Level: Enterprise (For each new Operating Unit, this will need to be completed) (including Manufacturing)
Navigator: Setup > Organizations > Locations
Step 3.2 [Oracle Required/ ERP Required]
Define Locations for Bill-To Sites
Navigator: Setup > Organizations > Locations
Level: Enterprise (For each new Operating Unit, this will need to be completed)
Purpose: Location used for AP Financial Options.
Step 4 [Oracle Required / ERP Required]
Define Business Groups
Level: Enterprise
Navigator: Setup > Organizations > Organizations
Purpose: Oracle Applications provides default Business Group: Setup Business Group. Create additional Business Group(s) associated with the planned Organization Structure.
Step 5 [Oracle Optional / ERP Required]
Assign Responsibilities with Business Groups
Change Responsibility to System Administrator
Level: Enterprise
Navigator: Profile> System
Step 6 [Oracle Required / ERP Required]
Define Legal Entities
Change Responsibility to Inventory
Level: Enterprise (For each new Operating Unit, this will need to be completed)
Navigator: Setup > Organizations > Organizations
Purpose: Define organizational relationships by assigning classifications to each organization. You can classify an organization as any combination of legal entity, operating unit and inventory organization. Specifications can only be done in the following order: 1.Legal Entity, 2.Operation Units, 3. Inventory Organizations.
Step 7 [Oracle Required / ERP Required]
Define Operating Units
Level: Enterprise (For each new Operating Unit, this will need to be completed)
Navigator: Setup > Organization > Organizations
Purpose: Define organizational relationships by assigning classifications to each organization. You can classify an organization as any combination of legal entity, operating unit and inventory organization. Specifications can only be done in the following order: 1.Legal Entity, 2.Operation Units, 3. Inventory Organizations.
Step 8 [Oracle Required / ERP Required]
Define Inventory Organization
Level: Enterprise (For each new Operating Unit, this will need to be completed) (including Manufacturing)
Navigator: Setup > Organizations > Organizations
Purpose: Define organizational relationships by assigning classifications to each organization. You can classify an organization as any combination of legal entity, operating unit and inventory organization. Specifications can only be done in the following order: 1.Legal Entity, 2.Operation Units, 3. Inventory Organizations.
Step 9 [ Oracle Required / ERP Required]
Define Auditable Units
Level: Enterprise
Navigator: Setup > Organization > Organizations
Purpose: Define organizational relationships by assigning classifications to each organization. You can classify an organization as many classifications
Step 10 [Oracle Optional / ERP Required]
Set MO: Operating Unit & GL Set of Books Name Profile Option
Change responsibility to System Administrator
Level: Enterprise (For each new Set of Books and Operating Unit, this will need to be completed) (including Manufacturing)
Navigator: Profile> System
Step 11 [Oracle Required / ERP Required]
Conversion to Multi-Org
Level: Enterprise (For each new Operating Unit, this will need to be completed)
Navigator: Requests > Run (this is to run the 'Replicate Seed Data' job)
Step 12 [Oracle Required / ERP Required]
Define Responsibilities
Level: Enterprise
Change responsibility to System Administrator
Navigator: Security > Responsibility > Define
Step 13.1 [Oracle Optional / ERP Required]
Set Profile Options for Operating Unit Responsibilities
Level: Enterprise
Navigator: Profile> System
Purpose: The following profile options need to be set for each custom responsibility for appropriate operating unit:
Step 13.2 [Oracle Optional / ERP Required]
Set Profile Options for Operating Unit Responsibilities
Level: Enterprise
Navigator: Profile> System
Purpose: The following profile options need to be set for each custom responsibility for appropriate operating unit:
Step 14 [Oracle Optional / ERP Required]
Define Inventory Organization Security
Purpose: With inventory organization security you can restrict inventory organization access to specific responsibilities. You may want to restrict your manufacturing users to certain organizations according to your organizational hierarchy. This feature has the following characteristics.
· Until you assign an organization to a responsibility in this window, all responsibilities have access to all organizations. Once you have restricted any responsibilities to certain organizations, you must then explicitly define the organizations that all responsibilities can access.
· This feature does not restrict access once the user is in he product. Users with access to functions that cross multiple organizations (such as ATP, Inter-Organization Transfers, Item Search, Multi-Org Quantity Report, and so forth) can still specify any valid organization when running these functions.
Step 15 [Oracle Required / ERP Required]
Implement the Applications Products
Level: Operating Unit
Step 16 [Oracle Optional / ERP Required]
Assign Key Flexfield Security Rule and Assign Security Rule
Level: Enterprise
Navigator: Setup > Financials > Flexfields > Key > Security > Assign
Purpose: Assign flexfield security rules to an application responsibility.
Step 17 [Oracle Recommended / ERP Required]
Run the Multi-Org Setup Validation Report
Change responsibility to System Administrator
Navigator: Requests > Run
Level: Enterprise (For each new Operating Unit, this will need to be completed)
Purpose: Verify the current multi-org setup and identify any problems with the setup.
Step 18 [Oracle Optional/ ERP Optional]
Implement Document Sequencing
Level: Enterprise
Navigator: Application > Document > Define and Assign
Purpose: After you have implemented Multiple Organizations and run the Multi-Org Setup Validation Report, you have the option to set up document sequencing (a common requirement for European countries) for each application that supports document sequencing. Sequence assignments are controlled at the set of books level
Step 19 [Oracle Optional / ERP Optional]
Define Intercompany Relations
Navigator: Application > Document > Define and Assign
Step 20 [Oracle Optional / ERP Optional]
Set Top Reporting Level Profile Options
Level: Enterprise
Navigator: Profile> System
Purpose: You need to define your reporting levels by setting the MO: Top Reporting Level profile option. To do this, you set your top reporting level to one of the following: Set of books, Legal Entity or Operating Unit. You will be able to report on anything that is within the reporting level. The default value is Operating Unit.
Step 21 [Oracle Optional / ERP Optional]
Set Up Conflicts Domains
Level: Enterprise
Navigator: Concurrent > Conflict Domains
Purpose: A conflict domain is an abstract representation of the groupings used to partition your data. When a program is listed as incompatible with another, the two programs cannot run simultaneously in the same conflict domain. Two incompatible concurrent programs may run simultaneously if they are submitted in different conflict domains. To maximize the concurrency in a multiple organization environment, you can set up conflict domains for your operating units. All programs are assigned a conflict domain when they are submitted. The following determines the conflict domain you use when you submit a concurrent request:
