Results for “igc_cc_arc_headers”

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

Overview

PO_VENDOR_CONTACTS is the Oracle Purchasing (PO) transactional table that stores supplier contact records associated with a supplier site. In Oracle E-Business Suite 12.1.1 and 12.2.2, this table underpins the "Contacts" region of the supplier site definition, storing the individuals at a vendor site who may be referenced on purchasing documents such as purchase orders, RFQs, quotations, requisitions, and sourcing events. It is the operational source for the contact name, telephone and address information surfaced on the printed and electronically transmitted procurement document.

The documented primary key is the PO_VENDOR_CONTACTS_PK constraint, defined on VENDOR_CONTACT_ID. The record's parent is the supplier site: the table carries a foreign key VENDOR_SITE_ID referencing PO_VENDOR_SITES_ALL. Based on the mined foreign-key topology — a single parent reference downward and numerous child references upward — the object exhibits a hub-leaning Data Vault classification. In a dimensional or Data Vault model this would be treated as a hub (or a satellite of the supplier site hub) for supplier contacts, with the many inbound references acting as link and satellite relationships.

Key Information Stored

The table's distinguishing column is VENDOR_CONTACT_ID, the surrogate primary key generated for each contact record. The business-key candidate that links a contact to its owning supplier location is VENDOR_SITE_ID, which is also the documented foreign key to PO_VENDOR_SITES_ALL. This pairing — the surrogate VENDOR_CONTACT_ID and the foreign-key VENDOR_SITE_ID — is the structural core of the record and the basis for nearly every join into the table.

The remaining attributes describe the person and their communication details: the contact's first and last name (or full name), job title, telephone number, fax number, and electronic mail address, together with the contact's purchasing-related role or responsibility at the site. Additional descriptive and audit columns, such as the enabled/inactive status flag, the effective dates of the contact record, and the standard Oracle Who columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY), complete the row. Documentation for this database instance notes the table as "Not implemented in this database," meaning the object is defined by the ETRM reference but is not populated in that specific instance; the physical structure remains consistent across standard 12.1.1 and 12.2.2 environments.

Common Use Cases and Queries

The most frequent use of the table is reporting and resolving the contact person on a procurement document. Because PO_HEADERS_ALL carries a VENDOR_CONTACT_ID, an analyst can join the document to its contact as follows:

• Contact lookup for a purchase order: join PO_HEADERS_ALL to PO_VENDOR_CONTACTS on VENDOR_CONTACT_ID to return the supplier contact name, telephone, and e-mail for a given PO.
• Site-level contact listing: query PO_VENDOR_CONTACTS filtering by VENDOR_SITE_ID to enumerate all active contacts at a supplier site, typically used for supplier master data validation and cleanup.
• Sourcing and RFQ reporting: join through PO_RFQ_VENDORS.VENDOR_CONTACT_ID to identify the contact addressed on each RFQ, and through PO_VENDOR_LIST_ENTRIES.VENDOR_CONTACT_ID to resolve the contact on a sourcing vendor list entry.
• Requisition and requisition-express analysis: PO_REQUISITION_LINES_ALL.VENDOR_CONTACT_ID and PO_REQEXPRESS_LINES_ALL.SUGGESTED_VENDOR_CONTACT_ID identify the requested or suggested contact on demand lines, supporting spend and sourcing audits.

Because the contact record is frequently duplicated and later inactivated by purchasing users, reconciliation queries commonly compare the contact referenced on a document against the contacts currently active at the associated site, flagging references to inactive contacts.

Related Objects

• PO_VENDOR_SITES_ALL — parent supplier site; joined on PO_VENDOR_CONTACTS.VENDOR_SITE_ID.
• PO_HEADERS_ALL and PO_HEADERS_ARCHIVE_ALL — purchase order headers; joined on VENDOR_CONTACT_ID to identify the document's supplier contact.
• PO_RFQ_VENDORS — RFQ-to-supplier assignment; joined on VENDOR_CONTACT_ID to resolve the RFQ contact.
• PO_VENDOR_LIST_ENTRIES — sourcing vendor list entry; joined on VENDOR_CONTACT_ID to resolve the listed contact.
• PO_REQUISITION_LINES_ALL, PO_REQUISITIONS_INTERFACE_ALL, and PO_REQEXPRESS_LINES_ALL — requisition lines and interfaces; joined on VENDOR_CONTACT_ID or SUGGESTED_VENDOR_CONTACT_ID.
• IGC_CC_HEADERS, IGC_CC_ARC_HEADERS, and IGC_CC_HEADERS_INTERFACE — Grants/Contracts Commitment Control extension tables; joined on VENDOR_CONTACT_ID.
• OKL_CURE_REPORTS — Oracle Lease Management reporting structure; joined on VENDOR_CONTACT_ID.

Together these relationships make PO_VENDOR_CONTACTS a central reference point for supplier contact information across procurement, sourcing, and contracting flows in Oracle EBS.