Search Results validate_dependent_steps




Overview
Explore in AI Chat

Overview

GME_COMPLETE_BATCH_STEP_PVT is a private PL/SQL API package in the APPS schema that supports the process manufacturing (OPM) batch completion workflow in Oracle E-Business Suite. Its specific responsibility is to complete individual batch steps within a process batch, rather than the batch as a whole. In the OPM execution model, a batch is composed of one or more routing steps, and each step carries its own material issues, resource charges, activities, and dependent step relationships. This package encapsulates the logic required to mark a batch step as complete, to cascade completion to dependent steps when required, and to validate that a step is eligible for completion before any status change occurs. Because it is classified as a PVT (private) package, it is not intended as a public integration point; it is the internal engine invoked by public APIs and by the batch completion orchestration logic. The package status is VALID and it is documented as referencing GME_BATCH_HEADER, GME_BATCH_STEPS, and GME_COMMON_PVT, and as being referenced by GME_API_MAIN, GME_API_PUB, GME_COMPLETE_BATCH_PVT, GME_MOBILE_TXN, and GME_RELEASE_BATCH_STEP_PVT.

Key Procedures and Functions

The ETRM 12.2.2 metadata documents seven procedures and functions within this package:

  • COMPLETE_STEP — the primary entry point that performs completion of a single batch step, invoking the appropriate validation and sub-processing logic.
  • COMPLETE_STEP_RECURSIVE — extends completion processing to dependent steps, allowing a completion request to cascade through the step dependency chain.
  • COMPLETE_STEP_LINE — handles completion processing at the step line level, addressing the transactional lines associated with a step.
  • COMPLETE_STEP_MATERIAL — manages the material-related aspects of step completion, including the treatment of issued and consumed materials.
  • VALIDATE_STEP_FOR_COMPLETE — performs pre-completion validation to confirm that a step satisfies the conditions required for completion.
  • VALIDATE_STEP_CMPLT_DATE — validates the completion date supplied for a step, ensuring date integrity for the transaction.
  • VALIDATE_DEPENDENT_STEPS — verifies the status of dependent steps so that sequencing rules are honored before a step is completed.

Parameters for these routines are not published in the metadata and should not be assumed; the descriptions above reflect documented purpose only.

Tables Accessed

The package operates against the core OPM batch tables via APPS synonyms. GME_BATCH_HEADER and GME_BATCH_STEPS provide the batch and step context, including step status and identifiers. GME_BATCH_STEP_ACTIVITIES, GME_BATCH_STEP_RESOURCES, and GME_BATCH_STEP_RSRC_SUMMARY hold activity, resource, and resource summary data affected by step completion. GME_BATCH_STEP_ITEMS and GME_MATERIAL_DETAILS support material and item-level processing. GME_BATCH_STEP_DEPENDENCIES is central to the recursive and dependent-step validation logic. GMD_RECIPE_VALIDITY_RULES and GMD_STATUS supply recipe and status validation lookups, while PLITBLM is the standard Oracle EBS PL/SQL index-by table used for internal ID list handling. GME_COMMON_PVT is referenced as a shared utility dependency.

Usage Notes

As a private package, GME_COMPLETE_BATCH_STEP_PVT is not called directly from forms or concurrent programs. It is invoked indirectly through public APIs such as GME_API_PUB and GME_API_MAIN, and through the higher-level completion packages GME_COMPLETE_BATCH_PVT and GME_RELEASE_BATCH_STEP_PVT. OPM mobile transactions (GME_MOBILE_TXN) also reach this package during shop-floor step completion. Custom code requiring step completion should call the supported public API layer rather than this package, since its interface is not guaranteed across releases. The dependency on GME_COMMON_PVT indicates reliance on standard OPM API error handling, message stacking, and commit control conventions.