):

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

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:

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

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

HZ_PARTIES

HZ_PERSON_PROFILES

HZ_PARTY_USAGE_ASSIGNMENTS

HZ_PARTY_RELATIONSHIPS

AP_SUPPLIER_SITES_ALL

HZ_LOCATIONS

HZ_LOCATION_PROFILE

HZ_PARTY_SITES

HZ_PARTY_SITE_USES

AP_SUPPLIER_CONTACTS

HZ_PARTIES

HZ_RELATIONSHIPS

HZ_PARTY_SITES

HZ_ORG_CONTACTS

HZ_CONTACT_POINTS
TCA ER-Diagram:

reference: www.docs.oracle.com

Introduction

Oracle Applications R12 Trading Community Architecture Tables

Background

What is TCA?

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.

The code

PARTIES:

The related tables are as follows:-

HZ_PARTIES : Stores information about parties.

HZ_FINANCIAL_PROFILE : Stores information about the financial accounts.

HZ_CREDIT_RATINGS : Stores information about the credit rating of parties

HZ_REFERENCES : Stores information about reference given by one party about another.

HZ_CERTIFICATIONS : Stores information about the certifications given by other parties.

PARTIES – TYPE PERSON:

The tables are as follows:-

HZ_PERSON_PROFILES : Stores details information about people.

HZ_PERSON_LANGUAGES :Stores information about the language that a person speaks, reads or
writes

HZ_PERSON_INTEREST : Stores information about a person’s personal interests.

HZ_ CITIZENSHIP : Stores information about a person’s claimed nationality.

HZ_EDUCATIONS : Store information about a person educations.

HZ_EMPLOYMENT_HISTORY : Stores information about where the person has been employed.

PARTIES – TYPE ORGANIZATION:

The tables are as follows:-

HZ_ORGANIZATION_PROFILES : Stores details information about credit rating, financial statistics,

socio-economic and corporate linkage information.

HZ_STOCK_MARKETS :Stores information about the selling and buying of financial instruments.

HZ_SECURITY_ISSUED : Stores information about financial instruments such as stocks and bonds that
has been issued by the organization.

HZ_INDUSTRIAL_CLASS_APP : It is a intersection tables that link industrial classifications stores in

HZ_INDUSTRIAL_CLASSES .

HZ_INDUSTRIAL_CLASSES : Stores information about names and descriptions of industrial

classifications.

HZ_FINANCIAL_REPORTS : Store information details of financial reports that describe the financial
status of the party.
HZ_INDUSTRIAL_REFERENCE : Stores information about industrial reference for organization.

CUSTOMER ACCOUNTS:

The tables are as follows:-

HZ_CUST_ACCOUNTS : Stores information about the relationship, if a party becomes a customer.

Basically stores information about customer accounts.

HZ_CUST_ACCT_SITES_ALL : Stores information about customer sites. One customer can have more
then multiple sites.

HZ_CUST_SITE_USES_ALL : Stores information about site uses or business purpose. A Single customer
site can have multiple sites uses such as Bill To or Ship To.

HZ_CUST_ACCT_RELATE_ALL : Stores information about relationships between customer accounts.

HZ_CUST_ACCOUNT_ROLES : Stores information about the roles that parties perform in customer
accounts.

HZ_BILLING_PREFERENCES : It describe the invoicing format preferred by customer accounts or

customer account sites.

HZ_CUSTOMER_PROFILES : Stores credit information for a customer account and customer account
sites.

HZ_CUST_PROFILE_AMTS : Stores profile amount limits for every currency defined for a customer
account or customer account site profile.

HZ_CUST_PROF_CLASS_AMTS :Stores customer profile class amount limits for currency.

HZ_CUST_PROFILE_CLASSES : Stores standard credit profile classes.

CONTACT POINTS:

The tables are as follows:-

HZ_CONTACT_POINTS : Stores electronic methods of communicating with entities such as parties,
party site. Each record in this table represents s different means of contacting an entity.

HZ_CUST_CONTACT_POINTS : This table is used to tie a contact point to a customer account,

customer account site or customer account role.

HZ_CONTACT_RESTRICTIONS : It stores information about restrictions on contacting parties.

SITES/LOCATIONS:

The tables are as follows:-

HZ_PARTIES_SITES : Stores information about parties and locations. Because there is a many-to-many
relationship between parties and locations.

HZ_PARTIES_SITE_USES : Stores information about the party site uses and business purposes. A party
site can have multiple site uses such as ‘bill to’ or ‘ship to’ and each site is stores as a record in this
table.

HZ_LOCATIONS : Stores information about the locations, namely, address information

HZ_LOC_ASSIGNMENTS : It ties locations stored in HZ_LOCATIONS to a LOC_ID stored in

AR_LOCATIONS_COMBINATIONS

What is TCA?

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.
Note: Customer, Vendor, Supplier are the terms that we come across very frequently.

For instance: We buy goods from a Shop Vendor so we are the Customer to that Vendor and the
Vendor is our Supplier for that good. The Vendor gets goods from a merchant who actually produces
it (Manufacturer), so now the vendor in-turn becomes a customer to the Manufacturer who is the
Supplier.

The complete TCA can be related and runs around all these terms, these may be people we meet
generally who might be a Supplier or Customer in our perspective.

Now moving ahead lets go in details about TCA.

How TCA Matters?

Before TCA:

There are multiple customer definitions across the enterprise.

It was very difficult to track current and historical information about the customers.

There was a lack of support for mixed business.

It was quite tough to understand relationships between customers and others (suppliers, partners,
competitors)

After TCA:

Create a 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.

Record complex business relationships between Trading Community entities (including 3rd party
relationships).

Support all business models, industries, and geographies.

TCA Data Model Components:

Party Represents any entity that can enter into business relationships with your organization –
Organization, Person, or Group
Party Relationship 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

Location A Street Address

Party Site Associates a party with a location, indicating that party’s usage of the location

ContactA person related to an organization, this can be a relationship between an organization and a
person as well as between two people

Contact Point Your avenue of contacting a party i.e. a phone number ,e-mail address or fax number

Customer Account Represents a customer relationship between your organization and a party

Customer Account Site A party Site that you use in relation to a customer account, i.e, a bill-to or
ship-to address

Customer Account Contacts A party contact that is used as a means of contacting the customer
regarding his/her account

TCA in 11i

11i TCA already equipped to handle the following entities

–>Customer

–>Employee

–>Student

Here is Summarize information of the tables Pre and Post 11i:

TCA in R12 Includes:

New trading entities

–>Suppliers
–>Banks & Bank Branches

–>Legal Entity

TCA Data Model : Supplier & Customer

TCA in R12: Supplier Representation

Supplier organizations are in TCA

Terms of doing business with the supplier are in Purchasing / Payables

Supplier organization, address, contact, phone, email etc. are all in TCA

Employees are already in TCA, Payables using the same employee records in TCA

TCA – Suppliers:

Technical details for R12 Supplier in TCA

TCA in R12: Supplier Data Mapping

TCA in R12: Bank Account Model

TCA in R12: Bank Model

New Bank Account Model

Central place to define internal bank accounts

–>Keep track of all bank accounts in one place

–>Explicitly grant account access to multiple operating units/functions and users

Multi-Org Access

–>In the new model, bank accounts are owned by Legal Entities with the option to grant account use
to Operating Unit (Payables, Receivables), Legal Entity (Treasury), Business Group (Payroll) .

R12 Multi-org access control

MOAC is new enhancement to Multiple Organization feature of Oracle Application

Enables Users to access the data from one or many Operating Units within a set of given
responsibility

Data Security is maintained using Multiple Organization Security Profile, Define in Oracle HRMS.

Three key CE tables now as

1. CE_BANK_ACCOUNTS

–>Stores bank account attributes

2. CE_BANK_ACCT_USES_ALL

–>Stores the bank account use attributes specific to Operating Unit (AR, AP) and Legal Entity
(Treasury).

3.CE_GL_ACCOUNTS_CCID

–>Accounting data pertaining to the bank account use

All of the bank, branch and bank account related attributes in AP_BANK_BRANCHES and
AP_BANK_ACCOUNTS_ALL tables will be upgraded to HZ_PARTIES and the new tables in Cash
Management.

The Changing model for Bank in Global working model

–> Release 12, what’s New:

TCA Bank Model in 11i and R12:

TCA in R12: Legal Entities

Legal entity is created as a party of party type ORGANIZATION or PERSON

An establishment is created as a party of party type ORGANIZATION.

TCA creates a new classification category called “Business Function”. It is used mainly to model what
business functions a party can perform in E-Business Suite

For modeling legal entities and establishments in TCA, classification code “Legal Entity” and
“Establishment” are created under the “Business Function” class category.

An establishment is created as a party and always link to a party that is classified as a legal entity
through the relationship model

TCA & Enhancement:

The Trading Community Manager Responsibility, allows users to create a setup or update data
sharing and security

Customer Standard form that has been existing till R11i is finally gone.

Oracle Introduced a brand new HTML UI built using OA Frame works leveraging TCA that can be used
to manage Customers, Accounts, etc.

TCA API’s List:

About these ads

Share this:

TwitterFacebook

Loading...

Like

One blogger likes this.

Related
Functional Approach for creating a Supplier in R12

In "Oracle Apps Technical and Functional Concepts by Suryakanth Gunti"

Existence of ERP and Oracle Application as a Vendor.

In "Oracle Apps Technical and Functional Concepts by Suryakanth Gunti"

O2C Cycle – (Order To Cash Cycle)

In "Oracle Apps Technical and Functional Concepts by Suryakanth Gunti"

June 1, 2012 15 Replies

« Previous

Next »

Leave a Reply

Your email address will not be published. Required fields are marked *

Name

Email

Website

Comment

Notify me of new comments via email.

Sloba on June 1, 2012 at 12:40 pm

Nice work … will look forward for more post on Oracle ERP … keep it up

Reply

Soumya on June 2, 2012 at 4:36 pm

Excellent work. Its really helpful. We’ll look forward for few more.

Reply

Suman on June 3, 2012 at 3:29 pm

Great work Surya.

Good initiative..keep it up.

Regarding the article, it is very informative, specially for beginners.

Looking forward for more aticles on different topics.

Reply

RaviKishore on June 3, 2012 at 3:38 pm

Hi its a nice work done and keep up the good work.Its a noble thought and great work to share the
Knowledge with the like minded people and the community.I am sure it will help you develop your
own skills and help others to learn from your experience.Its just a beginning and looking forward for
a similar contribution from you…Sharing always helps two people you and the person who is willing
to learn from the blogs…All the Best!

Reply

Mayur on June 4, 2012 at 9:58 am

Great Research Gunti….

Reply

Jawed Ansari on June 19, 2012 at 3:15 pm

Great note. You are a rich guy with highly useful information. Good presentation.

Thanks

Reply

Siddhi on December 11, 2012 at 5:51 am

Very nice and helpful doc…great work…

Reply
Gangareddy on January 4, 2013 at 4:58 am

Good Stuff.. Thanks lot

Reply

Joseph on March 7, 2013 at 4:14 pm

Hi Surya,

Nice document. Was really helpfull.. Keep going..

Reply

swati on April 28, 2013 at 7:49 am

Excellent info.

Reply

Read More on June 10, 2013 at 10:26 am

Neat page, Continue the excellent job. Thanks

for your time.

Reply

Amit Khunt on July 24, 2013 at 3:31 pm

Great Work..Keep It up!!!

Reply

Shantanu on September 16, 2013 at 8:42 pm

Thanks a tonne Surya…..very helpful article…..

Reply

Shravan Reddy on September 29, 2013 at 2:40 pm

Its Really Helpful for a new comer like me who is new to TCA

Reply
Roja on November 13, 2013 at 3:26 am

Good information.really helpful..Thank you

Reply

Recent Posts

Understanding the Process of DATA LOADER Tool

Revenue Recognition Process and Flow Functionality

Script To Add a List of Responsibility to Once User

Enhancements and New Features in Oracle 12c Summarized

Enhancement in 11g Database

Archives

February 2015

January 2015

March 2014

February 2014

January 2014

July 2013

April 2013

February 2013

December 2012

November 2012

August 2012

July 2012

June 2012

May 2012

April 2012
Categories

Advance Supply Chain Management

Oracle Apps Technical and Functional Concepts by Suryakanth Gunti

Oracle Apps Technical Query's by Suryakanth Gunti

Oracle Tips

R12 General Ledger Functional Concepts for Oracle Apps

R12 Inventory Management

R12 Procure to Pay Cycle

Unix Shell basic Commands

Meta

Register

Log in

Entries RSS

Comments RSS

WordPress.com

Follow Blog via Email

Enter your email address to follow this blog and receive notifications of new posts by email.

Join 334 other followers

View Full Site

Create a free website or blog at WordPress.com.

Now Available! Download WordPress for Android

Skip to primary content

Home

About Author

Stats: 14.1kB, 2.25s