Search Results ap_supplier_sites_u2

Overview

AP.AP_SUPPLIER_SITES_ALL is the supplier site master table within the Oracle Payables (AP) schema. Each row represents a unique combination of a supplier address, an operating unit, and the business relationship established with that supplier. Introduced as the replacement for the legacy PO_VENDOR_SITES_ALL table, it forms the operational backbone of supplier-facing transactions in Oracle E-Business Suite 12.1.1 and 12.2.2. Address information itself is no longer maintained in this table; instead, it is held in the Trading Community Architecture (TCA) and linked through AP_SUPPLIER_SITES_ALL.LOCATION_ID, with the associated party site referenced via PARTY_SITE_ID.

The table carries purchasing, invoicing, payment, tax, and general business attributes at the site level, making it the controlling record for how a supplier site behaves across Procurement, Payables, and Payments. In ETRM 12.2.2, the table is documented with 164 columns and resides in the APPS_TS_TX_DATA tablespace with a PCT Free of 10. Applying Data Vault heuristics to its foreign-key structure, AP_SUPPLIER_SITES_ALL is best modeled as a hub: it anchors a durable business key (the supplier site) around which transactional satellites such as invoices and payments accumulate.

Key Information Stored

The surrogate primary key is AP_SUPPLIER_SITES_PK, defined on VENDOR_SITE_ID, which is the supplier site's unique identifier referenced by downstream transactional tables. Two unique indexes represent business-key candidates:

• AP_SUPPLIER_SITES_U1 (VENDOR_SITE_ID) — the single-column unique index that the user searched for; it enforces uniqueness of the surrogate site identifier and supports primary-key lookups.
• AP_SUPPLIER_SITES_U2 (VENDOR_ID, VENDOR_SITE_CODE, ORG_ID) — the composite business key guaranteeing that a site code is unique per supplier within an operating unit.

The most significant operational columns include VENDOR_ID (the owning supplier, traced to AP_SUPPLIERS), VENDOR_SITE_CODE (the site name), and ORG_ID (the operating unit). Purchasing behavior is governed by PURCHASING_SITE_FLAG and RFQ_ONLY_SITE_FLAG; payment behavior by PAY_SITE_FLAG, PAYMENT_METHOD_LOOKUP_CODE, PAY_GROUP_LOOKUP_CODE, PAYMENT_PRIORITY, and PRIMARY_PAY_SITE_FLAG. Financial controls include TERMS_ID, INVOICE_AMOUNT_LIMIT, HOLD_ALL_PAYMENTS_FLAG, HOLD_FUTURE_PAYMENTS_FLAG, and HOLD_UNMATCHED_INVOICES_FLAG. Tax handling is captured by VAT_CODE, VAT_REGISTRATION_NUM, and AUTO_TAX_CALC_FLAG. Distribution and tolerance defaults are held in DISTRIBUTION_SET_ID and TOLERANCE_ID, while LOCATION_ID and PARTY_SITE_ID bridge the record to TCA. Standard Who columns (LAST_UPDATE_DATE, CREATED_BY, and related audit fields) track row history.

Common Use Cases and Queries

AP_SUPPLIER_SITES_ALL is central to supplier site validation, invoice entry, payment processing, and site-level reporting. A typical query retrieves active sites for a supplier within an operating unit:

• Look up a site by its business key: SELECT vendor_site_id, vendor_site_code FROM ap_supplier_sites_all WHERE vendor_id = :p_vendor_id AND org_id = :p_org_id;
• Identify pay sites available for payment: SELECT vendor_site_id FROM ap_supplier_sites_all WHERE vendor_id = :p_vendor_id AND pay_site_flag = 'Y' AND org_id = :p_org_id;
• Join to invoices to report invoice activity by site: SELECT s.vendor_site_code, i.invoice_num, i.invoice_amount FROM ap_invoices_all i, ap_supplier_sites_all s WHERE i.vendor_site_id = s.vendor_site_id;

Reporting scenarios include listing suppliers with payments on hold, auditing sites missing tax registration numbers, and reconciling TCA sync status using the TCA_SYNC_STATE column. Because indexes AP_SUPPLIER_SITES_N1 (VENDOR_SITE_CODE), AP_SUPPLIER_SITES_N5 (LOCATION_ID), and AP_SUPPLIER_SITES_N6 (PARTY_SITE_ID) exist, queries filtering on those columns perform efficiently.

Related Objects

AP_SUPPLIER_SITES_ALL sits at the center of a broad referential network. Its outgoing foreign keys point to AP_SUPPLIERS (via VENDOR_ID), AP_DISTRIBUTION_SETS_ALL (via DISTRIBUTION_SET_ID), and AP_TOLERANCE_TEMPLATES (via TOLERANCE_ID). Numerous tables reference it through VENDOR_SITE_ID, including AP_INVOICES_ALL, AP_INVOICE_PAYMENTS_ALL, AP_SUPPLIER_CONTACTS, JAI_AP_TDS_INV_PAYMENTS, JAI_RETRO_LINE_CHANGES, OKL_CURE_REPORTS_ALL, OKL_PARTY_PAYMENT_DTLS, and OKL_TXL_EXTENSION_B. Public APIs such as AP_VENDOR_PUB_PKG and the supplier site DML APIs are the supported mechanisms for creating and maintaining these records in a multi-org environment.