Search Results ap_supplier_contacts_pk

Overview

AP_SUPPLIER_CONTACTS is a Payables-owned table in the AP schema that stores contact records associated with supplier sites. Each row represents an individual contact person at a supplier location, capturing name, telephone, fax, e-mail, and organizational attributes used throughout Oracle Purchasing, Payables, and iSupplier workflows. Contacts created here are available for selection on purchasing documents, payment processing, and supplier-facing communication.

Under a heuristic Data Vault classification mined from its foreign-key structure, AP_SUPPLIER_CONTACTS exhibits satellite-leaning behavior. The table is anchored by a single surrogate primary key and depends on AP_SUPPLIER_SITES_ALL through VENDOR_SITE_ID, with no dependent child tables of the same grain other than downstream reporting references. In a Data Vault model it would typically be modeled as a satellite attached to a supplier-site hub/link, with descriptive and date-based attributes carried as satellite columns.

Key Information Stored

The table contains 52 documented columns. The most operationally significant are the identifier, foreign-key, and descriptive attributes:

• VENDOR_CONTACT_ID — surrogate primary key, enforced by AP_SUPPLIER_CONTACTS_PK and uniquely indexed by AP_SUPPLIER_CONTACTS_U1. This is the business-key candidate referenced by downstream tables.
• VENDOR_SITE_ID — foreign key to AP_SUPPLIER_SITES_ALL, deterministically tying each contact to a supplier site.
• FIRST_NAME, MIDDLE_NAME, LAST_NAME, PREFIX, TITLE — name and honorific information for the contact.
• AREA_CODE, PHONE, ALT_AREA_CODE, ALT_PHONE, FAX_AREA_CODE, FAX — primary and alternate telephony and facsimile details.
• EMAIL_ADDRESS, URL — electronic contact identifiers.
• MAIL_STOP, DEPARTMENT — internal routing and organizational descriptors.
• INACTIVE_DATE — effective-date marker for contact retirement.
• PER_PARTY_ID, RELATIONSHIP_ID, REL_PARTY_ID, PARTY_SITE_ID, ORG_CONTACT_ID, ORG_PARTY_SITE_ID — TCA/party-model linkage columns supporting integrated party and organization contact records.
• AU audit columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–15 — descriptive flexfield storage.
• REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — concurrent-program audit context.

Common Use Cases and Queries

Typical reporting includes listing active contacts per supplier site, identifying a primary purchasing contact, and reconciling TCA party links. Because INACTIVE_DATE governs retirement, active contacts are those with a null or future INACTIVE_DATE.

A representative query joining the parent site table:

• SELECT c.VENDOR_CONTACT_ID, c.FIRST_NAME, c.LAST_NAME, c.EMAIL_ADDRESS, s.VENDOR_SITE_CODE FROM AP.AP_SUPPLIER_CONTACTS c JOIN AP.AP_SUPPLIER_SITES_ALL s ON s.VENDOR_SITE_ID = c.VENDOR_SITE_ID WHERE c.INACTIVE_DATE IS NULL ORDER BY s.VENDOR_SITE_CODE, c.LAST_NAME;

Common use cases include: supplier directory extracts for purchasing agents; e-mail distribution lists drawn from EMAIL_ADDRESS; verification of TCA party synchronization via PER_PARTY_ID; and reporting on OKL_CURE_REPORTS_ALL relationships that reference VENDOR_CONTACT_ID.

Related Objects

• AP_SUPPLIER_SITES_ALL — parent entity; join on AP_SUPPLIER_CONTACTS.VENDOR_SITE_ID = AP_SUPPLIER_SITES_ALL.VENDOR_SITE_ID.
• OKL_CURE_REPORTS_ALL — references this table through VENDOR_CONTACT_ID (OKL_CURE_REPORTS_ALL.VENDOR_CONTACT_ID → AP_SUPPLIER_CONTACTS.VENDOR_CONTACT_ID).
• AP_SUPPLIERS / AP_SUPPLIER_SITES_ALL hierarchy — supplier master via the site relationship.
• TCA party entities (HZ_PARTIES, HZ_PARTY_SITES) — logical links through PER_PARTY_ID, REL_PARTY_ID, PARTY_SITE_ID, ORG_CONTACT_ID, and ORG_PARTY_SITE_ID.
• PO_HEADERS_ALL / PO_VENDOR_SITES_ALL — purchasing documents consuming supplier-site contacts.
• AP supplier and contact APIs / iSupplier Portal views — consuming and maintaining contact data programmatically.