Search Results puom_issued_qty

Overview

APPS.MTL_DEMAND_V is a reporting and integration view layered over the Oracle EBS inventory demand table, MTL_DEMAND. Unlike the base table, which stores every demand row created by reservations, sales orders, work in process, and internal requisitions, this view deliberately restricts its result set to a specific class of demand: reserved, child demand records that still carry an outstanding quantity. It is therefore a filtered, denormalized projection rather than a passthrough of the table.

The view is most frequently encountered in manufacturing, order management, and inventory reporting contexts, where it exposes the outstanding reservation detail associated with a parent demand. Because the view joins MTL_DEMAND to the item key flexfield view, it returns descriptive item attributes alongside the transactional demand columns, allowing a single query to produce both identifiers and human-readable item context. The user search term "orig_line_qty" maps directly to a column alias in this view.

Underlying Base Objects

Per the documented ETRM metadata, APPS.MTL_DEMAND_V is owned by APPS and is defined over two referenced objects, both exposed as synonyms in the APPS schema:

• MTL_DEMAND (SYNONYM) — aliased as M in the view text; the primary transactional source supplying demand identifiers, quantities, dates, and reservation attributes.
• MTL_SYSTEM_ITEMS_KFV (SYNONYM) — aliased as MSIK; the item key flexfield view supplying concatenated item segments, description, control codes, and primary unit of measure.

The two objects are joined on INVENTORY_ITEM_ID and ORGANIZATION_ID, meaning every row returned is item- and organization-qualified. The join to the KFV is an inner join, so demand rows whose item does not resolve in MTL_SYSTEM_ITEMS_KFV are excluded.

Key Columns

The view applies three hard-coded predicates in its WHERE clause: RESERVATION_TYPE = 2, PARENT_DEMAND_ID IS NOT NULL, and PRIMARY_UOM_QUANTITY > COMPLETED_QUANTITY. These filters define the view's semantics — only reserved detail demand with a positive remaining balance is visible. Notable columns include:

• DEMAND_ID, ORGANIZATION_ID, INVENTORY_ITEM_ID — primary identifiers for the demand record, organization, and item.
• ITEM, ITEM_DESCRIPTION — padded concatenated flexfield segments and item description from MTL_SYSTEM_ITEMS_KFV.
• ORIG_LINE_QTY — alias for MTL_DEMAND.LINE_ITEM_QUANTITY, the quantity as originally entered on the demand line, expressed in the line's transaction UOM.
• PUOM_ORIG_RSV_QTY — alias for PRIMARY_UOM_QUANTITY, the same demand converted to the item's primary UOM.
• PUOM_ISSUED_QTY — alias for COMPLETED_QUANTITY, the quantity already relieved against the demand.
• PUOM_REMAINING_QTY — a derived column computed as PRIMARY_UOM_QUANTITY minus COMPLETED_QUANTITY.
• REQ_DATE, UOM, REVISION, LOT_NUMBER, SUBINVENTORY, LOCATOR_ID — planning and material-control attributes.
• DEMAND_SOURCE_TYPE, DEMAND_SOURCE_HEADER_ID, DEMAND_SOURCE_LINE, PARENT_DEMAND_ID — traceability back to the originating source document.

Common Use Cases and Queries

Typical scenarios include reporting open reserved demand by item or subinventory, reconciling reservations against source orders, and feeding downstream planning extracts. Because ORIG_LINE_QTY is exposed under that alias, ad hoc queries searching for the term resolve here.

Sample query returning outstanding reserved demand for an organization:

• SELECT demand_id, item, orig_line_qty, puom_orig_rsv_qty, puom_issued_qty, puom_remaining_qty, req_date FROM apps.mtl_demand_v WHERE organization_id = :org_id AND inventory_item_id = :item_id ORDER BY req_date;

Sample aggregation by item to size remaining reservations:

• SELECT item, SUM(orig_line_qty) total_line_qty, SUM(puom_remaining_qty) total_remaining FROM apps.mtl_demand_v WHERE organization_id = :org_id GROUP BY item HAVING SUM(puom_remaining_qty) > 0;

Sample trace to source document:

• SELECT demand_source_type, demand_source_header_id, demand_source_line, parent_demand_id, orig_line_qty FROM apps.mtl_demand_v WHERE demand_id = :demand_id;

Because the view filters on a derived comparison and an inner join, it is not suitable for reporting fully fulfilled, parentless, or non-reserved demand; those cases require querying MTL_DEMAND directly.