- 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.
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: Geospatial points, usually defined by
an address
Contacts: People who have a contract or employment relationship with an
organization or person
Contact Points: Means of contact, for example,
phone and e-mail address
TCA-Bank and Bank Branches:
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 – Suppliers:
Ap_suppliers
- Hz _parties
- Hz_person_profiles
- Hz_party_relationships
- Hz_locations
- Hz_location_profile
- Hz_party_sites
- Hz_party_site_uses
- Hz _parties
- Hz_relationships
- Hz_party_sites
- Hz_org_contacts
- Hz_contact_points
PARTIES:
The related tables are as follows:
Hz _parties: stores
information about parties. (Party number, party name, address)
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 references given by
one party to another.
PARTIES – TYPE PERSON:
HZ_PERSON_PROFILES: Stores details information about people.
HZ_EMPLOYMENT_HISTORY: Stores information
about where the person has been employed.
PARTIES
– TYPE ORGANIZATION:
HZ_ORGANIZATION_PROFILES:
Stores details information about credit rating, financial statistics, and socio-economic and corporate linkage information. (organization_profile_id,
party_id, organization_name)
HZ_STOCK_MARKETS: Stores
information about the selling and buying of financial instruments.
CUSTOMER
ACCOUNTS:
HZ_CUST_ACCOUNTS: Stores
information about the relationship, if a party becomes a customer. Basically
stores information about customer accounts. (cust_account_id, party_id,
account_number)
HZ_CUST_ACCT_SITES_ALL:
Stores information about customer sites. One customer can have more than
multiple sites.
HZ_CUST_SITE_USES_ALL: Stores information about site uses
or business purposes. A single customer site can have multiple site 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_CUSTOMER_PROFILES:
Stores credit information for a customer account and customer account sites.
CONTACT POINTS:
HZ_CONTACT_POINTS: Stores electronic methods of communicating with
entities such as parties, and party sites. 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 contracting parties.
SITES/LOCATIONS:
HZ_PARTY_SITES:
Stores information about parties and locations.
Hz_locations: stores information about the locations, namely, address
information.
Important tables:
HZ_PARTIES
HZ_CUST_ACCOUNTS
HZ_CUST_SITE_USE_ALL
HZ_PARTY_SITES
HZ_LOCATIONS
HZ_PARTY_SITE_USES
HZ_CUSTOMER_PROFILES
HZ_ORGANIZATION_PROFILE
HZ_PERSON_PROFILES
No comments:
Post a Comment