Results for “gme_api_pub”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

APPS.GME_API_PUB is the public PL/SQL API package for Oracle Process Manufacturing (OPM) batch and resource transaction processing within Oracle E-Business Suite 12.1.1 and 12.2.2. The package exposes a governed interface through which batch records, phantom assemblies, process parameters, step definitions, material reservations, and actual resource consumption data are created, modified, and completed. Its header comment identifies it as GMEPAPIB.pls (version 120.62.12010000.1), confirming its lineage as a core OPM application module rather than a customer extension.

The package body is classified as PUB, meaning its procedures are intended for invocation from other Oracle EBS modules, forms, and customer code. It is referenced by nine other packages, which underscores its role as a central integration point for batch lifecycle operations. Internally it relies on standard EBS infrastructure: FND_API for return status constants, FND_MSG_PUB for exception messaging, and the GME debug utility (gme_debug) for conditional diagnostic logging controlled by the AFLOG_LEVEL profile option.

Key Procedures and Functions

The package documents 57 procedures and functions. Core batch management procedures include SAVE_BATCH (persists batch header and resource transaction data), CREATE_BATCH, CREATE_PHANTOM (generates phantom batch structures for co-products or intermediate assemblies), SCALE_BATCH (adjusts batch quantities for scale-up or scale-down), and THEORETICAL_YIELD_BATCH (computes expected yield). Lifecycle procedures RESCHEDULE_BATCH and RESCHEDULE_STEP allow adjustment of timing for batches and individual routing steps.

Resource usage procedures form the category relevant to the update_actual_rsrc_usage search term. UPDATE_ACTUAL_RSRC_USAGE updates recorded consumption of resources against a batch step. It is complemented by INSERT_INCR_ACTUAL_RSRC_TXN (incremental resource consumption transactions), INSERT_TIMED_ACTUAL_RSRC_TXN (time-based resource transactions), START_CMPLT_ACTUAL_RSRC_TXN, and END_CMPLT_ACTUAL_RSRC_TXN (start and end completion transactions). Together these procedures govern the actual-versus-theoretical resource accounting that drives OPM costing.

Parameter and step management procedures include INSERT_PROCESS_PARAMETER, UPDATE_PROCESS_PARAMETER, DELETE_PROCESS_PARAMETER, INSERT_STEP, CREATED, and DELETE_STEP, providing full CRUD control over batch routing and quality data. Reservation procedures CREATE_BATCH_RESERVATIONS and CREATE_LINE_RESERVATIONS create inventory reservations at the batch and line level respectively.

Tables Accessed

The package operates against OPM and Oracle Inventory tables accessed through APPS synonyms. Batch structures are held in GME_BATCH_HEADER, GME_BATCH_STEPS, GME_BATCH_STEP_ACTIVITIES, and GME_BATCH_STEP_RESOURCES. Material movement data is captured in GME_MATERIAL_DETAILS, MTL_MATERIAL_TRANSACTIONS, and MTL_TRANSACTIONS_INTERFACE, with lot control supported by MTL_LOT_NUMBERS and GME_PENDING_PRODUCT_LOTS. Resource consumption and usage are recorded in GME_RESOURCE_TXNS, CR_RSRC_DTL, and CR_RSRC_MST. Process parameter and operation definitions reside in GME_PROCESS_PARAMETERS and GMD_OPERATIONS_B. Reservation records are written to MTL_RESERVATIONS. The SAVE_BATCH procedure reads the GME_RESOURCE_TXNS_GTMP global temporary table to drive batch save logic.

Usage Notes

GME_API_PUB is typically invoked from the OPM Batch and Resource Transaction forms, from OPM concurrent programs such as batch save and resource transaction processing, and from custom PL/SQL code extending OPM functionality. Callers should supply the standard FND_API return status and message parameters, and inspect x_return_status for g_ret_sts_success, g_ret_sts_error, or g_ret_sts_unexp_error. Where p_commit is exposed, the caller retains control of transaction boundaries. The p_clear_qty_cache parameter on SAVE_BATCH (added under Bug 5255959 and converted from BOOLEAN to VARCHAR2 under Bug 5584699) should be passed FND_API.g_true to force recalculation of cached batch quantities. Because UPDATE_ACTUAL_RSRC_USAGE and the related resource transaction procedures affect costing and inventory valuation, they should be called only after the batch step is properly initialized and within a controlled transaction scope.