Search Results gme_batch_header_dbl




Overview
Explore in AI Chat

Overview

GME_BATCH_HEADER_DBL is a database-layer (DBL) PL/SQL package body in the APPS schema that encapsulates the persistence logic for batch header records in Oracle Process Manufacturing (OPM), now delivered as part of Oracle E-Business Suite 12.1.1 and 12.2.2. The package belongs to the Oracle Manufacturing module family surrounding the GME (Process Manufacturing) schema and functions as the data-access tier beneath the batch header business logic. In the standard OPM architecture, a batch represents a discrete production run, and the GME_BATCH_HEADER table stores its identifying attributes and lifecycle status. This DBL package mediates create, read, update, delete, and locking operations against that table, isolating the underlying SQL from the higher-level batch APIs and forms.

ETRM classifies the package as API classification OTHER, indicating it is not intended as a public, fully versioned interfaces API in the manner of the Open Interfaces, but is a supporting internal component. The body is documented as VALID and is referenced by 34 other database objects, confirming its role as a shared, low-level dependency across the OPM batch code stack.

Key Procedures and Functions

The documented interface comprises five procedures, each addressing a single operation in the batch header lifecycle:

  • INSERT_ROW — Creates a new batch header row, populating the GME_BATCH_HEADER record and allocating a generated object identifier.
  • FETCH_ROW — Retrieves one batch header record, typically by primary key, for consumption by calling business logic or user interface layers.
  • DELETE_ROW — Removes an existing batch header record.
  • UPDATE_ROW — Modifies the mutable attributes of an existing batch header record.
  • LOCK_ROW — Acquires a row-level lock on the batch header to enforce concurrency control during transactional processing.

Parameter lists are not reproduced in the ETRM extract; callers should inspect the live package specification in the target instance before invoking these procedures directly.

Tables Accessed

The package operates against the following tables through APPS synonyms:

  • GME_BATCH_HEADER — the primary batch header entity and the target of all insert, fetch, update, delete, and lock operations.
  • MTL_GEN_OBJECT_ID_S — the sequence used to generate unique object identifiers during row insertion.
  • WIP_ENTITIES and WIP_ENTITIES_S — the Work in Process entity registration table and its sequence, used to enroll the batch as a WIP entity so that it participates in the manufacturing execution model.
  • DUAL — used for trivial single-row SQL constructs, such as sequence retrieval or existence checks.

Additional declared dependencies include GME_COMMON_PVT (shared OPM utilities), GME_DEBUG (instrumentation), FND_MSG_PUB (message retrieval), FND_PROFILE (profile option access), and APP_EXCEPTION (standard error handling), reflecting the typical composition of an OPM persistence layer.

Usage Notes

GME_BATCH_HEADER_DBL is an internal component and is not documented as being referenced by any database object directly; rather, it is itself a dependency of 34 packages. It is normally invoked indirectly through higher-level OPM batch APIs, process execution logic, and OPM forms, rather than being called by custom code. Custom extensions should prefer the supported public batch APIs and treat this package as an implementation artifact; direct calls risk bypassing validation performed in the business layer. Because it is delivered as a standard APPS object, it should not be modified or recompiled with custom logic, as patches and upgrades may overwrite it. When troubleshooting batch creation, update, or locking anomalies in 12.1.1 or 12.2.2, this package is a relevant point to enable GME_DEBUG tracing and to inspect for concurrent access conflicts.