Results for “gme_transactions_pvt”

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

Overview

APPS.GME_TRANSACTIONS_PVT is the private PL/SQL package that underpins material transaction processing for Oracle Process Manufacturing (OPM) within Oracle E-Business Suite 12.1.1 and 12.2.2. It serves as the engine layer through which OPM batch material movements—issues, returns, completions, and backflush activity—are constructed, validated, staged, and ultimately written to Oracle Inventory. The package is classified as a PVT (private) API, meaning it is not intended for direct third-party invocation but is instead called by the public OPM APIs and batch-handling packages that the application exposes.

The package operates as part of the GME (Process Execution) module's transaction architecture. Its core responsibility is to translate OPM batch step consumption and production into records compatible with the MTL_TRANSACTIONS_INTERFACE, then drive those records through inventory's transaction processor. This design allows OPM batch logic to reuse standard inventory cost, lot, quantity, and accounting routines rather than duplicating them.

Key Procedures and Functions

The package exposes twenty-six documented procedures and functions, organized around the transaction lifecycle:

• CREATE_MATERIAL_TXN, UPDATE_MATERIAL_TXN, DELETE_MATERIAL_TXN — Manage the lifecycle of individual OPM material transaction records within the transaction pairs structure.
• BUILD_TXN_INTER, BUILD_TXN_INTER_HDR, BUILD_TXN_INTER_LOT — Construct the inventory interface rows, including header-level and lot-level detail, from validated transaction data.
• GET_TRANSACTIONS, GET_MAT_TRANS, GET_LOT_TRANS — Retrieve material and lot transaction information for processing or display.
• CONSTRUCT_MMTI — Assembles the MTL_MATERIAL_TRANSACTIONS_INTERFACE payload that inventory consumes.
• GME_PRE_PROCESS, PRE_PROCESS_VAL, GME_POST_PROCESS — Execute validation and state-management logic before and after the inventory transaction is processed.
• PROCESS_TRANSACTIONS — Drives the submission of staged transactions to inventory.
• GET_RETURNABLE_QTY — Determines the quantity available to be returned from a batch step.
• GME_TXN_MESSAGE — Produces diagnostic and error messaging for failed or flagged transactions.
• PURGE_TRANS_PAIRS — Cleans up transaction pair records after successful processing.
• QUERY_QUANTITIES, UPDATE_QUANTITIES — Read and maintain the on-hand and transaction quantities associated with batch steps.
• IS_LOT_EXPIRED — Evaluates lot expiry status during validation.

Tables Accessed

The package reads and writes inventory and OPM transaction tables through APPS synonyms. MTL_MATERIAL_TRANSACTIONS, MTL_MATERIAL_TRANSACTIONS_S, MTL_MATERIAL_TRANSACTIONS_TEMP, and MTL_TRANSACTIONS_INTERFACE form the inventory-facing core. MTL_TRANSACTION_LOTS_INTERFACE and MTL_TRANSACTION_LOT_NUMBERS, together with MTL_LOT_NUMBERS, carry lot and serial detail. GME_BATCH_HEADER, GME_BATCH_STEPS, and GME_BATCH_STEP_ITEMS supply the batch structure being transacted, while GME_MATERIAL_DETAILS and GME_TRANSACTION_PAIRS store the OPM-side transaction records. MTL_SYSTEM_ITEMS_B and MTL_SYSTEM_ITEMS_KFV provide item validation and descriptive flexfield information, and GME_ERES_GTMP supports electronic records functionality.

Usage Notes

GME_TRANSACTIONS_PVT is invoked indirectly. The documented calling packages include GME_API_PUB, GME_API_GRP, GME_COMPLETE_BATCH_PVT, GME_RELEASE_BATCH_PVT, GME_UNRELEASE_BATCH_PVT, GME_CANCEL_BATCH_PVT, GME_INCREMENTAL_BACKFLUSH_PVT, GME_MOVE_ORDERS_PVT, GME_MATERIAL_DETAIL_PVT, GME_MOBILE_TXN, GME_LPN_MOBILE_TXN, GME_SUPPLY_RES_PVT, GMD_SPREAD_FETCH_PKG, MTL_LOT_UOM_CONV_PVT, and GME_COMMON_PVT, and it is referenced by fifteen packages in total. In practice, users trigger it through OPM batch completion forms, the material transaction and mobile transaction interfaces, backflush processing, and any custom code that calls the GME public APIs. Because it is a private API, customization should target the public GME_API_PUB layer rather than calling this package directly, as its signature and internal behavior are not committed for external use.