Search Results process_ingredient

Overview

GME_RELEASE_BATCH_PVT is a private PL/SQL package in the APPS schema within Oracle E-Business Suite Process Manufacturing (OPM/GME). Its central business function is to release a batch to manufacturing execution: it validates that a batch is eligible for release, consumes ingedients and materials against the batch, constructs material transaction interface (MTI) records, and posts those transactions so that on-hand balances and material movements are updated. The package is classified as a PVT (private) API, meaning it is intended to be invoked by other GME packages rather than called directly by customers; the public entry points are the GME_API_PUB and GME_API_MAIN packages, which internally call this package.

The release process is transactional and integrates tightly with Inventory transaction processing through MTL_TRANSACTIONS_INTERFACE, ensuring that the batch production activity produces standard Oracle Inventory transactions.

Key Procedures and Functions

• VALIDATE_BATCH_FOR_RELEASE — Performs pre-release validation of the batch, checking status, recipe validity, and other eligibility conditions before any consumption or transaction activity begins.
• RELEASE_BATCH — The main orchestration routine that drives the release of a batch, coordinating validation, material consumption, and transaction creation.
• PROCESS_INGREDIENT — Handles the consumption of an individual ingredient line on the batch.
• CONSUME_MATERIAL — Consumes materials required by the batch, driving inventory reductions for the constituent items.
• BUILD_AND_CREATE_TRANSACTION — Builds and creates the Inventory transaction interface records needed to post the release activity.
• CONSTR_MMTI_FROM_RESERVATION — Constructs material transaction interface rows based on existing inventory reservations (MTL_RESERVATIONS).
• CONSTR_MMTI_FROM_QTY_TREE — Constructs material transaction interface rows from the quantity tree (the lot/serial/subinventory quantity structure).
• CREATE_BATCH_EXCEPTION — Records batch exceptions, typically into the GME_EXCEPTIONS_GTMP global temporary table.
• CHECK_UNEXPLODED_PHANTOM — Verifies whether a phantom item has been exploded, supporting correct material requirements handling.

Tables Accessed

• GME_BATCH_HEADER — The primary batch record; controls release status and batch context.
• GME_MATERIAL_DETAILS — Material lines associated with the batch.
• GME_BATCH_STEPS / GME_BATCH_STEP_ITEMS — Batch routing steps and their items used during consumption.
• GME_EXCEPTIONS_GTMP — Global temporary table for batch exceptions.
• MTL_RESERVATIONS — Existing inventory reservations used as the basis for constructing transaction interface rows.
• MTL_SYSTEM_ITEMS_B / MTL_SYSTEM_ITEMS_KFV / MTL_ITEM_REVISIONS_B — Item master and revision data for validation and transaction construction.
• MTL_LOT_NUMBERS / MTL_TRANSACTION_LOTS_INTERFACE — Lot/serial attribution for material transactions.
• MTL_TRANSACTIONS_INTERFACE — The Inventory open interface table into which release transactions are written.
• GMD_RECIPE_VALIDITY_RULES / GMD_STATUS — Recipe validity and status lookups used during validation.
• PLITBLM — Oracle PL/SQL table utility package.

Usage Notes

GME_RELEASE_BATCH_PVT is invoked indirectly. The public API layer (GME_API_PUB, GME_API_MAIN) exposes batch release to external callers, and this package performs the internal work. It is referenced by eight other packages including GME_COMPLETE_BATCH_PVT, GME_INCREMENTAL_BACKFLUSH_PVT, GME_RELEASE_BATCH_STEP_PVT, GME_UNRELEASE_BATCH_PVT, and GME_RESERVATIONS_PVT, reflecting its role across the batch lifecycle. Because it writes to MTL_TRANSACTIONS_INTERFACE, a subsequent Inventory transaction manager run is required to actually post the material movements. It is not intended for direct custom invocation; customizations should call the public GME APIs instead. The package depends on FND_API, GME_COMMON_PVT, and STANDARD for error handling and standard utilities.