TCA

Trading Community Architecture

The Trading Community Architecture holds information related to all trading partners with an organization, these are , Customers, Suppliers and Banks.

 Parties and Customers

In Oracle e-Business terminology a party is a person or organization that does not have customer account  called party, when a party posses customer account, that means it is eligible to to business with organization, is called customer. It is like, a person who is have account number in a bank able to do transaction called customer, without having an account number a person is merely a party to bank.

Customers are important entity or person who buy goods or services from an organization or business. In order to do business with customers, it is important to store their information in organization's system. The main entities of customers are Customer Account, Customer Account Sites, Customer Site Uses.

Below are the base tables relate to parties

HZ_PARTIES

HZ_PARTY_SITES

HZ_PARTY_SITE_USES

HZ_LOCATIONS

HZ_CONTACT_POINTS

HZ_RELATIONSHIPS

Creating a party and party sites is very straight forward which stores information into HZ_PARTIES,
HZ_PARTY_SITES, and HZ_PARTY_SITE_USES tables. But the contact points of customer( EMAIL/PHONE/URL) i
n TCA Architecture can be attached to different levels.
Party Directly
Party Relationship
Party Address(Site Level)

1.Party Directly:

When creating party, a record gets created in HZ_PARTIES, when creating contact to the party, the contact point created in HZ_CONTACT_POINTS, the OWNER_TABLE_ID in HZ_CONTACT_POINTS is PARTY_ID of HZ_PARTIES. The OWNER_TABLE_NAME is ‘HZ_PARTIES’.

2. Party Relationship

When creating a party the record gets created in HZ_PARTIES table.

Eg: NOMS HEALTHCARE

When creating a party contact  it create two records in HZ_PARTIES,

              Contact Person → 419-626-6161 SHELLY LINDENCAMP

              Relation between contact and party. → 419-626-6161 SHELLY LINDENCAMP-NOMS HEALTHCARE-701080.

Note: There are three parties created in HZ_PARTIES table.

It establishes relationship among these three parties in  HZ_RELATIONSHIPS table. In HZ_RELATIONSHIPS,

SUBJECT_ID → 419-626-6161 SHELLY LINDENCAMP

           PARTY_ID → 419-626-6161 SHELLY LINDENCAMP-NOMS HEALTHCARE-701080

           OBJECT_ID → NOMS HEALTHCARE

And, with PARTY_ID of HZ_RELATIONSHIPS is the OWNER_TABLE_ID in  HZ_CONTACT_POINTS which holds contact information of the party. The OWNER_TABLE_NAME is ‘HZ_PARTIES’.

3.Site Level

When creating contact point at site level, the OWNER_TABLE_ID of HZ_CONTACT_POINTS is PARTY_SITE_ID  of HZ_PARTY_SITES, and OWER_TABLE_NAME is ‘HZ_PARTY_SITES’.

Once party got customer account number and eligible to transact with organization, important information will be available under below tables.

HZ_PARTIES HZ_CUST_ACCOUNTS_ALL   ( PARTY_ID )

HZ_PARTY_SITES HZ_CUST_ACCT_SITES_ALL ( PARTY_SITE_ID,LOCATION_ID)

HZ_PARTY_SITE_USES HZ_CUST_SITE_USES_ALL

HZ_LOCATIONS

HZ_CONTACT_POINTS

HZ_RELATIONSHIPS

In order to create customers in Oracle e Business applications, either we can use APIs or Open Interfaces.

Below are the APIs used to create customer information in oracle e-Business Applications.

HZ_CUST_ACCOUNT_V2PUB.CREATE_CUST_ACCOUNT
HZ_LOCATION_V2PUB.CREATE_LOCATION
HZ_PARTY_SITE_V2PUB.CREATE_PARTY_SITE
HZ_CUST_ACCOUNT_SITE_V2PUB.CREATE_CUST_ACCT_SITE
HZ_CUST_ACCOUNT_SITE_V2PUB.CREATE_CUST_SITE_USE
HZ_CUSTOMER_PROFILE_V2PUB.CREATE_CUSTOMER_PROFILE
HZ_CUSTOMER_PROFILE_V2PUB.CREATE_CUST_PROFILE_AMT
HZ_CONTACT_POINT_V2PUB.CREATE_EMAIL_CONTACT_POINT
HZ_CONTACT_POINT_V2PUB.CREATE_PHONE_CONTACT_POINT
HZ_CONTACT_POINT_V2PUB.CREATE_EMAIL_CONTACT_POINT
HZ_PARTY_V2PUB.CREATE_PERSON
HZ_PARTY_CONTACT_V2PUB.CREATE_ORG_CONTACT
HZ_CUST_ACCOUNT_ROLE_V2PUB.CREATE_CUST_ACCOUNT_ROLE
HZ_CUST_ACCOUNT_ROLE_V2PUB.CREATE_ROLE_RESPONSIBILITY