Search Results supplier_org

Overview

The OKC_REP_PARTY_CONTACTS table is a core Contracts Core (OKC) repository object in Oracle E-Business Suite 12.1.1 and 12.2.2. It stores the contact records associated with a party on a contract, linking each contract party to one or more named individuals who serve as points of contact. Because a contract party can assume different roles (for example, a supplier, customer, or internal employee), the originating source of a given contact varies: contacts for a party whose role is SUPPLIER are drawn from PO_VENDOR_CONTACTS, while other contacts may originate from HZ_PARTIES or PER_PEOPLE_F. This design allows the Contracts application to present a unified contact list while preserving the authoritative source of each contact record.

The ETRM metadata classifies this object, using a heuristic derived from its foreign-key structure, as a link table in Data Vault terms. As a modeling suggestion, it should be treated as an associative entity that resolves relationships between contracts, parties, and contact roles rather than as an independent hub or a descriptive satellite.

Key Information Stored

The table contains 17 documented columns. The most significant are:

• PARTY_CONTACT_ID — the surrogate primary key, enforced by OKC_REP_PARTY_CONTACTS_PK. It uniquely identifies each contact association row.
• CONTRACT_ID — identifies the contract to which the party and contact belong.
• PARTY_ID — the party record with which the contact is associated.
• PARTY_ROLE_CODE — the role the party plays on the contract, which also determines the source system of the contact.
• CONTACT_ID — the identifier of the underlying contact record in the source table (PO_VENDOR_CONTACTS, HZ_PARTIES, or PER_PEOPLE_F).
• CONTACT_ROLE_ID — foreign key to OKC_REP_CONTACT_ROLES_B, describing the functional role of the contact (for example, signatory or technical contact).
• ESIGNATURE_TYPE and SIGNATURE_SEQUENCE — control electronic signature behavior and ordering for the contact.
• Standard WHO/audit columns — OBJECT_VERSION_NUMBER, CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, PROGRAM_ID, PROGRAM_LOGIN_ID, PROGRAM_APPLICATION_ID, and REQUEST_ID — support concurrency control, auditing, and concurrent program tracking.

A documented unique index, OKC_REP_PARTY_CONTACTS_U1, spans CONTRACT_ID, PARTY_ID, PARTY_ROLE_CODE, CONTACT_ID, and CONTACT_ROLE_ID, forming the business-key candidate that prevents duplicate contact-role assignments for the same party on the same contract.

Common Use Cases and Queries

Typical reporting scenarios include listing all contacts for a given contract, identifying signatories by role, and reconciling contract contacts back to their source systems.

• Retrieve every contact for a contract, joined to its role definition: SELECT c.*, r.NAME FROM OKC_REP_PARTY_CONTACTS c, OKC_REP_CONTACT_ROLES_B r WHERE c.CONTACT_ROLE_ID = r.CONTACT_ROLE_ID AND c.CONTRACT_ID = :contract_id;
• List contacts for a specific party and role: filter on PARTY_ID and PARTY_ROLE_CODE.
• Identify supplier contacts (those sourced from PO_VENDOR_CONTACTS) by constraining PARTY_ROLE_CODE.
• Determine electronic signature ordering using ESIGNATURE_TYPE and SIGNATURE_SEQUENCE for a signature workflow.
• Audit changes by filtering on LAST_UPDATE_DATE and LAST_UPDATED_BY.

Related Objects

The most significant related objects, based on documented foreign-key relationships, are:

• OKC_REP_CONTRACT_PARTIES — referenced via CONTRACT_PARTY_ID; the parent party-on-contract record.
• OKC_REP_CONTACT_ROLES_B — referenced via CONTACT_ROLE_ID; defines the contact role.
• PO_VENDOR_CONTACTS — authoritative source for supplier contacts.
• HZ_PARTIES — source for party-based contacts.
• PER_PEOPLE_F — source for internal employee contacts.

These relationships make OKC_REP_PARTY_CONTACTS the central link between contract structure, party roles, and contact master data within the OKC schema.