Search Results gmp_batch_wrapper_pkg




Overview
Explore in AI Chat

Overview

GMP_BATCH_WRAPPER_PKG is a PL/SQL package owned by the APPS schema in Oracle E-Business Suite, validated as VALID and classified under ETRM as an "OTHER" API type. It belongs to the Oracle Process Manufacturing (OPM) product family, as evidenced by its GMP_ prefix and its association with the GME_BATCH_HEADER table, which stores batch master records for process manufacturing. The package functions as a wrapper layer that encapsulates the logic required to create batch records, shielding calling modules from the underlying complexity of batch header creation and the interactions with OPM's common private APIs.

In the 12.1.1 and 12.2.2 releases, the package serves as an integration point between higher-level OPM scheduling or planning logic and the core batch data model. Its dependency on GME_COMMON_PVT and FND_API indicates that it leverages Oracle's standard API error-handling and message conventions, returning structured API status codes rather than raw exceptions. This design allows callers to invoke batch creation programmatically and interpret results consistently with other EBS APIs.

Key Procedures and Functions

The documented interface exposes a single procedure, CREATE_BATCH. Its purpose is to create a batch record in the OPM batch header table, providing a programmatic alternative to entering a batch manually in the OPM batch maintenance forms. Because the ETRM metadata does not publish parameter lists, the precise argument signature should be confirmed by inspecting the package specification in the database. Conceptually, CREATE_BATCH accepts the attributes required to define a new batch, validates them against OPM business rules, and persists the resulting batch header. It also returns API-style status and message information to the caller, consistent with the FND_API dependency, enabling the calling program to determine success or failure and to surface error text to the user or log.

Tables Accessed

  • GME_BATCH_HEADER — The primary table affected by the package. CREATE_BATCH inserts a new batch header row here, establishing the batch identity used by downstream OPM transactions such as batch steps, material issues, and batch closeout. The package reads and writes this table through its APPS synonym.

The ETRM metadata lists GME_BATCH_HEADER as the sole documented table reference accessed via APPS synonyms. Additional supporting logic is handled through the GME_COMMON_PVT and FND_API packages rather than through direct table access, which centralizes common validation and messaging behavior and reduces direct dependencies on lower-level tables.

Usage Notes

GMP_BATCH_WRAPPER_PKG is typically invoked from server-side PL/SQL rather than from a form. The ETRM dependency report shows that it is referenced by INV_MINMAX_PVT, indicating that min-max planning logic can trigger batch creation, for example when replenishment activity requires a corresponding manufacturing or process batch. This makes the package relevant when investigating why batches appear without direct user entry, particularly in flows that link inventory replenishment to process manufacturing.

Custom code and extensions that need to create OPM batches programmatically should call CREATE_BATCH in preference to direct inserts into GME_BATCH_HEADER, because the wrapper applies the validation and error-handling conventions expected by OPM. Callers should check the returned API status and message before proceeding to subsequent batch steps. Because the package depends on FND_API and GME_COMMON_PVT, its behavior follows standard OPM initialization and validation rules. As with any seeded EBS API, developers should confirm the current specification and never modify the package directly; use supported extension mechanisms instead. When troubleshooting, verify the package status is VALID and that dependent packages such as GME_COMMON_PVT and FND_API are also valid in the target environment.