Search Results demanded_quantity




Overview
Explore in AI Chat

Overview

APPS.INVFV_INVENTORY_DEMANDS is a reporting view in Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2 that consolidates material demand records held in the MTL_DEMAND table. It is defined in the INV (Inventory) application schema and exposes demand originating from multiple transaction source types—principally sales orders and account-based issues—while resolving organization units, item definitions, revision, lot, subinventory and locator context. The view is intended for inquiry, reporting and integration scenarios where a caller needs a denormalized, application-facing projection of open inventory demand rather than the raw table. Its definition uses a UNION ALL to combine different demand source categories, which is significant because column semantics shift between the two halves of the union.

Underlying Base Objects

Per the documented ETRM metadata, the view is defined over the following base objects, all referenced through APPS synonyms: MTL_DEMAND, MTL_SALES_ORDERS, MTL_SYSTEM_ITEMS, MTL_ITEM_LOCATIONS, MTL_TXN_SOURCE_TYPES, MTL_PARAMETERS, HR_ALL_ORGANIZATION_UNITS, MTL_GENERIC_DISPOSITIONS, and GL_CODE_COMBINATIONS. MTL_DEMAND is the driving table, supplying demand identifiers, reservation status and quantities. MTL_SYSTEM_ITEMS is joined on organization and inventory item to validate the item; MTL_ITEM_LOCATIONS is an outer join on locator; MTL_TXN_SOURCE_TYPES supplies the human-readable transaction source type name; HR_ALL_ORGANIZATION_UNITS and MTL_PARAMETERS provide the organization name and organization code. In the sales-order branch, MTL_SALES_ORDERS is joined on the demand source header. In the account branch, the account key flexfield is sourced via GL_CODE_COMBINATIONS, indicated by the "_KF:SQLGL:GL#:GLC" key flex marker. The view filters to reservation type 1 with no parent demand, and restricts to demand where line item quantity less reservation quantity remains positive.

Key Columns

Common Use Cases and Queries

Typical usage includes open demand reports, reservation analysis, and feeds into planning or fulfillment integration. A representative query filtering by item and organization is:

SELECT organization_code,
       inventory_item_id,
       demand_source_type,
       transaction_source_type_name,
       requirement_date,
       demanded_quantity,
       reserved_quantity,
       account_id,
       account_alias_id
FROM   apps.invfv_inventory_demands
WHERE  organization_id = :p_org_id
AND    inventory_item_id = :p_item_id
ORDER BY requirement_date;

Because ACCOUNT_ALIAS_ID resolves to NULL in both branches of the union, queries searching for "account_alias_id" against this view will not return meaningful values; callers requiring alias-based account identification must obtain it from the underlying accounting flexfield sources. The view remains the appropriate entry point for demand-centric reporting that requires organization, item and quantity context in a single projection.