Search Results po_vendor_list_entries_v




Overview
Explore in AI Chat

Overview

PO_VENDOR_LIST_ENTRIES_V is a denormalized reporting view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the Purchasing (PO) product family. It is documented in ETRM 12.2.2 and is also present in 12.1.1 with equivalent structure. The view exposes vendor list entry records — that is, the approved supplier entries associated with a sourcing or purchasing vendor list header — enriched with the human-readable vendor name, vendor site code, and vendor contact name. Rather than requiring callers to resolve numeric foreign keys against PO_VENDORS, PO_VENDOR_SITES, and PO_VENDOR_CONTACTS, the view performs that resolution at query time and presents a business-friendly projection.

Because it is a view and not a table, PO_VENDOR_LIST_ENTRIES_V holds no data of its own; it is a query wrapper over the underlying Purchasing vendor entities. Its principal role is reporting and integration: it provides a stable, description-bearing interface for extracting vendor list membership without embedding multi-table joins in every consumer. The ETRM record lists its status as VALID and characterizes the object as "Retrofitted," indicating it was carried forward through an upgrade or patch cycle rather than newly authored.

Underlying Base Objects

The documented referenced base objects are FND_GLOBAL (PACKAGE), PO_VENDORS (VIEW), PO_VENDOR_CONTACTS (VIEW), PO_VENDOR_LIST_ENTRIES (SYNONYM), and PO_VENDOR_SITES (VIEW). The view text joins these four data-bearing objects:

  • PO_VENDORS POV — joined on VENDOR_ID, supplying VENDOR_NAME and restricting to enabled vendors whose active date range brackets SYSDATE.
  • PO_VENDOR_SITES POVS — joined on VENDOR_SITE_ID, supplying VENDOR_SITE_CODE, ORG_ID, and filtering out sites whose INACTIVE_DATE has passed.
  • PO_VENDOR_CONTACTS POVC — outer-joined on VENDOR_CONTACT_ID, supplying the contact name.
  • PO_VENDOR_LIST_ENTRIES POVL — the driving object, supplying all list entry columns and the ROWID.

The outer join on the contacts table means list entries without an assigned contact are still returned, with a null contact description.

Key Columns

Common Use Cases and Queries

Typical uses include validating supplier list membership during sourcing analysis, reconciling approved vendor lists for a given operating unit, and feeding downstream integrations that require vendor name and site code rather than internal identifiers. All queries run in the APPS schema context or through a synonym.

List all entries for a given list header:

  • SELECT vendor_list_entry_id, vendor_name, vendor_site_code, vendor_contact FROM po_vendor_list_entries_v WHERE vendor_list_header_id = :p_header_id;

Filter by operating unit and supplier name:

  • SELECT vendor_name, vendor_site_code, org_id FROM po_vendor_list_entries_v WHERE org_id = :p_org_id AND vendor_name LIKE :p_name;

Because the view applies SYSDATE-based predicates to vendor and site active dates, results reflect only currently enabled vendors and active sites at execution time. Consumers requiring historical or inactive data must query the underlying PO_VENDOR_LIST_ENTRIES table directly.