Results for “mtl_demand”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

INV.MTL_DEMAND is the Inventory module's central transactional table for sales order demand and reservations. Each row represents a discrete demand line—an outstanding requirement for an inventory item within a specific organization, subinventory, and locator combination. The table records the quantity originally demanded, quantities already reserved and completed, and the scheduling dates that drive both Material Requirements Planning (MRP) and Available-to-Promise (ATP) processing. Because MRP, shipping, and order management all consume this table concurrently, it is one of the highest-volume and most frequently updated objects in a production EBS instance.

From a Data Vault modeling perspective, the mined foreign-key structure suggests a satellite-leaning classification. The table carries descriptive and mutable quantities (reservation, completed, MRP quantities) that change over the life of a demand line, which is characteristic of satellite behavior. However, the composite primary key MTL_DEMAND_PK (INVENTORY_ITEM_ID, DEMAND_SOURCE_HEADER_ID, DEMAND_SOURCE_TYPE, DEMAND_SOURCE_LINE, DEMAND_SOURCE_DELIVERY, COMPONENT_SEQUENCE_ID) behaves more like a multi-part business key. The distinct surrogate candidate MTL_DEMAND_U1 on DEMAND_ID supports this dual interpretation—DEMAND_ID serves as the stable hub key while the composite PK enforces the natural business key.

Key Information Stored

The 87 documented columns fall into several logical groups. The most operationally significant are listed below; the full column list is intentionally not enumerated.

• DEMAND_ID — surrogate identifier, enforced by the unique index MTL_DEMAND_U1; the anchor for most downstream references.
• DEMAND_SOURCE_TYPE, DEMAND_SOURCE_HEADER_ID, DEMAND_SOURCE_LINE, DEMAND_SOURCE_DELIVERY — the business-key tuple that identifies the originating sales order line and shipment. DEMAND_SOURCE_TYPE resolves against MTL_TXN_SOURCE_TYPES, while the header ID joins back to MTL_SALES_ORDERS.
• INVENTORY_ITEM_ID, ORGANIZATION_ID — the item and inventory organization context, referencing MTL_SYSTEM_ITEMS_B.
• LINE_ITEM_QUANTITY, PRIMARY_UOM_QUANTITY, RESERVATION_QUANTITY, LINE_ITEM_RESERVATION_QTY, MASTER_RESERVATION_QTY, COMPLETED_QUANTITY — the quantity lifecycle, from original demand through reservation to shipped/completed state.
• REQUIREMENT_DATE, MRP_DATE, MRP_QUANTITY, AVAILABLE_TO_MRP, AVAILABLE_TO_ATP — scheduling and planning attributes consumed by the MRP engine and ATP logic.
• SUBINVENTORY, LOCATOR_ID, LOT_NUMBER, SERIAL_NUMBER, REVISION — the specific material control dimensions, each with corresponding validation FKs.
• COMPONENT_SEQUENCE_ID, PARENT_DEMAND_ID, BOM_LEVEL — support for configured or bill-of-material parent/child demand hierarchies.
• CUSTOMER_ID, SHIP_TO_SITE_USE_ID, BILL_TO_SITE_USE_ID — customer-facing context for order fulfillment reporting.

Common Use Cases and Queries

The most frequent query pattern is retrieval of open demand for a given item or organization, typically filtered by requirement date window:

SELECT demand_id, inventory_item_id, organization_id,
       primary_uom_quantity, reservation_quantity, requirement_date
  FROM   mtl_demand
 WHERE  inventory_item_id = :p_item
   AND  organization_id   = :p_org
   AND  requirement_date BETWEEN :p_from AND :p_to;

Because the user search term was mrp_relief_interface, a common diagnostic involves verifying whether demand rows have been relieved into MRP. The MRP relief process writes disposition records into MRP_RELIEF_INTERFACE, keyed by DISPOSITION_ID, which traces back to MTL_DEMAND.DEMAND_ID. Queries joining the two tables identify demand lines that failed to relieve:

SELECT d.demand_id, d.demand_source_header_id, d.requirement_date, r.disposition_id
  FROM   mtl_demand d, mrp_relief_interface r
 WHERE  r.disposition_id = d.demand_id
   AND  r.process_status = 1;

Additional reporting use cases include reservation aging (comparing creation_date to requirement_date), backlog analysis by completed_quantity versus line_item_quantity, and reconciliation of sales order demand against MRP_SALES_ORDER_UPDATES.

Related Objects

• MRP_RELIEF_INTERFACE — references MTL_DEMAND via DISPOSITION_ID; tracks MRP relief of demand records.
• MRP_SALES_ORDER_UPDATES — references MTL_DEMAND via SALES_ORDER_ID; captures changes to sales order demand for MRP synchronization.
• MTL_DEMAND_INTERFACE — references MTL_DEMAND via DEMAND_ID; staging area for demand import and interface processing.
• MTL_SALES_ORDERS — parent sales order header for demand lines.
• MTL_SYSTEM_ITEMS_B — validated source for INVENTORY_ITEM_ID and DUPLICATED_CONFIG_ITEM_ID.
• MTL_SECONDARY_INVENTORIES — validates SUBINVENTORY and ORGANIZATION_ID.
• MTL_ITEM_LOCATIONS — validates LOCATOR_ID.
• MTL_LOT_NUMBERS, MTL_ITEM_REVISIONS_B — validate LOT_NUMBER and REVISION respectively.
• BOM_COMPONENTS_B — validates COMPONENT_SEQUENCE_ID for BOM-driven demand.
• MTL_TXN_SOURCE_TYPES — validates DEMAND_SOURCE_TYPE.