Search Results gme_release_batch_step_pvt




Overview
Explore in AI Chat

Overview

The APPS.GME_RELEASE_BATCH_STEP_PVT package is a private (PVT-classified) PL/SQL API within the Oracle E-Business Suite Process Manufacturing (OPM) module. It encapsulates the business logic required to release individual steps of a batch within the Oracle Process Manufacturing (OPM/GME) application. The package name, along with the primary procedure release_step referenced in the user search term "release_step," indicates its role in the batch execution lifecycle: moving a batch step from a planned or validated state into a releasable/executable state so that downstream activities, ingredients, and resources can be consumed.

In OPM batch manufacturing, a batch header (GME_BATCH_HEADER) is composed of multiple batch steps (GME_BATCH_STEPS). Releasing a step typically establishes its readiness for execution, validates recipe and status rules, and processes dependent steps, line-level information, and ingredient consumption or reservation. This package serves as the internal engine that the public batch release APIs and forms delegate to when a user or program initiates step release. The ETRM metadata notes that it is referenced by five other packages, confirming that it is a shared internal utility rather than a top-level entry point.

Key Procedures and Functions

The package exposes six documented procedures, all marked with the ship header revision 120.5. Each is described below by purpose only; parameter lists are intentionally omitted.

  • RELEASE_STEP — The primary entry point for releasing a single batch step. It accepts a batch step record and batch header record, returns the updated batch step record, accumulates exception material information, and returns a status indicator.
  • RELEASE_STEP_RECURSIVE — Performs the same release operation but follows dependency chains, recursing into dependent steps so that a release request propagates through the step hierarchy.
  • PROCESS_DEPENDENT_STEPS — Identifies and processes steps that depend on the step being released, ensuring dependencies are handled in the correct order and that exception materials are collected.
  • RELEASE_STEP_LINE — Handles the line-level details of a batch step release, updating the batch step record returned to the caller.
  • RELEASE_STEP_INGREDIENTS — Processes ingredient consumption or reservation for the step, with an update inventory indicator controlling whether inventory is affected, and collects exception material data.
  • VALIDATE_STEP_FOR_RELEASE — Performs validation of a batch step against its batch header prior to release, returning the validated batch step record and a status indicator.

Tables Accessed

The package interacts with the core OPM batch and recipe tables, accessed through APPS synonyms. The documented tables include:

  • GME_BATCH_HEADER — The parent batch record, providing header-level context and status necessary to validate and release a step.
  • GME_BATCH_STEPS — The primary table whose rows represent individual steps; the release logic reads and updates step status and related attributes.
  • GME_BATCH_STEP_ITEMS, GME_BATCH_STEP_RESOURCES, GME_BATCH_STEP_ACTIVITIES — Step-level ingredient items, resources, and activities that are processed during release.
  • GME_BATCH_STEP_DEPENDENCIES — Defines the dependency relationships between steps, supporting the recursive and dependent-step processing procedures.
  • GMD_RECIPE_VALIDITY_RULES and GMD_STATUS — Recipe validity and status definitions used during validation of the step for release.
  • GME_MATERIAL_DETAILS — Material and inventory details associated with ingredient consumption during release.
  • PLITBLM — A PL/SQL table used for bulk operations or temporary storage during processing.

Usage Notes

Because this package is classified as PVT and is referenced by five other packages, it is not intended for direct invocation by end users or external custom code. It is typically called from within other OPM packages, batch release forms, or concurrent programs that orchestrate batch execution. The procedures are designed to be invoked in sequence — validation first, then line, ingredient, and dependent-step processing — with the exception material table (gme_common_pvt.exceptions_tab) accumulating warnings or blocking conditions. Customizations should call the public batch release APIs rather than this private package, since the internal signature and behavior may change between patch levels. When troubleshooting a failed "release_step" action, the exception material table and the x_return_status output are the primary diagnostic outputs.