Subject: Multiple Organization Conversion White Paper For

Oracle Applications 10.7

Doc ID: Note:66635.1 Type: WHITE PAPER
Last Revision Status:
02-OCT-2003 PUBLISHED
Date:
Multiple Organizations
in Oracle Applications
White Paper

Introduction
~~~~~~~~~~~~
This white paper has been created as an overview and technical aide to
converting to multiple organizations. The implementation process is
directed
toward Release 11, but is basically the same for Release 10.7. Where
patches
apply, it has been separated into two categories; patches for Release
10.7 and
patches for Release 11. This article is not intended to replace existing
documentation, but is intended as an overview and supplement to current
documentation. For detalied information see Multiple Organizations in
Oracle
Applications manuals.

Multiple Organizations
~~~~~~~~~~~~~~~~~~~~~~
Multiple organizations and their relationships are defined in a single
installation of Oracle Applications. Multiple organizations can be
characterized as:

1. Set of books
2. Business groups
3. Legal entities
4. Balancing entities
5. Operating units
6. Inventory organizations

Two Model Types

~~~~~~~~~~~~~~~
Human Resources Organization Model:

Multilevel organization hierarchies that are headed by a business group

at the
top of the hierarchy.

Accounting / Distribution / Materials Management Organization Model:

A multilevel company structure defining relationships among

* Sets of books -- financial reporting entity that uses a

particular chart
of accounts, functions currency, and accounting calendar.

* Legal entities -- legal entities post to a set of book.

* Operating units -- operating units are part of a legal entity.

 * Inventory organizations -- inventory organizations re part of an
operating unit. They determine items available to order entry and
purchasing.

Multi-org Setup
~~~~~~~~~~~~~~~
1. Define Organization Structure.

* This is a pen and paper process of setting up the organizations

structure.

* Assign organization classification in the following order:

(1) legal entities, (2) operating units, and (3) inventory
organizations.

2. Define Sets of Books.

* Use Define Set of Books window to enter a set of books.

* Responsibilities used to assign sets of books:

- Assets - Setup -> Financials -> General Ledger -> Set of Books
- General Ledger - Setup -> Set of Books -> Define
- Inventory - Setup -> Financials -> Books
- Payables - Setup -> Set of Books -> Define
- Purchasing Receivables - Setup -> Organizations -> Set of Books
- Receivables - Set Up -> Financials -> Books
- Government General Ledger - Setup -> Set of Books -> Define

3. Define Organizations.

* Use Define Organizations window to define organizations.

* Responsibilities used to assign organizations:

- Inventory - Setup -> Organizations -> Organizations

- Purchasing - Setup -> Organizations -> Organizations
- Order Entry / Shipping - Set Up -> Organizations -> Organization
- Projects - Setup > Human Resources -> Organizations -> Define
- Receivables - Set Up > System -> Organization
- Government Purchasing - Setup -> Organizations -> Organizations
- Government Receivables - Set Up -> System -> Organization

* Define Business Groups. (Optional)

- Define if you have multiple business groups or do not use

default
business group.

- You must have at least one business group. Oracle Applications

supplies default business group, Setup business Group (fresh
install).

- If you define business group next step must be to associate

business
groups with a responsibility and verify the HR:Business Group
profile
option. (See step 5.)
4. Define Organization Relationships.

* Use the Define Organization window to define organization

relationships
by assigning classifications to each organization.

- Classification of an organization can be any combination in the

following order: (1) legal entities, (2) operating units, and
(3) inventory organizations.

- Legal entities must have a location specified.

(Zoom to Define Locations window.)

- A concurrent program automatically replicates seed data for

each new
organization.

5. Define Responsibilities.

* Use the Define Responsibility window to define responsibilities

for each
operating unit.

* Responsibilities used to assign responsibilities:

- System Administrator - Security -> Responsibility -> Define

* If you have multiple business group, you must associate each

responsibility with one and only one business group.
- Use the HR:Business Group system profile option to associate a
responsibility with a business group.

6. Set MO:Operating Unit Profile Option for Each Responsibility.

* MO:Operating Unit profile option must be set.

- System Administrator - Profile -> System
- Set profile option to appropriate operating unit id (ORG_ID).

* You must set the default operating unit setting MO:Operating Unit
at the
site level.

7. Run Convert to Multiple Organization using Adadmin utility.

* Process replicates seed data to all operating units that have been
defined.

* This step is irreversible.

* Adadmin will fail if previous steps have not been completed.

* Concurrent managers must be down and no one should access the

database.

* If adadmin fails during conversion and you are prompted to

proceed as
if successful, never select Yes, as the conversion process has
already begun, and steps that may be missed during the conversion
 process will need to be manually created and be difficult, costly
and
timely to recreate.

8. Define Inventory Organization Security (Optional).

* Restricts manufacturing users to specific organizations.

9. Change Order Entry Profile Options (Optional).

* OE:Item Validation Organization profile option is set a

responsibility
level if operating units have different item validation
organizations.

10. Update Profile Options Specific to Operating Units.

* Set profile options at the responsibility level e.g.:

- AR:Receippt Batch Source
- AR:Transaction Batch Source
- OE:Item Validation Organization
- OE:Set of Books
- GL:Set of Books Sequential Numbering

* Responsibilities used to assign profile options:

System Administrator - Profile -> System.

* Refer to individual Oracle Financial Applications Products User's

Guides
for specific information on profile options that need to be set.

11. Set up Oracle Applications Products.

* OE, PA, PO, AR and Sales Compensation must be set up for each
operating
unit it they the product groups are to be used.

* FA, GL INV and the rest of the Oracle Manufacturing product do

not need
to be set up for each operating unit.

12. Secure Balancing Segment Values by Legal Entity. (Optional)

* Use the Define Security Rule window to create rules that secure
data
entry of balancing segment values for each legal entity.
- Security rule elements specify a range of values to be included
or
excluded.

* Use the Assign Security Rules window to assign the same rule(s)
to all
responsibilities associated with the legal entity's operating
units.

* Define additional rules and assign them to all responsibilities

associated
with relevant operating units.
13. Run the Setup Validation Report to Identify Setup Problems.

* Data for disabled fields on Enter Customer and Enter Supplier

Window must
be deleted.
- Header information is shared across operating units and if you
do not
choose to delete the data, you must edit the database manually.

* All responsibilities in one operating unit must share the same

profile
option values and sequence numbering option.

Definitions
~~~~~~~~~~~

Set of Books:
-------------
A financial reporting entity that uses a particular chart of accounts,
functional currency, and accounting calendar. Oracle General Ledger
secures
transaction information (journal entries, balances) by set of books.
When you
use Oracle General Ledger, you choose a responsibility that specifies a
set of
books. You then see information for that set of books only.

Operating Unit:
---------------
An organization that uses Order Entry, Oracle Payables, Oracle
Purchasing, or
Oracle Receivables. It may be a sales office, a division, or a
department. An
operating unit is associated with a legal entity. Information is
secured by
operating unit for these applications; each user sees information only
for
their operating unit. To run any of these applications, you choose a
responsibility associated with an organization classified as an
operating unit.

Multi-Org Partitioned Objects:

------------------------------
Tables that contain Multi-Org data have the suffix _ALL in the table
name.
These tables include a column called ORG_ID that partitions Multi-Org
data by
organization.

Every Multi-Org table has a corresponding view that partitions the

table's data
by operating unit. Multi-Org views partition data by including a DECODE
of an
RDBMS function called CLIENT_INFO. CLIENT_INFO is similar in operation
to the
function LANGUAGE, which returns the language of the current session,
and is set
by the security system to the operating unit designated for the
responsibility.
SO_HEADERS_ALL,with its corresponding view SO_HEADERS, are examples of
Multi-Org partitioned objects. For a complete list refer to the Multiple
Organizations in Oracle Applications manual.

Additional Information:
-----------------------
Multiple Organizations in Oracle Applications manuals

Custom Access:
--------------
If you implement Multi-Org, you must be sure to access the data
correctly.
For example, custom scripts run ad hoc from SQL*Plus (and not run
through
Concurrent Processing) must reference the xx_ALL table and specify the
ORG_ID
value to correctly extract partitioned data:

SQL> select CURRENCY_CODE from SO_HEADERS_ALL

2> where ORG_ID = 129
3> and HEADER_ID = 1000
4> and ORDER_NUMBER = 1000
5> and ORDER_TYPE_ID = 1002 ;

Access through the view will not return the correct rows, as the
CLIENT_INFO
value is not set unless you connect through the Sign-On screen or use
Concurrent
Processing with Oracle Reports or SQL scripts.

Patches
~~~~~~~
(Apply patches only after checking for updates and patch bundles.
Contact each product group for current patches in those product groups.)

Release 10.7
------------
590158 - Alerts functionalities for multi-org. Special Instructions:
create a
new folder called REVIEWED_PARSING in any Oracle Office
account that
is used for Oracle Alert Response Processing.

663156 - This patch addresses the issue wherein the Operating Unit
profile option gets overridden by Oracle Alert when executing
an event alert for an organization.

669064 - This is a prerequisite patch to 663156 and replaces 655400.

This patch addresses the issue wherein the Operating Unit
profile option gets overridden by Oracle Alert when executing
an event alert for an organization

605531 - This patch adds the organization to the alert installations

screen.

*** Note:

The above patches have been upgraded/incorporated into Oracle Alert

cumulative patchsets for 10.7:

777169 - 10.7 server

777942 - 10.7 Prod 16.1 Smart Client
777396 - 10.7NCA

Additional patches to be applied after the above patchsets:

823499 - Correct the problem of Alert updating the MO:Operating unit

profile
option to blanks.

837897 - The windows NT mapi mail support was added in Alert 10.7 in a
patch bundle 777169 but this patch was missing one file - alumsn.sql.
alumsn.sql inserts a record in the Mail Systems screen. This patch
is to
deliver the alumsn.sql file. This patch also contains all files in
Patch 777169.

*** End of Note

461055 - A cumulative patch for the broken multi-org functionality in

10.7.
NCA customers can apply this patch. Run this patch after the
adadmin
Convert step has completed, once Multi-Org is setup. Contains
459006,
458867, 458785,458716, 458690, 458678, 458525, 458397, 455895,
436141,
440690.

510711 - Adadmin fails during multi-org conversion ORA-20000; ORA-1434,

due to
sequences that are incorrectly named. Run sql*plus
<APPS username>/<APPS password> @ad510711.sql <APPS username>
<APPS password> <AR username> <AR password>.
The script also generates another script adfixseq.sql that
needs to be
reviewed and run manually to fix the sequences. Run sql*plus
<APPS username>/<APPS password> @adfixseq, then rerun adadmin.

Note 1040365.6 provides work around for the same problem: ORA-
20000
ORA-01434 ORA-06512 when converting to multi-org.

515113 - AP patch. APSED53.sql does not insert seeded data needed for
multi-org
during conversion.

Release 11.0
------------
733829 - Multi-org procedures (repl & convert) must support newly
partioned
tables. This patch updates multi-org procedures to handle
tables that
 are newly partitioned for multi-org in a patch.

685585 - This patch fixes a bug in which the AD Administration utility

fails
when converting to Multi-Org with a "table or view does not
exist"
error on the following tables:

JE_ES_MESSAGES_ALL
JE_ES_MODELO_190_ALL
JE_ES_MODELO_347_ALL

The error only happens when you have not installed any European
localizations.

If you encounter the error above when converting to Multi-Org,

you should work around the problem by skipping the failed jobs
for
these three tables. Contact Oracle Support Services if you do
not
know how to do this.

Replicating Seed Data in Tables

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
In SQL*Plus run the following:
execute ad_morg.replicate_seed_data(null, <product short name>,
<table>);

You can specify NULL values for product/table to replicate data for ALL
products/tables.

Script Run During Conversion

~~~~~~~~~~~~~~~~~~~~~~~~~~~~
adorgconv.pls