Search Results line_item_quantity

Overview

The SO_MTL_DEMAND_INT_DELIVERY view is a dictionary object owned by the APPS schema within the Oracle E-Business Suite Order Entry (OE) product family. It functions as a filtered, delivery-oriented projection of the demand interface table, exposing availability and ATP (Available-to-Promise) information for open demand records awaiting scheduling or reservation processing. Unlike a base table that stores persistent data, this view derives its result set at runtime by applying a fixed predicate to MTL_DEMAND_INTERFACE and enriching each qualifying row through calls to the OE_QUERY packaged functions.

The view is especially relevant to integrations and reports that must determine the AVAILABLE_QUANTITY for a given inventory item within a specific scheduling session. Because the quantity is computed dynamically rather than stored, the view reflects the current state of supply, reservations, and on-hand balances at the moment the query executes.

Underlying Base Objects

The ETRM documentation identifies two referenced base objects:

• MTL_DEMAND_INTERFACE (accessed via a SYNONYM) — the transaction interface table into which demand records are staged before the demand manager processes them.
• OE_QUERY (PACKAGE) — the package supplying the ATP_DATE_DELIVERY, AVAILABLE_QUANTITY_DELIVERY, and DEMAND_INTERFACE_ROWID_DEL functions.

The view selects only rows where N_COLUMN4 IS NULL and LINE_ITEM_QUANTITY > 0, filtering out processed records and zero-quantity lines. Each returned row is correlated to its source record through the session identifier (SESSION_ID) and the delivery-level source key (DEMAND_SOURCE_DELIVERY), which together drive the function calls.

Key Columns

• DEMAND_SOURCE_DELIVERY — the delivery-level identifier used as the primary correlation key passed into the OE_QUERY functions.
• INVENTORY_ITEM_ID — the inventory item for which demand and availability are evaluated.
• SESSION_ID — the demand interface processing session that scopes the computation; multiple sessions may coexist concurrently.
• ATP_DATE — the available-to-promise date returned by OE_QUERY.ATP_DATE_DELIVERY, indicating when the item can be promised.
• AVAILABLE_QUANTITY — the computed quantity available for the item and delivery, returned by OE_QUERY.AVAILABLE_QUANTITY_DELIVERY. This is the column most commonly searched when validating whether demand can be met.
• DEMAND_INTERFACE_ROWID — the row identifier from the underlying interface table, retrieved via OE_QUERY.DEMAND_INTERFACE_ROWID_DEL, allowing direct linkage back to the originating record.

Common Use Cases and Queries

The view is typically queried to validate that staged demand carries sufficient availability before the demand manager runs, or to troubleshoot scheduling discrepancies. A representative query retrieving availability for a particular item and session:

• SELECT DEMAND_SOURCE_DELIVERY, INVENTORY_ITEM_ID, ATP_DATE, AVAILABLE_QUANTITY FROM APPS.SO_MTL_DEMAND_INT_DELIVERY WHERE INVENTORY_ITEM_ID = :item_id AND SESSION_ID = :session_id;
• SELECT * FROM APPS.SO_MTL_DEMAND_INT_DELIVERY WHERE AVAILABLE_QUANTITY < 0 ORDER BY DEMAND_SOURCE_DELIVERY; — isolates demand lines with insufficient supply.
• SELECT DEMAND_INTERFACE_ROWID, AVAILABLE_QUANTITY FROM APPS.SO_MTL_DEMAND_INT_DELIVERY WHERE SESSION_ID = :session_id; — supports reconciliation back to MTL_DEMAND_INTERFACE.

Because the availability functions execute per row, performance is sensitive to result set size and should be constrained by SESSION_ID and item filters in production queries.