Search Results mtl_demand




Overview
Explore in AI Chat

Overview

The MTL_DEMAND table is a core transactional table within the Oracle E-Business Suite Inventory (INV) module, specifically for versions 12.1.1 and 12.2.2. It serves as the primary repository for sales order demand and reservation records. Its fundamental role is to track and manage the specific allocation of on-hand inventory to fulfill sales orders and other demand sources. This table is critical for maintaining accurate available-to-promise (ATP) calculations, supporting reservation logic, and interfacing with Oracle Order Management and Advanced Supply Chain Planning modules. The data in MTL_DEMAND directly influences material availability, shipment scheduling, and fulfillment workflows.

Key Information Stored

The table stores detailed records linking demand sources to specific inventory items and their attributes. Key columns, as indicated by its primary and foreign keys, include DEMAND_ID (a unique system-generated identifier), INVENTORY_ITEM_ID, and ORGANIZATION_ID to identify the item and its owning inventory organization. Crucially, it tracks the demand source through DEMAND_SOURCE_HEADER_ID, DEMAND_SOURCE_TYPE, DEMAND_SOURCE_LINE, and DEMAND_SOURCE_DELIVERY, which typically reference sales order headers and lines. For reservations, it stores the precise inventory location using SUBINVENTORY and LOCATOR_ID, and can track specific lots (LOT_NUMBER) and revisions (REVISION). The COMPONENT_SEQUENCE_ID links demand for components to specific Bills of Material (BOM).

Common Use Cases and Queries

Common use cases include analyzing sales order reservations, troubleshooting fulfillment issues, and generating custom availability reports. Technical consultants often query this table to reconcile inventory commitments. A typical query pattern joins MTL_DEMAND with MTL_SYSTEM_ITEMS_B and OE_ORDER_HEADERS_ALL to report on all reservations for a specific item or sales order.

  • Sample Query: To find all reservations for a sales order:
    SELECT md.demand_id, msi.segment1 item_code, md.quantity
    FROM inv.mtl_demand md,
    inv.mtl_system_items_b msi
    WHERE md.inventory_item_id = msi.inventory_item_id
    AND md.organization_id = msi.organization_id
    AND md.demand_source_header_id = <order_header_id>
    AND md.demand_source_type = 2; -- Typically 'Sales Order'
  • Another critical use is interfacing with planning systems (MRP), as the table is referenced by MRP_RELIEF_INTERFACE and MRP_SALES_ORDER_UPDATES for demand relief and order update processes.

Related Objects

MTL_DEMAND has extensive foreign key relationships, centralizing its integration within the EBS schema. Key documented relationships include: