How to Convert Single To Multi-Org?

There are 3 steps involved in it explained below.

Step- 1

Before running the Convert to Multi-Org process, make sure you do the following:

• Apply the AD Patch 2412184: ADADMIN Convert to Multi-Org Performance Improvement: Increase parallelization

• Define at least one Operating Unit, and set the profile option, "MO: Operating Unit" at Site level, to that Operating Unit's value
 
Step- 2
 
Run Convert to Multi-Org process available from the Database Objects menu of the ADADMIN utility. The Convert to Multi-Org process upgrades a standard product group into a Multi-Org product group. You can choose this option only if you do not already have Multi-Org set up.

The Convert to Multi-Org program does the following:

• Populates the ORG_ID column in the Multi-Org tables with the new operating unit value you defined at the site level profile option: MO: Operating Unit

• Sets the MULTI_ORG_FLAG in the FND_PRODUCT_GROUPS table to “Y”

• Runs the “Replicate Seed Data” program

If you define more than one Operating Unit, the replicate seed data process is run for all Operating Units.
 
Step- 3
 
After running the Convert to Multi-Org process, make sure you apply the following TCA patch as post conversion process:

• Patch 2451368: Migrate data from Customers to Site Uses

Multi-Org Modules

Financials

Oracle Payables- AP
Oracle Receivables- AR
Oracle Cash Management- CE

Regional Localizations- JG

Latin America Localizations- JL
European Localizations- JE
Asia/Pacific Localizations- JA
Oracle Property Manager- PN
Subledger Accounting- XLA
Trading Community Architecture- TCA
iReceivables
iExpenses
Oracle Collections
Global Accounting Engine- AX

Public Sector Financials

Oracle Grants Management- GMS
Oracle Grants- IGW
Oracle Federal Financials- FV

Procurement

Oracle Purchasing- PO
Oracle Sourcing- PON
iSourcing
iProcurement
iSupplier Poral- POS

Manufacturing

Oracle Order Management- ONT
Oracle Release Management- RLM
Oracle Release Management Integration Kit- RLA
Oracle Shipping- WSH
Oracle Pricing- QP

Projects

Oracle Projects- PA

CRM

CRM Administrator- JTF

Sales

Oracle Sales Compensation- CN
Oracle Sales- AS

Service

Oracle Service- CS

Other

Oracle Scheduler- CSR
Oracle Banking Center- FPT
IStore- IBE

MOAC (Multi Org Access Control)

1) R12 offers true Multi-Org Access. Responsibilities are assigned with a Security profile which is a group of operating Units. Assignment is through the profile option 'MO: Security Profile' set at the Responsibility Level.

2) Security Profile is setup from HR Responsibility. The Security List Maintenance concurrent program must be run each time you add or change Security Profiles. So from one responsibility you can perform transactions and report on transactions from multiple operating units

3) Pre-R12 you could set your SQL session context for multi-org with the following, Or you could have used FND_GLOBAL.APPS_INITIALIZE to set your context.
BEGIN

dbms_application_info.set_client_info (2);
END;

4) In R12 you can set your SQL session context for a single OU with the following:
BEGIN
Execute mo_global.set_policy_context ('S', 2);
END;
• The ‘S’ means Single Org Context
• 2 is the ORG_ID I want set

5) Also in R12 you can set your SQL session context for multiple OU’s with the following:
BEGIN
Execute mo_global.set_org_access (NULL, 64, 'ONT');
END;
• 64 is the Security Profile you want to use
• ‘ONT’ is the application short name associated with the responsibility you will be using

6) The following SQL will dump out the Security Profiles and Operating Unit Names assigned to them
SELECT psp.SECURITY_PROFILE_NAME,
psp.SECURITY_PROFILE_ID, hou.NAME,
hou.ORGANIZATION_ID
FROM PER_SECURITY_PROFILES psp,
PER_SECURITY_ORGANIZATIONS pso,
HR_OPERATING_UNITS hou
WHERE pso.SECURITY_PROFILE_ID = psp.SECURITY_PROFILE_ID
AND pso.ORGANIZATION_ID = hou.ORGANIZATION_ID;

7) There are three Profile Options you need to be aware of related to Multi-Org that should be set at the Responsibility Level:
MO: Security Profile- Always evaluated first.
MO: Operating Unit- Secondary priority being evaluated after ‘MO: Security Profile’
MO: Default Operating Unit- Sets the default Operating Unit for transactions when running under a Security Profile