Skip to content
Fusion Reference

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

Notes

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.

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.

  • CrmAnalyticsAM.CrmExtractAM.HzBiccExtractAM.CustomerAcctSiteUseExtractPVO
    OTBI: 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.

Table fields: position, field name, description, data type, and flags. 13 fields.
#FieldDescriptionTypeFlags
1SITE_USE_IDSurrogate key of the site use — what AR transactions actually point atNUMBER
Key
2CUST_ACCT_SITE_IDThe account site the purpose is assigned toNUMBER
3SITE_USE_CODEThe business purpose — Bill-To, Ship-To, Statements, Market, and so onVARCHAR2
4SET_IDReference data set stripe — no ORG_ID on this table, and part of the documented unique key (SET_ID + SITE_USE_ID); see quirks #set-idNUMBER
Key
5PRIMARY_FLAGWhether this is the account's primary site for the purposeVARCHAR2
6STATUSSite-use statusVARCHAR2
CODE_STATUS
7LOCATIONSite-use identifier string shown in transaction UIsVARCHAR2
8BILL_TO_SITE_USE_IDFor a ship-to use, the bill-to use it settles through (self-referencing)NUMBER
9PAYMENT_TERM_IDDefault payment terms at this site useNUMBER
10GSA_INDICATORUS GSA agency indicatorVARCHAR2
11START_DATEUse validity startDATE
12END_DATEUse validity endDATE
13ORIG_SYSTEM_REFERENCELegacy-system site-use keyVARCHAR2

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.

Query parameters

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

  • 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
  • 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
  • RA_CUSTOMER_TRX_ALLHZ_CUST_SITE_USES_ALLforeign key · N:1
    ON RA_CUSTOMER_TRX_ALL.BILL_TO_SITE_USE_ID = HZ_CUST_SITE_USES_ALL.SITE_USE_ID
  • RA_CUSTOMER_TRX_ALLHZ_CUST_SITE_USES_ALLforeign key · N:1
    ON RA_CUSTOMER_TRX_ALL.SHIP_TO_SITE_USE_ID = HZ_CUST_SITE_USES_ALL.SITE_USE_ID
  • AR_PAYMENT_SCHEDULES_ALLHZ_CUST_SITE_USES_ALLforeign key · N:1
    ON AR_PAYMENT_SCHEDULES_ALL.CUSTOMER_SITE_USE_ID = HZ_CUST_SITE_USES_ALL.SITE_USE_ID
  • AR_CASH_RECEIPTS_ALLHZ_CUST_SITE_USES_ALLforeign key · N:1
    ON AR_CASH_RECEIPTS_ALL.CUSTOMER_SITE_USE_ID = HZ_CUST_SITE_USES_ALL.SITE_USE_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.