Results for “po_source_vendors_v”

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

Overview

APPS.PO_SOURCE_VENDORS_V is a Purchasing (PO) module view that consolidates approved sourcing information for inventory items and their associated vendors. It presents a unified result set combining two distinct sourcing mechanisms: item-level autosource rules defined in Purchasing, and vendor sourcing rules maintained in Oracle Master Scheduling/MRP as exposed through MRP_SOURCES_V. The view is a UNION of these two sources, allowing downstream consumers to retrieve vendor, price, and shipment information from a single object regardless of how the sourcing relationship was originally established.

Because the view is described as "Retrofitted" in the ETRM documentation, it represents an object that was adapted or recreated to preserve compatibility during an upgrade or patch cycle. It is owned by the APPS schema and carries a VALID status, confirming it is compiled and available for query use. The view is particularly relevant because it bridges the gap between Purchasing-sourced blanket/standard agreements and MRP-defined sourcing rules, making it useful in supply chain reporting and in customizations that need a single sourcing reference. The user search term "mrp_sources_v" reflects this close relationship; MRP_SOURCES_V is a documented base object referenced directly in the view's second UNION branch.

Underlying Base Objects

The view is defined over the following documented base objects, drawing from both the Purchasing and MRP schemas:

• PO_AUTOSOURCE_RULES — Item-level autosource rule definitions, including validity dates.
• PO_AUTOSOURCE_VENDORS — Vendors assigned to autosource rules, including rank and split allocation.
• PO_HEADERS_ALL — Purchase order headers, supplying vendor, rate, site, and creation date.
• PO_LINES — Purchase order lines, linking item to header.
• PO_LINE_LOCATIONS_ALL — Shipments, providing quantity, shipment type, and ship-to organization.
• PO_VENDORS — Vendor master view, supplying the vendor name.
• MRP_SOURCES_V — MRP sourcing rules, supplying rank, allocation percent, organization, assignment set, and effective/disable dates.

The first UNION branch joins the autosource rule and vendor tables to purchase order lines and shipments, filtered to shipment types STANDARD, BLANKET, and SCHEDULED, and constrained by the rule's start and end dates against SYSDATE. The second branch joins purchase order data to MRP_SOURCES_V, matching on inventory item, organization, vendor, and vendor site, and constrained by the sourcing rule's effective and disable dates. The two branches are combined with UNION, eliminating duplicate rows. The USE_SR_FLAG column distinguishes which branch produced each row.

Key Columns

• ITEM_ID — Inventory item identifier; maps to PAR.ITEM_ID in the autosource branch and SR.INVENTORY_ITEM_ID in the MRP branch.
• VENDOR — Vendor name sourced from PO_VENDORS.
• RANK — Vendor rank, from autosource vendors or from the MRP sourcing rule rank.
• QUANTITY / QUANTITY_CANCELLED — Shipment quantities from PO_LINE_LOCATIONS_ALL.
• PRICE_OVERRIDE — Line location price override value.
• RATE — Currency exchange rate from the PO header.
• SPLIT — Split allocation from autosource vendors, or allocation percent from MRP_SOURCES_V.
• ORGANIZATION_ID and ASSIGNMENT_SET_ID — Populated only in the MRP branch; NULL in the autosource branch.
• PO_CREATION_DATE — Header creation date.
• USE_SR_FLAG — 'N' for autosource rows, 'Y' for MRP sourcing rule rows.
• ORG_ID — Operating unit identifier from the purchase order line.

Common Use Cases and Queries

This view supports reporting on combined sourcing coverage, supplier rationalization, and reconciliation between Purchasing autosource and MRP sourcing rules. A typical query retrieves all sourcing for a given item:

SELECT item_id, vendor, rank, split, use_sr_flag
FROM   apps.po_source_vendors_v
WHERE  item_id = :p_item_id
ORDER  BY rank;

To isolate MRP-driven sourcing only, filter on the flag:

SELECT item_id, vendor, rank, organization_id, assignment_set_id
FROM   apps.po_source_vendors_v
WHERE  use_sr_flag = 'Y'
AND    org_id = :p_org_id;

Because quantity and rate columns reflect active PO shipments, the view also supports price and quantity analysis across approved sources. Queries should account for the UNION duplication behavior and apply DISTINCT where appropriate. Performance is governed by the underlying joins; indexed access on ITEM_ID and ORG_ID is recommended.