Results for “ap_suppliers_int”

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

Overview

AP_SUPPLIERS_INT is the Supplier Open Interface staging table in the Oracle Payables (AP) module, owned by the AP schema. It holds supplier header information loaded by users or external systems for import into Oracle E-Business Suite. The columns in this table map directly to corresponding columns in the PO_VENDORS table, which is the production supplier master. Oracle Payables reads the records staged here and creates new supplier records, or applies updates to existing suppliers, during the Supplier Open Interface import process. The table is documented as VALID and contains 165 columns in Oracle EBS 12.2.2, with a comparable footprint in 12.1.1.

The Data Vault classification (heuristic, mined from FK structure) for this table is standalone. In modeling terms, this suggests the table behaves as an interface or staging satellite rather than a true hub or link. Its primary key, VENDOR_INTERFACE_ID, is a surrogate identifier generated for each interface row, and it is not a durable business key. The table does carry audit and program context columns, which reinforces its role as a transient loading structure rather than a permanent master data entity.

Key Information Stored

The primary key is VENDOR_INTERFACE_ID, defined by the AP_SUPPLIERS_INT_PK constraint. This is the surrogate key that uniquely identifies each staged supplier row and is the value users search on when troubleshooting import batches. The principal business-identifying columns are VENDOR_NAME, VENDOR_NAME_ALT, and SEGMENT1, which together describe the supplier as it will appear in PO_VENDORS. The column VENDOR_TYPE_LOOKUP_CODE classifies the supplier (for example, employee, external, or one-time).

Payment and accounting attributes form the core of the record: TERMS_ID and TERMS_NAME define payment terms, SET_OF_BOOKS_ID anchors the supplier to a ledger, INVOICE_CURRENCY_CODE and PAYMENT_CURRENCY_CODE set currency defaults, and ACCTS_PAY_CODE_COMBINATION_ID and PREPAY_CODE_COMBINATION_ID hold the liability and prepayment accounting flexfield combinations. Distribution defaults rest in DISTRIBUTION_SET_ID and DISTRIBUTION_SET_NAME. Purchasing behavior is governed by columns such as SHIP_TO_LOCATION_ID, BILL_TO_LOCATION_ID, FREIGHT_TERMS_LOOKUP_CODE, FOB_LOOKUP_CODE, PAY_GROUP_LOOKUP_CODE, and PAYMENT_PRIORITY.

Process-control columns distinguish interface rows from production rows. IMPORT_REQUEST_ID ties the staged record to the concurrent request that processed it, while STATUS and REJECT_CODE report success or the reason for import failure. Standard audit columns include LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, and CREATED_BY. The fifteen ATTRIBUTE and twenty GLOBAL_ATTRIBUTE columns provide extensibility, and the PARTY_ID, PARTY_ORIG_SYSTEM, and PARTY_ORIG_SYSTEM_REFERENCE columns link the supplier to the TCA party model introduced in R12.

Common Use Cases and Queries

The primary use case is bulk supplier creation or migration. Data is inserted into AP_SUPPLIERS_INT, then the Supplier Open Interface concurrent program is submitted to validate and transfer the records into PO_VENDORS and the supplier sites tables. Querying the table before running the import is a standard validation step.

• Locating a staged supplier by interface key: SELECT vendor_interface_id, vendor_name, status, reject_code FROM ap.ap_suppliers_int WHERE vendor_interface_id = :id;
• Reviewing failed import rows for a batch: SELECT vendor_interface_id, vendor_name, reject_code FROM ap.ap_suppliers_int WHERE import_request_id = :request_id AND status = 'REJECTED';
• Reporting staged suppliers by ledger and terms: SELECT vendor_name, set_of_books_id, terms_name FROM ap.ap_suppliers_int WHERE set_of_books_id = :sob;

Because the table is a transient staging area, records are typically purged after successful import. Reports should therefore be run while the interface rows are still present, or reconstructed from the corresponding PO_VENDORS records after completion.

Related Objects

The table participates in a small but important dependency chain centered on the VENDOR_INTERFACE_ID surrogate key.

• PO_VENDORS — the production supplier master that AP_SUPPLIERS_INT columns map to; the import process writes here.
• AP_SUPPLIER_SITES_INT — references AP_SUPPLIERS_INT via VENDOR_INTERFACE_ID; holds staged supplier site records.
• AP_SUP_SITE_CONTACT_INT — references AP_SUPPLIERS_INT via VENDOR_INTERFACE_ID; holds staged site contact records.
• PSB_EMPLOYEES — referenced by AP_SUPPLIERS_INT.EMPLOYEE_ID for employee-type suppliers.
• Supplier Open Interface program (APXSUIMP) — the concurrent program that consumes these rows and creates suppliers.
• HZ_PARTIES — the TCA party record reached through PARTY_ID, PARTY_ORIG_SYSTEM, and PARTY_ORIG_SYSTEM_REFERENCE.

The dependency of AP_SUPPLIER_SITES_INT and AP_SUP_SITE_CONTACT_INT on the header interface key means the header row must exist before its sites and contacts can be staged, mirroring the parent-child structure of the final supplier model.