HZ_CUST_SITE_USES_ALL
Schema: ARmasterOU-striped (ORG_ID)Site business purposes — one row per use (ship-to, bill-to, statements…) of an account site per operating unit; the SITE_USE_ID here is what order headers carry as SHIP_TO_ORG_ID and INVOICE_TO_ORG_ID
One account site carries several uses — filter SITE_USE_CODE (and usually STATUS = 'A' and PRIMARY_FLAG) or joins double-count. The use, not the site, is the order-header pointer.
What the badges mean
- master
- Data class: what the table holds — master data, transaction documents, control/configuration, interface/staging, or an APPS-schema view.
Fields
12 fields · 1 key
| # | Field | Description | Type | Flags |
|---|---|---|---|---|
| 1 | SITE_USE_ID | Surrogate key of the use — the id order headers carry as SHIP_TO_ORG_ID / INVOICE_TO_ORG_ID | NUMBER | Key |
| 2 | CUST_ACCT_SITE_ID | The account site the use belongs to — one site, many uses | NUMBER | |
| 3 | SITE_USE_CODE | The business purpose — ship-to, bill-to, statements…; filter it or joins double-count | VARCHAR2 | |
| 4 | PRIMARY_FLAG | Whether this is the primary site for the purpose | VARCHAR2 | |
| 5 | STATUS | A = active, I = inactive | VARCHAR2 | |
| 6 | LOCATION | The human-facing site-use label (a text identifier, not the address table's key) | VARCHAR2 | |
| 7 | ORG_ID | Operating unit | NUMBER | |
| 8 | BILL_TO_SITE_USE_ID | For ship-to uses, the associated bill-to use | NUMBER | |
| 9 | PAYMENT_TERM_ID | Payment-terms default at the use level | NUMBER | |
| 10 | TERRITORY_ID | Territory of the use | NUMBER | |
| 11 | WAREHOUSE_ID | Default ship-from warehouse (an inventory org) for ship-to uses | NUMBER | |
| 12 | GL_ID_REC | AutoAccounting receivable-account default (CCID) | NUMBER |
Field provenance: hand-curated. 1 key field.
Boilerplate SQL
Starting point for reading HZ_CUST_SITE_USES_ALLon Databricks — real DATE columns need no conversion, and the org anchor and the LAST_UPDATE_DATE watermark are already in place. Set your Unity Catalog location, schema, and org values below; they’re substituted into the SQL and the copy button.
-- ============================================================
-- Table : HZ_CUST_SITE_USES_ALL — Site business purposes — one row per use (ship-to, bill-to, statements…) of an account site per operating unit; the SITE_USE_ID here is what order headers carry as SHIP_TO_ORG_ID and INVOICE_TO_ORG_ID
-- Purpose: Column-selected read of HZ_CUST_SITE_USES_ALL — auto-generated from field metadata
-- Grain : One row per operating unit (ORG_ID) + SITE_USE_ID
-- Notes : Auto-generated skeleton for Oracle EBS R12 data landed in your lakehouse. 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 use — the id order headers carry as SHIP_TO_ORG_ID / INVOICE_TO_ORG_ID",
t.CUST_ACCT_SITE_ID AS "The account site the use belongs to — one site, many uses",
t.SITE_USE_CODE AS "The business purpose — ship-to, bill-to, statements…; filter it or joins double-count",
t.PRIMARY_FLAG AS "Whether this is the primary site for the purpose",
t.STATUS AS "A = active, I = inactive",
t.LOCATION AS "The human-facing site-use label (a text identifier, not the address table's key)",
t.ORG_ID AS "Operating unit",
t.BILL_TO_SITE_USE_ID AS "For ship-to uses, the associated bill-to use",
t.PAYMENT_TERM_ID AS "Payment-terms default at the use level",
t.TERRITORY_ID AS "Territory of the use",
t.WAREHOUSE_ID AS "Default ship-from warehouse (an inventory org) for ship-to uses",
t.GL_ID_REC AS "AutoAccounting receivable-account default (CCID)"
FROM <catalog>.<schema>.HZ_CUST_SITE_USES_ALL t
WHERE
t.ORG_ID = <operating_unit_id> -- operating unit (MOAC does not filter extracts)
-- AND t.SITE_USE_ID = <SITE_USE_ID>
-- AND t.LAST_UPDATE_DATE >= TIMESTAMP '<watermark>' -- WHO watermark, bulk-stamped by batch jobs; see quirks guide #who-columns
ORDER BY t.SITE_USE_ID;5 parameters not filled: <catalog>, <schema>, <operating_unit_id>, <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
ON OE_ORDER_HEADERS_ALL.SHIP_TO_ORG_ID = HZ_CUST_SITE_USES_ALL.SITE_USE_ID AND OE_ORDER_HEADERS_ALL.ORG_ID = HZ_CUST_SITE_USES_ALL.ORG_IDON HZ_CUST_SITE_USES_ALL.CUST_ACCT_SITE_ID = HZ_CUST_ACCT_SITES_ALL.CUST_ACCT_SITE_ID AND HZ_CUST_SITE_USES_ALL.ORG_ID = HZ_CUST_ACCT_SITES_ALL.ORG_IDON RA_CUSTOMER_TRX_ALL.BILL_TO_SITE_USE_ID = HZ_CUST_SITE_USES_ALL.SITE_USE_ID AND RA_CUSTOMER_TRX_ALL.ORG_ID = HZ_CUST_SITE_USES_ALL.ORG_ID