Search Results gme_reopen_batch_pvt




Overview
Explore in AI Chat

Overview

The APPS.GME_REOPEN_BATCH_PVT package body is a private (PVT-classified) PL/SQL API within the Oracle E-Business Suite Process Manufacturing module. Its business purpose is to reverse the posting of a production batch so that the batch can be corrected and re-posted. In process manufacturing, batch transactions — material consumption, product completion, and cost collection — are committed through the transaction engine and become effectively frozen once posted. When an operator discovers an error after posting (an incorrect quantity, a missing ingredient, a wrong resource), the batch must be reopened, adjusted, and posted again. This package provides the programmatic mechanism to perform that reversal safely, restoring the batch to an editable state while unravelling the associated costing and history records. It is designated PRIVATE, meaning Oracle does not publish it as a supported integration interface; it is intended for internal consumption by other Oracle Process Manufacturing packages and forms rather than direct customer invocation.

Key Procedures and Functions

The ETRM documentation identifies three callable units within the package:

  • REOPEN_BATCH — The primary entry point. It drives the reversal of a posted batch, coordinating the unposting of batch steps, revaluation of material detail records, and insertion of an audit trail. It is the procedure that consumers of the package are expected to call.
  • IS_BATCH_POSTED — A validation function used to determine whether a given batch currently holds a posted status. Callers use this to guard against reopening a batch that is not posted, or to confirm state before further processing.
  • IS_PERIOD_OPEN — A validation function that checks whether the accounting period associated with the batch remains open. Because reopening a batch reverses cost ledger entries, the target period must accept the reversing entries; this function enforces that constraint.

All three follow the standard OPM API convention of returning a status and populating the FND message stack via FND_MSG_PUB on failure. Parameter lists are not reproduced in the ETRM metadata and are not stated here.

Tables Accessed

The package reads and writes the core Process Manufacturing batch and costing tables through APPS synonyms:

  • GME_BATCH_HEADER — The controlling batch record; its posting status and period attributes are read and updated to return the batch to an open state.
  • GME_MATERIAL_DETAILS — Ingredient consumption lines whose transaction and cost indicators are reversed during reopening.
  • GME_BATCH_HISTORY — The batch audit/status history table, where reopening activity is recorded.
  • GME_BATCH_STEP_ITEMS — Step-level item records that must be reconciled with the reopened batch state.
  • CM_ACST_LED and CM_CMPT_DTL — Cost management actual cost ledger and component detail tables that hold the cost entries generated at posting; these are adjusted to remove the original posting's cost impact.
  • GMF_PERIOD_STATUSES — Read to validate period openness through IS_PERIOD_OPEN.
  • PLITBLM — The standard PL/SQL index-by table used for bulk processing.

Usage Notes

GME_REOPEN_BATCH_PVT is not referenced by any other database object at the schema level, which confirms its private nature: it is invoked from within the Process Manufacturing application, historically from batch maintenance forms and from the public wrapper packages that expose reopen functionality. The documented dependencies on GME_REOPEN_STEP_PVT, GME_BATCH_HEADER_DBL, GME_TRANS_ENGINE_UTIL, GME_COMMON_PVT, and FND_API indicate that it delegates step-level reversal and transaction engine cleanup to sibling packages rather than performing all work itself. Custom developers should treat it as internal, prefer a documented public API, and be aware that behavior differs between 12.1.1 and 12.2.2 only insofar as the underlying OPM schema and public wrapper have evolved.