Skip to content
Fusion Reference

HZ_CUST_ACCT_SITES_ALL

Product: HZmaster

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
master
Data class: what the table holds — master data, transaction documents, control/configuration, interface/staging, or a documented view.
In field listings, K marks a primary-key field.

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.CustomerAccountSiteExtractPVO
    OTBI: Receivables - Customer Real Time

    Customer Account Site data store — keyed on CustAcctSiteId.

    Oracle data-store documentation →

Fields

12 fields · 1 key

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; see quirks #set-idNUMBER
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. 1 key field.

Boilerplate SQL

Starting point for reading the BICC-landed copy of HZ_CUST_ACCT_SITES_ALLon 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
-- ============================================================
-- 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
-- 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.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.SET_ID AS "Reference data set stripe — the column that replaced the EBS operating-unit ORG_ID; see quirks #set-id",
  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
  1 = 1  -- no partition column on this table; the filters below are optional
  -- 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;

4 parameters not filled: <catalog>, <schema>, <CUST_ACCT_SITE_ID>, <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

  • 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 →

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.