HZ_CUST_ACCOUNTS
Product: HZmasterThe customer account — the commercial (selling) relationship layered on a party; one party can carry several accounts, each with its own account number, status, and type
The EBS 12.2.2 vestigial ORG_ID is gone entirely — no org column of any kind. CUSTOMER_TYPE is a coded I/R split (internal vs revenue-generating external, page-documented). STATUS decodes through the CODE_STATUS lookup; the A/I value list EBS practitioners expect is not enumerated in the Fusion dictionary. Fusion drops the EBS SALES_CHANNEL_CODE and SUSPENSION_DATE columns.
What the badges mean
- Product: EGP
- Product: the Oracle product family that owns the object — the short code Oracle's Tables and Views documentation lists as the object owner. Fusion is SaaS, so this isn't a database schema; there's no SQL path to the tables at all (see the quirks guide).
- master
- Data class: what the table holds — master data, transaction documents, control/configuration, interface/staging, or a documented view.
- BU-striped (ORG_ID)
- Rows are scoped to a business unit. The column is still named
ORG_ID, but in Fusion it means business unit, not the EBS operating unit — treat any migrated “operating unit” filter as suspect (see the quirks guide). - Per inventory org
- Rows are scoped to an inventory organization via
ORGANIZATION_ID— always pair it withINVENTORY_ITEM_IDon item-level joins (see the quirks guide). - Set / ledger / named-BU striped
- Some tables stripe by a named column instead of
ORG_ID: reference data set (SET_ID— see the quirks guide), ledger (LEDGER_IDon the GL journal tables), or a named business-unit column (PRC_BU_ID/REQ_BU_IDin procurement). The table page’s partition line names the column, and the generated SQL anchors on it — never treat these tables as unpartitioned. - Language-striped
- The table carries a
LANGUAGEcolumn (a _TL translation table or FND_LOOKUP_VALUES) — one row per language. Filter to oneLANGUAGEor a join multiplies rows. - Date-effective
- This is an
_Ftable — one row per entity per effectivity window, withEFFECTIVE_START_DATEandEFFECTIVE_END_DATEpart of the key. Join without a window filter and every fact multiplies by history (see the quirks guide). - View
- This is a documented convenience view, not a physical table. Extract through the BICC data store that fronts its base objects instead of assuming the view lands as-is.
Structural facts — how the table is partitioned, not a trap by itself
Join & extract hazards — verify before you rely on this
Extract access
The delivered surfaces that reach this table — the BICC extract data store (PVO) for bulk extraction and the OTBI subject areas for real-time queries. There is no SQL path to the SaaS database.
- CrmAnalyticsAM.CrmExtractAM.HzBiccExtractAM.CustomerAccountExtractPVOOTBI: Receivables - Customer Real Time
Customer Account data store — keyed on CustAccountId. The Financials TBI customer subject area is the receivables-side query surface.
Oracle data-store documentation (opens in new tab)
Fields
12 fields · 1 key
12 fields.
| # | Field | Description | Type | Flags |
|---|---|---|---|---|
| 1 | CUST_ACCOUNT_ID | Surrogate key of the customer account — the id AR calls the customer | NUMBER | Key |
| 2 | PARTY_ID | The party this account belongs to | NUMBER | |
| 3 | ACCOUNT_NUMBER | Customer account number | VARCHAR2 | |
| 4 | ACCOUNT_NAME | Account description — not the party name | VARCHAR2 | |
| 5 | STATUS | Account status — the A/I list EBS practitioners expect is not enumerated here | VARCHAR2 | CODE_STATUS |
| 6 | CUSTOMER_TYPE | I for internal, R for revenue-generating external customers | VARCHAR2 | CUSTOMER_TYPE |
| 7 | CUSTOMER_CLASS_CODE | Customer classification (reseller, education, and so on) | VARCHAR2 | |
| 8 | ACCOUNT_ESTABLISHED_DATE | When the account relationship began | DATE | |
| 9 | ACCOUNT_TERMINATION_DATE | When the account relationship ended | DATE | |
| 10 | HOLD_BILL_FLAG | Whether bills receivable are on hold for the account | VARCHAR2 | |
| 11 | SELLING_PARTY_ID | The party selling to this account — an external-facing organization, not a BU or legal entity | NUMBER | |
| 12 | ORIG_SYSTEM_REFERENCE | Legacy-system customer key | VARCHAR2 |
Field provenance: hand-curated. 1 key field.
Boilerplate SQL
Starting point for reading the BICC-landed copy of HZ_CUST_ACCOUNTS on Databricks — real DATE columns need no conversion, and the org anchor and the LAST_UPDATE_DATE watermark (the column incremental BICC extracts key on) are already in place. Set your Unity Catalog location, schema, and org values below; they’re substituted into the SQL and the copy button.
4 parameters not filled: <catalog>, <schema>, <CUST_ACCOUNT_ID>, <watermark>
-- ============================================================
-- Table : HZ_CUST_ACCOUNTS — The customer account — the commercial (selling) relationship layered on a party; one party can carry several accounts, each with its own account number, status, and type
-- 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 Fusion Cloud data landed in your lakehouse by a BICC extract — there is no SQL path to the SaaS database. Column names follow Oracle's table documentation — if your landed data still carries PVO attribute headers, map names first; see quirks #pvo-drift. 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 customer account — the id AR calls the customer",
t.PARTY_ID AS "The party this account belongs to",
t.ACCOUNT_NUMBER AS "Customer account number",
t.ACCOUNT_NAME AS "Account description — not the party name",
t.STATUS AS "Account status — the A/I list EBS practitioners expect is not enumerated here", -- decode t.STATUS via FND_LOOKUP_VALUES (LOOKUP_TYPE = 'CODE_STATUS', LANGUAGE-filtered)
t.CUSTOMER_TYPE AS "I for internal, R for revenue-generating external customers", -- decode t.CUSTOMER_TYPE via FND_LOOKUP_VALUES (LOOKUP_TYPE = 'CUSTOMER_TYPE', LANGUAGE-filtered)
t.CUSTOMER_CLASS_CODE AS "Customer classification (reseller, education, and so on)",
t.ACCOUNT_ESTABLISHED_DATE AS "When the account relationship began",
t.ACCOUNT_TERMINATION_DATE AS "When the account relationship ended",
t.HOLD_BILL_FLAG AS "Whether bills receivable are on hold for the account",
t.SELLING_PARTY_ID AS "The party selling to this account — an external-facing organization, not a BU or legal entity",
t.ORIG_SYSTEM_REFERENCE AS "Legacy-system customer key"
FROM <catalog>.<schema>.HZ_CUST_ACCOUNTS t
WHERE
1 = 1 -- no automatic partition anchor on this table; the filters below are optional
-- AND t.CUST_ACCOUNT_ID = <CUST_ACCOUNT_ID>
-- AND t.LAST_UPDATE_DATE >= TIMESTAMP '<watermark>' -- the column incremental BICC extracts key on
ORDER BY t.CUST_ACCOUNT_ID;Verified September 2026 · docs release 26C
Column names differ in BICC extracts — see PVO header drift.
Relationships
Diagram of 1-hop neighbors — join details below. FND lookup decode and translation edges are highlighted; they’re the joins newcomers most often get wrong.
Join details
ON HZ_CUST_ACCOUNTS.PARTY_ID = HZ_PARTIES.PARTY_IDON HZ_CUST_ACCOUNTS.SELLING_PARTY_ID = HZ_PARTIES.PARTY_IDON HZ_CUST_ACCT_SITES_ALL.CUST_ACCOUNT_ID = HZ_CUST_ACCOUNTS.CUST_ACCOUNT_IDON RA_CUSTOMER_TRX_ALL.BILL_TO_CUSTOMER_ID = HZ_CUST_ACCOUNTS.CUST_ACCOUNT_IDON AR_PAYMENT_SCHEDULES_ALL.CUSTOMER_ID = HZ_CUST_ACCOUNTS.CUST_ACCOUNT_IDON AR_CASH_RECEIPTS_ALL.PAY_FROM_CUSTOMER = HZ_CUST_ACCOUNTS.CUST_ACCOUNT_ID
More Customers (TCA) tables
- HZ_CUST_ACCT_SITES_ALLCustomer account sites — an account's use of a party site (address); the layer order and invoice addresses hang off, with bill-to/ship-to/market purpose flags
- HZ_CUST_SITE_USES_ALLSite uses — the business purposes (bill-to, ship-to, statements) assigned to each customer account site; the bottom TCA layer, and the id AR transactions actually point at
- HZ_LOCATIONSThe location master — the physical postal address itself (street, city, postal code, country, coordinates), shared by every party and account site that points at it
- HZ_PARTIESThe party master — one row per person, organization, or group in the trading community, with the party number, type, status, and a denormalized identifying address and primary contact point; the top of the four-layer customer model
- HZ_PARTY_SITESParty sites — the link between a party and a location, carrying the site number, name, addressee, and mailstop; one party can have many sites and one location can serve many parties