Skip to content
Fusion Reference

HZ_PARTY_SITES

Product: HZmaster

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

Notes

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.
In field listings, K marks a primary-key field.

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

Table fields: position, field name, description, data type, and flags. 12 fields.
#FieldDescriptionTypeFlags
1PARTY_SITE_IDSurrogate key of the party siteNUMBER
Key
2PARTY_IDThe party the site belongs toNUMBER
3LOCATION_IDThe physical address record the site points atNUMBER
4PARTY_SITE_NUMBERUnique site numberVARCHAR2
5PARTY_SITE_NAMEUser-defined site nameVARCHAR2
6STATUSSite status flagVARCHAR2
7IDENTIFYING_ADDRESS_FLAGWhether this is the party's identifying address — the row denormalized onto the party masterVARCHAR2
8OVERALL_PRIMARY_FLAGThe party's primary address regardless of contextVARCHAR2
9ADDRESSEEAddressee line printed above the addressVARCHAR2
10START_DATE_ACTIVESite effective-from dateDATE
11END_DATE_ACTIVESite effective-to dateDATE
12ORIG_SYSTEM_REFERENCELegacy-system site keyVARCHAR2

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.

Query parameters
-- ============================================================
-- 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

  • HZ_CUST_ACCT_SITES_ALLHZ_PARTY_SITESforeign key · N:1
    ON HZ_CUST_ACCT_SITES_ALL.PARTY_SITE_ID = HZ_PARTY_SITES.PARTY_SITE_ID
  • HZ_PARTY_SITESHZ_PARTIESforeign key · N:1
    ON HZ_PARTY_SITES.PARTY_ID = HZ_PARTIES.PARTY_ID
  • HZ_PARTY_SITESHZ_LOCATIONSforeign key · N:1
    ON HZ_PARTY_SITES.LOCATION_ID = HZ_LOCATIONS.LOCATION_ID

Browse 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 Fusion Cloud Applications are registered trademarks of Oracle and/or its affiliates.