Search Results balance_default_lot




Overview
Explore in AI Chat

Overview

GMI_ALLOCATE_INVENTORY_PVT is a private PL/SQL package owned by APPS that encapsulates the auto-allocation logic used by Oracle Process Manufacturing (OPM) to reserve on-hand inventory against order and shipment lines. Its header identifies it as the engine containing "private procedures controlling auto-allocation of OPM inventory against a particular order/shipment line." In Oracle EBS 12.1.1 and 12.2.2, this processing supports the Order Management and shipping flows that draw against OPM lots and locations, complementing the discrete Oracle Inventory allocation path.

The package is classified as PVT, meaning it is not a published API and is intended for internal consumption by other Oracle applications components. It relies on AUTHID CURRENT_USER, so all unqualified table references resolve through the calling user's synonyms (documented as APPS synonyms). Two other packages reference it, which confirms its role as a subordinate implementation layer beneath a public allocation entry point.

Key Procedures and Functions

  • ALLOCATE_LINE — Performs allocation for a single order/shipment line. It accepts an allocation record, item and warehouse master row types, and an allocation parameter row, and returns allocated quantities along with the standard return status, message count, and message data outputs. A batch identifier parameter supports grouping allocations into a batch.
  • BALANCE_DEFAULT_LOT — Handles the balancing of default-lot quantities passed in as inputs. This is the procedure most relevant to the search term balance_default_lot: it reconciles default quantity values against the allocation record, item, and warehouse context, returning status and message outputs. It is the mechanism by which a pre-designated default lot quantity is adjusted or validated during allocation.
  • CHECK_EXISTING_ALLOCATIONS — A function that tests whether allocations already exist for a given document and line, using the pending transaction table as the source of truth. It prevents duplicate or conflicting allocation attempts.
  • UNSTAGED_ALLOCATIONS_EXIST — Determines whether allocation records remain unstaged, supporting cleanup and reconciliation before further processing.

Tables Accessed

The documented table references map directly to OPM inventory and order entities. IC_ITEM_MST and IC_WHSE_MST supply item and warehouse master attributes; OP_ALOT_PRM supplies allocation parameters. IC_TRAN_PND holds pending inventory transactions and underpins CHECK_EXISTING_ALLOCATIONS. IC_LOCT_MST and IC_LOTS_MST provide location and lot detail for lot selection. GMI_AUTO_ALLOCATION_BATCH stores batch-level allocation state. OE_ORDER_LINES_ALL links allocations to Order Management order lines, and PLITBLM is an OPM internal table used in lot/location processing.

Usage Notes

Because this is a private package, it should not be called directly from custom code. Invocation normally occurs indirectly through GMI_AUTO_ALLOCATE_PUB and the Order Management shipping and allocation forms or concurrent programs that require OPM lot-level reservation. Developers extending allocation behavior should prefer the public wrapper and treat BALANCE_DEFAULT_LOT and the other members here as internal implementation details subject to change between releases.