Search Results ap_supplier_sites_all




Overview
Explore in AI Chat

Overview

The AP_SUPPLIER_SITES_ALL table is a core data object within the Oracle E-Business Suite Payables (AP) module. It serves as the master repository for all operational and financial attributes defined at the supplier site level. While the AP_SUPPLIERS table stores general information about a trading partner, this table holds the specific details required to conduct transactions, such as payment terms, payment methods, and remittance addresses, for each distinct physical or logical location from which goods or services are procured. Its role is critical for enabling accurate invoice processing, payment execution, and financial reporting, as it links a single supplier to multiple transactional sites. The "_ALL" suffix indicates it is a multi-organization table, storing data partitioned by the ORG_ID column to support multiple operating units within a single installation.

Key Information Stored

The table's primary key is VENDOR_SITE_ID, a unique system-generated identifier for each site record. The mandatory VENDOR_ID column links the site to its parent supplier in the AP_SUPPLIERS table. Key operational columns include VENDOR_SITE_CODE (the user-defined site identifier), ADDRESS lines, CITY, STATE, ZIP, and COUNTRY for location data. Critical financial attributes include TERMS_ID (linking to payment terms), PAY_GROUP_LOOKUP_CODE (for payment grouping), PAYMENT_METHOD_LOOKUP_CODE, and BANK_ACCOUNT_NAME for electronic funds transfer. The INVOICE_CURRENCY_CODE and PAYMENT_CURRENCY_CODE columns define the currencies for invoicing and settlement. The ORG_ID column is essential for multi-org implementations, scoping the site's usability to a specific operating unit.

Common Use Cases and Queries

A primary use case is validating and reporting on supplier site setup for procurement and payment processes. Common queries include listing all active sites for a supplier to support invoice entry, identifying sites using a specific payment method for bank communication, or auditing sites assigned to a particular distribution set. For example, to retrieve key payment details for all sites of a specific supplier, a query would join to AP_SUPPLIERS: SELECT assa.VENDOR_SITE_CODE, assa.ADDRESS_LINE1, assa.CITY, assa.PAYMENT_METHOD_LOOKUP_CODE, ap.TERMS_NAME FROM AP_SUPPLIER_SITES_ALL assa, AP_TERMS_TL ap WHERE assa.VENDOR_ID = <supplier_id> AND assa.TERMS_ID = ap.TERM_ID AND assa.ORG_ID = <org_id>;. This table is also central in data migration scripts when loading new supplier sites via APIs or interfaces.

Related Objects

AP_SUPPLIER_SITES_ALL has extensive relationships with transactional and setup tables, as documented in the provided foreign key metadata. Its primary relationship is with the parent AP_SUPPLIERS table via VENDOR_ID. Key transactional dependencies include:

Other module-specific relationships include tables from India Localization (JAI_AP_TDS_INV_PAYMENTS, JAI_RETRO_LINE_CHANGES) and the OKL module (OKL_CURE_REPORTS_ALL, OKL_PARTY_PAYMENT_DTLS, OKL_TXL_EXTENSION_B), demonstrating the table's integration across the financial suite.