Search Results po_vendors_view




Overview
Explore in AI Chat

Overview

PO_VENDORS_VIEW is a reporting and integration view owned by the APPS schema in Oracle E-Business Suite, registered under the Purchasing (PO) product family. Its documented description is simply "Suppliers view," and it is classified as a VALID database view in both the 12.1.1 and 12.2.2 releases. The view exposes supplier header information from the supplier master so that Purchasing reports, concurrent programs, and external integrations can retrieve vendor data through a stable, denormalized interface.

The view is intentionally narrow. Rather than surfacing the full supplier record, it projects a curated subset of supplier attributes: the operating unit context (SET_OF_BOOKS_ID), the vendor primary key (VENDOR_ID), a concatenated vendor number, the vendor name, audit columns, status flags, and effective dates. It also renames several columns relative to the underlying source (for example, the concatenated number is aliased VENDOR_NUMBER and the audit columns are aliased VENDOR_LAST_UPDATE_DATE and VENDOR_LAST_UPDATED_BY), which gives report developers predictable, descriptive column labels without joining to base tables.

Because the view is owned by APPS and defined over standard Purchasing objects, it participates in the same grants and synonym conventions as other EBS dictionary objects. Responsibility-level access to supplier data is typically governed elsewhere, but the view itself is available wherever APPS objects are exposed.

Underlying Base Objects

Per the ETRM metadata, PO_VENDORS_VIEW is defined over a single referenced base object: PO_VENDORS, itself a view in the Purchasing schema. The documented view text confirms this:

There is no filter, DISTINCT, aggregation, or join in the view definition; it is a pure projection over PO_VENDORS. Consequently, the row count and cardinality of PO_VENDORS_VIEW match the source for any given predicate. The concatenation of SEGMENT1 through SEGMENT5 with single-space separators constructs the vendor number, which is why trailing spaces may appear in the output when lower segments are null. Because PO_VENDORS is itself a view, the ultimate base tables reside deeper in the supplier model, but the documented dependency chain is PO_VENDORS_VIEW to PO_VENDORS.

Key Columns

  • SET_OF_BOOKS_ID — the set of books (ledger) context under which the supplier record is visible; in multi-org configurations this is the key partitioning attribute.
  • VENDOR_ID — the supplier primary key, used to join to supplier sites, contacts, and purchasing documents.
  • VENDOR_NUMBER — the concatenated SEGMENT1 through SEGMENT5 value, representing the supplier number as displayed.
  • VENDOR_NAME — the supplier name.
  • VENDOR_LAST_UPDATE_DATE and VENDOR_LAST_UPDATED_BY — audit columns aliased from the source, useful for incremental extract logic.
  • SUMMARY_FLAG — indicates whether the record is a summary (parent) row in the key flexfield structure.
  • ENABLED_FLAG — Y/N indicator of whether the supplier is active for use.
  • CUSTOMER_NUMBER — the customer number where the supplier is also a customer.
  • ONE_TIME_VENDOR_FLAG — indicates a one-time (temporary) supplier.
  • VENDOR_START_DATE_ACTIVE and VENDOR_END_DATE_ACTIVE — the effective date range of the supplier record.

Common Use Cases and Queries

Typical scenarios include supplier validation during purchase order import, active-supplier listings for procurement reporting, incremental supplier extracts into a data warehouse, and lookups that need a vendor number and name without touching the full supplier master.

Retrieve active suppliers:

  • SELECT vendor_id, vendor_number, vendor_name FROM apps.po_vendors_view WHERE enabled_flag = 'Y' AND TRUNC(SYSDATE) BETWEEN NVL(vendor_start_date_active, TRUNC(SYSDATE)) AND NVL(vendor_end_date_active, TRUNC(SYSDATE));

Incremental extract based on audit columns:

  • SELECT vendor_id, vendor_number, vendor_name, vendor_last_update_date FROM apps.po_vendors_view WHERE vendor_last_update_date >= :last_run_date AND set_of_books_id = :ledger_id;

Exclude one-time suppliers:

  • SELECT vendor_id, vendor_name FROM apps.po_vendors_view WHERE NVL(one_time_vendor_flag, 'N') = 'N' AND summary_flag = 'N';

Because no filtering is built into the view, every query should apply its own predicates on ENABLED_FLAG, the effective dates, and SET_OF_BOOKS_ID to return only the suppliers relevant to the operating context.