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
- Product: EGP
- Product: the Oracle product family that owns the object — the short code Oracle's Tables and Views documentation lists as the object owner. Fusion is SaaS, so this isn't a database schema; there's no SQL path to the tables at all (see the quirks guide).
- master
- Data class: what the table holds — master data, transaction documents, control/configuration, interface/staging, or a documented view.
- BU-striped (ORG_ID)
- Rows are scoped to a business unit. The column is still named
ORG_ID, but in Fusion it means business unit, not the EBS operating unit — treat any migrated “operating unit” filter as suspect (see the quirks guide). - Per inventory org
- Rows are scoped to an inventory organization via
ORGANIZATION_ID— always pair it withINVENTORY_ITEM_IDon item-level joins (see the quirks guide). - Set / ledger / named-BU striped
- Some tables stripe by a named column instead of
ORG_ID: reference data set (SET_ID— see the quirks guide), ledger (LEDGER_IDon the GL journal tables), or a named business-unit column (PRC_BU_ID/REQ_BU_IDin procurement). The table page’s partition line names the column, and the generated SQL anchors on it — never treat these tables as unpartitioned. - 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. - Date-effective
- This is an
_Ftable — one row per entity per effectivity window, withEFFECTIVE_START_DATEandEFFECTIVE_END_DATEpart of the key. Join without a window filter and every fact multiplies by history (see the quirks guide). - View
- This is a documented convenience view, not a physical table. Extract through the BICC data store that fronts its base objects instead of assuming the view lands as-is.
Structural facts — how the table is partitioned, not a trap by itself
Join & extract hazards — verify before you rely on this
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 (opens in new tab)
Fields
12 fields · 1 key
12 fields.
| # | 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_SITES on 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.
4 parameters not filled: <catalog>, <schema>, <PARTY_SITE_ID>, <watermark>
-- ============================================================
-- 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 automatic partition anchor 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;Verified September 2026 · docs release 26C
Column names differ in BICC extracts — see PVO header drift.
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 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 (selling) relationship layered on a party; one party can carry several accounts, each with its own account number, status, and type
- HZ_CUST_ACCT_SITES_ALLCustomer account sites — an account's use of a party site (address); the layer order and invoice addresses hang off, with bill-to/ship-to/market purpose flags
- HZ_CUST_SITE_USES_ALLSite uses — the business purposes (bill-to, ship-to, statements) assigned to each customer account site; the bottom TCA layer, and the id AR transactions actually point at
- HZ_LOCATIONSThe location master — the physical postal address itself (street, city, postal code, country, coordinates), shared by every party and account site that points at it
- HZ_PARTIESThe party master — one row per person, organization, or group in the trading community, with the party number, type, status, and a denormalized identifying address and primary contact point; the top of the four-layer customer model