Search Results validate_step_for_unrelease




Overview
Explore in AI Chat

Overview

GME_UNRELEASE_STEP_PVT is an Oracle EBS Application Programming Interface (API) package owned by the APPS schema and classified as a Private (PVT) API within the Process Manufacturing (GME) module. It is part of the batch step management infrastructure that governs the lifecycle of discrete batch steps in Oracle Process Manufacturing (OPM). Specifically, this package performs the "unrelease" operation on individual batch steps, reversing a prior release action so that a step is returned to an earlier status in the batch execution lifecycle. Unreleasing is a controlled operation that allows process manufacturers to correct steps that were released prematurely, modify parameters, or match step state to actual shop-floor conditions before completion. As a PVT package, it is not intended for direct customer invocation; it is internal plumbing consumed by higher-level public APIs such as GME_API_MAIN, GME_API_PUB, and GME_UNRELEASE_BATCH_PVT, which expose the supported unrelease functionality to forms, concurrent programs, and custom extensions.

Key Procedures and Functions

  • UNRELEASE_STEP — The core routine that executes the unrelease of a single batch step. It reverses the released state of a step and manages the associated child records so that step activities, dependencies, items, and resources are consistently restored to a pre-release condition.
  • VALIDATE_STEP_FOR_UNRELEASE — A validation routine invoked before the unrelease operation proceeds. It confirms that the target batch step is in a state eligible for unrelease and that no downstream conditions (for example, completed successor steps) block the reversal.

Because this is a PVT package, the documented interface is limited to these two operations, both intended for internal orchestration by the public API layer rather than direct invocation. Specific parameter signatures are not documented here.

Tables Accessed

  • GME_BATCH_HEADER — Header-level batch record, read to establish batch context and validate the step's parent batch.
  • GME_BATCH_STEPS — The primary target table where the step's status is read and updated during unrelease.
  • GME_BATCH_STEP_ACTIVITIES — Step activity records affected by the status reversal.
  • GME_BATCH_STEP_DEPENDENCIES — Step-to-step dependency definitions validated during unrelease, supporting the VALIDATE_STEP_FOR_UNRELEASE logic.
  • GME_BATCH_STEP_ITEMS — Material items associated with the step, updated to reflect the unreleased state.
  • GME_BATCH_STEP_RESOURCES — Resource assignments for the step, maintained in sync with the status change.
  • GME_MATERIAL_DETAILS — Material detail records linked to step consumption and yield information.
  • PLITBLM — A standard EBS PL/SQL index-by table type used internally for bulk processing.

Usage Notes

GME_UNRELEASE_STEP_PVT is invoked indirectly by supported public APIs. GME_UNRELEASE_BATCH_PVT calls it to unrelease steps as part of a whole-batch unrelease, while GME_API_MAIN and GME_API_PUB expose it through the broader OPM batch API. Typical invocation paths include OPM batch maintenance forms, batch reversal or correction processes, and custom PL/SQL programs that call the public API layer rather than the PVT package directly. The package observes an ordering requirement: VALIDATE_STEP_FOR_UNRELEASE should be exercised before UNRELEASE_STEP. Customers should treat the package as non-supported for direct calls and route all operations through GME_API_PUB or GME_UNRELEASE_BATCH_PVT to preserve data integrity across the batch step, activity, item, and resource tables. Dependency analysis confirms the package is referenced only within the APPS schema and is dependent on the GME_BATCH_HEADER and GME_BATCH_STEPS tables plus the STANDARD SYS package, consistent with a tightly scoped internal utility.