Search Results mrp_primary_quantity




Overview
Explore in AI Chat

Overview

PO_REQ_SUPPLY_VIEW is an Oracle E-Business Suite 12.1.1 / 12.2.2 database view owned by the APPS schema within the PO – Purchasing product family. Its documented description is simply "Requisition supply," and its structural purpose is to expose requisition-driven supply records maintained in MTL_SUPPLY and enrich them with requisition header, line, and distribution attributes. Records appear only where MTL_SUPPLY.SUPPLY_TYPE_CODE = 'REQ', meaning every row represents supply created by the planning or sourcing engine in response to a purchase requisition.

Because requisition supply spans planning, purchasing, and inventory perspectives in the same physical supply row, the view presents each relevant quantity or date in three forms: the requisition context, the transactional UOM context, and the MRP/planning context. For a user searching on expected_delivery_date, the view is significant because it exposes both the requisition-driven EXPECTED_DELIVERY_DATE and the planning-driven MRP_EXPECTED_DELIVERY_DATE as separate columns, allowing reports to distinguish the documented delivery expectation from the planning horizon date. Revisions are active at the same time, so the view is a primary reference for reporting on open requisition supply across the enterprise.

Underlying Base Objects

Oracle documents seven referenced base objects (resolved through APPS synonyms) for this view:

The join chain is: supply to requisition line (MS.REQ_LINE_ID = PRL.REQUISITION_LINE_ID), line to distribution (PD.REQUISITION_LINE_ID = PRL.REQUISITION_LINE_ID), line to header (PRH.REQUISITION_HEADER_ID = MS.REQ_HEADER_ID), and supply to UOM. The predicate PRL.QUANTITY > 0 is applied to exclude zero-quantity lines. All header, line, and distribution quantities are divided by the requisition line quantity and multiplied by the distribution quantity, producing per-distribution supply amounts.

Key Columns

The view exposes 31 documented columns. Those most relevant to the expected-delivery-date search and to general supply reporting include:

Common Use Cases and Queries

Typical applications include open requisition supply reporting, expected delivery and need-by-date analysis, MRP-versus-requisition schedule variance, and supplier sourcing summaries.

To locate requisition supply by expected delivery date, filtered to the requisition-level date, a representative query is:

SELECT ri.requisition_number, ri.line_num, ri.item_id, ri.to_organization_id, ri.to_subinventory, ri.expected_delivery_date, ri.need_by_date, ri.quantity, ri.req_uom_code, ri.suggested_vendor_name
FROM apps.po_req_supply_view ri
WHERE TRUNC(ri.expected_delivery_date) BETWEEN :start_date AND :end_date
ORDER BY ri.expected_delivery_date, ri.requisition_number, ri.line_num;

To compare the requisition expectation against the planning schedule, a variance query projects both column values side by side:

SELECT requisition_number, line_num, item_id, expected_delivery_date, mrp_expected_delivery_date, (mrp_expected_delivery_date - expected_delivery_date) days_variance
FROM apps.po_req_supply_view
WHERE mrp_expected_delivery_date <> expected_delivery_date;

To summarize open requisition supply value by destination, aggregate over the primary-UOM columns:

SELECT to_organization_id, to_subinventory, SUM(primary_uom_quantity) supply_qty, SUM(primary_uom_quantity * unit_price) supply_value
FROM apps.po_req_supply_view
GROUP BY to_organization_id, to_subinventory;

Because the view is a single-row-per-distribution read-only construct, it can be consumed directly by BI Publisher reports, custom concurrent programs, and OBIEE or OTBI physical layer mappings without additional join logic. When building such reports on 12.1.1 or 12.2.2, note that the multiplication by requisition line quantity assumes one distribution per line; multiply-distribution requisitions will still yield one row per distribution, so aggregates must be grouped carefully to avoid double counting.