Oracle E-Business Suite

Single Org Vs Multi Org

In 11i and R12
 Comparison between Single Org and Multi Org
Objectives Single Org Multi Org Advantages Disadvantag
es
Modules affected CE, OE, AP, PR, Data is partitioned Maintenance of
PM, PO, Adv Access is Data
Collections, AR, restricted Reports across
Release Mgt, OIC, Security Org to be
OSO, OMO, established Customized
Service Modules
Need for Multi Org 1.Use Single Oracle provides a 1.Understanding
Instance to biggest advantage the concept by
support Multiple to partition data Client was difficult
Organizations based on Business 2.In 11i – Data is
2.Support multiple Need within single not partitioned by
Organizational database OU in GL. So any
Models user has access to
3.Secure data GL can post
based on user transactions of
4.Access multi org other OU
data using single 3.In R12 – In GL
responsibility also posting can
using Security be restricted using
Profiles Data access set
 Comparison between Single Org and Multi Org
Objectives Single Org Multi Org Advantages Disadvantag
es
Set up Set up for every Data is partitioned Maintenance of
Module for Multi Access is restricted Data
Org has to be Security Reports across Org
performed which is established to be Customized
time consuming
exercise one time if
the number of OU
is more (PO,AP, AR,
CE,OM, Inv etc.,)

Pre-requisites 1. Business Group a) Financial a) Standard

2. Ledger Statements can Reports are OU
3. Legal Entity be generated specific and if we
4. Multiple OU based on each need report across
5. Inventory Org OU line of Business
b) Each Line of then the same
Business can needs to be
be treated as Customized
independent
and operational
Performance
can be
measured
 Comparison between Single Org and Multi Org
Objectives Single Org Multi Org Advantages Disadvantag
es
OU specific Set up For example if you Line of Business Maintenance of
have Installments wise specific set Data
in Payment Terms up can be Reports across
in Real Estate and established Org to be
normal Payment Customized
Terms like 30
Days in Retail
Business, the
same can be set
to default
depending on
Business need

Control Access to Single User access can GL is not OU

Org or Multi Org be restricted specific and hence
can be provided to based on the if the user has
an User based on access to the access to GL he
Security Profile responsibilities can access other
and Operating unit OU Data in 11i.
profile This is now
resolved in R12 by
setting Data
access set
 Comparison between Single Org and Multi Org
Objectives Single Org Multi Org Advantages Disadvantag
es
Suppliers Supplier Header 1. Liabilities, 1. If You need to
Information is Prepayment, place hold on a
shared across all Payment Terms supplier, then
ledgers, OUs. etc., can be You need to
Supplier Site is managed Line of place hold in
specific to an OU. Businesswise. every OU
Transactions are 2. Using XML, Now 2. Classification
created at Supplier we can get the of Supplier is
Site level. Supplier Liability available only
across Line of at Header
Business in R12 Level.

Customers Customer Header 1. Salesperson, 1. Customer

Information is Dunning Letter Relationship
shared across all and cannot be
Ledgers, OUs. Statements established at Site
Customer Site is etc., can be Level and it is set
specific to an OU. defined at eachonly at Header
Transactions are OU Level Level across OU
created only at 2. Customer
Customer Site Receivables,
Level Unearned
Revenue,
Revenue,