Search Results mtl_demand_interface




Overview
Explore in AI Chat

Overview

The MTL_DEMAND_INTERFACE table is a core transactional interface within the Oracle E-Business Suite Inventory (INV) module. As documented in the ETRM, it serves as a temporary demand storage area for the transaction processor. Its primary role is to act as a staging table for demand data, such as sales orders, before this data is processed and transferred into the permanent demand tables of the system. This interface-based architecture allows for data validation, error handling, and batch processing, ensuring data integrity before it impacts live inventory availability and planning calculations. It is a critical component for the integration between Order Management and Inventory modules.

Key Information Stored

The table holds detailed records for demand lines awaiting processing. Key columns, as indicated by its foreign key relationships, include identifiers for the demand source (DEMAND_SOURCE_HEADER_ID, DEMAND_SOURCE_LINE_ID), the item (INVENTORY_ITEM_ID), and the organization (ORGANIZATION_ID). It stores critical fulfillment details such as the requested quantity, schedule dates, and sourcing instructions. The table also links to specific inventory attributes, including SUBINVENTORY, LOCATOR_ID, LOT_NUMBER, and REVISION, which define exactly from where the material should be supplied. The ATP_RULE_ID column references the Available-to-Promise rule used for the demand validation.

Common Use Cases and Queries

The most common use case is troubleshooting failed demand interface transactions, such as sales order import or backlog processing. Developers and support personnel frequently query this table to identify records with processing errors. A typical diagnostic query examines rows with an INTERFACE_STATUS other than a successful processed state, joining to item and sales order tables for context.

  • Sample Query for Pending/Errored Demand: SELECT mdi.* FROM inv.mtl_demand_interface mdi WHERE mdi.interface_status IN (2, 3) AND mdi.process_flag = 1;
  • Use Case - Data Validation: Before launching the standard "Process Interface" concurrent request, users may run custom scripts to validate data in this table against master data (items, locators, lots) to preempt failures.
  • Use Case - Integration Monitoring: Automated jobs may monitor the record count in this table to ensure the interface is being cleared and to alert on backlogs.

Related Objects

As per the provided ETRM metadata, MTL_DEMAND_INTERFACE has extensive foreign key relationships, highlighting its central position in the inventory schema. Key related objects include: