Search Results hz_cust_accounts




Overview
Explore in AI Chat

Overview

HZ_CUST_ACCOUNTS is the foundational customer account table within the Oracle E-Business Suite Trading Community Architecture (TCA). Owned by the AR schema and validated in both release 12.1.1 and 12.2.2, it stores the account-level record for every customer relationship defined in the system. While HZ_PARTIES holds the underlying party — a person, organization, or group — the customer account represents the specific business relationship that a party maintains with the selling enterprise. A single party may therefore own multiple customer accounts, each carrying its own account number, credit terms, profile settings, and transaction history.

In the ETRM metadata, HZ_CUST_ACCOUNTS is classified heuristically as a hub in Data Vault modeling terms. This is a sensible suggestion: the table is the central anchor to which a very large number of dependent transactional and profile tables attach via CUST_ACCOUNT_ID. Its surrogate primary key, defined by HZ_CUST_ACCOUNTS_PK, is CUST_ACCOUNT_ID.

Key Information Stored

The table contains 139 documented columns. The most operationally significant include:

The three unique indexes (U1 on CUST_ACCOUNT_ID, U2 on ACCOUNT_NUMBER, U3 on ORIG_SYSTEM_REFERENCE) distinguish the surrogate key from the two documented business-key candidates.

Common Use Cases and Queries

Because HZ_CUST_ACCOUNTS is the hub of the customer model, it is joined in nearly every receivables, order management, and collections report. A typical pattern retrieves the account together with its party and site:

  • Resolving an account number to a surrogate key: SELECT cust_account_id FROM hz_cust_accounts WHERE account_number = :p_account_number.
  • Joining to the party to obtain the customer name: SELECT a.account_number, p.party_name FROM hz_cust_accounts a, hz_parties p WHERE a.party_id = p.party_id.
  • Locating accounts that are inactive: SELECT account_number FROM hz_cust_accounts WHERE status = 'I'.
  • Reporting open balances by account: joining to AR_PAYMENT_SCHEDULES_ALL or AR_CUSTOMER_TRX_ALL on the customer ID columns to aggregate outstanding amounts.
  • Migrating legacy customers: querying on ORIG_SYSTEM_REFERENCE to reconcile loaded accounts against the source system.
  • Collections and credit exposure: joining to AR_CREDIT_HISTORIES for aging and current-balance analysis.

Related Objects

The FK relationship data shows HZ_CUST_ACCOUNTS as the target of an extensive set of dependencies. The most significant include:

Through these relationships, HZ_CUST_ACCOUNTS serves as the authoritative anchor for customer identity and account structure across the entire EBS application suite.