Skip to content
EBS Reference

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

Identity
Module: Customers (TCA)Operating-unit striped (ORG_ID)
Notes

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
Schema: INV
Schema: the Oracle product schema that owns the table (INV, ONT, WSH, PO, BOM, WIP, MRP, MSC, AR, AP, GL, HR, APPLSYS) — tells you which product family the object belongs to, not who can query it.
master
Data class: what the table holds — master data, transaction documents, control/configuration, interface/staging, or an APPS-schema view.

Structural facts — how the table is partitioned, not a trap by itself

OU-striped (ORG_ID)
Rows are scoped to an operating unit. A landed extract carries every operating unit’s rows — filter or join on ORG_ID, and don’t confuse it with ORGANIZATION_ID (see the quirks guide).
Per inventory org
Rows are scoped to an inventory organization (plant or warehouse) via ORGANIZATION_ID — a different partition from OU-striped tables (see the quirks guide).
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 (see the quirks guide).

Join & extract hazards — verify before you rely on this

View
This is an APPS-schema convenience view, not a physical table. Extract the base tables it joins instead — views can be slow at scale and aren't guaranteed stable across patches.
In field listings, the Key chip marks a primary-key field.

Fields

12 fields · 1 key

12 fields.

Table fields: position, field name, description, data type, and flags. 12 fields.
#FieldDescriptionTypeFlags
1SITE_USE_IDSurrogate key of the use — the id order headers carry as SHIP_TO_ORG_ID / INVOICE_TO_ORG_IDNUMBER
Primary-key field
2CUST_ACCT_SITE_IDThe account site the use belongs to — one site, many usesNUMBER
3SITE_USE_CODEThe business purpose — ship-to, bill-to, statements…; filter it or joins double-countVARCHAR2
4PRIMARY_FLAGWhether this is the primary site for the purposeVARCHAR2
5STATUSA = active, I = inactiveVARCHAR2
6LOCATIONThe human-facing site-use label (a text identifier, not the address table's key)VARCHAR2
7ORG_IDOperating unitNUMBER
8BILL_TO_SITE_USE_IDFor ship-to uses, the associated bill-to useNUMBER
9PAYMENT_TERM_IDPayment-terms default at the use levelNUMBER
10TERRITORY_IDTerritory of the useNUMBER
11WAREHOUSE_IDDefault ship-from warehouse (an inventory org) for ship-to usesNUMBER
12GL_ID_RECAutoAccounting receivable-account default (CCID)NUMBER

Field provenance: hand-curated. 1 key field.

Boilerplate SQL

Starting point for reading HZ_CUST_SITE_USES_ALL on Databricks — real DATE columns need no conversion, and the org anchor is already in place. The optional LAST_UPDATE_DATE watermark is included. 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>, <operating_unit_id>, <SITE_USE_ID>, <watermark>

-- ============================================================
-- 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;

Verified September 2026

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

  • OE_ORDER_HEADERS_ALLHZ_CUST_SITE_USES_ALLforeign key · N:1
    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_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 AND HZ_CUST_SITE_USES_ALL.ORG_ID = HZ_CUST_ACCT_SITES_ALL.ORG_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 AND RA_CUSTOMER_TRX_ALL.ORG_ID = HZ_CUST_SITE_USES_ALL.ORG_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 E-Business Suite are registered trademarks of Oracle and/or its affiliates.