Search Results total_reservation_quantity

Overview

APPS.MRP_DEMAND_OM_RESERVATIONS_V is an internal Oracle E-Business Suite view owned by the APPS schema and registered under FND Design Data as MRP.MRP_DEMAND_OM_RESERVATIONS_V. It exposes order management demand with associated reservation information in a form consumable by Oracle Materials Planning (MRP) and related supply chain planning processes. The view consolidates demand records originating from Oracle Order Management (OM) — including their reserved quantities — so that planning engines and reporting layers can treat sales order demand and its reservation status through a single interface.

The object is marked VALID and carries a critical Oracle internal-use-only warning: Oracle Corporation does not support direct access to this object except from standard Oracle Applications programs. Consequently, it should be treated as a planning-internal construct rather than a public integration API. In EBS 12.1.1 and 12.2.2 the view exists in the same conceptual role, though column-level availability and the exact planning dependency set may vary by patch level.

Because the view exposes TOTAL_RESERVATION_QUANTITY and LINE_ITEM_RESERVATION_QTY, it is commonly investigated when users search for total reservation quantity in the context of planning demands. It answers the question of how much of a given order line demand is currently reserved, expressed in both line and primary unit-of-measure terms.

Underlying Base Objects

The documented base objects referenced by the view are INV_DECIMALS_PUB (package), INV_SALESORDER (package), MRP_OE (package), and OE_ORDER_LINES_ALL (synonym). This indicates that the view is not a simple projection over a single table; it is constructed with logic supplied through the inventory decimal-handling package and the order management interfaces used by planning.

• OE_ORDER_LINES_ALL — the order line synonym, providing the fundamental demand attributes such as organization, item, ordered quantity, UOM, requirement date, and order line identifiers.
• INV_DECIMALS_PUB — used for unit-of-measure and numeric precision handling when converting between line-item quantity and primary UOM quantity.
• INV_SALESORDER — the inventory sales order package supporting reservation and demand processing.
• MRP_OE — the planning-to-order-management bridge package that filters and formats demand rows for the planning engine.

These dependencies confirm that the view is purpose-built for the planning demand stream, not a generic reporting view; MRP_OE in particular governs how scheduled and unscheduled order demand is surfaced.

Key Columns

The view exposes a broad set of demand, reservation, and supply reference columns. Notable entries include:

• DEMAND_ID — unique identifier for the demand record used by planning.
• ORGANIZATION_ID, INVENTORY_ITEM_ID — the planning organization and item context.
• DEMAND_SOURCE_TYPE, DEMAND_SOURCE_HEADER_ID, DEMAND_SOURCE_LINE, DEMAND_SOURCE_DELIVERY — identify the originating sales order and line.
• LINE_ITEM_QUANTITY, PRIMARY_UOM_QUANTITY — the ordered demand quantity in line and primary UOM terms.
• LINE_ITEM_RESERVATION_QTY, TOTAL_RESERVATION_QUANTITY — the reserved amounts on the line and the aggregate reservation quantity, the columns most often queried when reconciling reservations against demand.
• COMPLETED_QUANTITY — quantity already shipped or fulfilled.
• REQUIREMENT_DATE, MRP_DATE, MRP_QUANTITY — the scheduling dates and planning quantity.
• RESERVATION_TYPE, PARENT_DEMAND_ID, SUPPLY_SOURCE_TYPE, SUPPLY_SOURCE_HEADER_ID — reservation classification and supply linkage.
• REVISION, LOT_NUMBER, SERIAL_NUMBER, SUBINVENTORY, LOCATOR_ID — inventory detail dimensions for the reservation.
• CUSTOMER_ID, BILL_TO_SITE_USE_ID, SHIP_TO_SITE_USE_ID — customer and site references.

Common Use Cases and Queries

Typical usage centers on reconciling order demand with reservation quantities for planning, shortage analysis, and integration extracts. A representative query filters by organization and item and returns reservation totals:

SELECT demand_source_header_id, demand_source_line, inventory_item_id, line_item_quantity, total_reservation_quantity, requirement_date
FROM apps.mrp_demand_om_reservations_v
WHERE organization_id = :org_id
AND inventory_item_id = :item_id
ORDER BY requirement_date;

Planners also aggregate reserved demand by item to compare against on-hand and supply, or isolate lines where TOTAL_RESERVATION_QUANTITY is less than LINE_ITEM_QUANTITY to surface unreserved demand. Because the object is internal, any such query should be confined to diagnostic or read-only reporting and not embedded in supported production integrations; supported access is expected through Oracle Applications programs only.