Search Results po_vendor_sites_all




Overview
Explore in AI Chat

Overview

The PO_VENDOR_SITES_ALL view is a critical master data object within Oracle E-Business Suite, specifically for the Payables (AP) and Purchasing (PO) modules. It serves as the primary interface for accessing comprehensive information about a supplier's operational locations. This view consolidates data from the underlying transactional table, AP_SUPPLIER_SITES_ALL, and joins it with related data from the HZ_PARTY_SITES and HZ_LOCATIONS tables in the Trading Community Architecture (TCA) model. Its role is to provide a unified, multi-organization (multi-org) aware record of all vendor sites, which are the specific addresses and associated payment, shipping, and invoicing terms used for transacting with a supplier. This data is foundational for procurement, invoice processing, and payment execution.

Key Information Stored

The view contains a wide array of columns that define a vendor site's operational characteristics. Key columns include the unique identifier VENDOR_SITE_ID and its associated VENDOR_ID, linking to the parent supplier. The VENDOR_SITE_CODE is a user-defined identifier for the site. Critical financial columns include ACCTS_PAY_CODE_COMBINATION_ID and PREPAY_CODE_COMBINATION_ID for accounting, TERMS_ID for payment terms, and DISTRIBUTION_SET_ID for default invoice distributions. Shipping and logistics are defined by SHIP_TO_LOCATION_ID, BILL_TO_LOCATION_ID, SHIP_VIA_LOOKUP_CODE, FOB_LOOKUP_CODE, and FREIGHT_TERMS_LOOKUP_CODE. Currency controls are managed via INVOICE_CURRENCY_CODE and PAYMENT_CURRENCY_CODE. The view also integrates TCA address details like COUNTRY, PROVINCE, and COUNTY from the underlying location tables, and includes audit columns such as LAST_UPDATE_DATE and LAST_UPDATED_BY.

Common Use Cases and Queries

This view is central to numerous operational and reporting processes. Common use cases include generating supplier master lists for audits, validating site data during invoice entry, and supporting Open Interface programs. A typical query retrieves active sites for a specific vendor to populate a list of values in a purchase order form:

  • SELECT vendor_site_code, vendor_site_id FROM po_vendor_sites_all WHERE vendor_id = :p_vendor_id AND inactive_date IS NULL ORDER BY 1;

For financial reporting, a join to the PO_VENDORS view can produce a comprehensive supplier analysis:

  • SELECT pv.vendor_name, pvs.vendor_site_code, pvs.invoice_currency_code, pvs.payment_priority FROM po_vendors pv, po_vendor_sites_all pvs WHERE pv.vendor_id = pvs.vendor_id AND pvs.inactive_date IS NULL;

Technical integrations often use this view as the source for vendor site data when extracting information to external systems or data warehouses.

Related Objects

PO_VENDOR_SITES_ALL is a hub within the EBS data model, referenced extensively by transactional entities. As documented, its primary key (VENDOR_SITE_ID) is referenced by foreign keys in numerous core tables. Key relationships include: