Search Results gme_trans_engine_util




Overview
Explore in AI Chat

Overview

GME_TRANS_ENGINE_UTIL is a utility package in the Oracle E-Business Suite Process Manufacturing (OPM) product family, owned by the APPS schema. Its documented API classification is UTIL, indicating that it provides internal helper logic rather than a public business API. The package body supports the transaction engine that converts process manufacturing batch and resource activity into inventory and pending material transactions. It bridges batch execution data held in GME_BATCH_HEADER and GME_MATERIAL_DETAILS with the staging and transaction tables used by the inventory interface, including GME_INVENTORY_TXNS_GTMP, GME_RESOURCE_TXNS, GME_RESOURCE_TXNS_GTMP, and IC_TRAN_PND.

Because the object is a package body with no separate public specification listed as a distinct dependent object, its procedures are intended for consumption by the transaction engine layer itself, notably GMI_TRANS_ENGINE_PUB, and by related internal packages. The ETRM metadata records the object as VALID in the 12.1.1 and 12.2.2 environments.

Key Procedures and Functions

The documented package exposes seven procedures and functions:

  • LOAD_MAT_AND_RSC_TRANS — Orchestrating routine that loads material and resource transaction records into the transaction engine staging structures, driving the flow from batch detail data toward inventory transaction processing.
  • BUILD_TRANS_REC — Constructs an individual transaction record from the supplied batch, material, or resource context so that downstream processing receives a consistent row image.
  • LOAD_RSRC_TRANS — Loads resource transaction records, populating GME_RESOURCE_TXNS and its global temporary counterpart GME_RESOURCE_TXNS_GTMP.
  • SET_DEFAULT_LOT_FOR_BATCH — Determines and assigns the default lot number for an existing batch, based on batch context.
  • SET_DEFAULT_LOT_FOR_NEW_BATCH — Performs the equivalent default lot assignment for a batch being created, typically during initial transaction generation.
  • DEDUCE_TRANSACTION_WAREHOUSE — Derives the warehouse applicable to a transaction when the warehouse is not explicitly supplied, using warehouse and organization data to reach a default.
  • GET_DEFAULT_LOT — Returns the default lot value for the given context; a shared accessor used by the other lot-related routines.

The metadata does not document parameter lists for these units, and none should be assumed.

Tables Accessed

The package reads and writes the following tables through APPS synonyms:

  • GME_BATCH_HEADER — Source of batch identity and status used to qualify transactions.
  • GME_MATERIAL_DETAILS — Material consumption and production detail lines converted into inventory movements.
  • GME_INVENTORY_TXNS_GTMP — Global temporary staging area for inventory transactions before they reach the interface tables.
  • GME_RESOURCE_TXNS and GME_RESOURCE_TXNS_GTMP — Resource usage transactions and their temporary staging equivalents.
  • IC_TRAN_PND — Pending inventory transaction interface table; the terminal destination of the engine flow.
  • IC_ITEM_MST, IC_WHSE_MST, and PS_WHSE_EFF — Item, warehouse, and warehouse effectiveness master data used to validate and default transaction attributes.

Usage Notes

This package is internal infrastructure. It is not a documented public API and is not referenced by any database object per the ETRM dependency data, meaning no other stored object invokes it directly in the analyzed environment. In practice it is invoked from the process manufacturing transaction engine flow that ultimately calls GMI_TRANS_ENGINE_PUB, typically triggered by batch completion, batch close, or inventory transaction generation in OPM. It also relies on FND_API, FND_MSG_PUB, FND_PROFILE, GME_COMMON_PVT, GME_DEBUG, GMICUOM, and GMIGUTL for error handling, profile values, unit-of-measure conversion, and debugging.

Customizations should not call these routines directly, since the interface contract is undocumented and the procedures are subject to change between releases. The supported integration point for external code remains GMI_TRANS_ENGINE_PUB and the standard Open Interface tables. The package must remain VALID for batch transaction processing to succeed; invalidations caused by patching or table structure changes should be resolved by recompiling the package body in the APPS schema.