Search Results update_ic_tran_pnd

Overview

APPS.GMI_TRAN_PND_DB_PVT is a private PL/SQL package body in the Oracle E-Business Suite Process Manufacturing (OPM) schema. It provides the database-layer persistence logic for the pending transaction subsystem in the Process Execution / Transaction Engine area of OPM. Specifically, the package encapsulates the create, read, update, and delete operations against the pending transaction table IC_TRAN_PND, which serves as the staging area for inventory and process transactions that have been submitted to OPM but not yet processed by the transaction engine.

The package is classified as a PVT (private) API, meaning its procedures and functions are intended to be called by the owning subsystem's engine code — nominally GMI_TRANS_ENGINE_PUB — and not directly by external or public callers. It is documented as VALID and, per the ETRM metadata, is referenced by ten other packages, indicating it is a foundational dependency for transaction staging across the OPM inventory modules. The user search term "gem5_trans_id_s" corresponds to the GEM5_TRANS_ID_S sequence that this package depends upon to generate primary transaction identifiers.

Key Procedures and Functions

The package exposes four documented procedures, all following the standard CRUD pattern for the IC_TRAN_PND staging table:

• INSERT_IC_TRAN_PND — Inserts a new pending transaction row into IC_TRAN_PND, capturing the transaction payload submitted by the calling engine.
• FETCH_IC_TRAN_PND — Retrieves pending transaction records from IC_TRAN_PND for downstream processing by the transaction engine.
• DELETE_IC_TRAN_PND — Removes pending transaction rows, typically after successful processing or to purge obsolete staged records.
• UPDATE_IC_TRAN_PND — Modifies existing pending transaction rows, including status or processing-state changes.

Parameter lists and signatures are not documented in the ETRM extract and should be confirmed by inspecting the package specification and body directly in the APPS schema.

Tables Accessed

The package references three objects via APPS synonyms:

• IC_TRAN_PND — The central pending transaction table. All four procedures operate against this table; it is the persistence target for staged OPM transactions awaiting engine processing.
• GEM5_TRANS_ID_S — An Oracle sequence used to obtain unique transaction identifiers. This is the object matching the user's search term, and it explains the dependency chain requested.
• DUAL — The standard Oracle single-row utility table, consistent with sequence-based identifier generation.

Additional functional dependencies include FND_API, FND_MESSAGE, FND_MSG_PUB (error and message handling), GMI_TRANS_ENGINE_PUB, and the package itself (recursive or internal calls). The use of FND_MSG_PUB confirms the package adheres to the OPM/EBS stack error-handling convention.

Usage Notes

GMI_TRAN_PND_DB_PVT is not intended for direct invocation by customers or forms. It is a private underlying implementation package, called from GMI_TRANS_ENGINE_PUB and from the ten referencing packages documented in ETRM. Typical invocation occurs when OPM forms or concurrent programs submit inventory, lot, or process transactions that must be staged before being applied by the transaction engine. The package handles the database-side transaction staging step, while the engine package orchestrates business validation and final posting. Because the API classification is PVT, customizations should avoid calling it directly; instead, integrations should invoke the public transaction engine interfaces. Any code depending on the GEM5_TRANS_ID_S sequence should assume identifier generation is centralized here.