Search Results name_control




Overview
Explore in AI Chat

Overview

APPS.POS_PO_VENDORS_V is a reporting and integration view in Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2 that exposes supplier (vendor) master data sourced from the purchasing schema. It is a pass-through view defined over PO_VENDORS, presenting the full column set of that underlying purchasing vendor entity under the APPS application schema. Because it resides in APPS, it is visible to the broadest set of EBS responsibilities and is commonly referenced by concurrent programs, Oracle Reports, Oracle Forms-based inquiries, and third-party integration extracts that need supplier header information without qualifying a PO-schema object directly.

The description column names in the view mirror the PO_VENDORS structure, covering supplier identification, payment controls, withholding, purchasing controls, receiving controls, tax attributes, and descriptive flexfield columns ATTRIBUTE1 through ATTRIBUTE15, along with WHO columns and concurrent program audit columns. The user query term "hold_future_payments_flag" is one of the payment-control columns exposed by this view, indicating the view is frequently consulted for payables hold analysis.

Underlying Base Objects

Per the documented ETRM metadata, POS_PO_VENDORS_V is defined over a single referenced object: PO_VENDORS, itself classified as a view in the metadata. The DDL is a straightforward column projection — SELECT "VENDOR_ID", ... FROM PO_VENDORS — with no joins, filters, or aggregate functions. Consequently, the row grain is one row per supplier header record, keyed by VENDOR_ID, and no data transformation occurs between the base object and this view. Any filter, sorting, or security predicate must be applied by the consuming query. Because the base object PO_VENDORS is itself a view in the purchasing schema, POS_PO_VENDORS_V should be treated as an additional abstraction layer rather than a direct base-table access path.

Key Columns

Common Use Cases and Queries

The view is typically used to report supplier hold status, export supplier master data for interfaces, and drive validation queries during invoice or purchase order entry. A representative query identifying suppliers subject to future payment holds is:

  • SELECT vendor_id, vendor_name, hold_future_payments_flag, hold_all_payments_flag, hold_reason FROM apps.pos_po_vendors_v WHERE hold_future_payments_flag = 'Y' AND NVL(enabled_flag,'Y') = 'Y' ORDER BY vendor_name;
  • Reports listing all supplier payment controls, joining to PO_VENDOR_SITES_ALL by VENDOR_ID for site-level detail.
  • Integration extracts selecting VENDOR_ID, VENDOR_NAME, TERMS_ID, and currency defaults for downstream systems.
  • Data-quality queries verifying NAME_CONTROL uniqueness or missing 1099/TIN attributes.

Because the view applies no filtering, queries should always include an ENABLED_FLAG or date-effective predicate to avoid returning inactive suppliers, and should be tuned with the same considerations applied to PO_VENDORS access.