Search Results mtl_demand




The MTL_DEMAND table in Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2 is a critical inventory management entity that stores demand information for items across various modules, including Order Management, Inventory, Purchasing, and Manufacturing. This table acts as a central repository for tracking demand transactions, ensuring accurate material planning, replenishment, and fulfillment processes. Below is a detailed technical overview of its structure, purpose, and integration within Oracle EBS.

Purpose and Functional Role

The MTL_DEMAND table captures demand data generated from sales orders, work orders, replenishment requests, and other sources. It serves as an intermediary between transactional systems (e.g., Order Management) and inventory planning tools (e.g., MRP). Key functions include:
  • Demand Tracking: Records item-level demand quantities, dates, and sourcing details.
  • Integration Hub: Links to MTL_SUPPLY for supply-demand balancing.
  • MRP Processing: Provides input for Material Requirements Planning (MRP) runs.
  • ATP Checks: Supports Available-to-Promise (ATP) calculations by storing committed demand.

Key Columns and Relationships

The table's schema includes columns that define demand attributes and relationships with other EBS entities:
  • DEMAND_ID: Primary key, uniquely identifying each demand record.
  • INVENTORY_ITEM_ID: References MTL_SYSTEM_ITEMS_B for item details.
  • ORGANIZATION_ID: Links to HR_ALL_ORGANIZATION_UNITS for inventory org.
  • DEMAND_TYPE: Classifies demand (e.g., Sales Order, Work Order).
  • DEMAND_SOURCE_HEADER_ID: Foreign key to source documents (e.g., OE_ORDER_HEADERS_ALL for sales orders).
  • QUANTITY: Demand quantity in primary UOM.
  • DATE_REQUIRED: Fulfillment due date.
  • STATUS: Tracks lifecycle (e.g., Open, Closed, Cancelled).

Integration with Oracle EBS Modules

MTL_DEMAND interacts with multiple EBS modules:
  1. Order Management: Sales orders create demand records via OE_ORDER_LINES_ALL.
  2. Inventory: Supports reservations, allocations, and ATP checks.
  3. Manufacturing: Work order demands are stored for component requirements.
  4. Purchasing: Replenishment requests trigger demand for procurement.

Technical Considerations

  • Indexing: Key indexes include MTL_DEMAND_N1 (DEMAND_ID) and MTL_DEMAND_N2 (INVENTORY_ITEM_ID, ORGANIZATION_ID).
  • Purge Logic: Demand records are archived via concurrent programs like "Purge Obsolete Demand."
  • Performance: High-volume systems may require partitioning by DATE_REQUIRED or ORGANIZATION_ID.

Customization and Extensions

Common extensions include:
  • Custom demand types for specialized workflows.
  • Triggers to enforce business rules during demand creation.
  • APIs (e.g., INV_DEMAND_PUB) for programmatic demand manipulation.

Conclusion

The MTL_DEMAND table is foundational to Oracle EBS's inventory and supply chain orchestration. Its design ensures traceability of demand sources, supports complex planning algorithms, and facilitates cross-module integration. Proper understanding of this table is essential for troubleshooting fulfillment issues, optimizing MRP, and customizing demand-driven processes.