Search Results create_cust_acct_relate

Overview

APPS.HZ_CUST_ACCOUNT_V2PUB is the public application programming interface for the Oracle Trading Community Architecture (TCA) customer account entity. It is the interface through which Oracle E-Business Suite applications and external integrations create, maintain, and query customer account records and the relationships that link those accounts to one another.

The package is classified as a public (PUB) API and is owned by the APPS schema. Its header identifies it as containing "the public APIs for customer accounts and related entities," and ETRM associates it with the business entities HZ_CUSTOMER_ACCOUNT, HZ_ORGANIZATION, and HZ_PERSON. The package is documented in the Customer Account APIs chapter of the Oracle Trading Community Architecture Technical Implementation Guide (120hztig.pdf), and its lifecycle status is active.

Functionally, the package abstracts the underlying TCA data model for customer accounts. A customer account represents the commercial relationship between a party (a person or organization) and the operating unit that sells to it. Because the TCA model spreads this information across account, profile, and relationship tables, HZ_CUST_ACCOUNT_V2PUB provides a single, supported entry point that enforces the validation, defaulting, and multi-table consistency rules required to keep that model sound.

Key Procedures and Functions

ETRM documents nine callable units within HZ_CUST_ACCOUNT_V2PUB. Six are exposed to callers:

• CREATE_CUST_ACCOUNT — Creates a new customer account record. This is the procedure most often sought by developers searching for "create_cust_account." It accepts a typed record of account attributes and returns the generated identifier for the new account.
• UPDATE_CUST_ACCOUNT — Modifies an existing customer account. The caller supplies the account identifier along with the record of attributes to be changed.
• GET_CUST_ACCOUNT_REC — Retrieves a single customer account into the package's record structure, allowing a caller to read the current state of an account for display, comparison, or downstream processing.
• CREATE_CUST_ACCT_RELATE — Creates a relationship between two customer accounts, such as a parent-child or bill-to/ship-to association.
• UPDATE_CUST_ACCT_RELATE — Modifies an existing account-to-account relationship.
• GET_CUST_ACCT_RELATE_REC — Retrieves a single account relationship into a record structure.

The package also declares the cust_account_rec_type record, which carries the account number, the descriptive flexfield columns (attribute_category and attribute1 through attribute20), the global descriptive flexfield columns (global_attribute_category and global_attribute1 onward), and other account attributes between the caller and the API. The remaining documented units are supporting declarations within the specification. Parameter lists are intentionally not reproduced here; callers should consult the package specification and the TCA Technical Implementation Guide for the precise signatures of the current release.

Tables Accessed

The package reads and writes the core TCA customer account tables through APPS synonyms:

• HZ_CUST_ACCOUNTS — The primary account record, holding the account number, account name, party reference, and account-level attributes.
• HZ_CUSTOMER_PROFILES — The site-level profile that stores bill-to, ship-to, and statement-to settings associated with an account.
• HZ_CUST_ACCT_RELATE and HZ_CUST_ACCT_RELATE_ALL — The relationship tables that connect one customer account to another, including the intersection table used for multi-organization access.
• HZ_PARTIES — The master party record to which every customer account is anchored; the account cannot exist without a party.
• HZ_ORIG_SYS_REFERENCES — The cross-reference table that maps a TCA entity to its identifier in an external or legacy source system.

Usage Notes

HZ_CUST_ACCOUNT_V2PUB is invoked whenever an application must create or maintain customer accounts in a supported manner. In EBS, the Oracle Receivables customer forms and the TCA customer maintenance forms call the same underlying logic, and concurrent programs that import or migrate customers rely on it as well.

The package is referenced by twenty-seven other packages in the APPS schema, and custom integrations should call it rather than performing direct inserts or updates against HZ_CUST_ACCOUNTS. Direct DML bypasses the validations, flexfield handling, party linkage, and original-system reference maintenance that the API performs, and produces records that may be rejected or misread by later releases. Typical custom usage is from PL/SQL, for example a wrapper that calls CREATE_CUST_ACCOUNT with a populated cust_account_rec_type, captures the returned account identifier, and then calls CREATE_CUST_ACCT_RELATE to establish the required account hierarchy.