Search Results ap_supplier_contacts_n2

Overview

AP.AP_SUPPLIER_CONTACTS is the Oracle Payables base table that stores contact records associated with supplier sites in Oracle E-Business Suite Release 12.1.1 and 12.2.2. Each row represents an individual person or organizational contact attached to a supplier site, capturing the name, telephone, fax, e-mail, and descriptive attributes used throughout procurement, payables, and purchasing transactions. The table is registered under FND Design Data as SQLAP.AP_SUPPLIER_CONTACTS, resides in the APPS_TS_TX_DATA tablespace with PCT Free 10, and carries a VALID status in the ETRM catalog. Oracle classifies this object as Oracle Internal Use Only and does not support direct data access outside standard Applications programs.

From a Data Vault modeling perspective, the metadata heuristically classifies AP_SUPPLIER_CONTACTS as satellite-leaning. It is not a pure reference hub; instead it behaves as a descriptive satellite hanging off the supplier site entity, with additional link-like behavior introduced by the party-model columns PER_PARTY_ID, RELATIONSHIP_ID, REL_PARTY_ID, PARTY_SITE_ID, ORG_CONTACT_ID, and ORG_PARTY_SITE_ID. This classification is a modeling suggestion only and reflects the 12.2 party and relationship extensions layered onto the classic supplier contact model.

The unique index AP_SUPPLIER_CONTACTS_U1 on VENDOR_CONTACT_ID serves as the documented business-key candidate, while the primary key AP_SUPPLIER_CONTACTS_PK is also defined on VENDOR_CONTACT_ID. Nine non-unique indexes support lookups by site, name, and party relationship identifiers.

Key Information Stored

The most significant columns include:

• VENDOR_CONTACT_ID — the surrogate primary key and the column behind the unique index AP_SUPPLIER_CONTACTS_U1; uniquely identifies each contact row.
• VENDOR_SITE_ID — foreign key to AP.AP_SUPPLIER_SITES_ALL; the supplier site to which the contact belongs, and the basis of AP_SUPPLIER_CONTACTS_N1.
• FIRST_NAME, MIDDLE_NAME, LAST_NAME, PREFIX — name components; indexed separately by AP_SUPPLIER_CONTACTS_N2 and N3 on FIRST_NAME and LAST_NAME.
• TITLE, DEPARTMENT, MAIL_STOP — organizational and delivery routing information.
• AREA_CODE, PHONE, ALT_AREA_CODE, ALT_PHONE, FAX_AREA_CODE, FAX — primary and alternate telephone and facsimile numbers.
• EMAIL_ADDRESS, URL — electronic contact details.
• INACTIVE_DATE — effective-dating marker for retiring a contact.
• PER_PARTY_ID, RELATIONSHIP_ID, REL_PARTY_ID, PARTY_SITE_ID, ORG_CONTACT_ID, ORG_PARTY_SITE_ID — the 12.2 party and relationship model columns, each indexed (N4 through N9).
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — the standard Oracle descriptive flexfield (DFF) container.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — standard WHO audit columns.
• REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — concurrent program traceability columns.

Common Use Cases and Queries

Typical usage includes supplier contact list reporting, procurement buyer lookups, and integration extracts to external supply-chain or ERP systems. A representative query retrieving all active contacts for a supplier site is:

• SELECT vendor_contact_id, first_name, last_name, area_code, phone, email_address FROM ap.ap_supplier_contacts WHERE vendor_site_id = :p_site_id AND (inactive_date IS NULL OR inactive_date > SYSDATE);
• Joining to the site and supplier hierarchies: SELECT c.last_name, s.vendor_site_code, v.vendor_name FROM ap.ap_supplier_contacts c, ap.ap_supplier_sites_all s, ap.ap_suppliers v WHERE c.vendor_site_id = s.vendor_site_id AND s.vendor_id = v.vendor_id;
• Lookup by party model key: SELECT vendor_contact_id FROM ap.ap_supplier_contacts WHERE per_party_id = :party_id;
• Reverse lookup by unique key: SELECT * FROM ap.ap_supplier_contacts WHERE vendor_contact_id = :contact_id;

Because Oracle restricts supported access, these patterns should generally be exercised through standard supplier APIs or public views rather than direct DML.

Related Objects

The most significant related objects, drawn from the documented foreign-key relationships and party model, are:

• AP.AP_SUPPLIER_SITES_ALL — parent of AP_SUPPLIER_CONTACTS through VENDOR_SITE_ID.
• OKL_CURE_REPORTS_ALL — references AP_SUPPLIER_CONTACTS via VENDOR_CONTACT_ID; one of the few downstream dependencies recorded.
• AP.AP_SUPPLIERS — reached indirectly through AP_SUPPLIER_SITES_ALL to obtain supplier header attributes.
• HZ_PARTIES / HZ_PARTY_SITES — referenced conceptually by PER_PARTY_ID and PARTY_SITE_ID, supporting the 12.2 party model integration.
• HZ_RELATIONSHIPS — the relationship definition referenced by RELATIONSHIP_ID and REL_PARTY_ID.
• AP_SUPPLIER_CONTACTS_U1 through _N9 — the supporting index objects enabling keyed and name-based access.

These relationships confirm that the table sits between the supplier-site reference structure and the wider Trading Community Architecture party model.