Skip to content
Fusion Reference

HZ_CUST_SITE_USES_ALL

Product: HZmaster

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

Fields

13 fields · 1 key

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

Boilerplate SQL

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

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

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.