Purpose
The purpose of this article is to explain Customer Account Creation Flow and Data Model with the help of Trading Community Architecture (TCA) API scripts to create the data, and view the result using database queries, application navigation and screens.
Scope
This article will cover:
•Categories of Customer Entities
•TCA API Coding Steps
•Example of Customer Account Creation using TCA APIs
•TCA API Coding Steps
•Example of Customer Account Creation using TCA APIs
Details
CUSTOMER ENTITIES
Party Layer APIs
Customer Entities can be grouped under two main categories – Party layer and Account layer entities. These are the main entities that are used for Receivables Customer information. A party entity must exist before the Account entity can be created. They can be created using the Party APIs given here.
However, some party entities can also be created together with the Account, using the Account APIs.
Party Layer APIs
Customer Entities can be grouped under two main categories – Party layer and Account layer entities. These are the main entities that are used for Receivables Customer information. A party entity must exist before the Account entity can be created. They can be created using the Party APIs given here.
However, some party entities can also be created together with the Account, using the Account APIs.
Entity
|
API
|
Tables
|
Party – Organization
|
HZ_PARTY_V2PUB.create_organization
|
HZ_PARTIES
HZ_ORGANIZATION_PROFILES |
Party - Person
|
HZ_PARTY_V2PUB.create_person
|
HZ_PARTIES
HZ_PERSON_PROFILES |
Location
|
HZ_LOCATION_V2PUB.create_location
|
HZ_LOCATIONS
HZ_LOCATIONS_PROFILES |
Party Site
|
HZ_PARTY_SITE_V2PUB.create_party_site
|
HZ_PARTY_SITES
|
Party Site Use
|
HZ_PARTY_SITE_V2PUB.create_party_site_use
|
HZ_PARTY_SITE_USES
|
Party Contact (Organization Contact)
|
HZ_PARTY_CONTACT_V2PUB.create_org_contact
|
HZ_ORG_CONTACTS
HZ_RELATIONSHIPS (Subject: Contact person Object: Organization/Person) HZ_PARTIES (party_type=PARTY_RELATIONSHIP) |
Contact Role
|
HZ_PARTY_CONTACT_V2PUB.create_org_contact_role
|
HZ_ORG_CONTACT_ROLES
|
Contact Point
|
HZ_CONTACT_POINT_V2PUB.create_contact_point
HZ_CONTACT_POINT_V2PUB.create_phone_contact_point HZ_CONTACT_POINT_V2PUB.create_email_contact_point HZ_CONTACT_POINT_V2PUB.create_web_contact_point HZ_CONTACT_POINT_V2PUB.create_telex_contact_point HZ_CONTACT_POINT_V2PUB.create_edi_contact_point HZ_CONTACT_POINT_V2PUB.create_eft_ contact_point |
HZ_CONTACT_POINTS
Owner_table_name=HZ_PARTIES and owner_table_id=party_id Or Owner_table_name=HZ_PARTY_SITES and owner_table_id=party_site_id |
Entity
|
API
|
Tables
|
Customer Account
|
HZ_CUST_ACCOUNT_V2PUB.create_cust_account
|
HZ_CUST_ACCOUNTS
HZ_PARTIES HZ_CUSTOMER_PROFILES HZ_CUST_PROFILE_AMTS |
Account Site
|
HZ_CUST_ACCOUNT_SITE_V2PUB.create_cust_acct_site
|
HZ_CUST_ACCT_SITES_ALL
|
Account Site Use
|
HZ_CUST_ACCOUNT_SITE_V2PUB.create_cust_site_use
|
HZ_CUST_SITE_USES_ALL
HZ_CUSTOMER_PROFILES HZ_CUST_PROFILE_AMTS |
Account
Relationship
|
HZ_CUST_ACCOUNT_V2PUB.
create_cust_acct_relate
|
HZ_CUST_ACCT_RELATE_ALL
|
Account / Account
Site Use Profile
|
HZ_CUSTOMER_PROFILE_V2PUB.create_customer_profile
|
HZ_CUSTOMER_PROFILESHZ_CUST_PROFILE_AMTS
|
Account / Account
Site Use Profile Amount
|
HZ_CUSTOMER_PROFILE_V2PUB.create_cust_profile_amt
|
HZ_CUST_PROFILE_AMTS
|
Account / Account
Site Role (Contact)
|
HZ_CUST_ACCOUNT_ROLE_V2PUB.create_cust_account_role
|
HZ_CUST_ACCOUNT_ROLES
|
Account / Account
Site Role Responsibility
|
HZ_CUST_ACCOUNT_ROLE_V2PUB.create_role_responsibility
|
HZ_ROLE_RESPONSIBILITY
|
No comments:
Post a Comment