Search Results get_available_inventory

Overview

APPS.INV_SELECT_INVENTORY_PKG is a PL/SQL package body in Oracle E-Business Suite that supports inventory inquiry and selection functionality within the Oracle Inventory module. Its principal purpose is to resolve transaction context and return descriptive source information for inventory-related records, allowing calling forms and programs to display human-readable identifiers — such as order numbers, line numbers, and batch references — instead of internal numeric identifiers. The package is classified as an OTHER API in ETRM and is owned by the APPS schema, which indicates it is a supporting utility package rather than a fully published public interface. It is available in both 12.1.1 and 12.2.2 releases.

Key Procedures and Functions

The documented package exposes three procedures, each addressing a distinct inventory inquiry need:

• GET_SOURCE_INFO — Retrieves source document information based on a source type identifier, a source line identifier, and a source identifier. As documented in the package header comments, its role is to "get the source info from diff tables based on the source type id," and the original implementation explicitly states that support was added "only for sales orders." Depending on the source type, it resolves data from sales order headers and lines, WIP entities, or process manufacturing batch headers and material details. Results are returned as a header/document number and a line number, along with a return status flag. The internal logic branches on source type constants such as INV_GLOBALS.G_SOURCETYPE_SALESORDER and INV_GLOBALS.G_SOURCETYPE_WIP, and also accommodates a literal source type identifier of 8, which follows the same sales-order retrieval path.
• GET_DETAILS — Returns detailed attribute information associated with an inventory selection record, supporting the inquiry screens that display the full context of a selected lot, transaction, or material line.
• GET_AVAILABLE_INVENTORY — Resolves available inventory quantities for the requested selection criteria, typically by staging data through the available inventory temporary table before returning results to the caller.

The package relies on explicit cursors (for example, Cur_get_order, Cur_get_wip_entity, and Cur_get_batch) to fetch source attributes, and it follows the standard EBS API convention of initializing the return status to FND_API.G_RET_STS_SUCCESS at the start of execution.

Tables Accessed

The package references the following tables through APPS synonyms:

• OE_ORDER_HEADERS_ALL and OE_ORDER_LINES_ALL — joined on header identifier to resolve sales order number and line number for sales-order-sourced inventory transactions.
• WIP_ENTITIES — queried by WIP entity identifier to determine the entity type for work-in-process sourced records.
• GME_BATCH_HEADER and GME_MATERIAL_DETAILS — joined on batch identifier and material detail identifier to return batch number and line number for process manufacturing sources.
• MTL_AVAILABLE_INVENTORY_TEMP — used to stage and return available inventory results.
• MTL_LOT_NUMBERS, MTL_MATERIAL_TRANSACTIONS_TEMP, and MTL_TRANSACTION_LOTS_TEMP — accessed to resolve lot and transaction detail information.
• MTL_TXN_REQUEST_LINES — referenced for move order line detail.
• PLITBLM — the standard EBS PL/SQL table of numbers type used for internal collection handling.

Usage Notes

INV_SELECT_INVENTORY_PKG is typically invoked from Oracle Inventory inquiry and selection forms, and from custom code that needs to translate internal source identifiers into displayable document and line references. It may also be called from concurrent programs or personalizations that surface source document context on inventory transaction, lot, or material detail screens. Because it is owned by APPS and documented as an OTHER classification, callers should treat it as an internal supporting package: parameter contracts should be validated against the deployed source in the target release before reliance, and custom extensions are best implemented through wrapper logic rather than direct modification. No other packages in the documented inventory of ETRM objects reference this package, confirming that it is consumed primarily by forms and non-package callers.