Search Results mtl_user_demand




Overview
Explore in AI Chat

Overview

MTL_USER_DEMAND is an Inventory (INV) module table that stores external demand information to be considered during Available-to-Promise (ATP) processing. In Oracle EBS 12.1.1 and 12.2.2, ATP calculations traditionally draw upon scheduled shipments, sales orders, and internal requisitions. MTL_USER_DEMAND extends that picture by allowing planners and integrators to inject demand from external sources — forecasts, third-party systems, or what-if simulations — so that the ATP engine recognizes it when computing supply availability. Records are owned by the INV schema and are tightly coupled to a specific inventory item within a specific organization.

From a Data Vault modeling perspective, the mined foreign-key structure suggests a satellite-leaning classification. The table carries descriptive and measurable demand attributes (quantities, dates, demand classes) that describe a single item-organization nexus rather than establishing relationships between multiple hubs. It is best understood as an attribute-bearing satellite attached to the item and organization keys.

Key Information Stored

The documented physical schema contains 13 columns. The most significant are summarized below:

The metadata does not document a single-column surrogate primary key; the effective business key is the combination of ORGANIZATION_ID and INVENTORY_ITEM_ID, with the remaining attributes acting as descriptive payload.

Common Use Cases and Queries

Typical scenarios include validating that external demand was loaded correctly before an ATP run, reconciling forecast injections against requirements, and building reports of pending external demand by item and organization.

  • Reviewing all demand for a given item and organization:

SELECT INVENTORY_ITEM_ID, ORGANIZATION_ID, PRIMARY_UOM_QUANTITY, REQUIREMENT_DATE, DEMAND_CLASS FROM INV.MTL_USER_DEMAND WHERE ORGANIZATION_ID = :org AND INVENTORY_ITEM_ID = :item;

  • Aggregating demand by requirement date to feed a planning report or dashboard.
  • Filtering by SOURCE_TYPE_ID or SOURCE_NAME to audit a particular external system's contributions.
  • Joining to MTL_SYSTEM_ITEMS_B to obtain item descriptions and concatenated segments for user-friendly output.

Related Objects

The most significant related objects are:

  • MTL_SYSTEM_ITEMS_B — Referenced through MTL_USER_DEMAND.INVENTORY_ITEM_ID and MTL_USER_DEMAND.ORGANIZATION_ID; the primary FK target and the basis of most reporting joins.
  • ATP processing logic — The scheduling and ATP engines consume MTL_USER_DEMAND rows when computing availability.
  • Planning and forecasting modules — Depending on configuration, external demand records may complement or be reconciled with planning data.

Because the metadata documents only one foreign key relationship, MTL_SYSTEM_ITEMS_B remains the dominant dependency. Any query joining this table should anchor on ORGANIZATION_ID and INVENTORY_ITEM_ID to guarantee correct item-organization context.