Search Results demanded_quantity

Overview

INVFV_INVENTORY_DEMANDS is a reporting view owned by the APPS schema in Oracle E-Business Suite, defined within the Inventory (INV) product. In the ETRM metadata for release 12.2.2 it carries the description "Retrofitted," which indicates that the view was reconstructed to preserve a legacy interface or backward-compatible representation of inventory demand data, rather than representing an entirely new functional object. Functionally, the view consolidates open inventory demand lines derived from MTL_DEMAND and enriches them with descriptive attributes from organization, item, subinventory, locator, and transaction-source tables.

The view presents demand records that remain unreserved or partially reserved, since the defining predicate requires that the difference between the demanded line quantity and the reserved quantity be greater than zero. It also restricts output to parent demand records (where PARENT_DEMAND_ID is null) and to reservation type 1. As a result, INVFV_INVENTORY_DEMANDS serves as a convenient, denormalized source for reports and integrations that need a flattened picture of outstanding inventory demand without navigating the underlying normalized table structure directly.

Underlying Base Objects

The documented base objects referenced by the view are: MTL_DEMAND, MTL_SYSTEM_ITEMS, MTL_ITEM_LOCATIONS, MTL_PARAMETERS, MTL_SALES_ORDERS, MTL_TXN_SOURCE_TYPES, MTL_GENERIC_DISPOSITIONS, HR_ALL_ORGANIZATION_UNITS, and GL_CODE_COMBINATIONS. All are accessed through APPS synonyms.

MTL_DEMAND is the primary driving table, supplying demand identifiers, quantities, reservation quantities, requirement dates, source types and headers, revision, lot, subinventory, locator, and audit columns. The view's UNION ALL structure joins and branches across demand source types. In the visible excerpt, one branch handles source types 2, 8, and 12 and joins MTL_SALES_ORDERS on the demand source header; another branch addresses source type 3 (account) and references GL_CODE_COMBINATIONS for the account flexfield context. MTL_SYSTEM_ITEMS validates the item and organization combination, while MTL_ITEM_LOCATIONS is outer-joined so that demand rows without an assigned locator are still returned. MTL_PARAMETERS and HR_ALL_ORGANIZATION_UNITS supply organization code and organization name respectively, and MTL_TXN_SOURCE_TYPES resolves the numeric demand source type into its descriptive transaction source type name.

Key Columns

• DEMAND_ID — Primary identifier of the underlying MTL_DEMAND record.
• ORGANIZATION_ID / ORGANIZATION_CODE / NAME — Organization context; NAME derives from the organization unit definition and is protected by an organization security predicate.
• INVENTORY_ITEM_ID — Item identifier, presented with a key flexfield descriptor for the item flexfield.
• REQUIREMENT_DATE — Date the demand must be satisfied.
• DEMAND_SOURCE_TYPE and TRANSACTION_SOURCE_TYPE_NAME — Numeric source type and its resolved descriptive name.
• DEMAND_SOURCE_HEADER_ID / SALES_ORDER_ID — Source document reference; exposed as SALES_ORDER_ID for sales-order-originated demand.
• DEMANDED_QUANTITY — Mapped from LINE_ITEM_QUANTITY; this is the column most frequently queried when users search for demanded quantity, and it represents the total quantity requested on the demand line.
• RESERVED_QUANTITY — Mapped from LINE_ITEM_RESERVATION_QTY, the quantity already reserved against the demand.
• UOM — Unit of measure code for the demand quantity.
• REVISION, LOT_NUMBER, SUBINVENTORY, LOCATOR_ID — Material control attributes identifying where and which revision/lot the demand applies to.
• ACCOUNT_ID / ACCOUNT_ALIAS_ID — Account flexfield references, populated in the account-source branch.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE — Standard audit columns.

Common Use Cases and Queries

Typical applications include open-demand reporting, shortage analysis, reservation gap monitoring, and integration feeds that must identify quantities still requiring reservation or fulfillment.

• Listing outstanding demand quantities by item and organization.
• Comparing demanded versus reserved quantities to surface reservation shortfalls.
• Filtering demand by requirement date window for planning reports.
• Driving downstream supply or replenishment logic from unresolved demand records.

Sample query selecting the demanded quantity alongside reservation context:

SELECT organization_code, inventory_item_id, requirement_date,
demanded_quantity, reserved_quantity, uom, subinventory
FROM apps.invfv_inventory_demands
WHERE demanded_quantity > reserved_quantity
ORDER BY organization_code, requirement_date;

A shortage-focused variant aggregates by item:

SELECT inventory_item_id, SUM(demanded_quantity - reserved_quantity) open_qty
FROM apps.invfv_inventory_demands
WHERE organization_id = :org_id
GROUP BY inventory_item_id;

Because the view enforces reservation type 1, parent-level records only, and a positive unreserved balance, results reflect genuinely outstanding demand. Any report or interface relying on INVFV_INVENTORY_DEMANDS should apply the organization security context, since the view text includes an organization security predicate on M.ORGANIZATION_ID.