multi-or (1)

8/8/2019 multi-or (1)

1/42

Application Document

Multi-OrganizationSetup

Author: Rajani Didi BartakkeWilliam A. Green, Jr.

Creation Date: September 16, 2010

Last Updated: September 16, 2010

Control Number:

Version: 1

Multi-Org 10.7 Installation Steps Page 1

Copy Number _____

CompanyConfidential - For internal use only

8/8/2019 multi-or (1)

2/42

Document Control

Change Record

Date Author Version

Change Reference

16-Sep-10

Preferred Customer 1 No previous document

Reviewers

Name Position

Barry Parker Oracle Managing Principal

Distribution

CopyNo.

Name Location

1 Corporate Repository Oracle Corporation2 Fincon Mailing List Oracle Corporation



8/8/2019 multi-or (1)

3/42

Contents

Document Control........................................................................................................................................21. Introduction.............................................................................................................................................42. Preparation..............................................................................................................................................5

Considerations.........................................................................................................................................5Setup Schedule.........................................................................................................................................5

3. Summary of Terms..................................................................................................................................7Set of Books........................................................................................................................................................7

Organization.......................................................................................................................................................7Business Group...................................................................................................................................................7Legal Entity........................................................................................................................................................7Operating Unit....................................................................................................................................................7Inventory Organization.......................................................................................................................................8HR Organization.................................................................................................................................................8Responsibility.....................................................................................................................................................8Balancing Segment.............................................................................................................................................8Security Rules.....................................................................................................................................................8

4. Setting Up a Multi-Business Unit Enterprise.........................................................................................95. Multi-Org 10.7 Installation Steps.........................................................................................................10

Step 1. Develop the Organization Structure............................................................................................10Step 2. Define Sets of Books...................................................................................................................11Step 3. Define Organizations................................................................................................. ......... .......11

Defining Organizations................................................................................................................................13

Inventory Parameters....................................................................................................................................14Step 4 Define Organization Relationships.................................................................................... ......... .14Seed Data Replication..................................................................................................................................15

Step 5. Define responsibilities.................................................................................................... ......... ...17Step 6. Set Profile Option for Each Responsibility.................................................................................17

Multiple Business Groups ...........................................................................................................................17Multiple Operating Units.............................................................................................................................17

Step 7. Conversion to Multi-Org.............................................................................................................19Step 8. Define Inventory Organization Security (Optional)..................................................... ........ ......19Step 9. Change Order Entry Profile Options(Optional)....................................................................... ...19

Item Validation Organization.......................................................................................................................19Set of Books.................................................................................................................................................20Sequential Numbering..................................................................................................................................20

Step 10. Update Profile Options Specific to Operating Units..................................................................20Step 11. Implement the Applications Products...................................................................................... ..22

Order Entry.......................................................................................................................................................23Receivables.......................................................................................................................................................23Purchasing.........................................................................................................................................................23Payables............................................................................................................................................................23Step 12. Secure Balancing Segment Values by Legal Entity (Optional)............................................ ....24Step 13. Run the Setup Validation Report (Recommended)................................................................... .24Step 14. Document Sequencing................................................................................................................25

Open and Closed Issues.............................................................................................................................41Open Issues............................................................................................................................................41Closed Issues..........................................................................................................................................41

Resources....................................................................................................................................................42



8/8/2019 multi-or (1)

4/42

1. Introduction

This document details the setup steps required for theimplementation of multi-org for the client. This documentprovides for a checklist type of approach to installing Multi-Org. This is document is not meant to provide exhaustivedetail of the internals of Multi-Org but rather a step by stepprocess for installing the Multi-Org functionality. At timesinternal details will be discussed to facilitatetroubleshooting however no attempt is made to provide atechnical understanding of the Multi-Org technicalarchitecture.

This document assumes the reader already has a basicunderstanding of the 10.7 and the Multi-Organizationarchitectures. The Database Administrator should also beexperienced at installing the apps, applying patches andreviewing the foundation tables and dictionary views.



8/8/2019 multi-or (1)

5/42

2. Preparation

This section deals with some of the specifics of what needsto be in place prior to undertaking the implementation ofRelease 10.7 of Oracle Applications.

I would strongly recommend you visit the Multi_org HomePage before starting.

Many steps are order dependent. If you skip steps this maycause the install to fail.-.

Considerations

The current system architecture is as follows:

Component Version

ServerOperating SystemOracle RDBMSOracle ApplicationsOracle 10SC Prod

Setup Schedule

These are the standard 13 steps as discussed in the Multi-orgreference manual. The setup schedule is as follows:

Steps Responsible Person

1. Develop the OrganizationStructure.

Client & FunctionalConsultants

Define Set of Books Functional

Define Organizations Functional

Define Org. Relationship Functional

Define Responsibilities Sys Admin, Functional (DBAshort cut)

Set profile Option for EachResponsibility

Functional

Conversion to Multi-Org DBA

Define Inv. Org Security(Optional)

Functional

Define OE Profile Options(Optional)

Functional

Update Profile Options Specificto Operating Units.

Functional

Application Setups Functional

Secure Balancing SegmentValues by Legal Entity.(Optional)

Functional.

Run the Setup ValidationReport

Functional.

Define Document Sequences Functional



8/8/2019 multi-or (1)

6/42

Steps Responsible Person

Setting Up, Chapter 2(Multiple Organizations in Oracle Applications Reference Manual - Part N

A50771-1)



8/8/2019 multi-or (1)

7/42

3. Summary of Terms

Set of Books

This is the highest level at which the financial entities aresegregated. Any entity with a particular Chart of Accountsstructure, functional currency or calendar must be aseparate Set of Books.

Organization

Any entity you define using the Define Organizations formis called an Organization. Organizations are thenassigned Classifications. The Classification(s) anOrganization is assigned determines its type and use.Business Group, Legal Entity, Operating Unit, InventoryOrganization, and HR Organization are all Organization

Classifications. An Organization may be assigned morethan one Classification e.g. the Organization VisionOperations may be assigned the Classifications of LegalEntity, Operating Unit, HR Organization and InventoryOrganization

Business Group

Represents the highest level in the structure. Theconsolidated enterprise or a major division of a company.Currently, Business Group has no other purpose but tosegregate HR information. If you request a list ofemployees (in any module) you will only see those

employees in the Business Group of which your OperatingUnit is a part. Multiple Legal Entities can relate to a singleBusiness Group.

Legal Entity

Represents a legal company for which you prepare fiscal ortax reports. A Legal Entity relates to a single Set ofBooks. Currently Legal Entity has very limited use outsideof Intrastate movement reporting.

Operating Unit

Any autonomous organization which uses OracleReceivables, Oracle Payables, Oracle Order Entry, OraclePurchasing and Oracle Projects. An Operating Unit isassociated with a single Legal Entity. Information issecured by Operating Unit in the above products withsome shared information (e.g. customer and suppliernames with sites being specific to each Operating Unit).



8/8/2019 multi-or (1)

8/42

Inventory Organization

An Organization for which you track inventory transactionsand balances. Oracle Inventory, Bills of Material,Engineering, Work in Progress, Master Scheduling / MRP,Capacity and Purchasing (receiving) secure information byInventory Organization. Inventory Organizations may be

related to any Operating Unit(s) within the same Set ofBooks. The relationship between Inventory Organizationand Set of Books is used for financial purposes only(creating requisitions and replenishing supplies).

HR Organization

HR Organizations are only utilized by Oracle HR andOracle Projects products and have no impact on theFinancial or Manufacturing applications. This facilitates acomplex organization structure for HR tracking but a moresimplified structure for the operational side of the Business

Note: There is nothing to stop one entitybeing a Business Group, Legal Entity,

Operating Unit and InventoryOrganization all at the same time (or anycombination). This would assume a very

simple organization structure.

Responsibility

This is a Grouping of functionality and system data oftenrelated to a job role or responsibility. Responsibilities areassociated with a Set of Books, Operating Unit and

Inventory Organization where appropriate through profilesettings (e.g. MO: Operating Unit defines the OperatingUnit for that Responsibility).

Balancing Segment

This is a segment in the Accounting Flexfield structure(usually the Company segment) at which all accountingentries must balance. There may be multiple companieswithin the same structure, each of these must balancewithin itself. All required inter-company entries willautomatically be created within the Set of Books to ensurecompanies can never be out of balance.

Security Rules

Security rules limit (by responsibility) the values of aFlexfield which the user will see. e.g. a user will only seethe Department values in the Accounting Flexfield whichthey have authority to see.



8/8/2019 multi-or (1)

9/42

4. Setting Up a Multi-Business Unit Enterprise

This essay describes how to implement your organizationalstructure within the Oracle Applications MultipleOrganization model. Before beginning this implementationbe sure you are familiar with the terminology Oracle usesfor its business organization model.

These are the necessary steps involved in implementingthe Multiple Organization Support feature in OracleApplications. All steps with the exception of adadmin arenecessary if you are implementing for the first time, or ifyou are adding additional organizations to your existingimplementation. Running adadmin only needs to be done ifyou are implementing for the first time. These steps aredetailed below.

1. Develop the Organization Structure

2. Define Sets of Books

3. Define Organizations

4. Define Organization Relationships

5. Define Responsibilities

6. Set Profile Option for Each Responsibility

7. Conversion to Multi Org

8. Define Inventory Organization Security (optional)

9. Change Order Entry Profile Options (optional)

10. Update Profile Options Specific to OperatingUnits

11. Implement the Applications Products

12. Secure Balancing Segment Values by LegalEntity (optional)

13. Run the Setup Validation Report (recommended)

14. Document Sequencing



8/8/2019 multi-or (1)

10/42

5. Multi-Org 10.7 Installation Steps

Step 1. Develop the Organization Structure

A successful implementation of Multiple OrganizationSupport in Oracle Applications depends primarily ondefining your organizational structure correctly.

You should assign organization classifications in thefollowing order:

1. Legal Entities

2. Operating Units

3. Inventory Organizations

Here is a generic example of how Oracle Multi-Org sees amulti-level company setup. From the following diagramplease note:

A Business Group is the highest level of the structureand has no accounting impact. The Business Groupdetermines which employees will be available to Setsof Books and Operating Units related to that BusinessGroup

Set of Books is the highest level which impacts theaccounting side of the Business

Set of Books is associated with a single BusinessGroup, multiple Sets of Books may be associated witha single Business Group

Each Set of Books may have a different chart ofaccounts structure, calendar or functional currency

Each Legal Entity is associated to a single Set ofBooks, multiple Legal Entities may be associated withthe a single Set of Books

Each Operating Unit is associated with a single Legal

Entity, multiple Operating Units may be associatedwith a single Legal Entity

Note: Currently, it is recommended by OracleApplications Development to keep a one-one-onerelationship between Set of Books, Legal Entityand Operating Unit. This restriction isrecommended for the following reasons:



8/8/2019 multi-or (1)

11/42

Document Sequencing (important in Europeancountries) is at the Set of Books level

Standard reports are at the Operating Unit level

Period status control is at the Set of Books level e.g. If

you close the period in Oracle Payables, all equivalentOracle Payables periods will close in all Operating Unitswithin the same Set of Books/Legal Entity.

Following is an example Organization structure set up:

I n v e n

O r g a n i i

I n v e n

O r g a n i i

O p e r a i

U n i t

I n v e n

O r g a n i i

O p e r a i

U n i t

L e g a l i

O p e r a i

U n i t

I n v e n

O r g a n i i

O p e r a i

U n i t

L e g a l i

S e t O f S e t o f S e t O f

B u s i n e s

Step 2. Define Sets of Books

Use the define Set of Books form to enter your Set Of

Books.

In this example, U.S. Operations and CAD Operations arethe two Sets of Books defined.

Set of BooksName

FunctionalCurrency

Accounting FlexfieldStructure

Calendar

US Operations USD Global US Calendar

CAD Operations CAD Global US Calendar

Define Set of Books(Oracle General Ledger Reference Manual)

Step 3. Define Organizations

Use the Define Organizations form to define yourorganizations. You define your organizations and therelationships between organizations in this same form. Youmay want to perform this step and the next step (DefineOrganization Relationships) at the same time. They arepresented separately here to signify the difference between



8/8/2019 multi-or (1)

12/42

the organizational entity and the role it plays in yourorganizational structure.

Multiple Business Groups

Multiple Business Groups Oracle Applications secures

human resources information, including organizationdefinition, by Business Group. This section applies to youonly if you have multiple Business Groups, or if you do notchoose to use the default Business Group provided byOracle Applications.

You must have at least one Business Group. For a freshinstallation, Oracle Applications provides a default BusinessGroup, Setup Business Group. You can define additionalBusiness Groups as required for your enterprise. If you areupgrading to Release 10.7 Multi-Org, you will already haveyour first Business Group defined.

IMPORTANT:

If your enterprise structure requires that youdefine a Business Group, you should define Setsof Books before Business Groups.

If you require multiple Business Groups, you mustdefine all of your Business Groups at this step.DO NOT define any new organizations ororganization hierarchies until you have associatedeach Business Group with a responsibility. (See:Define Responsibilities).

Create the new Organization (Setup, Organization,Organizations) with the organization classification asBusiness Group, in Oracle Inventory.

Create the new responsibility in System Administrator(Security, Responsibility, Define). Associate the newresponsibility to the Business Group within the profileoptions (Profile, System, select responsibility, select profileas HR: Business Group, find).

At the responsibility block across from the profile, select theappropriate HR Business Group and save.

Only after you have correctly associated Business Groupsand responsibilities should you proceed with enteringBusiness Group setup information, such as additionalorganization information, Business Group classifications,and so on.

For example, if you have a Canadian Business Group and aU.S. Business Group. To define the U.S. organization



8/8/2019 multi-or (1)

13/42

structure select the responsibility with the U.S. BusinessGroup attached.

At Global, one HR Business Group is defined as the GlobalBusiness Group. The profile option is set at the site leveland each responsibility.

Organization Name

Global Business Group

Define Organization(Oracle Inventory Reference Manual)

Defining Organizations

1. Sign-on into Oracle with the correct responsibility tied tothe correct Business Group for your organization.

2. Define a Legal Entity and attach it to the correct Set ofBooks.

3. Define an Operating Unit(s) and attach it to the correctLegal Entity.

4. Define an Inventory Organization(s) for each OperatingUnit. DO NOT define the inventory parameters.Inventory parameters will be covered later.

5. Change to another responsibility in another BusinessGroup and continue to define your organization

structure. Repeating steps 1 through 4.

At Global, U.S. Operations and CAD Operations are the twoLegal Entities defined. US AAA Operating Unit, US BBBOperating Unit, and CAD AAA Operating Unit are the threeOperating Units defined. CAD Depot, US BBB New York, USAAA Depot, and US AAA Field Services are the InventoryOrganizations defined. Please refer to inventoryorganization structure depicted in Step 1.

Organization Name

US Operations Legal Entity

CAD Operations Legal

EntityUS AAA Operating Unit

US BBB Operating Unit

CAD AAA Operating Unit

US AAA Depot

US AAA Field Services

US BBB New York

CAD AAA Depot



8/8/2019 multi-or (1)

14/42


Inventory Parameters

At this time, you can not see organizations defined in oneBusiness Group if you are in another Business Group.

Therefore, if you are trying to select an Item Master definedin another Business Group, you will not be able to select it.

This will still be the case in 10.7 until you run adadminwhich will convert to a Multiple Organization architecture.After running this program, you will be able to select theItem Master across Business Groups. You still will not beable to query the Item Master in the Define OrganizationForm until you change to responsibility that has the sameBusiness Group as the Item Master Business Groupattached.

If you want to have a Global Item Master, you should waituntil Step 7 -10 are completed before defining inventoryparameters. If you want each Business Group to have theirown Item Master, define the inventory parameters beforestep 7.

At Global, Global Item Master will be the global Item MasterInventory Organization set up with a code of ZZZ and partof the Global Business Group.

Step 4 Define Organization Relationships

Use the Define Organization form to define yourorganizational relationships by assigning classifications toeach organization.

Attributes of certain classifications relate organizations andthe roles they play. You can classify an organization as anycombination of legal entity, Operating Unit, and InventoryOrganization. Specify your organization classifications inthe following order:

1. Legal Entities

2. Operating Units

3. Inventory Organizations



8/8/2019 multi-or (1)

15/42

8/8/2019 multi-or (1)

16/42

2. All organizations -This mode applies when the seeddata replication program is executed without anOperating Unit context.

The seed data replication program performs differentfunctions depending upon 1) the mode in which it is

operating, 2) the value of the multi_org_flag, and 3) thevalue of the ORG_ID for each Operating Unit. An ORG_ID of'-3113' identifies a table row of seed data that should bereplicated to each Operating Unit. An ORG_ID of '-3114'identifies a table row of seed data that should be replicatedas null, and shared across all Operating Units.

At Global, these are the relationships defined

Classification Information Type Required Fields

GRE/Legal Entity Legal Entity Accounting Set of Books

Operating Unit Operating Unit Information ORACLE ID, Legal Entity

Inventory Organization Accounting Information Set of Books, Legal Entity, OperatingUnit

OrganizationName

Is Legal

Entity?

Is Oper

Unit?

Is Inv

Org?

Set of

Books

Legal

Entity

Oper

Unit

US Operations Yes USOperations

CAD Operations Yes CADOperations

US AAA OperatingUnit Yes USOperations USOperations

US BBB OperatingUnit

Yes USOperations

USOperations

CAD AAA OperatingUnit

Yes CADOperations

CADOperations

US AAA Depot Yes USOperations

USOperations

US AAA

US AAA Field Svcs Yes USOperations

USOperations

US AAA

US BBB New York Yes USOperations

USOperations

US BBB

CAD Depot Yes CADOperations

CADOperations

CAD AAA




8/8/2019 multi-or (1)

17/42

Step 5. Define responsibilities

Use the Define Responsibility form to define theresponsibilities for each Operating Unit. A responsibility'sdata group determines its Operating Unit. When you signon to Oracle Applications, the responsibility you choosedetermines the data, forms, menus, reports, and concurrent

programs you can access.

Responsibilities defined at Global include the following:

Responsibility Description

US AAA Inventory Super User US AAA Operating UnitInventory Super User

US BBB Inventory Super User US BBB Operating UnitInventory Super User

CAD AAA Inventory Super User CAD AAA Operating UnitInventory Super User

Define Responsibility(Oracle System Administration Reference Manual)

Step 6. Set Profile Option for Each Responsibility

Multiple Business Groups

This section applies only if there are multiple Business

Groups, or no default Business Group selected (provided byOracle Applications).

If you create additional responsibilities, you must associateeach of your responsibilities to one and only one BusinessGroup (discussed in Step 3).

At Global, there is only one Business Group defined. At thesite level, HR Business Group is US Global Business Groupand CAD Global Business Group

Responsibility Business Group Organization

US AAA Inventory Super User US Global Business Group

US BBB Inventory Super User US Global Business GroupCAD AAA Inventory Super User CAD Global Business Group

Multiple Operating Units

The MO:Operating Unit profile option must be set for eachresponsibility. Set this profile option to the appropriateOperating Unit for each responsibility.



8/8/2019 multi-or (1)

18/42

Sign on in System Administrator. Associate the newresponsibility to the MO Operating Unit within the profileoptions (Profile, System, select responsibility, select profileas MO: Operating Unit, find).

At the responsibility block across from the profile, select the

appropriate Operating Unit and save.

This profile option must be set for Oracle TrainingAdministration (OTA) responsibilities when OTA is used in aMulti-Org environment. This is to ensure that the OTAcustomer and supplier functions work correctly in a Multi-Org environment.

You also need to define the default Operating Unit bysetting the MO:Operating Unit profile at the site level. Ifthis is a fresh installation, the default Operating Unit canbe any Operating Unit you have previously defined. If thisis an existing installation, the default Operating Unit should

be the Operating Unit to which all existing data shouldbelong.

Sign on in System Administrator. Associate the defaultOperating Unit to the MO Operating Unit within the profileoptions (Profile, System, select Site, select profile as MO:Operating Unit, find).

At the site block across from the profile, select theappropriate Operating Unit and save.

At Global, the MO: Operating Unit is set at US AAAOperating Unit, for all US AAA responsibilities, US BBB

Operating Unit, for all US BBB responsibilities and CAD AAAOperating Unit, for all Canadian AAA responsibilities.

At Global, the MO: Operating Unit is set at US AAAOperating Unit at the site level.

Responsibility Profile Options Value

US AAA Inventory Super User MO:Operating Unit US AAA Operating UnitUS BBB Inventory Super User MO:Operating Unit US BBB Operating UnitCAD AAA Inventory Super User MO:Operating Unit CAD AAA Operating Unit

Site Profile Options Value

MO:Operating Unit US AAA Operating Unit

Define Profile Options(Oracle Application Object Library Reference Manual)



8/8/2019 multi-or (1)

19/42

Step 7. Conversion to Multi-Org

Ask your database administrator to run the AutoInstallutility 'adadmin'. This utility must be run for a standard10.7 installation as well as for a Multi-Org 10.7 installation.One of the options in adadmin is to convert to MultipleOrganization architecture. Choosing this option will enable

the Multiple Organization Support feature as well as addOperating Unit context to all existing data.

Seed Data Replication, page 4-20(Oracle Applications Installation Manual)

Step 8. Define Inventory Organization Security (Optional)

With Inventory Organization security you can restrictInventory Organization access to specific responsibilities.

You may want to restrict your manufacturing users tocertain organizations according to your organizationalhierarchy.

Until you assign an organization to a responsibility in thiswindow, all responsibilities have access to all organizations.Once you have restricted any responsibility to anorganization, you must then explicitly define theorganizations which all responsibilities can access.

This feature does not restrict access once the user is in the

product. Users with access to functions that cross multipleorganizations (such as ATP, Inter-organization Transfers,Item Search, Multi-organization Quantity Report, and so on)can still specify any valid organization when running thesefunctions.

At Global, we did not set up any Inventory OrganizationSecurity.

Step 9. Change Order Entry Profile Options(Optional)

Item Validation Organization

If you have different Item Validation organizations for yourOperating Units, use the Define User Profile Option form tochange the level characteristics of your OE:Item ValidationOrganization profile option so they are visible andupdatable at the responsibility level.

Sign on in Applications Developer. Select Profile, queryuser profile name of OE: Item Validation Organization.



8/8/2019 multi-or (1)

20/42

Check the System Administrator access box for visible andupdatable at the responsibility level.

At Global, we selected responsibility and user as visible andupdatable.

Set of Books

For accounting purposes, you should ensure that anOperating Unit and the Item Validation organization thatyou choose for it share the same Set Of Books. TheValidation Report examines your implementation to verifythis and checks that an Operating Unit's Item Validationorganization is an Inventory Organization linked to thatOperating Unit. The two checks are performed separately.

If you have different Sets Of Books for your Operating Units,change the level characteristics of the OE: Set of Booksprofile option to be visible and updatable at the

responsibility level.

Sign on in Applications Developer. Select Profile, queryuser profile name of OE: Set of Books. Check the SystemAdministrator access box for visible and updatable at theresponsibility level.

At Global, we selected responsibility as visible andupdatable.

Sequential Numbering

If you have different sequential numbering requirements

(Always Used, Not Used, Partially Used) for your Sets OfBooks, change the Sequential Numbering profile option tobe visible and updatable at the responsibility level.

Sign on in Applications Developer. Select Profile, queryuser profile name of Sequential Numbering. Check theSystem Administrator access box for visible and updatableat the responsibility level.

At Global, we selected responsibility as visible andupdatable.


Step 10. Update Profile Options Specific to Operating Units

Use the Update System Profile Options form to set profileoptions that are specific to each Operating Unit. You need



8/8/2019 multi-or (1)

21/42

to set these profile option values for all relevantresponsibilities that connect to each Operating Unit.

For profile options referencing data that is secured byOperating Unit, including AR:Receipt Batch Source andAR:Transaction Batch Source, you must set their values at

the responsibility level.

For profile options that need to differ at the Operating Unitlevel, including OE:Item Validation Organization, OE:Set ofBooks, and GL: Set of Books, HR: Business Group, youshould set and review their values at the responsibilitylevel.

Oracle General Ledger forms use the GL Set of Books profileoption to determine your current Set Of Books. If you havedifferent Sets Of Books for your Operating Units, you shouldset the GL Set of Books profile option for each responsibilitythat includes Oracle General Ledger forms.

For profile options that need to differ at the Set Of Bookslevel, including Sequential Numbering, set their values atthe responsibility level.

Profile options specify default values that affect systemprocesses, system controls, and data entry. In a multipleorganization environment you may want to confine theeffect to a specific Operating Unit. Hence, you may want tochange your profile options to be visible and updatable atthe responsibility level.

At Global, the following profiles were updated for each

responsibility:

PROFILE OPTION RESPONSIBILITY (Super User)

HR: Business GroupGlobal Business Group US Operating Unit Application

CAD Operating Unit Application

GL: Set Of Books U.S. Operations US Operating Unit Application

CAD Operations CAD Operating Unit Application

MO: Operating Unit US AAA Operating Unit US AAAApplication

US BBB Operating Unit US BBB Application

CAD AAA Operating Unit CAD AAA Application



8/8/2019 multi-or (1)

22/42

OE: Set Of Books U.S. Operations US Operating Unit Application

CAD Operations CAD Operating Unit Application

OE: Item Validation Global Item Master US Operating Unit Application

CAD Operating Unit Application

Remember to do this for each and everyresponsibility.

At Global, Sequential Numbering is set at Partially Used atthe Site level and Always Used at the Application Level -General Ledger. Please read step 14.


Step 11. Implement the Applications Products

Once the setup steps above are complete, you go into eachOperating Unit and setup the Oracle Applications products.

The following products must be setup for each OperatingUnit in which you intend to perform the functions: Oracleorder Entry, Oracle Payables, Oracle Purchasing, Oracleprojects, Oracle Receivables and Oracle SalesCompensation.

Oracle Fixed Assets, Oracle General Ledger, OracleInventory and the rest of the Oracle Manufacturing productsonly need to be setup once for the installation, not once foreach Operating Unit. To perform this setup follow theinstructions in the Oracle Applications Installation Manual.

The following setup data need only be setup once for theEnterprise:

Flexfield Definitions

Customer Header

Vendor Header

All other information not listed below

the following setup data must be setup for each operatingunit:



8/8/2019 multi-or (1)

23/42

Order Entry

Hold Sources

Order Types

Holds

Receivables

Transaction Types

Remit to Addresses

Salesrep

Tax Exemptions

Batch Sources

VAT Taxes

System Parameters distributions

Memo lines

Auto-Accounting

Invoice Sources

Receipt Sources

Tax Codes

Tax Rates

Purchasing

Control functions/groups

System Parameters

Position Controls

Autosource documents

Account Distributions

Payables

Distribution Sets

Bank Accounts



8/8/2019 multi-or (1)

24/42

Tax names and groups

Expense Report Types

System Options

Oracle Applications Installation Manual

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

Use the Define Security Rule form to create rules thatsecure data entry of balancing segment values for eachlegal entity. Each security rule is composed of one or moresecurity rule elements that specify a range of values toinclude or exclude.

Use the Assign Security Rules form to assign the same

rule(s) to all responsibilities associated with the legalentity's Operating Units.

If you need further to secure balancing segment values foreach Operating Unit of a legal entity, you can defineadditional rules and assign them to all responsibilitiesassociated with the relevant Operating Units. If, forexample, you need to restrict the Northwest RegionOperating Unit to balancing segment value 01 and theSouthwest Region to balancing segment value 04, you canadd the following rules.

In addition to the previous rule assignments, you can

assign the new rules to all responsibilities associated withthe two Operating Units. When you assign multiple rules tothe same responsibility, only the overlapping values of therules are available to users of the responsibility.

Oracle General Ledger Reference Manual

Step 13. Run the Setup Validation Report (Recommended)

After you have implemented Multi-Org, run the Setup

Validation Report to identify any setup problems. Some ofthe errors that the report finds may be deleted optionallyvia the report form, while others require that you changeyour setup. All suggested changes can be confirmedoptionally so that you may retain your implementation evenif it fails validation.

Some of the errors that may be identified on the reportinclude:



8/8/2019 multi-or (1)

25/42

Disabled fields on Enter Customer and Enter Vendorforms

Consistency of Profile Option Values for each operatingunit

Item Validation Organization

Step 14. Document Sequencing

After you have implemented Multi-Org and ran the SetupValidation Report, setup Document Sequencing for eachApplication.

This explains how to assign unique numbers to documentsyou create using Oracle Applications. Each time you entera transaction, you create a document.

For example, when you enter a payment, you create apayment document. Or when you enter an invoice, youcreate an invoice document.

By assigning unique numbers to documents, you canaccount for each transaction you enter and the documentthat accompanies it.

The following is an essay explaining what documentsequences are and how they work in Oracle Applications.Following the essay are descriptions of the forms you useto:

Define sequences, which is how you number yourdocuments.

Define document categories, which allows you tocategorize or Group documents together.

Assign sequences to documents, which allows you todefine which documents you will number using aparticular sequence.

Business Requirements

All accounting systems have to prove completeness andprovide audibility. Document sequences can be used toprovide both proof of completeness and audibility.Completeness is proof that no documents have been lost,or not posted.

By assigning unique numbers to documents, evendocuments that are not successfully entered, document



8/8/2019 multi-or (1)

26/42

sequences can be used to account for every transaction,even transactions that fail.

Document sequences generate audit data, so even ifdocuments are deleted, their audit records remain.

Audibility is a mechanism for providing an audit trail from aGeneral Ledger balance to a transaction.

Audibility provides an audit trail back from the GeneralLedger into the subsidiary ledger, and to the documentthat originally affected the account balance.

Using Oracle financial applications, you initiate atransaction by entering data through a form andgenerating a document, for example, an invoice.

Document sequences generate an audit trail thatidentifies the application that created the transaction,

for example, Oracle Receivables, and the originaldocument that was generated, for example, invoicenumber 1234.

What is a Document Sequence?

You use a document sequence to uniquely numberdocuments generated by an Oracle Application, forexample, payments generated by Oracle Payables.

When you define a document sequence, you give thesequence a name, and define how the sequence numberseach document by:

Choosing whether numbers are automatically generatedin sequence, or entered manually by the user.

Entering the initial value or first number in thesequence.

Defining a Sequence

When you define a sequence you give the sequence aname and select an application that "owns" the sequence.

A sequence can number documents stored in database

tables belonging to its owning application.

Audit records for a sequence are stored in theapplication's audit table, titled Application ShortName_DOC_SEQUENCE_AUDIT. For example, the audittable for a sequence owned by Oracle Payables isAP_DOC_SEQUENCE_AUDIT.



8/8/2019 multi-or (1)

27/42

Your database administrator must grant access to anapplication's audit table for all ORACLE IDs associated withresponsibilities that will use the sequence (responsibilitiesthat access forms using the sequence).

You can set effective start and end dates for when the

sequence is available. The starting date defaults to thecurrent date. By default there is no end date, so thesequence definition does not expire.

You can choose whether a sequence numbers documentsautomatically, or accepts numbers manually entered by auser.

Automatic vs. Gapless vs. Manual Sequences

Automatic numbering sequentially assigns a uniquenumber to each document as it is generated, by its dateand time of creation.

Gapless numbering also automatically generates a uniquenumber for each document, but ensures that the documentwas successfully generated before assigning the number.With Gapless numbering, no sequence numbers are lostdue to incomplete or failed document creation.

We recommend that you choose this type only whengapless numbering is essential, as it may affect theperformance of your system.

Manual numbering requires a user to assign a uniquenumber to each document before it is generated.

Numerical ordering and completeness is not enforced.Users can skip or omit numbers when entering thesequence value.

Numbers should be nine digits or less.

Automatic Numbering - Initial Value and Message Display

If you define a sequence to automatically numberdocuments, you can:

Enter an initial value for your sequence. The default is

"1".

Choose whether you want to display a message when adocument is generated, telling the user the name of thesequence, and the sequence value (document number).

What is a Document Category?



8/8/2019 multi-or (1)

28/42

Use categories to categorize your documents into logicalGroups.

Document category, or type, as it may be titled on someforms, is one of the rules you use to define whichdocuments a sequence assigns numbers to.

You can separately number document categories byassigning different sequences to each category

Each category identifies a table that stores documentsresulting from transactions your users enter.

When you assign a sequence to a category, thesequence numbers the documents that are stored in thetable.

Use categories to more precisely classify your documents,for example, you can categorize accounts receivable

invoices into several different categories, such as:

Chargebacks

Deposits

Guarantees

Debit Memos

Credit Memos

Sales Invoices

Customer Service Invoices

Likewise, you can categorize accounts payable or purchaseinvoices into several different categories, such as:

Standard

Expense Report

Prepayment

Interest

Credit Memo

Debit Memo

What does it mean to Assign a Sequence?



8/8/2019 multi-or (1)

29/42

Before you can assign a sequence to number documents,you must define which documents are to be numbered.

Sequences versus Assignments

A sequence's definition is different from the rules used to

assign a sequence to a series of documents.

A sequence's definition determines whether adocument's number is automatically generated insequence, or manually entered by the user, and whatthe initial value (first number) of the sequence is.

A sequence's assignment, that is, the documents asequence is assigned to number, is defined by rulesentered in the Document Flexfield, on the AssignDocument Sequences form.

Defining Documents for numbering by Assigned Sequences

You specify a combination of four rules that define anygiven document for assignment to a specific sequencename.

You can then assign a different (numbering) sequence toeach document definition.

The four rules, that when combined, define whatdocuments a selected sequence assigns numbers to are:

Application

You select the application that generates the documentsyou wish to number.

For example, to number sales invoices, you select OracleReceivables.

Category

You select a document category to identify a logical subsetof documents.

For example, if you do not want to number all invoices inOracle Receivables, you can choose to number only thecategory of sales invoices.

A category identifies a table that stores transactionsentered (documents generated) using an OracleApplication.



8/8/2019 multi-or (1)

30/42

The Category values you can choose from to define adocument are dependent upon the application you select.

Set of Books

You select the chart of accounts for your Business that is

affected by the documents you wish to number. You mayoptionally enable this rule through the Document Flexfield.

Method

You select the method that your documents are entered,automatic or manual. You may optionally enable this rulethrough the Document Flexfield.

Automatic is when a concurrent process, such as anexternal program, is set up to enter transaction data into anOracle Application.

Manual is when a document is manually entered using aform in an application.

Assignment of Sequences to Document Definitions

For each unique document definition there can only be oneactive sequence assignment. A document definitionconsists of the Application, Category, and the optionalDocument Flexfield segments Set of Books and Method

When assigning sequences to a document definition, eachactive sequence can be assigned to only one uniquecombination of application and category (i.e., application

table).

Active Assignments and Active Sequences

An active sequence assignment does not have a post datedend date. That is, the assignment's end date is not beforethe current date.

An active sequence assignment either has no end date,or an end date that is not before the current date.

A sequence assignment and its dates of effectively aredefined on the Assign Document Sequences form.

A sequence definition must be active as well. That is, thesequence definition's end date (as opposed to itsassignment's end date) must not be before the currentdate.

A sequence definition and its dates of effectively aredefined on the Define Document Sequences form.



8/8/2019 multi-or (1)

31/42

Document Numbering vs. Document Entry

Do not confuse the type of document numbering asequence employs, which can be automatic or manual, with

the method of entering documents, which is also defined aseither automatic or manual.

Start Set Up of Sequences

Initiate Descriptive Flex Field

Sign into an Application (Oracle General Ledger SuperUser)

Standard menu path: Setup Financials Flex Field

Descriptive Segments

Query on title: Document Flexfield, select SegmentsButton, Display and Enable segment Set of Books, save.

Return to first screen, Freeze Flexfield Definition, Compile,and save.

Define Document Sequences

Standard menu path: Setup Financials Sequences Define

Use this form to name a new document sequence anddefine how the sequence numbers each document.

A document sequence numbers documents generated byan Oracle application, for example, invoices generated byOracle Receivables.

A document sequence uniquely numbers each documentthe sequence is assigned to. Using the Assign DocumentSequences form, you assign your sequence to number onlydocuments that satisfy rules you define.

Document sequences insure that every document yourusers create can be accounted for.

Document Sequences Zone



8/8/2019 multi-or (1)

32/42

Use this zone to define the name, type of numberingscheme, effective dates, and initial value for yourdocument sequence.

Name (Required) EDIT HELP

Enter a unique name for your document sequence. Thename you enter can be up to a maximum of 30 characters.Once entered, sequence names cannot be changed.

At Global, US Set of Books is the unique name defined.

Application (Required) EDIT PICK HELP

Select the name of an application to associate with yourdocument sequence. Once selected, the applicationassociated with your sequence cannot be changed.

At Global, Oracle General Ledger is the application defined

Access

You grant access to your document sequence from OracleApplications by selecting their ORACLE usernames in theAccess block.

At Global, GL is the access username, Oracle GeneralLedger Account.

Audit records for your sequence are stored in theapplication's audit table, titled Application ShortName_DOC_SEQUENCE_AUDIT. For example, the audit

table for a sequence owned by Oracle Payables isAP_DOC_SEQUENCE_AUDIT.

Your database administrator must grant access to anapplication's audit table for all ORACLE IDs associated withresponsibilities that will use the sequence (responsibilitiesthat access forms using the sequence).

Effective Dates Start (Default) HELP

Enter the date that your document sequence takes effect.This field automatically defaults to the current date. It isrecommended the date is five years old.

Once a sequence is defined, the start date cannot bechanged.

At Global, 01-May-1990 is the effective date.



8/8/2019 multi-or (1)

33/42

Effective Dates End (Optional) HELP

Enter a date after which your document sequence no longeris enabled. If you leave this field blank, your document

sequence does not expire.

If you enter an end date and define your sequence,the end date cannot be modified later.

If there is no end date defined and there are no activeassignments for a sequence, you can disable the sequenceby entering the current date as the end date. Oncedisabled, a sequence cannot be reactivated.

Type (Required) EDIT PICK HELP

Select the type of numbering sequence you want yourdocuments to have. Once a sequence is defined, youcannot change the type of document numbering.

Automatic

Sequentially assigns, by date and time of creation, a uniquenumber to each document as it is generated.

Gapless

Sequentially assigns a unique number to each document as

it is generated. Numbers are guaranteed to be sequential,with no gaps or skipped numbers.

We recommend that you choose this type only whengapless numbering is essential, as it may affect theperformance of your system.

Manual

Manual numbering requires a user to assign a number toeach document before it is generated.

You must enter unique values. However, please note that

numerical ordering and completeness is not enforced.

At Global, Automatic number is the type defined.

Initial Value (Default) EDIT HELP



8/8/2019 multi-or (1)

34/42

Enter a value for the first document in your sequence. Thisfield only applies to sequences with the automatic type ofnumbering. The maximum sequence value is 1.0e+27

If you leave this field blank, the first document isautomatically assigned a value of "1".

Once a sequence is defined, the initial value cannotbe changed.

At Global, 1 is the initial value.

Message (Optional) EDIT PICK HELP

Select whether you want each document to display amessage (in the message line near the bottom of thescreen) informing the user of the sequence name and value

(number).

This field only applies to sequences with the automatic typeof numbering. Messages appear only on form displays, andare not written to a request's log file.

Once a sequence is defined, the message choicecannot be changed.

At Global, message is not enabled.

Access Zone

Use this block to allow your document sequence to beaccessed from your Oracle applications. You can extendaccess to your document sequence from additionalapplications by selecting each application's ORACLE ID.

Extending access to your document sequence from morethan one ORACLE ID is especially useful when there is morethan one installation of a given product, for example, whenthere are multiple Sets Of Books.

Oracle Username (Required) EDIT PICK HELP

Select the Oracle IDs that that can access your sequence;more than one application may use a sequence to numbertheir own documents.

Once your sequence is defined, you cannot delete accessprivileges to Oracle Usernames.



8/8/2019 multi-or (1)

35/42

At Global, GL is the username.

Description (Display only) EDIT HELP

This field shows the description of the Oracle Username youselected in the previous field.

At Global, Oracle General Ledger is the description.

Define Document Categories

Standard menu path: Application Document Categories

Use this form to define categories for your documents. Usecategories to divide your documents into logical Groups,which you can number separately by assigning differentsequences.

A document sequence uniquely numbers each documentthe sequence is assigned to.

Using the Assign Document Sequences form, you assignyour sequence to number only documents that satisfyrules you define.

Document category, or type, as it may be titled on someforms, is one of the rules that define what documents asequence assigns numbers to.

Each category identifies a table that stores documents

resulting from transactions your users generate.

When you assign a sequence to a category, thesequence numbers the documents that are stored in thetable.

Document Categories Zone

Use this zone to name a document category, and associatea table with the category.

When the sequential numbering feature checks forcompleteness or generates a report, it locates thecategory's documents in the table.

When you enter this zone, Oracle automatically queries forany existing document categories.




8/8/2019 multi-or (1)

36/42

Select the name of an application.

Only tables belonging to the selected application can beassigned to a category.

Once a category is defined, you cannot change the

choice of application.

Code (Required) EDIT HELP

Enter a code for your document category.

Category code must be unique within an application.

Once a category is defined, you cannot update its code.

Name (Required) EDIT HELP

Enter a name for your document category.

You can update the name, if you wish. For example, ifthe category name is predefined, you can change thename to a more familiar value.

Description (Optional) EDIT HELP

Enter a description for your document category, if you wish.

Descriptions can be up to a maximum of 255characters.

You can update the description, if you wish. For

example, if the category description is predefined, youcan change the description to a more familiar value.

Table (Required) EDIT PICK HELP

Select the name of the table that stores the documents youwant to identify by your category.

When the sequential numbering feature checks forcompleteness or generates a report, it locates thecategory's documents in the table.

Only tables belonging to the application associated with

the category can be chosen.

Once a category is defined, you cannot change thechoice of table.

At Global, no additional categories are defined.



8/8/2019 multi-or (1)

37/42

Assign Document Sequences

Standard menu path: Setup Financial Sequences Assign

Use this form to define which documents a documentsequence will number, and then assign the document

sequence to your definition.

A document sequence numbers documents generated byan Oracle application, for example, invoices generated byOracle Receivables.

Besides entering a document definition and assigning asequence to it, you can, if you wish, enter effective datesfor the assignment.

Prerequisites

Before using this form to define the documents a documentsequence will number, and then assign a documentsequence to your definition, you should define anydocument sequences you wish to assign, using the DefineDocument Sequences form.

Document Sequence Assignments Zone

Use this zone to define documents by the application thatgenerates them, the Set Of Books they affect, the category

of the document, and the method the document is entered.

Once a document definition is entered, you can select asequence to assign it to. Since the effective dates for anassignment must fall within the sequence's start and enddates, the list of available sequences depends on the startand end dates, if any, specified for the assignment.

There can only be one active sequence assigned to eachunique combination of Application, Category, Set of Books,and Method. The last two criterion are optional, and are setin the Document Flexfield.

However, the same sequence can be assigned to more thanone combination of Application, Category, Set of Books, andMethod as long as the Application and Category remain thesame.


Select the application that generates the documents youwish to number.



8/8/2019 multi-or (1)

38/42

8/8/2019 multi-or (1)

39/42

Manual is when a document is manually entered using aform in an application.

You may not define additional segments for the DocumentFlexfield.

At Global, Method was not enabled.

Effective Date Start (Default) HELP

Enter the date that the sequence assignment to yourdocument definition takes effect. This field automaticallydefaults to the current date.

Once a sequence assignment is defined, the start datecannot be changed.

At Global, the same date is entered (01-May-90) for thestart.

Effective Date End (Optional) HELP

Enter a date after which your sequence assignment is nolonger enabled. If you leave this field blank, your sequenceassignment does not expire.

If you enter an end date and define your sequenceassignment, the end date cannot be modified later.

If there is no end date defined and there are no activeassignments for a sequence, you can disable the sequenceassignment by entering the current date as the end date.

Once disabled, a sequence assignment cannot bereactivated.

At Global, no end date is entered.

Sequence Name (Optional) EDIT PICK HELP

This field allows you to assign a sequence name to adocument definition (Document Flexfield combination).

Only sequences defined for the document's application canbe selected. Once you define a sequence assignment, thesequence name cannot be updated later.

If you want to disable the sequence assignment and assigna new sequence to the document definition (DocumentFlexfield combination), you must first, enter an End Date todisable the current sequence assignment, then, second,create a new record (row) for the new assignment.

At Global, U.S. Set of Books is the sequence name.



8/8/2019 multi-or (1)

40/42

8/8/2019 multi-or (1)

41/42

Open and Closed Issues

Open Issues

Closed Issues



8/8/2019 multi-or (1)

42/42

Resources

Oracle Applications, Oracle Multi-Org for Dummies,Russell Pike, March 1997

Multiple Organizations in Oracle Applications, Setting Upa Multi-Organization Enterprise

Application Configuration Document , Multi-OrganizationSetup, Rodney Bates, April 1997

Oracle Applications, Oracle System AdministratorsManual, Chapter 12: Document Sequences