Skip to content
Fusion Reference

HZ_PARTIES

Product: HZmaster

The 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

Notes

Global — no BU, org, or set striping anywhere in the TCA party layer. PARTY_TYPE is Person/Organization/Group. The address and contact columns here are denormalized copies of the identifying address — the real address spine is party site → location. Suppliers resolve here too: the supplier master's PARTY_ID is where the supplier name lives (see quirks #tca-layers).

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.PartyExtractPVO
    OTBI: Sales - CRM Customers and Contacts Real Time

    Party data store — keyed on PartyId. Lives in the CX extract book under the CrmAnalyticsAM root (TCA is a CX-owned product family in Fusion).

    Oracle data-store documentation →

Fields

15 fields · 1 key

Table fields: position, field name, description, data type, and flags. 15 fields.
#FieldDescriptionTypeFlags
1PARTY_IDSurrogate key of the party — what customers, suppliers, and sites all resolve toNUMBER
Key
2PARTY_NUMBERThe party's unique numberVARCHAR2
3PARTY_NAMEThe party's name — the customer or supplier display name reports actually wantVARCHAR2
4PARTY_TYPEPerson, Organization, or GroupVARCHAR2
5STATUSParty status flag — values not enumerated in the dictionaryVARCHAR2
6CATEGORY_CODEUser-defined party categoryVARCHAR2
CUSTOMER_CATEGORY
7DUNS_NUMBER_CD&B DUNS number — stored as text, not validated to nine digitsVARCHAR2
8JGZZ_FISCAL_CODETax / fiscal registration identifierVARCHAR2
9EMAIL_ADDRESSPrimary email — a denormalized copy of the contact pointVARCHAR2
10PRIMARY_PHONE_NUMBERPrimary phone in local format — no country or area codeVARCHAR2
11ADDRESS1First line of the denormalized identifying addressVARCHAR2
12CITYCity of the identifying addressVARCHAR2
13COUNTRYCountry of the identifying address (territory code)VARCHAR2
14VALIDATED_FLAGWhether the party has been validatedVARCHAR2
15ORIG_SYSTEM_REFERENCELegacy-system key the party was migrated underVARCHAR2

Field provenance: hand-curated. 1 key field.

Boilerplate SQL

Starting point for reading the BICC-landed copy of HZ_PARTIESon 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_PARTIES — The 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
-- Purpose: Column-selected read of HZ_PARTIES — auto-generated from field metadata
-- Grain  : One row per PARTY_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_ID AS "Surrogate key of the party — what customers, suppliers, and sites all resolve to",
  t.PARTY_NUMBER AS "The party's unique number",
  t.PARTY_NAME AS "The party's name — the customer or supplier display name reports actually want",
  t.PARTY_TYPE AS "Person, Organization, or Group",
  t.STATUS AS "Party status flag — values not enumerated in the dictionary",
  t.CATEGORY_CODE AS "User-defined party category",  -- decode t.CATEGORY_CODE via FND_LOOKUP_VALUES (LOOKUP_TYPE = 'CUSTOMER_CATEGORY', LANGUAGE-filtered)
  t.DUNS_NUMBER_C AS "D&B DUNS number — stored as text, not validated to nine digits",
  t.JGZZ_FISCAL_CODE AS "Tax / fiscal registration identifier",
  t.EMAIL_ADDRESS AS "Primary email — a denormalized copy of the contact point",
  t.PRIMARY_PHONE_NUMBER AS "Primary phone in local format — no country or area code",
  t.ADDRESS1 AS "First line of the denormalized identifying address",
  t.CITY AS "City of the identifying address",
  t.COUNTRY AS "Country of the identifying address (territory code)",
  t.VALIDATED_FLAG AS "Whether the party has been validated",
  t.ORIG_SYSTEM_REFERENCE AS "Legacy-system key the party was migrated under"
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>'  -- the column incremental BICC extracts key on
ORDER BY t.PARTY_ID;

4 parameters not filled: <catalog>, <schema>, <PARTY_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_ACCOUNTSHZ_PARTIESforeign key · N:1
    ON HZ_CUST_ACCOUNTS.PARTY_ID = HZ_PARTIES.PARTY_ID
  • HZ_CUST_ACCOUNTSHZ_PARTIESforeign key · N:1
    ON HZ_CUST_ACCOUNTS.SELLING_PARTY_ID = HZ_PARTIES.PARTY_ID
  • HZ_PARTY_SITESHZ_PARTIESforeign key · N:1
    ON HZ_PARTY_SITES.PARTY_ID = HZ_PARTIES.PARTY_ID
  • POZ_SUPPLIERSHZ_PARTIESforeign key · N:1
    ON POZ_SUPPLIERS.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 →

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.