Search Results mrp_rhx_purchasing_supply_v

Overview

The MRP_RHX_PURCHASING_SUPPLY_V view is a component of the Oracle E-Business Suite Integration Toolkit for the Master Scheduling/MRP (MRP) module. Its stated purpose is to expose information regarding the supply of planned items — specifically purchase-order-based supply that Master Scheduling/MRP evaluates when determining whether demand can be satisfied. The RHX naming convention identifies this object as part of the MRP integration repository, a family of views designed to present planning data in a stable, queryable form for external reporting tools, custom integrations, and third-party planning systems. The view is documented in ETRM under the MRP product family for both 12.1.1 and 12.2.2, and the supplied metadata notes that it is not implemented in the reference database from which the documentation was drawn — a common situation for optional Integration Toolkit objects that must be enabled or for views whose underlying sources are not populated in a given environment. Implementers should therefore verify existence in their own instance before relying on it.

Underlying Base Objects

The view text is defined as a UNION ALL of at least two query branches. The first branch joins the following base objects:

• PO_PO_SUPPLY_VIEW (aliased PO) — the primary purchase-order supply source, contributing header, line, delivery, quantity, and destination attributes.
• MRP_RHX_PLANNED_ITEMS_V (aliased ITEMS) — the planned-item master, supplying INVENTORY_ITEM_ID, ITEM_NUMBER, ORGANIZATION_ID, and SHRINKAGE_RATE.
• PO_VENDORS — furnishes the vendor name associated with the purchase order.
• MTL_UNITS_OF_MEASURE — resolves the primary unit-of-measure code.
• PO_LINES_ALL — supplies descriptive-flexfield attributes (ATTRIBUTE_CATEGORY through ATTRIBUTE15) at the line level.

The second branch sources shipment-level supply from a shipment supply view (aliased SSV, contributing SHIPMENT_HEADER_ID) with matching columns and a distinct source-type indicator. Joins are keyed on PO_LINE_ID, VENDOR_ID, and matching inventory item/organization combinations. Filters restrict the result to destination type 'INVENTORY', positive to-organization quantities, and non-null line identifiers.

Key Columns

• INVENTORY_ITEM_ID / ITEM_NUMBER / ORGANIZATION_ID — identifies the planned item and the owning organization.
• MRP_TO_ORGANIZATION_ID — the destination organization used in the planning calculation.
• PO_HEADER_ID / PO_LINE_ID / PO_NUMBER — purchase order document identifiers.
• VENDOR_ID / VENDOR_NAME — supplier information.
• MRP_EXPECTED_DELIVERY_DATE / EXPECTED_DELIVERY_DATE / EXPECTED_DOCK_DATE — the planning-relevant and transactional delivery dates.
• MRP_PRIMARY_QUANTITY / TO_ORG_PRIMARY_QUANTITY — supply quantities, with a shrinkage-adjusted variant computed via DECODE(SIGN(SHRINKAGE_RATE)...).
• QUANTITY / UNIT_PRICE / UOM_CODE — order quantity, price, and unit of measure.
• FIRM_PLANNED_STATUS_FLAG — decoded to distinguish firm versus planned supply (1 = firm, 2 = planned).
• MRP_DESTINATION_TYPE_CODE / DESTINATION_TYPE_CODE — supply destination classification.
• ATTRIBUTE1–15 / ATTRIBUTE_CATEGORY — line-level descriptive flexfields.

Common Use Cases and Queries

Typical uses include reconciling MRP-recognized purchase-order supply against actual open PO commitments, feeding external planning engines, and auditing shrinkage-adjusted quantities by item and vendor. A representative query filters on organization and item:

SELECT item_number, po_number, vendor_name,
       mrp_expected_delivery_date, mrp_primary_quantity, uom_code
FROM   mrp_rhx_purchasing_supply_v
WHERE  organization_id = :org_id
AND    inventory_item_id = :item_id
ORDER  BY mrp_expected_delivery_date;

Because the view is not guaranteed to exist in every environment, a pre-flight check against ALL_VIEWS is advisable before embedding it in dependent code.