Search Results po_vendors




Overview
Explore in AI Chat

Overview

PO_VENDORS is a legacy compatibility view owned by the APPS schema in Oracle E-Business Suite, listed under the Payables (AP) product family. It exposes supplier (vendor) header information in the column layout that applications and custom code originally expected from the pre-R12 PO_VENDORS base table. Beginning with Release 12, Oracle restructured the supplier data model: vendor master records moved to AP_SUPPLIERS, and party-level information such as names, addresses, and identifiers moved to the TCA (Trading Community Architecture) tables, principally HZ_PARTIES and its related entities. Rather than break the large volume of existing reports, interfaces, and extensions that referenced PO_VENDORS directly, Oracle retained PO_VENDORS as a view over the new tables. It is defined in APPS and reported as VALID in both 12.1.1 and 12.2.2.

Underlying Base Objects

The documented ETRM metadata for 12.2.2 lists exactly two referenced base objects: AP_SUPPLIERS (accessed through a synonym) and HZ_PARTIES (accessed through a synonym). AP_SUPPLIERS supplies nearly all transactional supplier attributes — identifiers, payment terms, currency defaults, hold flags, withholding information, and classification flags. HZ_PARTIES supplies party-level attributes that are not stored on the supplier record itself, notably the phonetic organization name (mapped to VENDOR_NAME_ALT) and the fiscal code (mapped to NUM_1099). This split reflects the R12 architecture, in which a supplier is a party playing the "supplier" role, with the TCA registry serving as the single source of truth for identity data.

Key Columns

The view exposes the primary supplier key VENDOR_ID, which is drawn from AP_SUPPLIERS and remains the join key for purchasing and payables transactions. Descriptive columns include VENDOR_NAME, VENDOR_NAME_ALT (the phonetic party name), SEGMENT1 through SEGMENT5, and ACTIVE date range fields (START_DATE_ACTIVE, END_DATE_ACTIVE). Financial attributes encompass TERMS_ID, SET_OF_BOOKS_ID, INVOICE_CURRENCY_CODE, PAYMENT_CURRENCY_CODE, INVOICE_AMOUNT_LIMIT, PAYMENT_PRIORITY, PAY_DATE_BASIS_LOOKUP_CODE, and PAY_GROUP_LOOKUP_CODE. Payment control columns include HOLD_ALL_PAYMENTS_FLAG, HOLD_FUTURE_PAYMENTS_FLAG, HOLD_REASON, HOLD_FLAG, and PURCHASING_HOLD_REASON. Tax and reporting attributes include NUM_1099, INDIVIDUAL_1099, TYPE_1099, WITHHOLDING_STATUS_LOOKUP_CODE, and WITHHOLDING_START_DATE. Structural and classification columns include PARENT_VENDOR_ID, ONE_TIME_FLAG, SUMMARY_FLAG, ENABLED_FLAG, EMPLOYEE_ID, VENDOR_TYPE_LOOKUP_CODE, and the diversity flags (MINORITY_GROUP_LOOKUP_CODE, WOMEN_OWNED_FLAG, SMALL_BUSINESS_FLAG). Standard WHO columns are also present.

Common Use Cases and Queries

PO_VENDORS is most often used in custom reports, Oracle Discoverer workbooks, and legacy interfaces that predate the R12 data model. A typical lookup of active suppliers is:

  • SELECT vendor_id, vendor_name, segment1, terms_id FROM po_vendors WHERE enabled_flag = 'Y' — filters to currently enabled suppliers.
  • SELECT vendor_id, vendor_name FROM po_vendors WHERE hold_all_payments_flag = 'Y' — identifies suppliers whose payments are entirely suspended.
  • SELECT vendor_id, num_1099, type_1099 FROM po_vendors WHERE type_1099 IS NOT NULL — supports 1099 reporting extracts.
  • SELECT v.vendor_id, v.vendor_name, s.vendor_site_id FROM po_vendors v, po_vendor_sites_all s WHERE v.vendor_id = s.vendor_id — joins the supplier header to its sites.

Maintenance caution applies: because PO_VENDORS is a view, it is intended for query access only. Direct DML against suppliers should be performed through the Oracle Payables supplier entry forms or the supported supplier APIs, not against this view or AP_SUPPLIERS. For new development in 12.1.1 and 12.2.2, Oracle recommends querying AP_SUPPLIERS and the HZ_PARTIES tables directly, since PO_VENDORS exists primarily to preserve backward compatibility.