Search Results check_event

Overview

GME_BATCH_WKFL_PKG (APPS schema, AUTHID CURRENT_USER) is a Workflow integration package that supports Oracle Process Manufacturing (OPM/GME) to Oracle Order Management (OM) integration, specifically the reservation of batch-linked sales order demand. The package header identifies its purpose as containing "Workflow procedures for GME-OM Integration reservation." It is registered in Oracle E-Business Suite 12.1.1 and 12.2.2 with an API classification of OTHER, meaning it is not published as a general-purpose public API but is instead an internal component invoked by the Workflow engine and integration code. The package was created 10-Oct-2003 by nchekuri, and the version header (GMEBTWFS.pls 120.0) reflects the 11i/12.x code line. Because it is an internal Workflow support package, it is documented as being referenced by zero other packages, indicating it is an entry point rather than a shared library.

Key Procedures and Functions

The package exposes two documented procedures:

• INIT_WF — Initializes a GME-OM integration workflow process for a specific batch and sales order context. Its parameter list carries the Workflow item type and item key, an approver, sales order header and line identifiers, batch and batch line identifiers, a flow/process order identifier, an organization identifier, an optional lot number, and an action code. In practice this procedure seeds the Workflow activity with the OPM batch and OM order keys required for the downstream reservation and approval activities.
• CHECK_EVENT — The procedure most relevant to the search term "check_event." It is a standard Oracle Workflow PL/SQL callback/selector procedure, accepting the Workflow item type, item key, activity ID, function mode, and returning a result string via a NOCOPY OUT parameter. CHECK_EVENT evaluates the business state of the batch/order reservation at the point the Workflow engine invokes it, returning a result value that the engine uses to branch — for example, to determine whether the batch is ready to reserve against the sales order or whether the workflow must wait or take an exception path.

Tables Accessed

Documented table references confirm the package's bridging role between OPM manufacturing and OM order data:

• GME_BATCH_HEADER, GME_MATERIAL_DETAILS — OPM batch master and batch material lines; supply the batch context being reserved.
• OE_ORDER_HEADERS_ALL, OE_ORDER_LINES_ALL, OE_TRANSACTION_TYPES_ALL — the sales order being reserved against, including transaction type validation.
• MTL_SYSTEM_ITEMS, MTL_PARAMETERS — inventory item master and organization parameters used to validate items and inventory organizations.
• FND_USER — resolves the approver/Workflow role identity.

Usage Notes

GME_BATCH_WKFL_PKG is invoked by Oracle Workflow rather than by end-user forms or concurrent programs directly. INIT_WF is typically called programmatically by GME-OM integration code (such as the batch-to-sales-order reservation flow launched from OPM batch or order entry) to start a workflow process instance. CHECK_EVENT is then called by the Workflow engine as a function activity, using its result to control process branching. Customizations should not modify this package; any extension should instead attach to the Workflow item type. Because it is classified as OTHER and not a public API, its signature is not guaranteed across patches, and upgrading from 12.1.1 to 12.2.2 should be preceded by review of the GMEBTWFS.pls version in the target release.