Search Results external_source_code




Overview
Explore in AI Chat

Overview

APPS.MTL_DEMAND_OM_VIEW is a VALID database view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the INV (Inventory) product module. It presents order-management demand records in the standard MTL_DEMAND format, deriving its rows from order management lines rather than from the physical MTL_DEMAND table. Its principal role is to expose open sales order line demand to the material planning and inventory reservation engines—specifically MRP, ATP, and reservation processing—in a normalized structure that mirrors the columns of MTL_DEMAND.

The view is significant because the RESERVATION_TYPE column is hard-coded to the literal 1 in the view definition. This distinguishes order-management demand from other demand sources and provides the attribute that reservation and planning logic uses to classify the record. Because the view synthesizes MTL_DEMAND-shaped output from OE_ORDER_LINES_ALL, it allows planning and reservation routines to consume sales order demand without requiring that demand to be staged into MTL_DEMAND first.

Underlying Base Objects

The documented base objects underlying this view are: OE_ORDER_LINES_ALL (SYNONYM), MTL_DEMAND (SYNONYM), and the packages INV_DECIMALS_PUB, INV_SALESORDER, MRP_OE, and OE_INSTALL.

  • OE_ORDER_LINES_ALL — the primary source of demand rows; aliased as OOL in the view text, supplying line ID, ship-from organization, inventory item, order quantity, shipped quantity, schedule ship date, demand class, and customer/site identifiers.
  • MTL_DEMAND — the reference structure the view emulates column-for-column; rows are shaped to match its demand model.
  • INV_DECIMALS_PUB — provides GET_PRIMARY_QUANTITY, converting ordered and shipped quantities into the item's primary unit of measure.
  • INV_SALESORDER — provides GET_SALESORDER_FOR_OEHEADER, resolving the header ID to the sales order number.
  • MRP_OE — supplies planning-related functions: UPDATED_FLAG, AVAILABLE_TO_MRP, AVAILABLE_TO_ATP, MRP_DATE, and MRP_QUANTITY, which inject MRP/ATP eligibility and calculated dates and quantities.
  • OE_INSTALL — an order management installation/utility package referenced in the view's dependency chain.

Key Columns

Common Use Cases and Queries

A principal scenario is identifying order-management reservations and their type, aligned with the "reservation_type" search context:

  • Retrieve all reservation-typed order demand for an item in an organization.
  • Report sales order demand available to MRP or ATP for a planning horizon.
  • Reconcile order line quantities against reserved and completed quantities.

Representative query:

SELECT demand_id, organization_id, inventory_item_id, demand_source_header_id,
  reservation_type, reservation_quantity, primary_uom_quantity,
  completed_quantity, requirement_date, available_to_mrp, available_to_atp
FROM apps.mtl_demand_om_view
WHERE inventory_item_id = :item_id
  AND organization_id = :org_id
  AND reservation_type = 1;

Because the view relies on PL/SQL functions within its SELECT list, users should account for per-row function execution cost when querying large order volumes.