Skip to content
EBS Reference

HZ_PARTIES

Schema: ARmaster

The trading-community party master — one row per person, organization, or group before any commercial context; customers AND suppliers resolve back to a party here

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

A party is not a customer — the commercial relationship lives on the account layer, and one party can hold several accounts, so counting parties overcounts customers. PARTY_NAME is not unique; never join or dedupe on it. The address columns here are a denormalized convenience copy of the identifying address — the address master is the locations table.

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

14 fields · 1 key

14 fields.

Table fields: position, field name, description, data type, and flags. 14 fields.
#FieldDescriptionTypeFlags
1PARTY_IDSurrogate key of the party — what customer accounts and the supplier master resolve toNUMBER
Primary-key field
2PARTY_NUMBERThe unique party number users seeVARCHAR2
3PARTY_NAMEThe party's name — NOT unique; never a join or dedupe keyVARCHAR2
4PARTY_TYPEOrganization, person, group, or relationship (per the data dictionary's comment)VARCHAR2
5STATUSA = active, I = inactive — party merges can leave other single-letter states; verify beyond A/I on your instanceVARCHAR2
6ORIG_SYSTEM_REFERENCEThe legacy/source-system key the party was created fromVARCHAR2
7VALIDATED_FLAGWhether the party has been validatedVARCHAR2
8CREATED_BY_MODULEWhich application created the partyVARCHAR2
9PERSON_FIRST_NAMEFirst name, on person-type partiesVARCHAR2
10PERSON_LAST_NAMELast name, on person-type partiesVARCHAR2
11ADDRESS1Denormalized identifying-address line — a convenience copy, not the address masterVARCHAR2
12COUNTRYIdentifying-address country (territory code)VARCHAR2
13SIC_CODEIndustry classification codeVARCHAR2
14DUNS_NUMBER_CD-U-N-S number, character formVARCHAR2

Field provenance: hand-curated. 1 key field.

Boilerplate SQL

Starting point for reading HZ_PARTIES 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_ID>, <watermark>

-- ============================================================
-- Table  : HZ_PARTIES — The trading-community party master — one row per person, organization, or group before any commercial context; customers AND suppliers resolve back to a party here
-- Purpose: Column-selected read of HZ_PARTIES — auto-generated from field metadata
-- Grain  : One row per PARTY_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_ID AS "Surrogate key of the party — what customer accounts and the supplier master resolve to",
  t.PARTY_NUMBER AS "The unique party number users see",
  t.PARTY_NAME AS "The party's name — NOT unique; never a join or dedupe key",
  t.PARTY_TYPE AS "Organization, person, group, or relationship (per the data dictionary's comment)",
  t.STATUS AS "A = active, I = inactive — party merges can leave other single-letter states; verify beyond A/I on your instance",
  t.ORIG_SYSTEM_REFERENCE AS "The legacy/source-system key the party was created from",
  t.VALIDATED_FLAG AS "Whether the party has been validated",
  t.CREATED_BY_MODULE AS "Which application created the party",
  t.PERSON_FIRST_NAME AS "First name, on person-type parties",
  t.PERSON_LAST_NAME AS "Last name, on person-type parties",
  t.ADDRESS1 AS "Denormalized identifying-address line — a convenience copy, not the address master",
  t.COUNTRY AS "Identifying-address country (territory code)",
  t.SIC_CODE AS "Industry classification code",
  t.DUNS_NUMBER_C AS "D-U-N-S number, character form"
FROM <catalog>.<schema>.HZ_PARTIES t
WHERE
  1 = 1  -- no partition column on this table; the filters below are optional
  -- AND t.PARTY_ID = <PARTY_ID>
  -- AND t.LAST_UPDATE_DATE >= TIMESTAMP '<watermark>'  -- WHO watermark, bulk-stamped by batch jobs; see quirks guide #who-columns
ORDER BY t.PARTY_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_SUPPLIERSHZ_PARTIESforeign key · N:1
    ON AP_SUPPLIERS.PARTY_ID = HZ_PARTIES.PARTY_ID
  • PO_VENDORSHZ_PARTIESforeign key · N:1
    ON PO_VENDORS.PARTY_ID = HZ_PARTIES.PARTY_ID
  • HZ_CUST_ACCOUNTSHZ_PARTIESforeign key · N:1
    ON HZ_CUST_ACCOUNTS.PARTY_ID = HZ_PARTIES.PARTY_ID
  • HZ_PARTY_SITESHZ_PARTIESforeign key · N:1
    ON HZ_PARTY_SITES.PARTY_ID = HZ_PARTIES.PARTY_ID
  • AP_INVOICES_ALLHZ_PARTIESforeign key · N:1
    ON AP_INVOICES_ALL.PARTY_ID = HZ_PARTIES.PARTY_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.