Search Results reopen_all_steps

Overview

GME_REOPEN_STEP_PVT is a private (PVT-classified) PL/SQL API belonging to the Oracle Process Manufacturing (OPM) batch execution modules within Oracle E-Business Suite. As its name and header comment indicate, the package is the "Package Specification for the GME batch reopen api." Its purpose is to reverse the closure of a previously completed or closed batch header and its associated process steps, returning them to an open, editable state so that operators or planners may correct data, adjust quantities, or resume processing.

The package is declared with AUTHID CURRENT_USER, meaning it executes with the privileges of the calling schema rather than the defining schema. Its header ($Header: GMEVROSS.pls 120.1 2005/06/03) shows it was authored by Olivier DABOVAL of OPM Development in May 2001, with a subsequent modification in August 2001 to support phantom implementation logic. It is documented identically against ETRM 12.2.2 and is applicable to the 12.1.1 release family, with the source predating the 12.2 online patching model by many years.

Key Procedures and Functions

The package exposes two documented procedures, both relating to re-opening batch structures:

• REOPEN_ALL_STEPS – Reopens the entire set of steps belonging to a single batch. It accepts a batch header record (modeled on gme_batch_header%ROWTYPE) as its input and returns a status indicator so the caller can determine whether the reopen completed successfully. This is the procedure most commonly sought when administrators or developers search for "reopen_all_steps," because it performs a batch-wide reopen in a single call.
• REOPEN_STEP – Reopens an individual batch step. It takes a single batch step record (modeled on gme_batch_steps%ROWTYPE) as input and returns the resulting batch step record together with a return status. This procedure is used when only a specific step, rather than the whole batch, must be returned to an open state.

Both procedures emit a standard x_return_status output, consistent with Oracle's concurrent/API error-handling conventions. No other public procedures or functions are documented.

Tables Accessed

The package operates against the following OPM tables, accessed through APPS synonyms:

• GME_BATCH_HEADER – the controlling batch record; supplies the row passed into REOPEN_ALL_STEPS and is updated to reflect the reopened header status.
• GME_BATCH_STEPS – the individual process steps within a batch; read and updated when steps are reopened, and used as the input/output record type for REOPEN_STEP.
• GME_BATCH_STEP_DEPENDENCIES – defines predecessor/successor relationships between steps. It is consulted and maintained so that reopening a step does not violate the batch's sequencing logic.
• PLITBLM – an OPM internal temporary/utility table used for intermediate processing, parsing, or bulk operations during the reopen routine.

Usage Notes

GME_REOPEN_STEP_PVT is classified as a private API and is therefore not intended for direct customer invocation; it is called internally by other OPM packages and by the standard OPM batch maintenance forms when a user selects the reopen action. The ETRM metadata records that it is referenced by two other packages, confirming its role as a subordinate worker routine. Because it is not a public interface, no supported external signature is guaranteed across releases, and customizations should invoke the higher-level public reopen API rather than calling this package directly. Where a batch or step has been closed in error and must be corrected, the supported path is through the OPM Batch Maintenance window or the parent public API, which will delegate to this package. Any direct use in custom code should include error handling on the returned status and should respect the AUTHID CURRENT_USER privilege model.