Escolar Documentos
Profissional Documentos
Cultura Documentos
---------------------http://www.club-oracle.com/articles/oracle-apps-tca-tables-809/
---------------------------------------------------------------http://appstechnotes.wordpress.com/2...-architecture/
http://prasanthapps.blogspot.com/201...acle-apps.html
---------------------------------------------------------------by Sri Ganesh Published on 04-19-2013 03:34 AM
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 m
anage complex information about the parties, or customers.
Trading Community Architecture is the implementation of technology and applicati
ons 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 enterp
rise.
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 anot
her.
HZ_CERTIFICATIONS : Stores information about the certifications given by other p
arties.
PARTIES
TYPE PERSON:
TYPE ORGANIZATION:
The tables are as follows:HZ_ORGANIZATION_PROFILES : Stores details information about credit rating, finan
cial statistics, socio-economic and corporate linkage information.
HZ_STOCK_MARKETS :Stores information about the selling and buying of financial i
nstruments.
HZ_SECURITY_ISSUED : Stores information about financial instruments such as stoc
ks and bonds that has been issued by the 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 c
an 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 custome
r 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 cust
omer account sites.
HZ_CUST_PROFILE_AMTS : Stores profile amount limits for every currency defined f
or a customer account or customer account site profile.
HZ_CUST_PROF_CLASS_AMTS :Stores customer profile class amount limits for currenc
y.
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 suc
h 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
ach site is stores as a record in this table.
HZ_LOCATIONS : Stores information about the locations, namely, address informati
on
HZ_LOC_ASSIGNMENTS : It ties locations stored in HZ_LOCATIONS to a LOC_ID stored
and e
in AR_LOCATIONS_COMBINATIONS
- 7069
- 7072
072)
IN(7069,7