A global implementation of your Oracle Applications enables you to do business in multiple countries, languages, and currencies. Leveraging Oracle Multiple Organization Architecture ("multi-org"), a global implementation allows you to:

• Create multiple sets of books/Ledgers, each with its own unique calendar, chart of accounts, and functional currency. Each set of books then can be tied to a sub-organization of your master organization, and to separate legal entities.
• Sell Inventory from one legal entity (which uses one set of books) and ship them from another legal entity (using a different set of books). Oracle Receivables can automatically record the appropriate intercompany sales by posting intercompany accounts payable and accounts receivable invoices.
• Reuse database tables, meaning one-time data entry.
• Ability to segregate transactions by operating unit -- since each organization is uniquely linked to an operating unit -- yet still share certain information (such as customers) between organizations.
• Support multiple currencies (including the Euro) and several languages.

Customer Application Responsibilities
Each site supports multiple responsibilities, and each iteration of a site and a responsibility make a specialty site accessible in the Customer UI. It is recommended that you set up your sites to each support a single responsibility (and thus a single specialty site). This single specialty site then can be rendered in different languages and currencies.

When a user's registration is approved, he is granted at least one responsibility. A match between a customer's responsibility and the responsibility supported by a site allows the customer to see the specialty site. Oracle iStore seeds a default responsibility, IBE_CUSTOMER, for use with your sites.

The operating unit (OU) tied to the responsibility a customer is using when he places an order determines the OU in which the order is recorded. In a multiple-OU scenario, you would create a separate IBE customer responsibility to link to different OUs. The OU associated with a customer when he places an order is determined by the settings of two multi-org profile options, as discussed in the following use cases.

Use Case 1: Multi-Org Implemented; MO: Security Profile Set to Single OU
MO: Security Profile is set to a single OU at Oracle iStore customer responsibility level. Sites using this customer responsibility are associated to the specified OU, and all the transactions are placed in this OU. In this case, the profile, MO: Operating Unit, should be set to the same OU as in the security profile.

Use Case 2: Multi-Org Implemented; MO: Security Profile Set to Multiple OUs
MO: Security Profile is set to multiple OUs, either through security profile hierarchy or to a list of valid OUs defined in Oracle Human Resources. Oracle iStore will retrieve the OU associated to the site/responsibility based on the value defined in the profile option, MO: Operating Unit.
This profile option is required and should be set to a single OU. The OU associated to the Oracle iStore customer responsibility through MO: Operating Unit should be one of the OUs in the list of operating units associated to MO: Security Profile.
Note that the Security Profile should list all the OUs that are used in iStore as well as those in used in Oracle Order Management/OrderCapture products; this is required in order for the iStore end user to be able to cancel orders.

Use Case 3: Multi-Org Not Implemented
MO: Security Profile is not set. MO: Operating Unit is set to one OU for each Oracle iStore Customer UI responsibility. Oracle iStore will retrieve the OU associated to the site/responsibility based on the value defined for this profile option.
Oracle iSupport and Oracle Partner Management applications should follow the same logic when using the iStore framework to create their sites.

When a customer enters a specialty site, Oracle iStore notes the customer's responsibility and the OU to which it is assigned, then restricts the customer to the items in the Inventory Organization that is associated with the OU. Oracle iStore accomplishes this by retrieving the Inventory Organization ID for the current user responsibility's OU from the OE_SYSTEM_PARAMETERS_ALL table. Use Oracle Order Management to associate Inventory Organization IDs with OUs.

Note: In all cases, the profile option, MO: Operating Unit, must be set.

Sample Responsibilities Setup for Oracle iStore Multi-Org
Following is a sample responsibilities setup for a multi-org implementation:
1. Create a separate responsibility for each operating unit. You can use the seeded responsibility, IBE_CUSTOMER, as one of these responsibilities. Each operating unit must be tied uniquely to a single responsibility.
Example: Create IBE_CUSTOMER_G for your German operating unit, and use IBE_CUSTOMER for your U.S. operating unit.

2. Link each responsibility to an operating unit by setting the multi-org profile options discussed in the above section.