HZ_PARTY_SITES
Product: HZmasterParty sites — the link between a party and a location, carrying the site number, name, addressee, and mailstop; one party can have many sites and one location can serve many parties
The party-level address spine: account sites reference a PARTY_SITE_ID, and the supplier-site master carries one too. IDENTIFYING_ADDRESS_FLAG marks the row denormalized onto the party; the validity window is START_DATE_ACTIVE/END_DATE_ACTIVE (a third date-naming convention in this module alone).
What the badges mean
- master
- Data class: what the table holds — master data, transaction documents, control/configuration, interface/staging, or a documented view.
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.PartySiteExtractPVO
Party Site data store — keyed on PartySiteId. No dedicated subject area — addresses surface as dimensions inside the customer subject areas.
Oracle data-store documentation →
Fields
12 fields · 1 key
| # | Field | Description | Type | Flags |
|---|---|---|---|---|
| 1 | PARTY_SITE_ID | Surrogate key of the party site | NUMBER | Key |
| 2 | PARTY_ID | The party the site belongs to | NUMBER | |
| 3 | LOCATION_ID | The physical address record the site points at | NUMBER | |
| 4 | PARTY_SITE_NUMBER | Unique site number | VARCHAR2 | |
| 5 | PARTY_SITE_NAME | User-defined site name | VARCHAR2 | |
| 6 | STATUS | Site status flag | VARCHAR2 | |
| 7 | IDENTIFYING_ADDRESS_FLAG | Whether this is the party's identifying address — the row denormalized onto the party master | VARCHAR2 | |
| 8 | OVERALL_PRIMARY_FLAG | The party's primary address regardless of context | VARCHAR2 | |
| 9 | ADDRESSEE | Addressee line printed above the address | VARCHAR2 | |
| 10 | START_DATE_ACTIVE | Site effective-from date | DATE | |
| 11 | END_DATE_ACTIVE | Site effective-to date | DATE | |
| 12 | ORIG_SYSTEM_REFERENCE | Legacy-system site key | VARCHAR2 |
Field provenance: hand-curated. 1 key field.
Boilerplate SQL
Starting point for reading the BICC-landed copy of HZ_PARTY_SITESon 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.
-- ============================================================
-- Table : HZ_PARTY_SITES — Party sites — the link between a party and a location, carrying the site number, name, addressee, and mailstop; one party can have many sites and one location can serve many parties
-- 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 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.PARTY_SITE_ID AS "Surrogate key of the party site",
t.PARTY_ID AS "The party the site belongs to",
t.LOCATION_ID AS "The physical address record the site points at",
t.PARTY_SITE_NUMBER AS "Unique site number",
t.PARTY_SITE_NAME AS "User-defined site name",
t.STATUS AS "Site status flag",
t.IDENTIFYING_ADDRESS_FLAG AS "Whether this is the party's identifying address — the row denormalized onto the party master",
t.OVERALL_PRIMARY_FLAG AS "The party's primary address regardless of context",
t.ADDRESSEE AS "Addressee line printed above the address",
t.START_DATE_ACTIVE AS "Site effective-from date",
t.END_DATE_ACTIVE AS "Site effective-to date",
t.ORIG_SYSTEM_REFERENCE AS "Legacy-system site key"
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>' -- the column incremental BICC extracts key on
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 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