Search Results gme_api_main




Overview
Explore in AI Chat

Overview

GME_API_MAIN is a public PL/SQL package in the APPS schema that provides the core transaction API for Oracle Process Manufacturing (OPM) batch processing. It serves as the primary programmatic interface through which batches, steps, and material lines are created, modified, and progressed through the production lifecycle within Oracle E-Business Suite 12.1.1 and 12.2.2. Business logic that would otherwise be embedded in individual forms or concurrent programs is centralized here, ensuring that batch-specific validation, reservation handling, and yield calculations are applied consistently regardless of the calling channel. The package derives its stability and scope from its dependencies on GME_BATCH_HEADER, GME_BATCH_STEPS, and GME_MATERIAL_DETAILS, which represent the persistent batch state.

Key Procedures and Functions

The documented interface exposes 37 procedures and functions, classified as OTHER in ETRM. The principal groups are as follows:

No parameter lists are documented in the ETRM extract; callers should consult the package specification for exact signatures.

Tables Accessed

The package operates against GME_BATCH_HEADER (batch identity and status), GME_BATCH_STEPS (routing step execution), GME_MATERIAL_DETAILS (batch material lines and quantities), and GME_PENDING_PRODUCT_LOTS (product lots awaiting completion). It also reads MTL_SYSTEM_ITEMS_KFV for item validation and PLITBLM for reservation-related processing. All access is performed through APPS synonyms, and the package additionally depends on FND_API for its standard messaging and exception interfaces, as well as GME_COMMON_PVT for shared OPM utilities.

Usage Notes

GME_API_MAIN is typically invoked indirectly. The dependency metadata shows it is referenced by GME_API_PUB and GME_MOBILE_TXN, meaning the public business API layer and the mobile transaction interface call into it rather than calling the main package directly. In standard process manufacturing flows, it is executed from batch maintenance and material transaction forms, from the batch release and close concurrent programs, and from custom code only where the public wrapper does not expose the required operation. Because it is classified as VALID in both releases and is re-entrant through the FND_API message stack, callers should initialize the API context and inspect the returned message list before committing. Direct invocation is generally reserved for extensions that must alter batch state atomically, and any such use should be regression-tested against patch levels for 12.1.1 and 12.2.2.