Results for “po_lines_supplier_items_all_v”

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

Overview

The PO_LINES_SUPPLIER_ITEMS_ALL_V view is a lightweight, read-only database object owned by the APPS schema in Oracle E-Business Suite. It is registered under the Purchasing (PO) product family and is documented in ETRM with the terse annotation "10SC ONLY," indicating it was introduced to support a specific supplier-item lookup requirement rather than general purchasing reporting. The view exposes a de-duplicated list of supplier item identifiers — the vendor product number — combined with the operating unit (ORG_ID) under which each was transacted.

Functionally, the view answers the question: "For which vendor part numbers do we hold purchasing activity, and in which operating units?" Because the definition applies a DISTINCT operator and filters out null vendor product numbers, the result set is compact and well suited to value-list validation, supplier catalog reconciliation, blanket agreement review, and integration extracts where a distinct supplier-item master list is required. It carries no descriptive supplier, item, or price attributes; it is purely an enumeration of supplier item numbers and their owning operating unit.

Underlying Base Objects

The ETRM metadata documents two referenced base objects, both accessed through APPS synonyms:

• PO_LINES (alias PL) — supplies the VENDOR_PRODUCT_NUM value and the foreign key PO_HEADER_ID used to join the header.
• PO_HEADERS_ALL (alias PH) — supplies the document type (TYPE_LOOKUP_CODE), which is constrained to the purchasing document classes considered relevant.

The join clause links each line to its header on PL.PO_HEADER_ID = PH.PO_HEADER_ID. The header filter restricts rows to TYPE_LOOKUP_CODE IN ('STANDARD', 'BLANKET', 'PLANNED'), so quotations, RFQs, and other non-purchasing document types are excluded. A final predicate, PL.VENDOR_PRODUCT_NUM IS NOT NULL, removes lines where no supplier part number was captured. The view is org-striped through ORG_ID, which is projected from PO_LINES; consumers filtering by operating unit should apply an ORG_ID predicate for Multi-Org compliance.

Key Columns

• VENDOR_PRODUCT_NUM — the supplier's own identifier for the item, as entered on the purchase order, blanket, or planned order line. This is the column most commonly searched, and users searching for "vendor_product_num" will find this view to be the most direct source for distinct supplier item numbers.
• ORG_ID — the operating unit identifier associated with the line. It enables Multi-Org security and lets consumers group supplier item numbers by procurement organization.

No item, supplier, quantity, or date columns are exposed. Any requirement for supplier name, item description, or pricing must be met by joining to PO_LINES, PO_HEADERS_ALL, POZ_SUPPLIERS, or the item master independently.

Common Use Cases and Queries

Typical uses include populating supplier-item value lists, detecting vendor part numbers active in one operating unit but not another, and driving supplier catalog clean-up or cross-reference loads. A representative query follows:

• List all supplier item numbers for an operating unit:
  SELECT vendor_product_num FROM apps.po_lines_supplier_items_all_v WHERE org_id = :p_org_id ORDER BY 1;
• Count distinct supplier items per operating unit:
  SELECT org_id, COUNT(*) FROM apps.po_lines_supplier_items_all_v GROUP BY org_id;
• Validate a supplier part number exists in purchasing:
  SELECT DISTINCT vendor_product_num FROM apps.po_lines_supplier_items_all_v WHERE vendor_product_num = :p_vendor_part;

Because the view performs a DISTINCT over PO_LINES, it should not be used for transactional or volume reporting; PO_LINES or the purchasing document tables are preferable for those purposes.