OracleOps AI
← All tables
Oracle Fusion/Financials/Customers

HZ_CONTACT_POINTS

Actual contact-method details (phone, email, etc.) for a party — this, not HZ_PARTY_SITES, is where phone/email actually live.

Key Columns

CONTACT_POINT_IDOWNER_TABLE_NAMEOWNER_TABLE_IDCONTACT_POINT_TYPEPHONE_NUMBEREMAIL_ADDRESS

Common Joins

HZ_PARTIESvia OWNER_TABLE_ID = PARTY_ID (where OWNER_TABLE_NAME = 'HZ_PARTIES')

The party (e.g. a contact person) this phone/email belongs to — OWNER_TABLE_ID is a polymorphic FK, so OWNER_TABLE_NAME must be filtered too.

Used In

CustomersAR

Notes

Fusion stores phone/email largely inline on this one table (CONTACT_POINT_TYPE = 'PHONE' or 'EMAIL', with PHONE_NUMBER/EMAIL_ADDRESS columns) rather than requiring separate attribute sub-tables the way EBS-era TCA did.

Related

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.

Ask Oracle AI about HZ_CONTACT_POINTS