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
- master
- Data class: what the table holds — master data, transaction documents, control/configuration, interface/staging, or an APPS-schema view.
Fields
9 fields · 1 key
| # | Field | Description | Type | Flags |
|---|---|---|---|---|
| 1 | PARTY_SITE_ID | Surrogate key of the party site | NUMBER | Key |
| 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_SITESon 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_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;4 parameters not filled: <catalog>, <schema>, <PARTY_SITE_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 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