Search Results net_available_quantity




Overview
Explore in AI Chat

Overview

APPS.ICX_MTL_DEMAND_ITEM_SUM_V is a summary view in the Oracle E-Business Suite ETRM (E-Business Suite Technology Reference Manual) layer, owned by the APPS schema. It consolidates on-hand, demand, reservation, and availability information at the inventory item level, providing a denormalized, ready-to-query dataset for inventory and order-management reporting. The view is defined in the Oracle iProcurement / iStore-related ICX module family, which supplies the demand-summary infrastructure used by sourcing, replenishment, and storefront applications.

The view is explicitly documented in ETRM 12.2.2 and remains valid through 12.1.1, where the same column set and aggregation behavior apply. Its role is to collapse the lower-level row-per-organization or row-per-subinventory detail found in ICX_MTL_DEMAND_SUMMARY_V into a single row per inventory item, making it suitable for item-centric inquiries, dashboards, and integration feeds that require aggregate quantity positions rather than organization-level breakdowns.

Underlying Base Objects

According to the documented metadata, the view is defined over the following referenced objects:

  • ICX_MTL_DEMAND_SUMMARY_V (VIEW) — the immediate source of all data columns; ICX_MTL_DEMAND_ITEM_SUM_V selects from it and applies aggregation.
  • INV_DECIMALS_PUB (PACKAGE) — supplies unit-of-measure precision handling used in quantity presentation and rounding.
  • HR_GENERAL (PACKAGE) — provides organizational and security context functions.
  • HR_SECURITY (PACKAGE) — enforces role-based access restrictions so that demand-summary results honor the user's organization and item security profile.

The definition performs a GROUP BY across INVENTORY_ITEM_ID, ITEM, DESCRIPTION, and PRIMARY_UNIT_OF_MEASURE, with each quantity column wrapped in SUM(NVL(column, 0)) so that null quantities are treated as zero and safely aggregated.

Key Columns

  • INVENTORY_ITEM_ID — the surrogate key of the inventory item; the primary grouping and join attribute.
  • ITEM — the item number (concatenated segment value) presented for user-facing identification.
  • DESCRIPTION — the item description, carried into the grouping to preserve display context.
  • PRIMARY_UNIT_OF_MEASURE — the item's primary UOM, as requested in the user's search term. Because the view groups by this column, quantities at different UOMs are never mixed within a row.
  • ONHAND_QUANTITY — total on-hand quantity across the summarized scope.
  • DEMAND_QUANTITY — total outstanding demand for the item.
  • HARD_RESERVATION_QUANTITY — quantity hard-reserved against specific demand.
  • SUPPLY_RESERVATION_QUANTITY — quantity reserved to supply sources.
  • TRANSACTABLE_QUANTITY — the quantity available for further transaction processing.
  • NET_AVAILABLE_QUANTITY — on-hand net of reservations and demand, the principal availability metric.

Common Use Cases and Queries

Typical usages include item availability dashboards, replenishment exception reports, iProcurement sourcing checks, and reconciliation of demand against on-hand at the item level.

Listing availability for a specific item, restricted to its primary UOM:

SELECT item, description, primary_unit_of_measure,
       onhand_quantity, net_available_quantity
  FROM apps.icx_mtl_demand_item_sum_v
 WHERE inventory_item_id = :item_id;

Identifying items with demand exceeding supply:

SELECT item, primary_unit_of_measure,
       onhand_quantity, demand_quantity,
       net_available_quantity
  FROM apps.icx_mtl_demand_item_sum_v
 WHERE net_available_quantity < 0
 ORDER BY net_available_quantity;

Because the view aggregates to the item level and depends on HR security packages, queries automatically observe the calling user's organization and item access privileges.