Search Results line_item_quantity




Overview
Explore in AI Chat

Overview

APPS.SO_MTL_DEMAND_INT_DELIVERY is a reporting and integration view in the Oracle E-Business Suite Order Management (OM) module. It exposes delivery-related demand interface records from the MTL_DEMAND_INTERFACE table, enriched with schedule-related attributes derived at runtime from the OE_QUERY package. The view is scoped specifically to delivery demand — that is, demand records identified by the DEMAND_SOURCE_DELIVERY column — and provides a consolidated, query-friendly projection for ATP (Available-to-Promise) reporting and delivery scheduling activities. In the context of Oracle EBS 12.1.1 and 12.2.2, this view is typically consumed by scheduling and availability reports, and by components that need to resolve ATP dates and available quantities for pending delivery demand lines without directly invoking the OE_QUERY package APIs. Because the view filters on MTL_DEMAND_INTERFACE and calls packaged PL/SQL functions, it is a query-only construct and is not intended for DML. The session-scoped design means its output is meaningful only for the active scheduling session identified by SESSION_ID.

Underlying Base Objects

The view is defined over two documented base objects: MTL_DEMAND_INTERFACE (referenced through its synonym) and the OE_QUERY package. MTL_DEMAND_INTERFACE stores unprocessed demand lines awaiting processing by the order management demand interface, including delivery-sourced demand. The OE_QUERY package supplies the three derived columns — ATP date, available quantity, and the demand interface row identifier — through a set of package functions keyed on both SESSION_ID and DEMAND_SOURCE_DELIVERY. The view joins these by passing the matching row values into each function call, so that each returned row is correlated to its session and delivery source. The restricting predicate N_COLUMN4 IS NULL AND LINE_ITEM_QUANTITY > 0 ensures only qualifying, unmarked demand rows are surfaced. Dependence on OE_QUERY's function results means query performance is directly tied to the efficiency of those package routines and the presence of session data in the interface table.

Key Columns

  • DEMAND_SOURCE_DELIVERY — The delivery source identifier for the demand line; also used as the second key into each OE_QUERY function.
  • INVENTORY_ITEM_ID — The inventory item for which delivery demand exists; the primary item dimension for reporting.
  • SESSION_ID — The scheduling session identifier that scopes the OE_QUERY function calls; central to the view's purpose and the column most often filtered by users.
  • ATP_DATE — Result of OE_QUERY.ATP_DATE_DELIVERY(SESSION_ID, DEMAND_SOURCE_DELIVERY); the calculated ATP date for the delivery demand.
  • AVAILABLE_QUANTITY — Result of OE_QUERY.AVAILABLE_QUANTITY_DELIVERY(SESSION_ID, DEMAND_SOURCE_DELIVERY); the quantity available to promise for the line.
  • DEMAND_INTERFACE_ROWID — Result of OE_QUERY.DEMAND_INTERFACE_ROWID_DEL(SESSION_ID, DEMAND_SOURCE_DELIVERY); the physical row identifier of the underlying MTL_DEMAND_INTERFACE record.

Common Use Cases and Queries

Typical use cases include ATP review for a scheduling session, reconciliation of available quantity against existing delivery demand, and drill-back from a derived row to its originating MTL_DEMAND_INTERFACE record via the returned ROWID.

A session-focused query is the most common access pattern:

  • SELECT DEMAND_SOURCE_DELIVERY, INVENTORY_ITEM_ID, ATP_DATE, AVAILABLE_QUANTITY FROM APPS.SO_MTL_DEMAND_INT_DELIVERY WHERE SESSION_ID = :session_id;

To review items with shortfall against demand, filter on available quantity:

  • SELECT INVENTORY_ITEM_ID, AVAILABLE_QUANTITY FROM APPS.SO_MTL_DEMAND_INT_DELIVERY WHERE SESSION_ID = :session_id AND AVAILABLE_QUANTITY < 0;

For drill-back to the interface record, select the returned ROWID and query MTL_DEMAND_INTERFACE directly. Because SESSION_ID parameterizes every OE_QUERY call, always supply it as a bind variable; unconditional queries force function evaluation across all interface rows and degrade performance on large interface tables.