Oracle Multi-Org - AR and OM Data Structure Changes Team: Technology Creation Date: 1 July 2009 Created By: Brendan Furey Last Updated: Control: document.doc Version: 1.0 Introduction..................................................2 Customer Model (TCA)..........................................3 Entity Relationship Diagrams...............................3 Record Duplication.........................................4 Oracle Applications Modules...................................6 Entity Relationship Diagrams...............................6 Multi-Org Setup............................................7 Transactional Entities........................................8 AR Invoices................................................8 AR Receipts................................................9 OM Transactions...........................................10 Entity Listing...............................................11 Org Setup Required........................................11 Transactional Org-Striped Entities........................11 Org Setup Not Required....................................12 1 Introduction
13
Embed
Oracle Multi-Org - AR and OM Data Structure Changes
Companies sometimes implement Oracle AR and OM using a single operating unit, and add more operating units later. This document outlines at a high level the structural data changes involved in setting up new operating units, using an upgrade from one to four operating units as an example. The document follows a graphical, ERD-based approach. It does not attempt to detail the actual functional setup steps required
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
Oracle Multi-Org - AR and OM Data Structure Changes
AR Invoices.......................................................................................................8AR Receipts.......................................................................................................9OM Transactions.............................................................................................10
Org Setup Required.........................................................................................11Transactional Org-Striped Entities....................................................................11Org Setup Not Required...................................................................................12
1Introduction
Introduction
Companies sometimes implement Oracle AR and OM using a single operating unit, and later add additional operating iunits. This document outlines at a high level the structural data changes required in setting up new operating units, using an upgrade from one to four operating units as an example. It does not attempt to detail the actual functional setup steps required.
The first section deals with the structural data changes in the Oracle customer model, with diagrams representing the entities and relationships concerned. The setup required here involves duplicating certain of the entities across the new operating units, and we distinguish between those entities that require duplication across the new operating units and those that don’t.The second section deals with the setup required in the various Oracle modules, such as AR and OM, where the setup generally involves creating parallel records in the new operating units, with different values for certain attributes, such as accounting fields. The final section tabulates all the entities depicted, noting the Oracle table names and the type of method used for setup where applicable.
This document may help to identify custom reports and programs that need modifying for the new data structures.
2Introduction
Customer Model (TCA)
Entity Relationship Diagrams
Oracle TCA ERD
3Introduction
Operating Units ERD
ERD Key
The entities are formatted according to three types:
Entity Type NotesNon-Org Entity Global entity requiring no setup across new AR operating unitsOrg-Striped Entity Org-striped requiring setup across new AR operating units
Org-Linked EntityGlobal entity, but referencing an org-striped entity, and therefore also requiring setup across new AR operating units
AR and OM Operating Units
Note that, generally, the new operating units may already exist, but without setup for order and invoice processing. In the example considered three new AR operating units OU2, OU3, OU4 will be implemented for AR by this set up, while only two OU2, OU3 (so it is thought) will be implemented for OM, since OU4 will not need to take orders.
Record Duplication
Customer Conversion
The records corresponding to the entities in the AR Operating Unit Entity will be copied from the existing records for OU1 to new records for:
4Introduction
OU2
OU3
OU4
No other records need be copied, so that customers, addresses, and contact details will remain global.
Customer Synchronisation
Changes to addresses and site contact details may be made in any operating unit, and will be visible in all. Changes to Operating Unit entity records will be synchronised across the operating units by means of database triggers that propagate the changes.
5Introduction
Oracle Applications Modules
Entity Relationship Diagrams
Responsibilities
OE Transaction Types
Remit To Addresses
6Introduction
Other Org-Striped/Linked Entities
Multi-Org Setup
The org-striped and org-linked entities will be set up across the new operating units by a mixture of manual and automated methods, summarised in the last section.
7Introduction
Transactional Entities
AR Invoices
8Introduction
AR Receipts
9Introduction
OM Transactions
10Introduction
Entity Listing
Org Setup Required
Entity Table NameLinked/Striped
Setup Type
# per OU
Oracle Screen
TCA
Responsbiility HZ_ROLE_RESPONSIBILITYLinked
(none) 0
CustomersSite Contact Role HZ_CUST_ACCOUNT_ROLES
Program
385,493
Site HZ_CUST_ACCT_SITESStriped
124,683
Site Use HZ_CUST_SITE_USES 194,627
FND
Responsibility FND_RESPONSIBILITY
Linked FNDLOAD
45Responsibility
Responsibility Exclusion FND_RESP_FUNCTIONS 682
User Responsibility FND_USER_RESP_GROUPS 34,762 User