Results for “hz_org_contacts”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

HZ_ORG_CONTACTS is the Oracle E-Business Suite table that stores people who act as contacts for parties. It resides in the AR (Receivables) schema, is owned by the Oracle Trading Community Architecture (TCA) data model, and holds a status of VALID in both 12.1.1 and 12.2.2. Each row represents an organizational contact — an individual associated with a party, party site, or party relationship — and carries descriptive information such as job title, department, contact ranking, and decision-maker status. The table is central to TCA because contacts are consumed by Order Management, Advanced Sales, Resource Management, and event registration flows.

From a dimensional modeling perspective, the documented foreign key structure classifies HZ_ORG_CONTACTS as hub-leaning. It behaves primarily as a hub entity keyed by a surrogate identifier, with satellite-style descriptive attributes and link-style references to HZ_PARTY_RELATIONSHIPS, HZ_RELATIONSHIPS, and HZ_PARTY_SITES.

Key Information Stored

The primary key is the surrogate column ORG_CONTACT_ID, enforced by the constraint HZ_ORG_CONTACTS_PK and backed by the unique index HZ_ORG_CONTACTS_U1. This is the single documented unique business-key candidate; there is no separate natural key column defined in the metadata.

• PARTY_RELATIONSHIP_ID — the relationship record that ties the contact to a party; the principal linkage into the TCA relationship model.
• PARTY_SITE_ID — the party site at which the contact is registered, supporting site-specific contact assignment.
• CONTACT_NUMBER — user-facing identifier for the contact.
• CONTACT_KEY — alternate reference key used for integration and staging.
• TITLE / JOB_TITLE / JOB_TITLE_CODE — the contact's role or position within the organization.
• DEPARTMENT / DEPARTMENT_CODE — organizational department assignment.
• DECISION_MAKER_FLAG — indicates whether the contact has purchasing or decision authority.
• RANK — priority ordering of contacts for a party.
• STATUS — active/inactive lifecycle state of the contact record.
• MANAGED_BY — ownership or administration indicator for the contact.
• MAIL_STOP and MAILING_ADDRESS_ID — internal mail routing and mailing address reference.
• OBJECT_VERSION_NUMBER — optimistic locking column used by the TCA APIs.
• WHO columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN.
• ATTRIBUTE1–ATTRIBUTE24 and GLOBAL_ATTRIBUTE1–GLOBAL_ATTRIBUTE20 — extensibility (DDF) columns for customer-defined data.
• ORIG_SYSTEM_REFERENCE — identifies the source system for imported contacts.

Common Use Cases and Queries

The table is used to retrieve contact details for customers and prospects, to populate order fulfillment contact references, and to drive Resource Manager linkage for sales representatives. A typical query joins contacts to their party relationship and site:

• SELECT oc.org_contact_id, oc.contact_number, oc.job_title FROM hz_org_contacts oc WHERE oc.party_site_id = :site_id AND oc.status = 'A';
• Join to HZ_ORG_CONTACT_ROLES on ORG_CONTACT_ID to retrieve role assignments for a contact.
• Join to HZ_PARTY_RELATIONSHIPS on PARTY_RELATIONSHIP_ID to resolve the owning party.
• Filter by DECISION_MAKER_FLAG = 'Y' for sales targeting and lead qualification reports.
• Join to JTF_RS_RESOURCE_EXTNS on CONTACT_ID to reconcile contacts with Resource Manager resources.

Because Object Version Number and WHO columns are maintained through the TCA APIs, direct DML should be avoided; use the public contact APIs for creation and update.

Related Objects

• HZ_PARTY_RELATIONSHIPS — referenced via PARTY_RELATIONSHIP_ID; defines the contact's party context.
• HZ_RELATIONSHIPS — also referenced via PARTY_RELATIONSHIP_ID for the underlying relationship definition.
• HZ_PARTY_SITES — referenced via PARTY_SITE_ID; site-level contact assignment.
• HZ_ORG_CONTACT_ROLES — child table keyed by ORG_CONTACT_ID holding contact role assignments.
• HZ_STAGED_CONTACT_POINTS / HZ_STAGED_PARTY_SITES — staging tables referencing ORG_CONTACT_ID during import.
• AS_LEAD_CONTACTS_ALL and AS_INTERESTS_ALL — link contacts into sales lead and interest tracking via CONTACT_ID.
• AMS_EVENT_REGISTRATIONS — references contacts as registrant, attendant, and original registrant.
• OE_LINES_IFACE_ALL — references contacts for ship-to, invoice-to, deliver-to, and end-customer roles.
• JTF_RS_RESOURCE_EXTNS — maps contacts into Resource Manager via CONTACT_ID.