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

Identity
Module: Customers (TCA)Not org-partitioned
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
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.

Structural facts — how the table is partitioned, not a trap by itself

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 with INVENTORY_ITEM_ID on 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_ID on the GL journal tables), or a named business-unit column (PRC_BU_ID / REQ_BU_ID in 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 LANGUAGE column (a _TL translation table or FND_LOOKUP_VALUES) — one row per language. Filter to one LANGUAGE or a join multiplies rows.

Join & extract hazards — verify before you rely on this

Date-effective
This is an _F table — one row per entity per effectivity window, with EFFECTIVE_START_DATE and EFFECTIVE_END_DATE part 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.
In field listings, the Key chip marks a key field — a member of the documented primary key or of a documented unique index.

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.

Fields

12 fields · 1 key

12 fields.

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_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.

Query parameters

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

  • 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

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.