Please if anybody has production document on multi org, pls put it on the forum for us. This must contain many operating units ap ar po om for different legal entities- companies. The steps to create them.
Regards
Yemfola
Multi-org
-
ahmadbilal
- Posts: 615
- Joined: Mon Sep 18, 2006 1:32 am
- Location: United Arab Emirates
- Contact:
<b>Steps to Create Multi Org</b>
The following steps represent the required setup sequence for multi-org functionality:
Develop the Organization Structure. When developing your organizational structure, run through different process scenarios on paper before entering setup data in the system. Consider your business groups, requirements for accounting sets of books, operating units, and inventory organizations.
Define your sets of books. Each set of books you define requires that an accounting calendar, a chart of accounts consisting of your key accounting flexfield structure, and an active currency be set up prior to defining the set of books. Be sure to set up values for your retained earnings and intercompany accounts if you are using them because these will be required to complete your set of books' configuration. Make sure your choice of the balancing segment in the chart of accounts fits your organization's reporting, security, and intercompany transaction requirements.
Define your locations (names and addresses) for legal entities and inventory organizations in the Define Location window.
Define at least one business group. This task is optional because Oracle provides a predefined business group. You may modify the predefined business group. You should define all your business groups before defining any other type of organization.
Next, associate responsibilities with business groups. If you have several business groups, you associate each responsibility with only one business group. You may have to create many new responsibilities to implement the security and partitioning of your design.
Define the rest of your organizations. Be sure to use the correct responsibility for each organization when proceeding with the remaining setup.
Set up all your legal entities and then finally your operating units. By defining all of your organizations at this step, you help to ensure a streamlined configuration process when you define organizational relationships.
Define Organization Relationships. Remember that business groups and legal entities are separate structures. Business groups and legal entities are linked through responsibilities using the system profile options. Legal entities and inventory organizations are linked by a set of books.
Define responsibilities using the Define Responsibilities window as system administrator. Responsibilities define what functionality of an application is available to a user.
Set the operating unit profile option for each responsibility. The profile option is "MO: Operating Unit."
Convert to Multiple Organization Architecture. When your setup is complete, have your database administrator run the AutoInstall utility adadmin. Be sure to choose the option to convert to multi-org. This process should only take a few minutes to run.
Set the profile option "OM: Item Validation Organization" if you have a different item validation organization.
Set profile options specific to your operating units. For each responsibility, set the following:
HR: Business Group
HR: User Type
GL: Set of Books Name
OM: Item Validation Organization
INV: Intercompany Currency Conversion
TAX: Allow Override of Tax Code
TAX: Invoice Freight as Revenue
TAX: Inventory Item for Freight
Sequential Numbering
Define Inventory Organization Security (optional). You can restrict your inventory users to selected inventory organizations by defining security based on responsibility.
Configure each application for each operating unit.
Use the Define Security Rule window to create various rules that secure data entry by balancing each segment of the key accounting flexfield for each legal entity. Each security rule specifies a range of values to include or exclude from the rule.
Run the Multi-Org Setup Validation report. This report will help you identify setup issues. Use the System Administrator Responsibility to run the report. This report gives you information on specific attributes on customers and suppliers and verifies that you have set up consistent profile option values for all your responsibilities.
Implement document sequencing if you wish to use this feature of the Oracle Applications. For each application that supports document sequences, make the configuration at the set of books level.
If you use the Multiple Organization Intercompany Invoicing function, define your intercompany relations.
Set the profile option MO: Top Reporting Level. The default is the most restrictive and is set for the operating unit.
Configure the conflict domains for each operating unit if you need to run two or more incompatible concurrent programs simultaneously. Incompatible concurrent programs from different conflict domains can run simultaneously. This step is optional.
The following steps represent the required setup sequence for multi-org functionality:
Develop the Organization Structure. When developing your organizational structure, run through different process scenarios on paper before entering setup data in the system. Consider your business groups, requirements for accounting sets of books, operating units, and inventory organizations.
Define your sets of books. Each set of books you define requires that an accounting calendar, a chart of accounts consisting of your key accounting flexfield structure, and an active currency be set up prior to defining the set of books. Be sure to set up values for your retained earnings and intercompany accounts if you are using them because these will be required to complete your set of books' configuration. Make sure your choice of the balancing segment in the chart of accounts fits your organization's reporting, security, and intercompany transaction requirements.
Define your locations (names and addresses) for legal entities and inventory organizations in the Define Location window.
Define at least one business group. This task is optional because Oracle provides a predefined business group. You may modify the predefined business group. You should define all your business groups before defining any other type of organization.
Next, associate responsibilities with business groups. If you have several business groups, you associate each responsibility with only one business group. You may have to create many new responsibilities to implement the security and partitioning of your design.
Define the rest of your organizations. Be sure to use the correct responsibility for each organization when proceeding with the remaining setup.
Set up all your legal entities and then finally your operating units. By defining all of your organizations at this step, you help to ensure a streamlined configuration process when you define organizational relationships.
Define Organization Relationships. Remember that business groups and legal entities are separate structures. Business groups and legal entities are linked through responsibilities using the system profile options. Legal entities and inventory organizations are linked by a set of books.
Define responsibilities using the Define Responsibilities window as system administrator. Responsibilities define what functionality of an application is available to a user.
Set the operating unit profile option for each responsibility. The profile option is "MO: Operating Unit."
Convert to Multiple Organization Architecture. When your setup is complete, have your database administrator run the AutoInstall utility adadmin. Be sure to choose the option to convert to multi-org. This process should only take a few minutes to run.
Set the profile option "OM: Item Validation Organization" if you have a different item validation organization.
Set profile options specific to your operating units. For each responsibility, set the following:
HR: Business Group
HR: User Type
GL: Set of Books Name
OM: Item Validation Organization
INV: Intercompany Currency Conversion
TAX: Allow Override of Tax Code
TAX: Invoice Freight as Revenue
TAX: Inventory Item for Freight
Sequential Numbering
Define Inventory Organization Security (optional). You can restrict your inventory users to selected inventory organizations by defining security based on responsibility.
Configure each application for each operating unit.
Use the Define Security Rule window to create various rules that secure data entry by balancing each segment of the key accounting flexfield for each legal entity. Each security rule specifies a range of values to include or exclude from the rule.
Run the Multi-Org Setup Validation report. This report will help you identify setup issues. Use the System Administrator Responsibility to run the report. This report gives you information on specific attributes on customers and suppliers and verifies that you have set up consistent profile option values for all your responsibilities.
Implement document sequencing if you wish to use this feature of the Oracle Applications. For each application that supports document sequences, make the configuration at the set of books level.
If you use the Multiple Organization Intercompany Invoicing function, define your intercompany relations.
Set the profile option MO: Top Reporting Level. The default is the most restrictive and is set for the operating unit.
Configure the conflict domains for each operating unit if you need to run two or more incompatible concurrent programs simultaneously. Incompatible concurrent programs from different conflict domains can run simultaneously. This step is optional.
Hi,
Indeed very good article. I have following questions to which I hope some wise functional architect would take his precious time to respond.
Where to define Location (responsibility/navigation path) ?
Where to define Business group?
Where to associate responsibilities with business groups?
How to define legal entities and operating units?
Could you explain what are Flexfield Qualifiers (in definition, I know where they are but don't know the usage)? And Why they are used ?
What?s the difference between Cross-Validation Rules and Security Rules.
Regards
Dinesh
Indeed very good article. I have following questions to which I hope some wise functional architect would take his precious time to respond.
Where to define Location (responsibility/navigation path) ?
Where to define Business group?
Where to associate responsibilities with business groups?
How to define legal entities and operating units?
Could you explain what are Flexfield Qualifiers (in definition, I know where they are but don't know the usage)? And Why they are used ?
What?s the difference between Cross-Validation Rules and Security Rules.
Regards
Dinesh
Hi,
The response by AhmedBilal is very detailed. Great job.
Could anyone share what was your thought processing to come up with the org structure before you created it in oracle apps.
Typically what questions should be asked to the user so that we can conclude the company should be setup up as a BG/ LE/ OU/ Inventory org.
Your inputs much appreciated
Thanks
The response by AhmedBilal is very detailed. Great job.
Could anyone share what was your thought processing to come up with the org structure before you created it in oracle apps.
Typically what questions should be asked to the user so that we can conclude the company should be setup up as a BG/ LE/ OU/ Inventory org.
Your inputs much appreciated
Thanks
-
stanleypramood
- Posts: 1
- Joined: Fri Jul 13, 2007 11:15 am
- Location: South Africa
Who is online
Users browsing this forum: No registered users and 23 guests