Search Results purch_ord

Overview

The APPS.ICX_MTL_SUPPLY_DEMAND_V view is a supply and demand reporting object used by Oracle E-Business Suite's iProcurement and supply chain visibility components. It exposes consolidated supply and demand information for inventory items at the organization level, presenting reservation, receipt, purchase order, requisition, sales order, work in process (WIP), and on-hand availability data in a single denormalized result set. The view transforms the raw numeric source type identifiers stored in the underlying temporary table into human-readable document numbers by calling the ICX_GET_ORDER package functions. This makes it suitable for embedded reporting regions, item availability inquiries, and drill-down pages where users must see recognizable order and document references rather than internal disposition IDs.

Because the object is a view rather than a base table, it carries no storage of its own and reflects the state of the underlying supply and demand data at query time. It is documented identically for both the 12.1.1 and 12.2.2 releases, indicating that its definition and dependencies remained stable across those versions.

Underlying Base Objects

The view is defined over two documented base objects:

• MTL_SUPPLY_DEMAND_TEMP (SYNONYM) — the primary source of rows. Despite the "TEMP" naming convention, this is the table aliased as SUPDEM in the view text, supplying organization, item, requirement date, source type, supply/demand type, and on-hand quantities. The view restricts rows to those with a non-null SUPPLY_DEMAND_SOURCE_TYPE and a RECORD_TYPE of 'SD'.
• ICX_GET_ORDER (PACKAGE) — a PL/SQL package invoked inline through scalar functions such as GET_PO_NUMBER, GET_REQ_NUMBER, GET_SO_NUMBER, and GET_WIP_NUMBER. These functions translate the numeric DISPOSITION_ID values into display-ready document numbers for purchase orders, requisitions, sales orders, and WIP jobs.

Key Columns

• ORGANIZATION_ID — the inventory organization to which the supply and demand record belongs.
• INVENTORY_ITEM_ID — the item identifier for the record.
• REQ_DATE — the requirement date, sourced from REQUIREMENT_DATE, indicating when the supply or demand is needed.
• PURCH_ORD — the purchase order number, populated via ICX_GET_ORDER.GET_PO_NUMBER when the supply/demand source type is 1.
• REQUISITIONS — the requisition number, populated when the source type is 18.
• SALES_ORD — the sales order number, resolved via ICX_GET_ORDER.GET_SO_NUMBER when the source type is 2 or 9. This is the column most relevant to users searching for sales order demand.
• ACCOUNT_NO — the disposition identifier shown for source types 3 and 10.
• W_I_P — the WIP job number, populated via ICX_GET_ORDER.GET_WIP_NUMBER for source types 4, 5, 7, 13, 14, and 23.
• OTHER — the disposition ID exposed for a broad set of remaining source types (6, 8, 11, 12, 15, 16, 17, 19, 20, 21, 22).
• RESRVNS — the reserved quantity, shown when SUPPLY_DEMAND_TYPE equals 1.
• RECEIPTS — the receipt quantity, shown when SUPPLY_DEMAND_TYPE equals 2.
• AVAILABLE — the on-hand quantity (ON_HAND_QUANTITY), representing available supply.

Common Use Cases and Queries

A frequent scenario is identifying which sales orders are consuming supply for a given item, which aligns with the "sales_ord" search term. The following query returns sales order demand for an item within an organization:

• SELECT organization_id, inventory_item_id, req_date, sales_ord, resrvns FROM apps.icx_mtl_supply_demand_v WHERE sales_ord IS NOT NULL AND inventory_item_id = :item_id AND organization_id = :org_id ORDER BY req_date;

Another common use is an availability summary comparing receipts, reservations, and on-hand quantities for planning purposes:

• SELECT inventory_item_id, SUM(receipts) receipts, SUM(resrvns) reservations, SUM(available) available FROM apps.icx_mtl_supply_demand_v WHERE organization_id = :org_id GROUP BY inventory_item_id;

Because document numbers are resolved through PL/SQL function calls, queries against this view can incur per-row overhead on large result sets; filtering by organization and item is advisable.