Results for “gmi_auto_alloc_batch_pkg”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

GMI_AUTO_ALLOC_BATCH_PKG is an APPS-owned PL/SQL package within the Oracle E-Business Suite Process Manufacturing (OPM/GMI) module. Its business purpose is to drive automated allocation of on-hand inventory lots against sales order delivery lines and move those lines toward pick confirmation, without requiring manual intervention from warehouse or order management staff. In OPM environments, allocation determines which specific lots, subinventories, and warehouses satisfy a given demand line; the package encapsulates the batch-oriented orchestration logic that ties the EBS order management and shipping tables (OE_ORDER_LINES_ALL, WSH_DELIVERY_DETAILS) to the OPM lot, inventory, and warehouse master data.

The package is classified as OTHER in the ETRM documentation, meaning it is not a published public API in the same sense as GMI_AUTO_ALLOCATE_PUB, but a supporting implementation package. It delegates core allocation logic to GMI_AUTO_ALLOCATE_PUB and depends on FND_API for the standard EBS API error-handling and message stack conventions. It is also recursive in the dependency model: APPS.GMI_AUTO_ALLOC_BATCH_PKG is referenced by itself, indicating internal procedure calls such as AUTO_ALLOCATE_BATCH invoking helper routines within the same package.

Key Procedures and Functions

• AUTO_ALLOCATE_BATCH — The primary driver procedure. It processes a set of delivery detail or order lines as a batch and orchestrates automatic allocation across them.
• AUTO_ALLOC_WDD_LINE — Handles allocation for an individual WSH delivery detail line (WDD = WSH Delivery Detail). This is the per-line unit of work invoked by the batch procedure.
• CALL_PICK_CONFIRM — Invokes pick confirmation for lines that have been successfully allocated, advancing the shipping flow from allocation to picking.
• GET_ALLOCATION_RECORD — Retrieves the allocation record for a given demand or delivery line, used to determine current allocation state before processing.
• INSERT_ROW — Performs the physical insert of an allocation row into the GMI allocation batch structure.
• SUBMIT_ALLOCATION_REQUEST — Submits the allocation request, likely serving as the entry point that queues batch processing or invokes the concurrent request mechanism.

Tables Accessed

The package reads and writes across OPM inventory masters and Oracle shipping/order tables, joined through APPS synonyms:

• GMI_AUTO_ALLOCATION_BATCH — The central staging/control table that tracks batches and allocation rows produced by the package.
• WSH_DELIVERY_DETAILS — The shipping delivery detail lines being allocated and later pick-confirmed.
• OE_ORDER_LINES_ALL — Source sales order lines supplying demand quantities.
• MTL_SYSTEM_ITEMS, MTL_PARAMETERS — Item and inventory organization parameters governing allocation behavior.
• IC_ITEM_MST, IC_WHSE_MST, IC_TRAN_PND, IC_TXN_REQUEST_LINES, SY_ORGN_MST — OPM item, warehouse, pending transaction, and organization masters used for lot and warehouse resolution.
• OP_ALOT_PRM, PLITBLM — OPM lot parameters and item/lot master support tables.
• FND_USER — Used to resolve the executing user for audit and API context.

Usage Notes

GMI_AUTO_ALLOC_BATCH_PKG is typically invoked indirectly rather than from custom code. In EBS 12.1.1 and 12.2.2, it is driven through the OPM automatic allocation concurrent program or from the shipping/pick release workflow when auto-allocation is enabled for a warehouse or order type. Forms-based flows for sales order and delivery processing call into the module, and the package itself calls GMI_AUTO_ALLOCATE_PUB and GMI_RESERVATION_UTIL for allocation and reservation utilities. Because it is not referenced by any other package according to the ETRM metadata, it should be treated as a top-level implementation component; customizations should prefer the published GMI_AUTO_ALLOCATE_PUB API or GMI_RESERVATION_UTIL rather than calling GMI_AUTO_ALLOC_BATCH_PKG procedures directly, since its internal signatures and behavior are not guaranteed stable across patches.