Trade Community Architecture TCA

Below give you the list of Trading Community Architecture API’s with the links to their test script. All the test scripts are tested in R12.1.1 Version.

SI NO	Tested API's List
1	HZ_CUST_ACCOUNT_V2PUB.CREATE_CUST_ACCOUNT
2	HZ_CUSTOMER_PROFILE_V2PUB.CREATE_CUSTOMER_PROFILE
3	HZ_CUST_ACCOUNT_SITE_V2PUB.CREATE_CUST_ACCT_SITE
4	HZ_CUST_ACCOUNT_SITE_V2PUB.CREATE_CUST_SITE_USE
5	HZ_PARTY_SITE_V2PUB.CREATE_PARTY_SITE
6	HZ_PARTY_SITE_V2PUB.CREATE_PARTY_SITE_USE)
7	HZ_CONTACT_POINT_V2PUB.CREATE_CONTACT_POINT
8	HZ_LOCATION_V2PUB.UPDATE_LOCATION
9	HZ_CUST_ACCOUNT_V2PUB.UPDATE_CUST_ACCOUNT
10	HZ_PARTY_V2PUB.CREATE_GROUP
11	HZ_CUST_ACCOUNT_V2PUB.CREATE_CUST_ACCOUNT
12	HZ_CUST_ACCOUNT_V2PUB.CREATE_CUST_ACCOUNT
13	HZ_LOCATION_V2PUB.CREATE_LOCATION
14	HZ_TAX_ASSIGNMENT_V2PUB. CREATE_LOC_ASSIGNMENT
15	HZ_CUST_ACCOUNT_V2PUB.UPDATE_CUST_ACCT_RELATE
16	HZ_CUSTOMER_PROFILE_V2PUB.UPDATE_CUSTOMER_PROFILE
17	HZ_PARTY_V2PUB.CREATE_ORGANIZATION
18	HZ_CUST_ACCOUNT_V2PUB.CREATE_CUST_ACCT_RELATE
19	HZ_PARTY_CONTACT_V2PUB.CREATE_ORG_CONTACT

Test Scripts:

NO	TRADING COMMUNITY ARCHITECTURE API’s Test Scripts
1	API to Create a Customer Account for an existing Party TCA R12 (HZ_CUST_ACCOUNT_V2PUB.CREATE_CUST_ACCOUNT)
2	API to Create a Customer Profile TCA R12
3	API to Create a Customer Site TCA R12 (HZ_CUST_ACCOUNT_SITE_V2PUB.CREATE_CUST_ACCT_SITE)
4	API to Create a Customer Site Use TCA R12 (HZ_CUST_ACCOUNT_SITE_V2PUB.CREATE_CUST_SITE_USE)
5	API to Create a Party Site TCA R12 (HZ_PARTY_SITE_V2PUB.CREATE_PARTY_SITE)
6	API to Create a Party Site Use TCA R12 (HZ_PARTY_SITE_V2PUB.CREATE_PARTY_SITE_USE)
7	API to Create a Phone Number (Contacts) TCA R12 (HZ_CONTACT_POINT_V2PUB.CREATE_CONTACT_POINT)
8	API to Update Customer Address in Oracle TCA R12 (HZ_LOCATION_V2PUB.UPDATE_LOCATION)
9	API to Update a Customer Account TCA R12 (HZ_CUST_ACCOUNT_V2PUB.UPDATE_CUST_ACCOUNT)
10	API to create Group in TCA R12 (HZ_PARTY_V2PUB.CREATE_GROUP)
11	API to create Party and Customer Account in R12 (HZ_CUST_ACCOUNT_V2PUB.CREATE_CUST_ACCOUNT)
12	API to create a Person Type Party and Customer Account TCA R12 (HZ_CUST_ACCOUNT_V2PUB.CREATE_CUST_ACCOUNT)
13	API to create customer Addresses in TCA R12 (HZ_LOCATION_V2PUB.CREATE_LOCATION)
14	API to populate loc_id HZ_LOCATIONS R12 (HZ_TAX_ASSIGNMENT_V2PUB. CREATE_LOC_ASSIGNMENT )
15	API to update a Customer Account Relationship TCA R12 (HZ_CUST_ACCOUNT_V2PUB.UPDATE_CUST_ACCT_RELATE)
16	API to update a Customer Profile TCA R12 (HZ_CUSTOMER_PROFILE_V2PUB.UPDATE_CUSTOMER_PROFILE)
17	Create Party of type Organization in Oracle TCA using API hz_party_v2pub.create_organization
18	Create a Customer Account Relationship API HZ_CUST_ACCOUNT_V2PUB.CREATE_CUST_ACCT_RELATE
19	hz_party_contact_v2pub.create_org_contact - API to create a Contact person for an organization in Oracle TCA

In this post, I have tried to explain the architecture of TCA in oracle apps using graphical representations and welcoming your comments.

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 of parties credit rating

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

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

LOGICAL MODEL DIAGRAM

PARTIES – TYPE PERSON

       are as follows:-The tables

§  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.

LOGICAL MODEL DIAGRAM

 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 that has been issued by the organization. stocks and bonds

§  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 of the party. financial status

§  HZ_INDUSTRIAL_REFERENCE : Stores information about industrial reference for organization.

LOGICAL MODEL DIAGRAM

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.

LOGICAL MODEL DIAGRAM

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.

LOGICAL MODEL DIAGRAM

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

LOGICAL MODEL DIAGRAM