Search Results n_column4

Overview

The SO_MTL_DEMAND_INT_LINE_ID view is a reporting and integration object owned by the APPS schema within the Oracle E-Business Suite Order Entry (OE) module. It presents a filtered, function-enriched projection of the MTL_DEMAND_INTERFACE table, which is the staging table used by Oracle Order Management to hold demand records prior to their processing by the scheduling and availability engine. The view is documented in ETRM for both Oracle EBS 12.1.1 and 12.2.2 and carries a VALID status in the data dictionary.

The view's distinguishing characteristic is its use of the N_COLUMN4 indicator column in its filter predicate. Only rows where N_COLUMN4 IS NULL are exposed, which isolates demand records that have not been flagged for suppression or exclusion by upstream processing logic. The view also computes derived scheduling values on the fly, making it a convenient single source for ATP (Available-to-Promise) reporting and for reconciliation of demand lines awaiting supply matching.

Underlying Base Objects

The view text references two documented primary objects. The first is MTL_DEMAND_INTERFACE, accessed as a SYNONYM in the APPS schema. This table stores the inbound demand lines that drive the order scheduling process. The second is the OE_QUERY package, which supplies three scalar functions invoked per row:

• OE_QUERY.ATP_DATE_LINE_ID(SESSION_ID, DEMAND_SOURCE_LINE, INVENTORY_ITEM_ID) returns the availability date for the demand line.
• OE_QUERY.AVAILABLE_QUANTITY_LINE_ID(SESSION_ID, DEMAND_SOURCE_LINE, INVENTORY_ITEM_ID) returns the quantity available against the demand line.
• OE_QUERY.DEMAND_INTERFACE_ROWID_LINE_ID(SESSION_ID, DEMAND_SOURCE_LINE) returns the ROWID of the corresponding source row in the interface table.

Because the view calls packaged functions, it is not a simple relational projection and cannot be treated as a base table for bulk data movement. Its dependency on OE_QUERY links its behavior to the OE scheduling engine configuration.

Key Columns

• DEMAND_SOURCE_LINE — Identifier of the originating demand line within the interface. It forms part of the composite key passed to the OE_QUERY functions.
• INVENTORY_ITEM_ID — Internal identifier of the inventory item for which demand exists.
• SESSION_ID — Session identifier binding the demand row to a specific scheduling run or user context.
• ATP_DATE — Derived date on which the item is expected to be available; computed via OE_QUERY.ATP_DATE_LINE_ID.
• AVAILABLE_QUANTITY — Derived quantity available to satisfy the line; computed via OE_QUERY.AVAILABLE_QUANTITY_LINE_ID.
• DEMAND_INTERFACE_ROWID — ROWID pointing back to the underlying MTL_DEMAND_INTERFACE record, enabling drill-back and update correlation.

Common Use Cases and Queries

The view is typically used to inspect pending demand lines for a given scheduling session, to diagnose why a line is not being scheduled, and to reconcile ATP results with the underlying interface rows. A representative query lists demand with computed availability for one session:

• SELECT demand_source_line, inventory_item_id, atp_date, available_quantity FROM apps.so_mtl_demand_int_line_id WHERE session_id = :p_session_id;
• SELECT d.demand_source_line, m.line_item_quantity, d.available_quantity FROM apps.so_mtl_demand_int_line_id d, apps.mtl_demand_interface m WHERE m.rowid = d.demand_interface_rowid;
• SELECT COUNT(*) FROM apps.so_mtl_demand_int_line_id WHERE available_quantity < 0; — identifies demand lines with negative availability requiring attention.

Because the view filters on N_COLUMN4 IS NULL and LINE_ITEM_QUANTITY > 0, it excludes suppressed and zero-quantity lines by design. Reports that require the full population of interface records must query MTL_DEMAND_INTERFACE directly rather than this view.