Search Results gme_batch_steps_dbl




Overview
Explore in AI Chat

Overview

GME_BATCH_STEPS_DBL is a database-layer (DBL) PL/SQL package body owned by the APPS schema in Oracle E-Business Suite. It belongs to the Process Manufacturing (OPM/GME) product family and provides the low-level row-handling operations for the GME_BATCH_STEPS entity, which stores the individual routing steps that make up a process batch or recipe. In the Oracle EBS architecture, a "_DBL" package is the generated or hand-maintained database block layer that a corresponding client-side form (typically the Batch Steps / Process Instructions form) delegates to for its INSERT, UPDATE, DELETE, FETCH, and locking operations. The package therefore acts as the persistence façade between the Oracle Forms user interface and the underlying base tables, isolating the form from direct DML against the tables.

The object is documented as VALID in both the 12.1.1 and 12.2.2 ETRM repositories, and its API classification is OTHER rather than a public or open interface, confirming it is intended as an internal form-support layer rather than an integration API.

Key Procedures and Functions

The documented interface consists of five procedures that implement the standard block-level row operations used by the associated Oracle Forms block:

  • INSERT_ROW — Creates a new batch step record for the current batch, derived from the form block's current item values.
  • UPDATE_ROW — Modifies the attributes of an existing batch step row, typically after the user edits step information in the form.
  • DELETE_ROW — Removes the identified batch step row from the entity.
  • FETCH_ROW — Retrieves a single batch step row, populating the form block during query and navigation.
  • LOCK_ROW — Acquires the row-level lock required before an update or delete, enforcing concurrency control within the block.

No parameter lists are documented in the ETRM metadata; parameter signatures should be confirmed by inspecting the package specification in the target environment.

Tables Accessed

The package references two base tables through APPS synonyms:

  • GME_BATCH_STEPS — The primary transactional table holding batch step (routing operation) records, including step sequencing, operation, and resource assignments. INSERT_ROW, UPDATE_ROW, DELETE_ROW, and FETCH_ROW operate against this table.
  • GME_BATCH_STEP_S — The translated/secure-lookup companion table for batch step descriptive text, used to resolve step names and descriptions for the user's language and security profile.

Dependency metadata further shows the package body calling GME_BATCH_STEP_S, GME_COMMON_PVT, GME_DEBUG, FND_MSG_PUB, FND_PROFILE, and APP_EXCEPTION, indicating it uses shared OPM utility routines for validation and common processing, standard EBS message handling for error reporting, profile option lookups, and centralized exception handling.

Usage Notes

GME_BATCH_STEPS_DBL is not a public integration API; ETRM reports it as referenced by 25 other database objects but it is itself a consumer of, rather than provider to, external interfaces. It is invoked indirectly through Oracle Forms when users maintain batch steps in the Process Manufacturing batch and recipe screens, and it may also be called from other OPM package bodies that perform batch-step maintenance. Custom code should not call this package directly, because it is an internal form-support layer with no documented parameter contracts, and its procedures assume the form block's context and column values. Oracle recommends that integrations use the supported, published GME batch and recipe APIs instead. Any modification of batch steps outside these supported paths risks bypassing the validation, translation, and concurrency logic implemented in this layer.