HZ_CUST_SITE_USES_ALL
Product: HZmasterSet-striped (SET_ID)Site 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
SET_ID-striped like its parent — no ORG_ID (see quirks #set-id). A ship-to use points at its bill-to use through BILL_TO_SITE_USE_ID (self-referencing). Fusion drops the EBS order-defaulting columns (salesrep, warehouse, order type, price list, freight terms, demand class, GL_ID_*) — defaulting moved to setup, not the site use.
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.CustomerAcctSiteUseExtractPVOOTBI: Receivables - Customer Real Time
Customer Account Site Use data store — keyed on SiteUseId. Note the abbreviated "Acct" in this one store name (its parent site store spells "Account" out).
Oracle data-store documentation (opens in new tab)
Fields
13 fields · 2 key
13 fields.
| # | Field | Description | Type | Flags |
|---|---|---|---|---|
| 1 | SITE_USE_ID | Surrogate key of the site use — what AR transactions actually point at | NUMBER | Key |
| 2 | CUST_ACCT_SITE_ID | The account site the purpose is assigned to | NUMBER | |
| 3 | SITE_USE_CODE | The business purpose — Bill-To, Ship-To, Statements, Market, and so on | VARCHAR2 | |
| 4 | SET_ID | Reference data set stripe — no ORG_ID on this table, and part of the documented unique key (SET_ID + SITE_USE_ID); see quirks #set-id | NUMBER | Key |
| 5 | PRIMARY_FLAG | Whether this is the account's primary site for the purpose | VARCHAR2 | |
| 6 | STATUS | Site-use status | VARCHAR2 | CODE_STATUS |
| 7 | LOCATION | Site-use identifier string shown in transaction UIs | VARCHAR2 | |
| 8 | BILL_TO_SITE_USE_ID | For a ship-to use, the bill-to use it settles through (self-referencing) | NUMBER | |
| 9 | PAYMENT_TERM_ID | Default payment terms at this site use | NUMBER | |
| 10 | GSA_INDICATOR | US GSA agency indicator | VARCHAR2 | |
| 11 | START_DATE | Use validity start | DATE | |
| 12 | END_DATE | Use validity end | DATE | |
| 13 | ORIG_SYSTEM_REFERENCE | Legacy-system site-use key | VARCHAR2 |
Field provenance: hand-curated. 2 key fields.
Boilerplate SQL
Starting point for reading the BICC-landed copy of HZ_CUST_SITE_USES_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.
5 parameters not filled: <catalog>, <schema>, <SET_ID>, <SITE_USE_ID>, <watermark>
-- ============================================================
-- Table : HZ_CUST_SITE_USES_ALL — Site 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
-- Purpose: Column-selected read of HZ_CUST_SITE_USES_ALL — auto-generated from field metadata
-- Grain : One row per SITE_USE_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.SITE_USE_ID AS "Surrogate key of the site use — what AR transactions actually point at",
t.SET_ID AS "Reference data set stripe — no ORG_ID on this table, and part of the documented unique key (SET_ID + SITE_USE_ID); see quirks #set-id",
t.CUST_ACCT_SITE_ID AS "The account site the purpose is assigned to",
t.SITE_USE_CODE AS "The business purpose — Bill-To, Ship-To, Statements, Market, and so on",
t.PRIMARY_FLAG AS "Whether this is the account's primary site for the purpose",
t.STATUS AS "Site-use status", -- decode t.STATUS via FND_LOOKUP_VALUES (LOOKUP_TYPE = 'CODE_STATUS', LANGUAGE-filtered)
t.LOCATION AS "Site-use identifier string shown in transaction UIs",
t.BILL_TO_SITE_USE_ID AS "For a ship-to use, the bill-to use it settles through (self-referencing)",
t.PAYMENT_TERM_ID AS "Default payment terms at this site use",
t.GSA_INDICATOR AS "US GSA agency indicator",
t.START_DATE AS "Use validity start",
t.END_DATE AS "Use validity end",
t.ORIG_SYSTEM_REFERENCE AS "Legacy-system site-use key"
FROM <catalog>.<schema>.HZ_CUST_SITE_USES_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.SITE_USE_ID = <SITE_USE_ID>
-- AND t.LAST_UPDATE_DATE >= TIMESTAMP '<watermark>' -- the column incremental BICC extracts key on
ORDER BY t.SITE_USE_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_SITE_USES_ALL.CUST_ACCT_SITE_ID = HZ_CUST_ACCT_SITES_ALL.CUST_ACCT_SITE_ID- HZ_CUST_SITE_USES_ALLHZ_CUST_SITE_USES_ALLforeign key · N:1
ON HZ_CUST_SITE_USES_ALL1.BILL_TO_SITE_USE_ID = HZ_CUST_SITE_USES_ALL2.SITE_USE_ID ON RA_CUSTOMER_TRX_ALL.BILL_TO_SITE_USE_ID = HZ_CUST_SITE_USES_ALL.SITE_USE_IDON RA_CUSTOMER_TRX_ALL.SHIP_TO_SITE_USE_ID = HZ_CUST_SITE_USES_ALL.SITE_USE_IDON AR_PAYMENT_SCHEDULES_ALL.CUSTOMER_SITE_USE_ID = HZ_CUST_SITE_USES_ALL.SITE_USE_IDON AR_CASH_RECEIPTS_ALL.CUSTOMER_SITE_USE_ID = HZ_CUST_SITE_USES_ALL.SITE_USE_ID
More Customers (TCA) tables
- 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
- HZ_CUST_ACCOUNTSThe 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
- 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