Search Results revert_step

Overview

APPS.GME_REVERT_STEP_PVT is a private (PVT) PL/SQL package belonging to the Oracle Process Manufacturing (OPM) product family in Oracle E-Business Suite 12.1.1 and 12.2.2. Its principal business function is to reverse, or "revert," a previously executed step within a process manufacturing batch. When a batch step has been entered through batch step entry, or executed through the OPM batch execution flow, the application may need to undo that transaction before the batch is closed or advanced to the next step. GME_REVERT_STEP_PVT encapsulates this reversal logic so that the associated step activities, dependencies, items, and resource consumptions are consistently unwound rather than handled through ad hoc updates.

The package is classified as private, which indicates that it is an internal implementation utility invoked by other EBS packages rather than being exposed as a public API for direct customer or partner use. It stores no data of its own; instead it orchestrates the reversal against the underlying batch step tables, preserving data integrity across the batch execution model.

Key Procedures and Functions

The documented package exposes a single procedure:

• revert_step — This is the core routine that performs the reversal of a single batch step. It accepts an input batch step record and an associated batch header record, and returns an output batch step record together with a return status. The procedure coordinates the removal or invalidation of the step-level detail rows, ensures the batch header reflects the reversal, and communicates success or failure through the output status indicator, allowing the calling program to decide whether to proceed, roll back, or report an error.

No other procedures or functions are documented. The package specification is minimal, confirming its narrow purpose as a targeted reversal helper rather than a broad batch management API. Because it is a PVT package, its procedures are not documented for direct external invocation, and parameter lists should be treated as internal implementation details subject to change across versions or patches.

Tables Accessed

The package references a focused set of OPM batch tables through APPS synonyms:

• GME_BATCH_HEADER — the batch master record, used to validate the batch context and to update header-level status.
• GME_BATCH_STEPS — the batch step definition and execution records that are the primary subject of the reversal.
• GME_BATCH_STEP_ACTIVITIES — activities recorded against the step, which must be undone to keep the step consistent.
• GME_BATCH_STEP_DEPENDENCIES — dependency relationships between steps that affect whether and how a step can be reverted.
• GME_BATCH_STEP_ITEMS — ingredient and material entries associated with the step.
• GME_BATCH_STEP_RESOURCES — resource usage recorded against the step.
• GME_MATERIAL_DETAILS — material detail records that may require reversal or adjustment alongside the step.
• PLITBLM — the standard Oracle Applications PL/SQL integer table type, typically used internally for bulk processing or set-based operations.

Together these tables represent the complete footprint of a batch step, which explains why the package touches all of them: reverting a step requires unwinding its activities, items, resources, and material details in a coordinated manner.

Usage Notes

As a private package, GME_REVERT_STEP_PVT is invoked by one other documented package rather than directly by end users. In practice, it is called when a user or process requests reversal of a batch step through the OPM batch entry or batch execution forms, or when an internal batch engine needs to unwind a step as part of a larger adjustment. Custom code should avoid invoking private packages directly, since their interfaces are not guaranteed and may change with patches; where step reversal is required programmatically, customers should prefer any public OPM batch API that internally delegates to this package. For 12.1.1 and 12.2.2, the behavior is consistent with the standard OPM batch execution model, with the package header carrying a 2005 copyright, indicating a long-standing component of the OPM batch framework.