Search Results requirement_date




Overview
Explore in AI Chat

Overview

The APPS.MRP_DEMAND_OM_RESERVATIONS_V view is a Master Scheduling/MRP (MRP) reporting object that consolidates order management demand and reservation information for consumption by Oracle MRP planning engines and custom reporting. The view exposes sales order lines from Oracle Order Management in a demand-oriented shape compatible with the MRP demand interface, translating Order Management line attributes into the standardized demand columns (DEMAND_ID, DEMAND_SOURCE_TYPE, DEMAND_SOURCE_LINE, REQUIREMENT_DATE, and so on) expected by MRP planning logic. It is validated and owned by the APPS schema in both EBS 12.1.1 and 12.2.2, and functions as a read-only data source rather than a stored table.

Its principal value is that it normalizes order management quantities into the inventory primary unit of measure, enabling planners and reporting tools to reason about demand consistently across items maintained with differing UOMs.

Underlying Base Objects

The documented view metadata lists the following referenced objects: the packages INV_DECIMALS_PUB, INV_SALESORDER, and MRP_OE, and the synonym OE_ORDER_LINES_ALL (which resolves to the base Order Management lines table).

Key Columns

  • DEMAND_ID — derived from OOL.LINE_ID; the unique identifier for the demand record.
  • ORGANIZATION_ID — the ship-from inventory organization.
  • DEMAND_SOURCE_TYPE — DECODE of SOURCE_DOCUMENT_TYPE_ID and LINE_CATEGORY_CODE, assigning the MRP demand source classification (for example 8, 2, or 12).
  • UOM_CODE — the order quantity UOM from OOL.ORDER_QUANTITY_UOM.
  • LINE_ITEM_QUANTITY — the ordered quantity as entered on the order line.
  • PRIMARY_UOM_QUANTITY — the ordered quantity converted to the inventory primary UOM using INV_DECIMALS_PUB.GET_PRIMARY_QUANTITY; this is the value most commonly searched for by planners reconciling demand to on-hand inventory.
  • TOTAL_RESERVATION_QUANTITY — SUM of NAVL(MD1.PRIMARY_UOM_QUANTITY, 0), aggregating reservation quantities.
  • COMPLETED_QUANTITY — the shipped quantity converted to the primary UOM.
  • REQUIREMENT_DATE — from OOL.SCHEDULE_SHIP_DATE; the date MRP uses for scheduling.
  • DEMAND_CLASS_CODE and VISIBLE_DEMAND_FLAG — classification and visibility indicators for the demand record.
  • MRP_DATE and MRP_QUANTITY — MRP-derived planning values returned by the MRP_OE package.

Common Use Cases and Queries

Typical applications include reconciling open sales order demand against MRP planned orders, auditing primary UOM conversions where order and inventory UOMs differ, and confirming whether a line is visible to planning.

Sample query returning primary UOM quantities for a given organization and item:

SELECT demand_id,
       organization_id,
       inventory_item_id,
       uom_code,
       line_item_quantity,
       primary_uom_quantity,
       total_reservation_quantity,
       requirement_date
FROM   apps.mrp_demand_om_reservations_v
WHERE  organization_id = :org_id
AND    inventory_item_id = :item_id
AND    visible_demand_flag = 'Y';

A second common pattern inspects MRP planning output for a demand line:

SELECT demand_id, mrp_date, mrp_quantity, row_status_flag
FROM   apps.mrp_demand_om_reservations_v
WHERE  demand_source_header_id = :order_number
ORDER  BY demand_id;

Because the view relies on package functions INV_DECIMALS_PUB.GET_PRIMARY_QUANTITY, MRP_OE.MRP_DATE, and MRP_OE.MRP_QUANTITY, heavy ad hoc queries over large order volumes can be expensive; filtering by organization and item before aggregation is recommended.