R12 Trading Community Architecture

Oracle Trading Community Architecture (TCA) is a data model that allows you to manage complex information about the parties, or customers. Trading Community Architecture is the implementation of technology and applications to allow users to create and maintain relationships among entities. It is a way to understand who your customer interacts with inside and outside the enterprise. Central repository for the entire E-Business Suite to store information relating to all members of a trading community versus separate tables for each member-Prospects, Customers, Contacts, Employees, Partners, Distributors, Suppliers, Banks, etc. Following are the selected three entities involved in the R12 Trading Community Architecture:

    • Bank and Branch
    • Customers
    • Suppliers

Banks and Bank Branches:   The TCA party model is being used to model banks and bank branches as parties with the associated attributes of Relationships, Address, Contact and Locations. The TCA tables used by Cash Management for modeling Banks and Bank Branches are listed below:

Three key CE tables now as:

    • CE_BANK_ACCOUNTS for bank accounts
    • CE_BANK_ACCT_USES_ALL for account uses by Operating Units & Legal Entities
    • CE_GL_ACCOUNTS_CCID for bank account use accounting data

Entity Relationship Diagram:



The Concept of Customer is separated in two layers, Party Layer and Account Layer. 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.

Entity Relationship Diagram:


Three new AP tables containing supplier unique data have been introduced. They have the links to TCA tables:


And more important we understood three old PO Vendors tables obsolete, by Views provided for backward compatibility.

Entity Relationship Diagram:

TCA Table Description:

HZ_PARTIES Represents any entity that can enter into business relationships with your organization – Organization, Person, or Group.
HZ_PARTY_SITES Associates a party with a location, indicating that party’s usage of the location
HZ_PARTY_SITE_USES The HZ_PARTY_SITE_USES table stores information about how a party site is used. Party sites can have multiple uses, for example Ship-To and Bill-To.
HZ_LOCATIONS The HZ_PARTY_SITES table links a party (see HZ_PARTIES) and a location (see HZ_LOCATIONS) and stores location-specific party information such as MAILSTOP and ADDRESSEE.
HZ_ORG_CONTACTS The HZ_ORG_CONTACTS table stores information about the position of the contact for a party or party site.
HZ_PARTY_RELATIONSHIPS A binary relationship between two parties such as a partnership. Example: Adam is a specific person party and Eve Inc. is an organization party. Adam at Eve Inc. is also treated as a party with the type relationship
HZ_CUST_ACCOUNTS The HZ_CUST_ACCOUNTS table stores information about customer accounts, or business relationships that the deploying company establishes with a party of type Organization or Person.
HZ_CUST_ACCT_SITES_ALL The HZ_CUST_ACCT_SITES_ALL table stores all customer account sites across all operating units.
HZ_CUST_ SITE_USES_ALL The HZ_CUST_SITE_USES_ALL table stores business purposes assigned to customer account sites, for example Bill-To, Ship-To, and Statements.
HZ_CUSTOMER_PROFILES The HZ_CUSTOMER_PROFILES table stores information about the credit characteristics of a single customer account or a customer account site or a party.
HZ_CUST_PROFILE_AMTS The HZ_CUST_PROFILE_AMTS table stores information about the credit limits specified for a customer profile in different currencies.
HZ_PERSON_PROFILES The HZ_PERSON_PROFILES table stores personal and family information about a party of the Person type.
HZ_ORGANIZATION_PROFILES The HZ_ORGANIZATION_PROFILES table gets populated when a party of the Organization type is created.
HZ_CUST_ACCT_RELATE_ALL The HZ_CUST_ACCT_RELATE_ALL table stores information about relationships between customer accounts.
HZ_CUST_ACCOUNT_ROLES The HZ_CUST_ACCOUNT_ROLES table stores information about a role or function that a party performs in relation to a customer account.
HZ_CONTACT_POINTS The HZ_CONTACT_POINTS table stores information about how to communicate to parties or party sites using electronic media or methods such as Electronic Data Interchange (EDI), e-mail, telephone, telex, and the Internet.

About pushpal

Oracle Apps Technical Developer
This entry was posted in Oracle Applications Functional, Oracle Applications Technical. Bookmark the permalink.

5 Responses to R12 Trading Community Architecture

  1. Amol says:

    A very informative blog Pushpal… Keep it up 🙂

  2. ashish gupta says:

    excellent write up. Good work.

  3. Amit Khunt says:

    Well Done!! Keep it up!!

  4. NEERAJ says:

    Brilliant Article on TCA! Thanks a million for sharing 🙂

  5. Mike Reid says:

    Pushpal, great post, thank you, very useful!

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s