Results for “ap_supplier_sites_int_all”

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

Overview

AP_SUPPLIER_SITES_INT (also documented as AP_SUPPLIER_SITES_INT_ALL) is an Oracle Payables interface table that holds supplier site information loaded by users for import. Its columns map directly to corresponding columns in PO_VENDOR_SITES_ALL, and the Oracle Payables application consumes this information during supplier import processing to create or update supplier sites in the base supplier tables. The table resides in the AP schema and is part of the AP - Payables product module.

In Oracle EBS 12.1.1 and 12.2.2, this table functions as a staging area: records are inserted, validated, and then processed by the Supplier Open Interface concurrent program, which applies the records to the production supplier site tables and writes back a processing status. With 185 documented columns in ETRM 12.2.2, the table closely mirrors the structure of the destination supplier site entity.

From a Data Vault modeling perspective, the mined foreign key structure suggests a satellite-leaning classification. The table references parent interface entities rather than acting as an independent hub, which is consistent with its role as a dependent interface staging object.

Key Information Stored

The table carries both surrogate and business identifiers, along with a wide range of site attributes:

• VENDOR_SITE_INTERFACE_ID — the surrogate primary key for the interface record itself.
• VENDOR_INTERFACE_ID — foreign key to AP_SUPPLIERS_INT, linking the site to its parent supplier interface record.
• VENDOR_ID — the supplier identifier in the base supplier tables.
• VENDOR_SITE_CODE and VENDOR_SITE_CODE_ALT — the supplier site business key and its alternate.
• ORG_ID — the operating unit that owns the site record.
• PAY_SITE_FLAG, PURCHASING_SITE_FLAG, RFQ_ONLY_SITE_FLAG — site usage indicators.
• TERMS_ID / TERMS_NAME — payment terms assignment.
• PAYMENT_METHOD_LOOKUP_CODE and PAYMENT_CURRENCY_CODE — payment configuration.
• INVOICE_CURRENCY_CODE — invoicing currency default.
• STATUS and REJECT_CODE — interface processing status and error disposition.
• IMPORT_REQUEST_ID — the concurrent request that submitted the import.
• REQUEST_ID, PROGRAM_ID, PROGRAM_APPLICATION_ID — standard concurrent program audit columns.

Business-key candidates center on the combination of supplier and site code; the STATUS column distinguishes successfully imported rows from those requiring correction.

Common Use Cases and Queries

The primary use case is bulk supplier site migration or creation. ETL routines populate the table, then the Supplier Open Interface program is submitted to process pending rows. Typical operational queries include:

• Monitoring pending versus rejected rows: SELECT * FROM ap.ap_supplier_sites_int WHERE status = 'REJECTED';
• Correlating sites to their parent supplier: joining on VENDOR_INTERFACE_ID to AP_SUPPLIERS_INT.
• Auditing import loads by IMPORT_REQUEST_ID to trace which concurrent request created which site records.
• Reviewing reject reasons via REJECT_CODE to guide correction of address, currency, or payment data before resubmission.

Reporting scenarios include reconciliation of imported sites against PO_VENDOR_SITES_ALL, validation of operating unit assignment via ORG_ID, and verification of payment fields before records reach production.

Related Objects

The documented foreign keys and interface dependencies establish these key relationships:

• AP_SUPPLIERS_INT — parent supplier interface table, joined on VENDOR_INTERFACE_ID.
• AP_TOLERANCE_TEMPLATES — referenced by TOLERANCE_ID.
• PO_VENDOR_SITES_ALL — destination table to which interface rows are applied.
• PO_VENDORS — supplier master for vendor-level associations.
• AP_SUPPLIER_INT_REJECTIONS — captures rejection messages generated during import.
• IBY_PAYMENT_INSTRUCTIONS — related payment configuration carried by the EDI and bank instruction columns.
• HZ_PARTY_SITES / HZ_LOCATIONS — TCA entities referenced through PARTY_SITE_ID and LOCATION_ID.