Search Results po_vendor_sites_all




Overview
Explore in AI Chat

Overview

The PO_VENDOR_SITES_ALL table is a fundamental data object within Oracle E-Business Suite (EBS) Purchasing (PO) and Payables (AP) modules. It serves as the central repository for all supplier (vendor) site information. While its name originates from the Purchasing module, its role is critical across financial operations, as it stores the specific locations or business units of a supplier with whom an organization transacts. Each record defines a unique ship-to, bill-to, or pay-to address and its associated operational rules, enabling precise control over procurement and payment processes. The table supports the multi-organization architecture of EBS through its `ALL` suffix, meaning it contains data partitioned by the `ORG_ID` column for use in Multi-Org configurations.

Key Information Stored

The table's primary key is `VENDOR_SITE_ID`, which uniquely identifies each supplier site. A critical foreign key, `VENDOR_ID`, links the site to its parent supplier in the PO_VENDORS table. Essential columns define the site's operational and financial characteristics. These include the site address (`ADDRESS_LINE1`, `CITY`, `STATE`, `ZIP`, `COUNTRY`), contact information, and site-specific identifiers like `VENDOR_SITE_CODE`. Financial control columns are paramount, such as `INVOICE_CURRENCY_CODE` and `PAYMENT_CURRENCY_CODE` (linked to FND_CURRENCIES), `ACCTS_PAY_CODE_COMBINATION_ID` for the default liability account (linked to GL_CODE_COMBINATIONS), and `DISTRIBUTION_SET_ID` (linked to AP_DISTRIBUTION_SETS_ALL) for automating invoice distributions. Flags like `PAY_SITE_FLAG`, `PAY_GROUP_LOOKUP_CODE`, and `INVOICE_CURRENCY_CODE` determine payment and invoicing behaviors for the site.

Common Use Cases and Queries

This table is central to reporting and data validation in procurement-to-pay cycles. Common use cases include generating supplier master lists with site details, validating site setup before transaction processing, and supporting custom payment or invoicing reports. A typical query retrieves active supplier sites with their key financial setups:

  • SELECT pvsa.vendor_site_code, pvsa.address_line1, pvsa.city, pvsa.country, pvsa.invoice_currency_code, pv.vendor_name FROM po_vendor_sites_all pvsa JOIN po_vendors pv ON pvsa.vendor_id = pv.vendor_id WHERE pvsa.inactive_date IS NULL AND pvsa.org_id = :org_id;

Another critical pattern involves joining to Payables tables like AP_INVOICES_ALL to analyze invoice volume or payment history per vendor site. Data fixes often target this table to update currency codes, default accounts, or tax registrations for specific sites.

Related Objects

PO_VENDOR_SITES_ALL has extensive relationships across EBS. Its primary parent is PO_VENDORS. It is a key parent table for numerous Payables transaction tables, including AP_INVOICES_ALL, AP_CHECKS_ALL, AP_EXPENSE_REPORT_HEADERS_ALL, and AP_RECURRING_PAYMENTS_ALL, linking transactions to the specific pay-to site. It also relates to setup tables like AP_BANK_ACCOUNT_USES_ALL for payment methods and AP_AWT_TAX_RATES_ALL for withholding tax. The foreign keys to GL_CODE_COMBINATIONS and FND_CURRENCIES integrate it with General Ledger and currency master data. For reporting, views like AP_SUPPLIER_SITES (AP_SUPPLIER_SITES_AUG) often provide a more accessible layer over this base table.