Skip to content
EBS Reference

HZ_PARTY_SITES

Schema: ARmaster

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

Identity
Module: Customers (TCA)Not org-partitioned
Notes

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
Schema: INV
Schema: the Oracle product schema that owns the table (INV, ONT, WSH, PO, BOM, WIP, MRP, MSC, AR, AP, GL, HR, APPLSYS) — tells you which product family the object belongs to, not who can query it.
master
Data class: what the table holds — master data, transaction documents, control/configuration, interface/staging, or an APPS-schema view.

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

OU-striped (ORG_ID)
Rows are scoped to an operating unit. A landed extract carries every operating unit’s rows — filter or join on ORG_ID, and don’t confuse it with ORGANIZATION_ID (see the quirks guide).
Per inventory org
Rows are scoped to an inventory organization (plant or warehouse) via ORGANIZATION_ID — a different partition from OU-striped tables (see the quirks guide).
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 (see the quirks guide).

Join & extract hazards — verify before you rely on this

View
This is an APPS-schema convenience view, not a physical table. Extract the base tables it joins instead — views can be slow at scale and aren't guaranteed stable across patches.
In field listings, the Key chip marks a primary-key field.

Fields

9 fields · 1 key

9 fields.

Table fields: position, field name, description, data type, and flags. 9 fields.
#FieldDescriptionTypeFlags
1PARTY_SITE_IDSurrogate key of the party siteNUMBER
Primary-key field
2PARTY_IDThe party at this addressNUMBER
3LOCATION_IDThe physical address — joins the location masterNUMBER
4PARTY_SITE_NUMBERThe unique site number users seeVARCHAR2
5PARTY_SITE_NAMEUser-defined site nameVARCHAR2
6STATUSA = active, I = inactiveVARCHAR2
7IDENTIFYING_ADDRESS_FLAGY marks the party's identifying (primary) address — the one denormalized onto the party rowVARCHAR2
8ORIG_SYSTEM_REFERENCEThe legacy/source-system keyVARCHAR2
9CREATED_BY_MODULEWhich application created the siteVARCHAR2

Field provenance: hand-curated. 1 key field.

Boilerplate SQL

Starting point for reading HZ_PARTY_SITES on Databricks — real DATE columns need no conversion, and the org anchor is already in place. The optional LAST_UPDATE_DATE watermark is included. 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 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;

Verified September 2026

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

  • AP_SUPPLIER_SITES_ALLHZ_PARTY_SITESforeign key · N:1
    ON AP_SUPPLIER_SITES_ALL.PARTY_SITE_ID = HZ_PARTY_SITES.PARTY_SITE_ID
  • 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 E-Business Suite are registered trademarks of Oracle and/or its affiliates.