single org vs multi org

Oracle E-Business Suite

Single Org Vs Multi OrgIn 11i and R12

Comparison between Single Org and Multi Org

Objectives Single Org Multi Org Advantages DisadvantagesModules affected CE, OE, AP, PR, PM,

PO, Adv Collections, AR, Release Mgt, OIC, OSO, OMO, Service Modules

Data is partitionedAccess is restrictedSecurity established

Maintenance of DataReports across Org to be Customized

Need for Multi Org 1.Use Single Instance to support Multiple Organizations2.Support multiple Organizational Models3.Secure data based on user4.Access multi org data using single responsibility using Security Profiles

Oracle provides a biggest advantage to partition data based on Business Need within single database

1.Understanding the concept by Client was difficult2.In 11i – Data is not partitioned by OU in GL. So any user has access to GL can post transactions of other OU3.In R12 – In GL also posting can be restricted using Data access set

Comparison between Single Org and Multi Org Objectives Single Org Multi Org Advantages DisadvantagesSet up Set up for every

Module for Multi Org has to be performed which is time consuming exercise one time if the number of OU is more (PO,AP, AR, CE,OM, Inv etc.,)

Data is partitionedAccess is restrictedSecurity established


Pre-requisites 1. Business Group2. Ledger3. Legal Entity4. Multiple OU5. Inventory Org

a) Financial Statements can be generated based on each OU

b) Each Line of Business can be treated as independent and operational Performance can be measured

a) Standard Reports are OU specific and if we need report across line of Business then the same needs to be Customized

Comparison between Single Org and Multi Org

Objectives Single Org Multi Org Advantages DisadvantagesOU specific Set up For example if you

have Installments in Payment Terms in Real Estate and normal Payment Terms like 30 Days in Retail Business, the same can be set to default depending on Business need

Line of Business wise specific set up can be established


Control Access to Single Org or Multi Org can be provided to an User based on Security Profile and Operating unit profile

User access can be restricted based on the access to the responsibilities

GL is not OU specific and hence if the user has access to GL he can access other OU Data in 11i.This is now resolved in R12 by setting Data access set

Comparison between Single Org and Multi Org Objectives Single Org Multi Org Advantages DisadvantagesSuppliers Supplier Header

Information is shared across all ledgers, OUs.Supplier Site is specific to an OU. Transactions are created at Supplier Site level.

1. Liabilities, Prepayment, Payment Terms etc., can be managed Line of Businesswise.2. Using XML, Now we can get the Supplier Liability across Line of Business in R12

1. If You need to place hold on a supplier, then You need to place hold in every OU

2. Classification of Supplier is available only at Header Level.

Customers Customer Header Information is shared across all Ledgers, OUs.Customer Site is specific to an OU. Transactions are created only at Customer Site Level

1. Salesperson, Dunning Letter and Statements etc., can be defined at each OU Level

2. Customer Receivables, Unearned Revenue, Revenue, Freight, Tax Accounts can be defined for each site

1. Customer Relationship cannot be established at Site Level and it is set only at Header Level across OU

single org vs multi org

Documents