HZ_PARTY_SITES
Schema: ARmasterParty sites — the reusable link from a party to a location, carrying the site number and the identifying-address flag; both customer account sites and supplier sites resolve their address through here
Global — the OU-specific reuse happens on the customer account-site layer. The effectivity date pair on this table is marked "no longer used" in the data dictionary — don't filter on it.
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.
- 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 withORGANIZATION_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
LANGUAGEcolumn (a _TL translation table or FND_LOOKUP_VALUES) — one row per language. Filter to oneLANGUAGEor a join multiplies rows (see the quirks guide). - 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.
Structural facts — how the table is partitioned, not a trap by itself
Join & extract hazards — verify before you rely on this
Fields
9 fields · 1 key
9 fields.
| # | Field | Description | Type | Flags |
|---|---|---|---|---|
| 1 | PARTY_SITE_ID | Surrogate key of the party site | NUMBER | Primary-key field |
| 2 | PARTY_ID | The party at this address | NUMBER | |
| 3 | LOCATION_ID | The physical address — joins the location master | NUMBER | |
| 4 | PARTY_SITE_NUMBER | The unique site number users see | VARCHAR2 | |
| 5 | PARTY_SITE_NAME | User-defined site name | VARCHAR2 | |
| 6 | STATUS | A = active, I = inactive | VARCHAR2 | |
| 7 | IDENTIFYING_ADDRESS_FLAG | Y marks the party's identifying (primary) address — the one denormalized onto the party row | VARCHAR2 | |
| 8 | ORIG_SYSTEM_REFERENCE | The legacy/source-system key | VARCHAR2 | |
| 9 | CREATED_BY_MODULE | Which application created the site | VARCHAR2 |
Field provenance: hand-curated. 1 key field.
Boilerplate SQL
Starting point for reading HZ_PARTY_SITES 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.
4 parameters not filled: <catalog>, <schema>, <PARTY_SITE_ID>, <watermark>
-- ============================================================
-- Table : HZ_PARTY_SITES — Party sites — the reusable link from a party to a location, carrying the site number and the identifying-address flag; both customer account sites and supplier sites resolve their address through here
-- Purpose: Column-selected read of HZ_PARTY_SITES — auto-generated from field metadata
-- Grain : One row per PARTY_SITE_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.PARTY_SITE_ID AS "Surrogate key of the party site",
t.PARTY_ID AS "The party at this address",
t.LOCATION_ID AS "The physical address — joins the location master",
t.PARTY_SITE_NUMBER AS "The unique site number users see",
t.PARTY_SITE_NAME AS "User-defined site name",
t.STATUS AS "A = active, I = inactive",
t.IDENTIFYING_ADDRESS_FLAG AS "Y marks the party's identifying (primary) address — the one denormalized onto the party row",
t.ORIG_SYSTEM_REFERENCE AS "The legacy/source-system key",
t.CREATED_BY_MODULE AS "Which application created the site"
FROM <catalog>.<schema>.HZ_PARTY_SITES t
WHERE
1 = 1 -- no partition column on this table; the filters below are optional
-- AND t.PARTY_SITE_ID = <PARTY_SITE_ID>
-- AND t.LAST_UPDATE_DATE >= TIMESTAMP '<watermark>' -- WHO watermark, bulk-stamped by batch jobs; see quirks guide #who-columns
ORDER BY t.PARTY_SITE_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
ON AP_SUPPLIER_SITES_ALL.PARTY_SITE_ID = HZ_PARTY_SITES.PARTY_SITE_IDON HZ_CUST_ACCT_SITES_ALL.PARTY_SITE_ID = HZ_PARTY_SITES.PARTY_SITE_IDON HZ_PARTY_SITES.PARTY_ID = HZ_PARTIES.PARTY_IDON HZ_PARTY_SITES.LOCATION_ID = HZ_LOCATIONS.LOCATION_ID
More Customers (TCA) tables
- HZ_CUST_ACCOUNTSThe customer account — the commercial relationship layered over a party, and the id order headers actually carry as SOLD_TO_ORG_ID; one party, many accounts
- HZ_CUST_ACCT_SITES_ALLCustomer account sites — one row binding an account to a party site (address) within one operating unit, with the bill-to/ship-to capability flags
- HZ_CUST_SITE_USES_ALLSite 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
- HZ_LOCATIONSThe physical address master — pure address rows with no party context; one location can serve many parties, customer sites, and supplier sites
- HZ_PARTIESThe trading-community party master — one row per person, organization, or group before any commercial context; customers AND suppliers resolve back to a party here