Search Results demand




The INV.MTL_DEMAND table in Oracle E-Business Suite (EBS) versions 12.1.1 and 12.2.2 serves as a critical repository for demand information within the Inventory (INV) module. This table captures demand data generated from various sources, including sales orders, work orders, and other supply chain planning activities, enabling organizations to manage inventory requirements effectively. Below is a detailed analysis of its structure, purpose, and integration within Oracle EBS.

Purpose and Functionality

The MTL_DEMAND table stores transactional demand records that drive inventory replenishment, material planning, and order fulfillment processes. It acts as an intermediary between demand sources (e.g., Order Management, Manufacturing) and supply planning tools like Oracle Advanced Supply Chain Planning (ASCP). Key functionalities include:

  • Demand Tracking: Records demand types such as sales orders, forecasts, and interplant transfers.
  • Integration with MRP/ASCP: Supplies data for Material Requirements Planning (MRP) runs to generate supply recommendations.
  • Inventory Optimization: Helps balance stock levels by aligning demand with available supply.

Table Structure

The table comprises columns that categorize and quantify demand. Notable columns include:

Column Name Data Type Description
DEMAND_ID NUMBER Primary key, uniquely identifies each demand record.
INVENTORY_ITEM_ID NUMBER References MTL_SYSTEM_ITEMS to link the demand to a specific item.
ORGANIZATION_ID NUMBER Indicates the inventory organization where the demand applies.
DEMAND_TYPE NUMBER Classifies demand (e.g., 1 for sales orders, 2 for forecasts).
QUANTITY NUMBER The demanded quantity.
DEMAND_DATE DATE Date when the demand is required.
SOURCE_HEADER_ID NUMBER Links to the originating document (e.g., OE_ORDER_HEADERS for sales orders).

Integration with Oracle EBS Modules

The MTL_DEMAND table integrates with multiple EBS modules:

  • Order Management (OM): Sales orders create demand records via the OE_ORDER_LINES interface.
  • Manufacturing (WIP): Work orders generate demand for components.
  • Planning (MRP/ASCP): Demand data feeds into planning engines to recommend purchases, transfers, or production.

Key Processes

Demand Creation: Triggered by order entry or planning systems, records are inserted into MTL_DEMAND via APIs or direct SQL.
Demand Consumption: During MRP runs, demand is matched with supply (e.g., on-hand stock, purchase orders).
Purge Mechanism: Obsolete demands are archived or deleted via concurrent programs like "Purge Obsolete Demand."

Performance Considerations

Large datasets in MTL_DEMAND can impact MRP performance. Indexes on INVENTORY_ITEM_ID, ORGANIZATION_ID, and DEMAND_DATE are critical. Partitioning by date ranges is recommended for high-volume environments.

Conclusion

The INV.MTL_DEMAND table is a cornerstone of Oracle EBS inventory and supply chain planning, bridging transactional systems with planning engines. Its design supports traceability, scalability, and integration, ensuring accurate demand visibility across the enterprise. Proper maintenance and indexing are essential to sustain performance in complex deployments.