HZ_PARTIES
Trading Community Architecture (TCA) party master — the underlying person or organization, independent of any role (customer, supplier, contact) it plays.
Key Columns
Child Tables
Common Joins
HZ_CUST_ACCOUNTSvia PARTY_IDThe customer account(s) created for this party — a party only becomes a transactable 'customer' once an account exists against it.
HZ_PARTY_SITESvia PARTY_IDThe physical site(s)/addresses associated with this party.
HZ_RELATIONSHIPSvia PARTY_ID = OBJECT_ID (as the org side) or PARTY_ID = SUBJECT_ID (as the person side)Relationships this party has to other parties — e.g. which people are contacts for this organization.
Used In
Notes
TCA is shared infrastructure — the same HZ_PARTIES table underlies customers, suppliers and other party types across Fusion; a party's role is determined by which account/registration tables reference it, not by a column on this table.
Related
Customer / Trading Community data model
Oracle Fusion models customers through Trading Community Architecture (TCA): a HZ_PARTIES record is the underlying person or organization, which becomes a transactable customer once a HZ_CUST_ACCOUNTS row exists against it. Addresses live on HZ_PARTY_SITES at the party level, and are assigned to a specific account (HZ_CUST_ACCT_SITES_ALL) with a business purpose like Bill-To or Ship-To (HZ_CUST_SITE_USES_ALL) — those site-use records are what AR and Order Management actually default onto a transaction.
Party contacts (people) for a customer/organization
A 'contact' in TCA is a person party related to an organization party — never a single 'HZ_CONTACTS' table, and HZ_PARTY_SITES is not it either (that's addresses only, no phone/email). The relationship itself lives on HZ_RELATIONSHIPS (SUBJECT_ID = the person's PARTY_ID, OBJECT_ID = the organization's PARTY_ID, RELATIONSHIP_TYPE identifying it as a contact relationship), specialized by a HZ_ORG_CONTACTS row (PARTY_RELATIONSHIP_ID = the relationship, plus role attributes like JOB_TITLE). The contact person's actual phone/email lives separately on HZ_CONTACT_POINTS (OWNER_TABLE_ID = the person's PARTY_ID, OWNER_TABLE_NAME = 'HZ_PARTIES', CONTACT_POINT_TYPE = 'PHONE' or 'EMAIL'). So a full 'contacts with phone/email for this org' query joins HZ_PARTIES (org) -> HZ_RELATIONSHIPS -> HZ_ORG_CONTACTS, plus HZ_PARTIES again (for the contact's own name) -> HZ_CONTACT_POINTS (for that contact's phone/email) — five tables, not three.