Search Results is_wms_installed

Overview

GMO_VBATCH_TASK_PVT is an Oracle EBS Process Manufacturing (formerly Oracle Manufacturing Execution System / OPM) private PL/SQL package owned by the APPS schema. It is classified as a PVT (private) API, meaning it is intended for internal invocation by other EBS components rather than as a supported public integration interface. The package encapsulates the server-side logic that drives batch task execution within the Process Execution / Manufacturing Execution System (MES) workbench. Its responsibilities span resource transaction maintenance, batch save operations, material transaction and reservation handling, dispense configuration, and unit-of-measure conversion for batch steps. In effect, it provides the programmatic backbone that forms and concurrent programs call when an operator or background process records work performed against a batch.

Key Procedures and Functions

The documented interface comprises 26 procedures and functions. The x_message_data parameter the user searched for appears repeatedly as an OUT NOCOPY VARCHAR2 argument, paired with x_return_status and x_message_count, and is used to return diagnostic or message text to the calling layer.

• IS_WMS_INSTALLED — Function returning a flag indicating whether Warehouse Management System functionality is installed, allowing the package to branch on WMS availability.
• UPDATE_PROCESS_PARAMETER — Updates process parameter records for a given batch, step, activity, and parameter, accepting and returning parameter value tables and reporting status through x_message_data.
• SETUP_RESOURCE_TRANSACTION — Initializes the context required before resource transaction processing for a given organization and batch.
• CREATE_RESOURCE_TRANSACTION / UPDATE_RESOURCE_TRANSACTION / DELETE_RESOURCE_TRANSACTION — Perform the corresponding create, update, and delete operations on resource transaction records, each returning status, message count, and message data.
• SAVE_BATCH — Persists pending batch changes, driven by a table-type input and reporting outcome via the standard status/message outputs.
• GET_RESOURCE_TXN_END_DATE / GET_RESOURCE_TXN_USAGE — Derive the end date and usage quantity for a resource transaction from start date, usage, and transaction UOM inputs.
• CONVERT_UM — Performs unit-of-measure conversion for quantities.
• QTY_WITHIN_DEVIATION — Evaluates whether a quantity falls within an allowed deviation tolerance.
• GET_MATERIAL_TRANSACTIONS / GET_MATERIAL_RESERVATIONS / GET_MATERIAL_PPLOTS / GET_LOT_TRANSACTIONS — Retrieve material transaction, reservation, pending-plot, and lot transaction information for batch processing.
• GET_DISPENSE_UM — Returns the dispense unit of measure based on dispense configuration.
• RELIEVE_RESERVATION / RELIEVE_PENDING_LOT — Release reservations and pending lots once material is consumed.
• CREATE_MATERIAL_TRANSACTION / UPDATE_MATERIAL_TRANSACTION — Create and update material transaction records for the batch.

Tables Accessed

The package reads and writes the following documented tables via APPS synonyms. GME_BATCH_HEADER, GME_BATCH_STEPS, and GME_BATCH_STEP_RESOURCES store the batch definition, step, and step-resource structures central to task execution. GME_PROCESS_PARAMETERS holds process parameter values managed by UPDATE_PROCESS_PARAMETER. GME_RESOURCE_TXNS_GTMP is a global temporary table used to stage resource transaction data during validation and save. GMO_DISPENSE_CONFIG supplies dispense configuration used by GET_DISPENSE_UM. MTL_LOT_NUMBERS, MTL_TRANSACTIONS_INTERFACE, and MTL_TRANSACTION_LOTS_INTERFACE support lot handling and the movement of material transactions into the Oracle Inventory interface for processing. PLITBLM is an OPM/PLI table referenced during batch-related processing.

Usage Notes

Because GMO_VBATCH_TASK_PVT is a private package, it is not intended for direct customer invocation. It is typically called by the Process Execution workbench forms and their underlying libraries, and by concurrent programs that process batch tasks, resource transactions, and material movements. The recurring x_return_status, x_message_count, and x_message_data output trio follows the Oracle Application Object Library error-handling convention, where x_return_status indicates success, unexpected error, or expected error, and x_message_data carries the associated message. The ETRM metadata records that the package is referenced by zero other packages, confirming its role as a leaf-level implementation package. Custom code should not call this package directly; supported integration should instead use public OPM and MES APIs, since private package signatures may change between releases such as 12.1.1 and 12.2.2.