Search Results req_date

Overview

The APPS.ICX_MTL_SUPPLY_DEMAND_V view belongs to the ICX - Oracle iProcurement product family within Oracle E-Business Suite. Its ETRM status is VALID, and its recorded description is simply "Obsolete." This classification indicates that the object was historically used by iProcurement's sourcing and replenishment features but has since been superseded by later functionality. It remains present in the APPS schema primarily for backward compatibility with customizations, historical reports, and dependent objects that have not been migrated.

The view presents a unified supply and demand picture at the inventory item and organization level. It merges multiple planning source types — purchase orders, requisitions, sales orders, WIP jobs, and account references — into a single flattened result set. The central mechanism is the DISPOSITION_ID column, which the view decodes conditionally based on SUPDEM.SUPPLY_DEMAND_SOURCE_TYPE. This makes DISPOSITION_ID the semantic anchor of the view: it is the foreign key whose meaning shifts depending on the originating supply/demand type.

Underlying Base Objects

The documented referenced base objects are:

• MTL_SUPPLY_DEMAND_TEMP (SYNONYM) — the driving source, aliased as SUPDEM. This carries ORGANIZATION_ID, INVENTORY_ITEM_ID, REQUIREMENT_DATE, SUPPLY_DEMAND_SOURCE_TYPE, SUPPLY_DEMAND_TYPE, DISPOSITION_ID, QUANTITY, and ON_HAND_QUANTITY.
• ICX_GET_ORDER (PACKAGE) — provides the lookup functions ICX_GET_ORDER.GET_PO_NUMBER, GET_REQ_NUMBER, GET_SO_NUMBER, and GET_WIP_NUMBER, which translate DISPOSITION_ID into readable document numbers.

The view filters with WHERE SUPDEM.SUPPLY_DEMAND_SOURCE_TYPE IS NOT NULL AND SUPDEM.RECORD_TYPE = 'SD', ensuring only genuine supply/demand records are returned. The use of a DECODE against SUPPLY_DEMAND_SOURCE_TYPE repeatedly means the view is essentially a CASE-style pivoting layer over the temporary table, resolving each disposition into the correct business context.

Key Columns

• ORGANIZATION_ID, INVENTORY_ITEM_ID — the inventory context for each row.
• REQ_DATE — aliased from REQUIREMENT_DATE, the date the supply or demand is needed.
• DISPOSITION_ID — returned inline (via DECODE) for source types 1, 18, 2, 9, 3, 10, 4, 5, 7, 13, 14, 23, 6, 8, 11, 12, 15, 16, 17, 19, 20, 21, and 22. Its value is a purchase order, requisition, sales order, WIP job, or account identifier depending on the type.
• PURCH_ORD, REQUISITIONS, SALES_ORD, W_I_P, ACCOUNT_NO, OTHER — human-readable document numbers produced by ICX_GET_ORDER functions or, in the ACCOUNT_NO/OTHER cases, the raw disposition.
• RESRVNS, RECEIPTS — quantities where SUPPLY_DEMAND_TYPE is 1 (reservations) or 2 (receipts).
• AVAILABLE — from ON_HAND_QUANTITY.

Common Use Cases and Queries

Typical uses include item availability reporting and tracing the origin document behind a supply or demand record. Because DISPOSITION_ID is often the join key users search on, a common query retrieves it alongside its resolved document number:

SELECT organization_id, inventory_item_id, req_date, purch_ord, requisitions, sales_ord, w_i_p, account_no, other, resrvns, receipts, available FROM apps.icx_mtl_supply_demand_v WHERE organization_id = :org AND inventory_item_id = :item;

To isolate purchase-order-driven supply, filter on PURCH_ORD IS NOT NULL or SUPPLY_DEMAND_SOURCE_TYPE = 1. Given the view's Obsolete designation, new development should target supported iProcurement and planning views; ICX_MTL_SUPPLY_DEMAND_V should be retained only for legacy compatibility.