Results for “po_vendors_all_v”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

PO_VENDORS_ALL_V is a view owned by the APPS schema in Oracle E-Business Suite, documented under the Payables (AP) product family. The ETRM metadata identifies this object explicitly as a Release 10SC-only construct, meaning it was introduced in an early Oracle Applications release and retained in the data dictionary for backward compatibility rather than as a currently recommended interface. In Oracle EBS 12.1.1 and 12.2.2 the object remains VALID, so it can still be queried, but it should be regarded as a legacy compatibility view rather than a supported integration point.

The view presents a simplified, denormalized projection of supplier (vendor) information: the supplier name, the supplier number, and the 1099 reporting flag. Its stated role is to expose supplier attributes in a stable column layout that predates the more comprehensive supplier views available in later releases. Because the definition is trivial — a straight column projection over PO_VENDORS — the view adds no filtering, joining, or transformation logic, and therefore inherits the full row set and security behaviour of its base object.

Underlying Base Objects

The documented base object is PO_VENDORS (itself a VIEW, not a physical table). The view text supplied in the ETRM excerpt is:

• SELECT PV.VENDOR_NAME VENDOR_NAME, PV.SEGMENT1 VENDOR_NUMBER, PV.NUM_1099 NUM_1099 FROM PO_VENDORS PV

Two consequences follow from this definition. First, PO_VENDORS_ALL_V is a view over a view; any change to PO_VENDORS, or to the base tables beneath it, propagates directly. Second, because only three columns are projected, the view deliberately narrows the supplier record to the minimum fields needed by legacy 1099 reporting and vendor lookup code paths. The "ALL" suffix in the name is a legacy naming convention and does not imply multi-org or multi-organization filtering in this definition; no organization security predicate appears in the documented view text.

Key Columns

• VENDOR_NAME — The supplier name as held on PO_VENDORS. This is the descriptive identifier used in reports and list-of-values displays.
• VENDOR_NUMBER — Sourced from PO_VENDORS.SEGMENT1, the supplier number. This is the unique, system-assigned or user-entered key by which a supplier is referenced in purchasing and payables transactions.
• NUM_1099 — The 1099 reporting indicator, sourced from PO_VENDORS.NUM_1099. This column drives US tax reporting eligibility for the supplier. It is the column returned when users search the dictionary for "num_1099", and it is the primary reason this legacy view is still consulted.

Common Use Cases and Queries

The view is typically used for lightweight supplier lookups and for diagnosing 1099 configuration on a supplier record. A representative query for validating 1099 flagging is:

• SELECT vendor_name, vendor_number, num_1099 FROM apps.po_vendors_all_v WHERE num_1099 IS NOT NULL ORDER BY vendor_name;

To resolve a supplier number to a name for reconciliation purposes:

• SELECT vendor_name, num_1099 FROM apps.po_vendors_all_v WHERE vendor_number = :p_vendor_number;

For inclusion in a 1099 extract against invoices or payments, the view can be joined to AP distribution or payment tables on vendor_number or vendor_name:

• SELECT p.vendor_name, p.vendor_number, i.invoice_num FROM apps.po_vendors_all_v p, apps.ap_invoices_all i WHERE p.vendor_number = i.vendor_num AND p.num_1099 = 'Y';

Because the object is documented as Release 10SC only and defined over PO_VENDORS, developers on 12.1.1 or 12.2.2 should prefer the supported supplier views (for example, the POZ_SUPPLIERS family of views) for new development, and treat PO_VENDORS_ALL_V strictly as a read-only legacy query surface.