Search Results mtl_supply_demand_temp




Overview
Explore in AI Chat

Overview

MTL_SUPPLY_DEMAND_TEMP is a temporary (transient) table owned by the INV schema in Oracle E-Business Suite. As documented in the ETRM metadata for releases 12.1.1 and 12.2.2, its purpose is to hold ATP (Available-to-Promise) detail records returned from an ATP user-exit. The table functions as a staging area into which a user-exit program writes computed supply, demand, and availability information, which downstream Oracle Inventory scheduling and ATP logic then consume. Because records are transient by design, rows are typically populated and consumed within a single concurrent process or session and are not intended for long-term retention.

From a data-modeling perspective, the heuristic Data Vault classification derived from the foreign-key structure is satellite-leaning. This suggests the table is best understood as a descriptive satellite attached to the core item/organization hub (MTL_SYSTEM_ITEMS_B), carrying measures and context rather than defining new business entities. It should not be treated as a source of truth for persistent supply/demand balances.

Key Information Stored

The documented physical schema contains 45 columns. The most consequential are:

While the metadata documents foreign keys to MTL_SYSTEM_ITEMS_B, AHL_PRD_DISPOSITIONS_B, and BOM_DEPARTMENTS, no explicit surrogate primary key is listed; SEQ_NUM or GROUP_ID combined with the item/organization pair typically serves as the practical identifier.

Common Use Cases and Queries

Typical usage involves querying staged ATP results for a specific item and organization within a run, or joining to master data for reporting.

  • Retrieve staged ATP for an item/organization: SELECT ATP_PERIOD_START_DATE, ATP, PERIOD_NET_AVAILABLE FROM MTL_SUPPLY_DEMAND_TEMP WHERE INVENTORY_ITEM_ID = :item AND ORGANIZATION_ID = :org;
  • Summarize supply and demand by period using ATP_PERIOD_TOTAL_SUPPLY and ATP_PERIOD_TOTAL_DEMAND.
  • Debugging ATP user-exit logic by inspecting ROW_NUMBER, RECORD_TYPE, and the C_/N_/D_ overflow columns.
  • Reconciling on-hand versus available quantities via ON_HAND_QUANTITY and ATP.

Related Objects

  • MTL_SYSTEM_ITEMS_B — joined on INVENTORY_ITEM_ID and ORGANIZATION_ID.
  • AHL_PRD_DISPOSITIONS_B — joined on DISPOSITION_ID.
  • BOM_DEPARTMENTS — joined on DEPARTMENT_ID.
  • MTL_ONHAND_QUANTITIES and MTL_DEMAND — primary supply/demand sources compared during ATP.
  • ATP user-exit APIs — populate this table at runtime.
  • MRP/Planning and Order Management ATP — consumers of the resulting availability data.