Search Results amv_vendor_keys

Overview

The PO_VENDORS table is the central repository for supplier master data within the Oracle E-Business Suite Purchasing (PO) module. It stores the foundational information for all trading partners from whom an organization procures goods and services. This table is critical for the procure-to-pay lifecycle, as it is referenced by numerous transactions in Purchasing, Payables (AP), and other integrated modules. The table's primary key, VENDOR_ID, serves as the unique identifier for a supplier across the application. The metadata indicates a complex relational structure, with foreign key relationships to core tables like GL_CODE_COMBINATIONS for accounting and FND_CURRENCIES for financial settings, underscoring its integral role in financial and operational processes.

Key Information Stored

The table's structure, as indicated by its foreign keys, stores comprehensive supplier information. Key columns include VENDOR_ID (the primary key), VENDOR_NAME, and various control and financial attributes. Critical financial columns link to other key entities: DISTRIBUTION_SET_ID (from AP_DISTRIBUTION_SETS_ALL) defaults accounting distributions; SET_OF_BOOKS_ID (from GL_SETS_OF_BOOKS) defines the supplier's accounting context; and INVOICE_CURRENCY_CODE and PAYMENT_CURRENCY_CODE (from FND_CURRENCIES) govern transactional currency. The table also holds several General Ledger account code combinations for liabilities (ACCTS_PAY_CODE_COMBINATION_ID), discounts, expenses, and prepayments. The PARENT_VENDOR_ID column supports hierarchical vendor relationships, and HOLD_BY can link to a purchasing agent (PO_AGENTS) for approval controls.

Common Use Cases and Queries

This table is fundamental for supplier management reporting, data validation, and integration tasks. Common queries involve joining with related transactional tables to analyze supplier activity. For instance, to generate a list of active suppliers with their associated Payables invoices, a query would join PO_VENDORS with AP_INVOICES_ALL on VENDOR_ID. Another typical use case is validating supplier setup by checking for missing critical accounting flexfields, such as the liability account. The user's search for "fv_inv_selected_duedate_temp," while not directly related to PO_VENDORS, suggests a Payables invoice workflow; a relevant query might trace from an invoice payment hold back to the vendor's financial or hold settings in PO_VENDORS to diagnose issues.

• Basic Supplier List: SELECT vendor_id, vendor_name, segment1 FROM po_vendors WHERE enabled_flag = 'Y';
• Supplier with Invoice Summary: SELECT pv.vendor_name, COUNT(aia.invoice_id) FROM po_vendors pv, ap_invoices_all aia WHERE pv.vendor_id = aia.vendor_id GROUP BY pv.vendor_name;

Related Objects

As evidenced by the extensive foreign key metadata, PO_VENDORS is a hub table with dependencies across multiple EBS modules. Within Purchasing and Payables, it is directly referenced by core transactional tables including AP_INVOICES_ALL, AP_CHECKS_ALL, AP_SELECTED_INVOICES_ALL, and PO_AGENTS. Its relationships extend to financial setup tables like GL_CODE_COMBINATIONS and AP_DISTRIBUTION_SETS_ALL. Furthermore, integration with other product families is shown through references from tables in modules like Complex Maintenance (AHL_OSP_ORDERS_B) and Marketing (AMV_VENDOR_KEYS). This wide integration highlights that PO_VENDORS is not merely a Purchasing table but a shared enterprise master data entity critical for financial integrity and cross-functional processes.