Skip to content
EBS Reference

HZ_CUST_ACCOUNTS

Schema: ARmaster

The customer account — the commercial relationship layered over a party, and the id order headers actually carry as SOLD_TO_ORG_ID; one party, many accounts

Module: Customers (TCA)Not org-partitioned
Notes

Accounts are global, not operating-unit striped — a vestigial nullable ORG_ID column exists in the 12.2.2 dictionary but is not a striping column and is not cataloged here. The OU striping starts one layer down, on account sites.

What the badges mean
master
Data class: what the table holds — master data, transaction documents, control/configuration, interface/staging, or an APPS-schema view.
In field listings, K marks a primary-key field.

Fields

13 fields · 1 key

Table fields: position, field name, description, data type, and flags. 13 fields.
#FieldDescriptionTypeFlags
1CUST_ACCOUNT_IDSurrogate key of the account — the id order headers carry as SOLD_TO_ORG_IDNUMBER
Key
2PARTY_IDThe party behind the account — one party can hold several accountsNUMBER
3ACCOUNT_NUMBERThe account number users seeVARCHAR2
4ACCOUNT_NAMEAccount descriptionVARCHAR2
5STATUSA = active, I = inactive (the CODE_STATUS lookup, per the data dictionary's comment)VARCHAR2
6CUSTOMER_TYPEExternal vs internal customerVARCHAR2
7CUSTOMER_CLASS_CODECustomer classificationVARCHAR2
8SALES_CHANNEL_CODESales channel of the accountVARCHAR2
9ACCOUNT_ESTABLISHED_DATEWhen the account was opened — the lifecycle analysis dateDATE
Filter date
10ACCOUNT_ACTIVATION_DATEWhen the account was activatedDATE
11ACCOUNT_TERMINATION_DATEWhen the account was closed — NULL while activeDATE
12STATUS_UPDATE_DATEWhen the status last changedDATE
13ORIG_SYSTEM_REFERENCEThe legacy/source-system keyVARCHAR2

Field provenance: hand-curated. 1 key field.

Boilerplate SQL

Starting point for reading HZ_CUST_ACCOUNTSon Databricks — real DATE columns need no conversion, and the org anchor and the LAST_UPDATE_DATE watermark are already in place. Set your Unity Catalog location, schema, and org values below; they’re substituted into the SQL and the copy button.

Query parameters
-- ============================================================
-- Table  : HZ_CUST_ACCOUNTS — The customer account — the commercial relationship layered over a party, and the id order headers actually carry as SOLD_TO_ORG_ID; one party, many accounts
-- Purpose: Column-selected read of HZ_CUST_ACCOUNTS — auto-generated from field metadata
-- Grain  : One row per CUST_ACCOUNT_ID
-- Notes  : Auto-generated skeleton for Oracle EBS R12 data landed in your lakehouse. Dates are real DATE/TIMESTAMP columns — no conversion needed. WHO audit columns omitted (see the quirks guide); the optional LAST_UPDATE_DATE watermark filter supports incremental extracts.
-- ============================================================
SELECT
  t.CUST_ACCOUNT_ID AS "Surrogate key of the account — the id order headers carry as SOLD_TO_ORG_ID",
  t.PARTY_ID AS "The party behind the account — one party can hold several accounts",
  t.ACCOUNT_NUMBER AS "The account number users see",
  t.ACCOUNT_NAME AS "Account description",
  t.STATUS AS "A = active, I = inactive (the CODE_STATUS lookup, per the data dictionary's comment)",
  t.CUSTOMER_TYPE AS "External vs internal customer",
  t.CUSTOMER_CLASS_CODE AS "Customer classification",
  t.SALES_CHANNEL_CODE AS "Sales channel of the account",
  t.ACCOUNT_ESTABLISHED_DATE AS "When the account was opened — the lifecycle analysis date",
  t.ACCOUNT_ACTIVATION_DATE AS "When the account was activated",
  t.ACCOUNT_TERMINATION_DATE AS "When the account was closed — NULL while active",
  t.STATUS_UPDATE_DATE AS "When the status last changed",
  t.ORIG_SYSTEM_REFERENCE AS "The legacy/source-system key"
FROM <catalog>.<schema>.HZ_CUST_ACCOUNTS t
WHERE
  1 = 1  -- no partition column on this table; the filters below are optional
  -- AND t.CUST_ACCOUNT_ID = <CUST_ACCOUNT_ID>
  -- AND t.ACCOUNT_ESTABLISHED_DATE >= DATE '<DATE_FROM>'
  -- AND t.ACCOUNT_ESTABLISHED_DATE <= DATE '<DATE_TO>'
  -- AND t.LAST_UPDATE_DATE >= TIMESTAMP '<watermark>'  -- WHO watermark, bulk-stamped by batch jobs; see quirks guide #who-columns
ORDER BY t.CUST_ACCOUNT_ID;

6 parameters not filled: <catalog>, <schema>, <CUST_ACCOUNT_ID>, <DATE_FROM>, <DATE_TO>, <watermark>

Relationships

1-hop neighbors — click a table to navigate there. FND lookup decode and translation edges are highlighted; they’re the joins newcomers most often get wrong.

Join details

  • OE_ORDER_HEADERS_ALLHZ_CUST_ACCOUNTSforeign key · N:1
    ON OE_ORDER_HEADERS_ALL.SOLD_TO_ORG_ID = HZ_CUST_ACCOUNTS.CUST_ACCOUNT_ID
  • WSH_DELIVERY_DETAILSHZ_CUST_ACCOUNTSforeign key · N:1
    ON WSH_DELIVERY_DETAILS.CUSTOMER_ID = HZ_CUST_ACCOUNTS.CUST_ACCOUNT_ID
  • WSH_NEW_DELIVERIESHZ_CUST_ACCOUNTSforeign key · N:1
    ON WSH_NEW_DELIVERIES.CUSTOMER_ID = HZ_CUST_ACCOUNTS.CUST_ACCOUNT_ID
  • HZ_CUST_ACCOUNTSHZ_PARTIESforeign key · N:1
    ON HZ_CUST_ACCOUNTS.PARTY_ID = HZ_PARTIES.PARTY_ID
  • HZ_CUST_ACCT_SITES_ALLHZ_CUST_ACCOUNTSforeign key · N:1
    ON HZ_CUST_ACCT_SITES_ALL.CUST_ACCOUNT_ID = HZ_CUST_ACCOUNTS.CUST_ACCOUNT_ID
  • RA_CUSTOMER_TRX_ALLHZ_CUST_ACCOUNTSforeign key · N:1
    ON RA_CUSTOMER_TRX_ALL.BILL_TO_CUSTOMER_ID = HZ_CUST_ACCOUNTS.CUST_ACCOUNT_ID
  • AR_PAYMENT_SCHEDULES_ALLHZ_CUST_ACCOUNTSforeign key · N:1
    ON AR_PAYMENT_SCHEDULES_ALL.CUSTOMER_ID = HZ_CUST_ACCOUNTS.CUST_ACCOUNT_ID
  • AR_CASH_RECEIPTS_ALLHZ_CUST_ACCOUNTSforeign key · N:1
    ON AR_CASH_RECEIPTS_ALL.PAY_FROM_CUSTOMER = HZ_CUST_ACCOUNTS.CUST_ACCOUNT_ID

Browse more Customers (TCA)tables →

Maintained by Summit Analytics, a supply chain analytics practice. The tools and references are free — the consulting is selective.

Part of the Summit Analytics reference library.

Work with the practice →

Not affiliated with or endorsed by Oracle. Oracle and Oracle E-Business Suite are registered trademarks of Oracle and/or its affiliates.