Mr. Sandeep M Shinde www.eTutorInfotech.
com
eTutorInfotech@gmail.com 8308800428/99309754
Oracle Trading Community Architecture (TCA)
Oracle Trading Community Architecture (TCA) is a data model that allows you to manage
complex information about the parties, or customers, who belong to your commercial
community, including organizations, locations, and the network of hierarchical relationships
among them using the TCA registry.
TCA registry is the single source of trading community information for Oracle E-Business Suite
applications which provide user interfaces, batch data entry functionality, and other features to
view, create, and update Registry information.
TCA key entities:
Parties: Parties are the entities of type person/organization that enter into a business relationship
Party Sites: Addresses of the parties
Customers: Parties with whom you have a selling relationship
Customer Accounts: The business relationships between you and your customers
Customer Account Sites: Address of the party used in the case of customer accounts
Locations: Geo-spatial points, usually defined by an address
Contacts: People who have a contact or employment relationship with an organization or person
Contact Points: Means of contact, for example, phone and e-mail address
Process Flow:
This diagram shows the process flow for managing, searching, creating, and updating customer
information.
R12 Trading Community Architecture:
Includes following new trading entities:
Bank and Bank Branches
Customers
Suppliers
Mr. Sandeep M Shinde www.eTutorInfotech.com
eTutorInfotech@gmail.com 8308800428/99309754
Mr. Sandeep M Shinde www.eTutorInfotech.com
eTutorInfotech@gmail.com 8308800428/99309754
TCA-Bank and Bank Branches:
The TCA tables used by Cash Management for modeling Banks and Bank Branches are listed
below:
Three key CE tables now as:
o CE_BANK_ACCOUNTS for bank accounts
o CE_BANK_ACCT_USES_ALL for account uses by Operating Units & Legal
Entities
o CE_GL_ACCOUNTS_CCID for bank account use accounting data
TCA-Customers:
The word “Customer” is the combination of both the “Party layer” and the “Account layer”.
Party layer exists independent of any selling or buying relationship.
Customer Account layer exists in the context of a Party and only when a selling
relationship exists.
The Party Layer captures intrinsic truths about a person or organization.
The Account Layer captures the details describing the Party’s financial relationship with
the implementing organization.
The Account Layer cannot exist without the Party Layer.
TCA-Suppliers:
Following are the three new AP tables’ technical details for R12 Supplier in TCA. They have the
links to TCA tables which are listed below.
AP_SUPPLIERS
1. HZ_PARTIES
2. HZ_PERSON_PROFILES
3. HZ_PARTY_USAGE_ASSIGNMENTS
4. HZ_PARTY_RELATIONSHIPS
AP_SUPPLIER_SITES_ALL
1. HZ_LOCATIONS
2. HZ_LOCATION_PROFILE
3. HZ_PARTY_SITES
4. HZ_PARTY_SITE_USES
Mr. Sandeep M Shinde www.eTutorInfotech.com
eTutorInfotech@gmail.com 8308800428/99309754
AP_SUPPLIER_CONTACTS
1. HZ_PARTIES
2. HZ_RELATIONSHIPS
3. HZ_PARTY_SITES
4. HZ_ORG_CONTACTS
5. HZ_CONTACT_POINTS
TCA ER-Diagram: