Skip to content
Fusion Reference

HZ_CUST_ACCT_SITES_ALL

Product: HZmasterSet-striped (SET_ID)

Customer 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

Notes

The _ALL suffix survives but the stripe changed: there is NO ORG_ID — the striping column is SET_ID (reference data set), part of both unique keys (see quirks #set-id). The purpose flags are three-valued: Y, N, or P for primary. START_DATE/END_DATE bound the site's validity — plain dates, not the _F effectivity pattern.

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.

Structural facts — how the table is partitioned, not a trap by itself

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 with INVENTORY_ITEM_ID on 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_ID on the GL journal tables), or a named business-unit column (PRC_BU_ID / REQ_BU_ID in 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 LANGUAGE column (a _TL translation table or FND_LOOKUP_VALUES) — one row per language. Filter to one LANGUAGE or a join multiplies rows.

Join & extract hazards — verify before you rely on this

Date-effective
This is an _F table — one row per entity per effectivity window, with EFFECTIVE_START_DATE and EFFECTIVE_END_DATE part 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.
In field listings, the Key chip marks a key field — a member of the documented primary key or of a documented unique index.

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.

Fields

12 fields · 2 key

12 fields.

Table fields: position, field name, description, data type, and flags. 12 fields.
#FieldDescriptionTypeFlags
1CUST_ACCT_SITE_IDSurrogate key of the account siteNUMBER
Key
2CUST_ACCOUNT_IDThe customer account the site belongs toNUMBER
3PARTY_SITE_IDThe party site (address) this account site usesNUMBER
4SET_IDReference data set stripe — the column that replaced the EBS operating-unit ORG_ID, and part of both documented unique keys; see quirks #set-idNUMBER
Key
5STATUSSite statusVARCHAR2
CODE_STATUS
6BILL_TO_FLAGBill-to purpose — Y, N, or P for the account's primary bill-to siteVARCHAR2
7SHIP_TO_FLAGShip-to purpose — Y, N, or P for primaryVARCHAR2
8MARKET_FLAGMarketing purpose — Y, N, or P for primaryVARCHAR2
9CUSTOMER_CATEGORY_CODEUser-defined site categoryVARCHAR2
ADDRESS_CATEGORY
10START_DATESite validity startDATE
11END_DATESite validity endDATE
12ORIG_SYSTEM_REFERENCELegacy-system address keyVARCHAR2

Field provenance: hand-curated. 2 key fields.

Boilerplate SQL

Starting point for reading the BICC-landed copy of HZ_CUST_ACCT_SITES_ALL 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.

Query parameters

5 parameters not filled: <catalog>, <schema>, <SET_ID>, <CUST_ACCT_SITE_ID>, <watermark>

-- ============================================================
-- Table  : HZ_CUST_ACCT_SITES_ALL — Customer 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
-- Purpose: Column-selected read of HZ_CUST_ACCT_SITES_ALL — auto-generated from field metadata
-- Grain  : One row per CUST_ACCT_SITE_ID + SET_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_ACCT_SITE_ID AS "Surrogate key of the account site",
  t.SET_ID AS "Reference data set stripe — the column that replaced the EBS operating-unit ORG_ID, and part of both documented unique keys; see quirks #set-id",
  t.CUST_ACCOUNT_ID AS "The customer account the site belongs to",
  t.PARTY_SITE_ID AS "The party site (address) this account site uses",
  t.STATUS AS "Site status",  -- decode t.STATUS via FND_LOOKUP_VALUES (LOOKUP_TYPE = 'CODE_STATUS', LANGUAGE-filtered)
  t.BILL_TO_FLAG AS "Bill-to purpose — Y, N, or P for the account's primary bill-to site",
  t.SHIP_TO_FLAG AS "Ship-to purpose — Y, N, or P for primary",
  t.MARKET_FLAG AS "Marketing purpose — Y, N, or P for primary",
  t.CUSTOMER_CATEGORY_CODE AS "User-defined site category",  -- decode t.CUSTOMER_CATEGORY_CODE via FND_LOOKUP_VALUES (LOOKUP_TYPE = 'ADDRESS_CATEGORY', LANGUAGE-filtered)
  t.START_DATE AS "Site validity start",
  t.END_DATE AS "Site validity end",
  t.ORIG_SYSTEM_REFERENCE AS "Legacy-system address key"
FROM <catalog>.<schema>.HZ_CUST_ACCT_SITES_ALL t
WHERE
  t.SET_ID = <SET_ID>  -- reference data set — the stripe that replaced the org stripe; one set or codes double-load; see quirks guide #set-id
  -- AND t.CUST_ACCT_SITE_ID = <CUST_ACCT_SITE_ID>
  -- AND t.LAST_UPDATE_DATE >= TIMESTAMP '<watermark>'  -- the column incremental BICC extracts key on
ORDER BY t.CUST_ACCT_SITE_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

  • 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
  • HZ_CUST_ACCT_SITES_ALLHZ_PARTY_SITESforeign key · N:1
    ON HZ_CUST_ACCT_SITES_ALL.PARTY_SITE_ID = HZ_PARTY_SITES.PARTY_SITE_ID
  • HZ_CUST_SITE_USES_ALLHZ_CUST_ACCT_SITES_ALLforeign key · N:1
    ON HZ_CUST_SITE_USES_ALL.CUST_ACCT_SITE_ID = HZ_CUST_ACCT_SITES_ALL.CUST_ACCT_SITE_ID

Browse more Customers (TCA) tables

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 Fusion Cloud Applications are registered trademarks of Oracle and/or its affiliates.