Search Results pending_issue_quantity




Overview
Explore in AI Chat

Overview

APPS.INVFV_INVENTORY_RESERVATIONS is a Business Intelligence System (BIS) view in Oracle E-Business Suite, owned by the APPS schema and registered under FND Design Data INV.INVFV_INVENTORY_RESERVATIONS. The view presents the holds placed on specific inventory items, assuring that a defined quantity of an item is available on a given required date when a transaction is processed against a particular charge entity. In practical terms, it exposes reservation and demand information maintained by Oracle Inventory, allowing reservations to be analyzed without navigating the underlying MTL_DEMAND and MTL_SALES_ORDERS tables directly.

Because it is a BIS view rather than a transactional table, INVFV_INVENTORY_RESERVATIONS is intended for read-only reporting, ad-hoc querying, and data extraction. The view is documented as VALID in both 12.1.1 and 12.2.2, and appears in ETRM metadata with the dependency chain expanded to its base objects. Its principal value to report developers and integration specialists is that it flattens organization, item, demand source, reservation, and issuance information into a single queryable structure, which is useful when investigating the pending_issue_quantity — the quantity reserved against a demand but not yet issued.

Underlying Base Objects

The documented dependency list for this view includes GL_CODE_COMBINATIONS (SYNONYM), HR_ALL_ORGANIZATION_UNITS (SYNONYM), INV_CONVERT (PACKAGE), MTL_DEMAND (SYNONYM), MTL_GENERIC_DISPOSITIONS (SYNONYM), MTL_ITEM_LOCATIONS (SYNONYM), MTL_PARAMETERS (SYNONYM), MTL_SALES_ORDERS (SYNONYM), MTL_SYSTEM_ITEMS (SYNONYM), and MTL_TXN_SOURCE_TYPES (SYNONYM).

MTL_DEMAND is the central transactional source of the reservation records; each reservation corresponds to a demand row, identified by DEMAND_ID. MTL_SYSTEM_ITEMS supplies the item definition and key flexfield name, while HR_ALL_ORGANIZATION_UNITS and MTL_PARAMETERS provide the inventory organization name and code. MTL_SALES_ORDERS links reservations back to sales orders, and MTL_TXN_SOURCE_TYPES supplies the demand source type name. MTL_ITEM_LOCATIONS resolves the locator into a readable location name, and GL_CODE_COMBINATIONS supports the accounting context associated with the reservation. INV_CONVERT is referenced as a package, typically for unit-of-measure conversion logic. Because the view is defined over synonyms, all objects resolve to the APPS schema, keeping the view consistent with INV's standard access model.

Key Columns

Common Use Cases and Queries

A frequent reporting requirement is identifying reservations where a quantity remains unissued. The following query lists outstanding pending issue quantities by organization and item:

SELECT organization_code, _KF:INVENTORY_ITEM_NAME, demand_source_name,
  reserved_quantity, issued_quantity, pending_issue_quantity, required_date
FROM APPS.INVFV_INVENTORY_RESERVATIONS
WHERE pending_issue_quantity > 0
ORDER BY organization_code, required_date;

Other typical scenarios include reconciling sales order reservations against issued quantities, examining required dates to anticipate shortages, and filtering reservations by subinventory or locator for warehouse-level analysis. Because the view exposes subinventory and locator detail alongside demand source information, it also supports demand-versus-supply investigations and integration extracts that feed downstream planning systems. All queries should be executed read-only, and column names containing the _KF prefix should be quoted or aliased as required by the reporting tool.