Results for “ap_sup_site_contact_int”

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

Overview

AP_SUP_SITE_CONTACT_INT is an Oracle Payables interface table that holds supplier contact data destined for creation or update of supplier contact records in Oracle E-Business Suite. The table resides in the AP schema and is documented as VALID in ETRM for release 12.2.2, with a physical definition of 54 columns. Its columns map directly to corresponding columns in the PO_VENDOR_CONTACTS table, and Oracle Payables consumes the rows to create supplier contact records during supplier import processing.

Functionally, the object is a staging and inbound interface entity for supplier site contacts. Rows are populated by external sources, conversion routines, or integration programs, then processed by the Payables supplier import concurrent program to validate and transfer contact data into the production supplier contact structures. In 12.1.1 and 12.2.2 the object also supports the party-model columns (PARTY_ID, PER_PARTY_ID, REL_PARTY_ID, and associated ORIG_SYSTEM attributes) that map contacts to the Trading Community Architecture (TCA) model.

From a heuristic Data Vault classification mined from the foreign key structure, AP_SUP_SITE_CONTACT_INT is treated as standalone rather than as a hub, link, or satellite. In modeling terms, this suggests the table behaves as a transient staging or interface entity rather than a durable core entity: it carries the descriptive attributes that would ultimately classify as satellite data in a downstream hub-and-link model, while its relationship to AP_SUPPLIERS_INT is an interface-level dependency rather than a persisted analytical relationship.

Key Information Stored

The table stores supplier contact attributes across personal, communication, and integration dimensions. The most significant columns are:

• VENDOR_CONTACT_INTERFACE_ID — the interface-level surrogate identifier for the contact row.
• VENDOR_INTERFACE_ID — foreign key to AP_SUPPLIERS_INT, tying the contact to its supplier interface record.
• VENDOR_ID — the supplier identifier to which the contact belongs.
• VENDOR_SITE_ID and VENDOR_SITE_CODE — the supplier site the contact is associated with.
• ORG_ID and OPERATING_UNIT_NAME — the operating unit context for multi-org processing.
• CONTACT_NAME_ALT, FIRST_NAME, MIDDLE_NAME, LAST_NAME, PREFIX, and TITLE — the contact's name and salutation components.
• DEPARTMENT and MAIL_STOP — organizational routing attributes.
• AREA_CODE, PHONE, ALT_AREA_CODE, ALT_PHONE, FAX_AREA_CODE, and FAX — communication details.
• EMAIL_ADDRESS and URL — electronic contact information.
• INACTIVE_DATE — effective dating for the contact record.
• STATUS and REJECT_CODE — interface processing outcome indicators.
• IMPORT_REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, REQUEST_ID, and SDH_BATCH_ID — audit and batch control columns.
• PARTY_ID, PER_PARTY_ID, REL_PARTY_ID, RELATIONSHIP_ID, and ORG_CONTACT_ID — TCA party-model linkage columns.

The documented metadata does not enumerate a unique index or declared primary key; VENDOR_CONTACT_INTERFACE_ID functions as the surrogate row identifier, while combinations such as VENDOR_SITE_ID with a contact name attribute serve as practical business-key candidates for matching during import.

Common Use Cases and Queries

The principal use case is supplier contact conversion and inbound integration. Inbound files or APIs populate AP_SUP_SITE_CONTACT_INT, then the Supplier Import program validates and transfers rows. Reporting and reconciliation queries typically monitor interface status and rejection reasons before and after the import run.

• Monitoring pending interface rows:
  SELECT vendor_interface_id, vendor_site_code, last_name, status, reject_code FROM ap.ap_sup_site_contact_int WHERE status IS NULL;
• Joining contacts to their supplier interface header:
  SELECT c.last_name, s.vendor_name FROM ap.ap_sup_site_contact_int c, ap.ap_suppliers_int s WHERE c.vendor_interface_id = s.vendor_interface_id;
• Tracking a batch by request:
  SELECT request_id, count(*) FROM ap.ap_sup_site_contact_int GROUP BY request_id;
• Identifying rejected records for correction:
  SELECT vendor_contact_interface_id, reject_code FROM ap.ap_sup_site_contact_int WHERE reject_code IS NOT NULL;

These patterns support data-quality review, pre-import reconciliation, and audit of integration activity across operating units.

Related Objects

The most significant related objects are those referenced by, or conceptually paired with, this interface table:

• AP_SUPPLIERS_INT — referenced through VENDOR_INTERFACE_ID, providing the supplier interface header.
• PO_VENDOR_CONTACTS — the destination table whose columns this interface table maps to.
• PO_VENDOR_SITES_ALL — supplier site records identified through VENDOR_SITE_ID and VENDOR_SITE_CODE.
• AP_SUPPLIERS — the production supplier entity associated via VENDOR_ID.
• TCA party objects (HZ_PARTIES and related party entities) linked through PARTY_ID, PER_PARTY_ID, and REL_PARTY_ID.
• The Oracle Payables Supplier Import concurrent program and associated supplier/contact open APIs, which consume this interface table and create the resulting supplier contact records.