Search Results gme_reopen_step_pvt




Overview
Explore in AI Chat

Overview

GME_REOPEN_STEP_PVT is a private PL/SQL API (PVT classification) in the Oracle E-Business Suite Process Manufacturing (GME) module. Its business function is to reverse the effect of a completed or partially completed batch step closure, returning a batch step to an open, editable state so production can resume. In discrete and process manufacturing execution, a step or operation on a batch may be closed prematurely — for example, when actual material consumption, yields, or resource charges need correction, or when downstream quality or reconciliation issues surface. Rather than reversing the entire batch, this package allows targeted reopening at the step level, preserving valid work already recorded.

The package is a companion to GME_REOPEN_BATCH_PVT, which handles batch-level reopening. GME_REOPEN_STEP_PVT encapsulates the validation and transactional logic required to ensure steps are reopened only when the batch context permits and when dependent steps or step dependencies are not violated. It follows the standard Oracle API pattern, using FND_API for the return status, FND_MSG_PUB for message stack handling, and SAVEPOINT/rollback semantics so callers can participate in a larger transaction. It is currently VALID in the APPS schema.

Key Procedures and Functions

  • REOPEN_STEP — Reopens a single, specified batch step. This procedure validates that the step is eligible for reopening, checks the parent batch status and any step-to-step dependencies, reverses the step's closed indicator, and records the resulting change so the step can be reworked. It is the primary entry point when an operator or process needs to release one step for additional transactions.
  • REOPEN_ALL_STEPS — Reopens all currently closed steps belonging to a batch in a single call. This is typically used when a batch-level correction requires the entire execution sequence to be released again. It performs the appropriate per-step validations in bulk and applies the same closure-reversal logic across the batch's step set.

Parameter lists are intentionally not reproduced here; callers should obtain the exact signatures from the package specification in the deployment. Both procedures operate through the standard GME private-API convention of returning status and message information via FND_API / FND_MSG_PUB rather than raised exceptions.

Tables Accessed

  • GME_BATCH_HEADER — The parent batch record. Read to establish batch status and context before any step is reopened, and used to confirm the batch itself permits step reopening (for example, that it is not fully closed or interfaced).
  • GME_BATCH_STEPS — The core batch step table. This is the principal table updated: the closed/open indicator and related status columns are reset so the step becomes editable and re-transactable.
  • GME_BATCH_STEP_DEPENDENCIES — Defines prerequisite relationships between steps. Read to validate that reopening a step will not break sequencing rules or leave dependent steps in an inconsistent state.
  • PLITBLM — A standard Oracle PL/SQL index-by table type used internally for array processing, typically when REOPEN_ALL_STEPS iterates over a batch's step set.

Usage Notes

Because GME_REOPEN_STEP_PVT is a private (PVT) API, it is not intended to be called directly from forms or concurrent programs. It is invoked indirectly by the public batch-maintenance APIs. The dependency metadata confirms this: the package is referenced by two other packages and references GME_REOPEN_BATCH_PVT, GME_CLOSE_BATCH_PVT, GME_COMMON_PVT, GME_PHANTOM_PVT, and the GME_BATCH_STEPS_DBL table handler, indicating it participates in coordinated close/reopen orchestration.

Typical invocations occur when a user, through the Process Manufacturing batch forms, requests reopening of a step or all steps on a batch. The calling public API validates user privileges via FND_PROFILE, delegates to this package, and returns messages through FND_MSG_PUB. Custom code that needs step-level reopening should call the supported public wrapper and supply the appropriate batch and step identifiers, rather than calling GME_REOPEN_STEP_PVT directly, to preserve API contracts and message-handling behavior across EBS 12.1.1 and 12.2.2.