Search Results set_pick_lots




Overview

GMI_RESERVATION_UTIL is an internal utility package in the Oracle Process Manufacturing (OPM) reservation subsystem. Its stated purpose, per the package header, is to house private utilities relating to OPM reservation, bridging Oracle Order Management (OM) demand with OPM lot, inventory, and warehouse data. The package supports reservation, allocation, and default lot creation for sales order lines that must be satisfied from OPM-controlled inventory. Because reservation logic in OPM requires translating between Oracle Applications items/UOMs and their OPM equivalents, and because lot selection must respect item control rules and horizon periods, this body consolidates the supporting lookups, validations, and transactions used by higher-level reservation APIs. It is classified as a UTIL package in ETRM 12.2.2, owned by APPS, and is referenced by 38 other packages, confirming its role as a shared internal dependency rather than a user-facing entry point.

Key Procedures and Functions

Tables Accessed

Through APPS synonyms the package reads and writes OPM master and transaction tables including IC_ITEM_MST, IC_LOCT_INV, IC_LOCT_MST, IC_LOTS_MST, IC_TRAN_PND, IC_TXN_REQUEST_LINES, and IC_WHSE_MST for item control, location, lot, pending transaction, and warehouse data. It references Oracle Inventory tables MTL_SYSTEM_ITEMS, MTL_ITEM_LOCATIONS, MTL_SECONDARY_INVENTORIES, MTL_UNITS_OF_MEASURE, and MTL_SALES_ORDERS for item, subinventory, UOM, and sales order linkage. Order Management data is read from OE_ORDER_HEADERS_ALL, and FND_LANGUAGES and FND_USER supply language and user context for messaging and audit.

Usage Notes

GMI_RESERVATION_UTIL is not invoked directly by end users. It is called from OPM reservation and order fulfillment flows, including OM file OEXVIIFB.pls (per bug fix 2536589), and from other PL/SQL packages—38 documented dependents. Typical invocation occurs during sales order reservation, pick release, and default lot assignment, including the SET_PICK_LOTS path. Customizations should not call these private utilities directly; the supported approach is to use the public reservation APIs that internally delegate here.