Search Results insert_gml_batch_so_workflow

Overview

GML_BATCH_WORKFLOW_PKG is an Oracle E-Business Suite PL/SQL package owned by the APPS schema and classified under the generic OTHER API category. Its stated purpose is to contain the Workflow procedures supporting the GME-to-Order Management (GME-OM) integration for batch reservations. In process manufacturing environments, finished goods are produced as batches rather than discrete assemblies, and the reserved quantity of a sales order line must be tied to a specific batch and lot. This package provides the orchestration layer that raises and drives an Oracle Workflow process (item type GMLBTRES, process GMLBTRES_PROCESS) so that batch-to-sales-order reservation activity is routed to an approver and recorded for downstream consumption.

The header comment block identifies the file as GMLBTWFB.pls (version 120.0, last updated 25-May-2005), created on 10-Oct-2003. The core design pattern is that a caller supplies the reservation context — session identifier, approver, sales order header and line, batch and batch line, warehouse, lot, and an action code — and the package constructs a unique workflow item key from the session identifier and the current timestamp before launching the workflow in the background by setting the engine threshold to -1 (WF_ENGINE.THRESHOLD).

Key Procedures and Functions

Three procedures are documented in the ETRM metadata for this package.

• INIT_WF — The entry point for initiating the batch reservation workflow. It accepts the reservation identifiers (session, approver, sales order header/line, batch, batch line, warehouse, lot, and action code), derives display values such as order number, line number, item number, order type, batch number, plant code, and planned completion date, resolves the approver's user name, then submits the GMLBTRES workflow process using the generated item key. Internal cursors such as Get_user_name and Get_order_info support this enrichment; the searched term "get_order_info" refers to the cursor that joins OE_ORDER_HEADERS_ALL, OE_ORDER_LINES_ALL, OE_TRANSACTION_TYPES_ALL, and MTL_SYSTEM_ITEMS to retrieve line number, item segment, transaction type code, and order number.
• CHECK_EVENT — Evaluates the workflow event condition associated with the reservation, allowing the process to branch or terminate based on the applicable business rule.
• INSERT_GML_BATCH_SO_WORKFLOW — Inserts the batch-to-sales-order workflow record, persisting the reservation linkage that the workflow and subsequent processing rely upon.

Tables Accessed

The package operates across both Oracle Process Manufacturing and Oracle Order Management schemas, accessed through APPS synonyms.

• OE_ORDER_HEADERS_ALL and OE_ORDER_LINES_ALL — Source of sales order header and line details, including order number and line number.
• OE_TRANSACTION_TYPES_ALL — Supplies the transaction type code used to classify the order.
• MTL_SYSTEM_ITEMS — Provides the item identifier (segment1) for the reserved product.
• FND_USER — Resolves the approver user identifier to a user name for notification purposes.
• GML_BATCH_SO_WORKFLOW and GML_BATCH_SO_WORKFLOW_S — The base table and its sequence (or secondary) object used to store the batch-to-sales-order workflow linkage.
• GME_BATCH_HEADER — Batch-level information supporting the reservation context.
• DUAL — Used for singleton evaluations within the procedural logic.

Usage Notes

In Oracle EBS 12.1.1 and 12.2.2, this package is invoked indirectly rather than through a standard concurrent program submission. It is triggered by the GME-OM integration flow when a batch reservation requires workflow-driven approval or notification — typically originating from process manufacturing batch reservation forms or from order management reservation logic that calls into the GML batch reservation path. Because INIT_WF launches the workflow with a background threshold, the submission returns promptly while the workflow engine processes the approval asynchronously. The package is referenced by one other package in the ETRM inventory, confirming that it is a dependency of a higher-level integration unit rather than a self-contained entry point. Customizations and extensions that need to raise the batch reservation workflow directly should replicate the full INIT_WF parameter context, since the workflow item key and all notification attributes are derived from those inputs; omitting the action code or lot number may cause CHECK_EVENT to suppress processing. As the underlying file has been stable since 2005, the package behavior is consistent across both 12.1.1 and 12.2.2 releases.