Search Results hz_cust_accounts_u2

Overview

AR.HZ_CUST_ACCOUNTS is the master customer account table within the Oracle E-Business Suite Trading Community Architecture (TCA) model. It stores the business relationships the deploying company establishes with a party of type Organization or Person, and it defines how transactions are conducted within that relationship. Because a single party may maintain multiple customer accounts — for example, an individual holding a personal, family, and professional account — the table can hold several records per PARTY_ID. The table resides in the APPS_TS_TX_DATA tablespace with a PCT Free of 10 and is owned by the AR schema.

Within a Data Vault modeling heuristic, HZ_CUST_ACCOUNTS functions as a hub. Its primary key, CUST_ACCOUNT_ID, is a surrogate identifier that anchors a stable business concept (the customer account), while descriptive and relationship attributes are distributed across satellite and link structures elsewhere in the model. This classification reflects the table's position as the central reference point from which transactions, sites, profiles, and contacts emanate.

Key Information Stored

The table comprises 139 documented columns. The surrogate primary key is CUST_ACCOUNT_ID (NUMBER(15)), enforced through the HZ_CUST_ACCOUNTS_PK constraint and mirrored by the unique index HZ_CUST_ACCOUNTS_U1. Two additional unique indexes represent business-key candidates: HZ_CUST_ACCOUNTS_U2 on ACCOUNT_NUMBER, which is the user-facing account identifier, and HZ_CUST_ACCOUNTS_U3 on ORIG_SYSTEM_REFERENCE, which preserves the source-system identifier for imported or legacy accounts. The latter index is directly relevant to searches such as "hz_cust_accounts_u2," which resolve to the ACCOUNT_NUMBER uniqueness constraint.

Among the most significant columns are:

• CUST_ACCOUNT_ID — surrogate primary key and the join target for the vast majority of dependent tables.
• PARTY_ID — foreign key to HZ_PARTIES; identifies the underlying party (Organization or Person) behind the account.
• ACCOUNT_NUMBER — the business-facing account number, uniquely indexed, and often the value users search and reconcile against.
• ACCOUNT_NAME — descriptive account name, indexed by HZ_CUST_ACCOUNTS_N3 and, for case-insensitive lookup, by the function-based index HZ_CUST_ACCOUNTS_N4 on UPPER("ACCOUNT_NAME").
• SELLING_PARTY_ID — foreign key to HZ_PARTIES denoting the selling party; indexed non-uniquely by HZ_CUST_ACCOUNTS_N5.
• CUSTOMER_TYPE and CUSTOMER_CLASS_CODE — classify the account for reporting, credit, and processing rules.
• PAYMENT_TERM_ID — foreign key to PN_PAYMENT_TERMS_ALL, establishing default payment terms.
• ORDER_TYPE_ID — foreign key to SO_ORDER_TYPES_115_ALL, governing default order processing.
• PRICE_LIST_ID and TAX_CODE — define pricing and tax treatment defaults.
• STATUS and ACCT_LIFE_CYCLE_STATUS — control whether the account is active and where it resides in its lifecycle.
• CURRENT_BALANCE and CREDIT_CLASSIFICATION_CODE — support credit exposure and collections analysis.
• ORIG_SYSTEM_REFERENCE — the source-system key underpinning the U3 unique index.
• ORG_ID — the multi-org operating unit identifier, essential for data segregation in multi-org deployments.
• CREATED_BY_MODULE, APPLICATION_ID, and OBJECT_VERSION_NUMBER — support API-driven creation, module attribution, and optimistic locking.
• Standard WHO columns — LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN.

Common Use Cases and Queries

HZ_CUST_ACCOUNTS is queried in virtually every receivables, order management, collections, and credit workflow. Typical patterns include resolving an account number to its identifier, retrieving the party behind an account, and listing all accounts for a given party.

• Lookup by account number: SELECT cust_account_id, party_id, account_name FROM hz_cust_accounts WHERE account_number = :acct;
• Enumerate a party's accounts: SELECT cust_account_id, account_number, status FROM hz_cust_accounts WHERE party_id = :party;
• Case-insensitive name search leveraging the function-based index: SELECT cust_account_id FROM hz_cust_accounts WHERE UPPER(account_name) LIKE UPPER(:name || '%');
• Credit and balance reporting: aggregating CURRENT_BALANCE by ORG_ID, CUSTOMER_CLASS_CODE, or credit classification.
• Migration and reconciliation: matching imported records through ORIG_SYSTEM_REFERENCE, the column behind HZ_CUST_ACCOUNTS_U3.

Related Objects

The table is a hub with an exceptionally broad dependency footprint. The most significant related objects include:

• HZ_PARTIES — joined via PARTY_ID and SELLING_PARTY_ID; the party master that the account relationship is built upon.
• HZ_CUST_ACCT_SITES_ALL — joined via CUST_ACCOUNT_ID; holds the account's sites and addresses.
• HZ_CUSTOMER_PROFILES — joined via CUST_ACCOUNT_ID; stores profile-class definitions governing transactions.
• HZ_CUST_ACCOUNT_ROLES — joined via CUST_ACCOUNT_ID; contacts and their roles on the account.
• HZ_CUST_ACCT_RELATE_ALL — joined via CUST_ACCOUNT_ID and RELATED_CUST_ACCOUNT_ID; captures account-to-account relationships.
• RA_CUSTOMER_TRX_ALL — references BILL_TO_CUSTOMER_ID, SHIP_TO_CUSTOMER_ID, PAYING_CUSTOMER_ID, and SOLD_TO_CUSTOMER_ID; the transaction backbone.
• OE_ORDER_HEADERS_ALL — references END_CUSTOMER_ID; order entry linkage.
• AR_PAYMENT_SCHEDULES_ALL — references CUSTOMER_ID; receivables scheduling and aging.
• IBY_EXTERNAL_PAYERS_ALL and PN_PAYMENT_TERMS_ALL — payments and payment terms dependencies.
• HZ_CUST_ACCOUNTS-centric APIs such as the TCA customer account public API, which enforce the uniqueness of ACCOUNT_NUMBER (U2) and ORIG_SYSTEM_REFERENCE (U3) during account creation and update.