Search Results gml_batch_so_workflow

Overview

GML_BATCH_SO_WORKFLOW is a table owned by the GML schema (Process Manufacturing Logistics) within Oracle E-Business Suite. Its documented purpose is to support the Oracle Order Management (OM) batch reservation workflow — the orchestration mechanism by which process manufacturing batches are matched against sales order lines and then reserved. In practice, this object functions as a staging and state-tracking store for pending batch-to-order reservation requests, giving the workflow engine a persistent record of what needs to be processed and what has already been actioned.

The table is classified as standalone under the heuristic Data Vault analysis mined from its foreign key structure. In data-vault modeling terms it behaves much like a link table that associates workflow instances with order and batch entities, but because no inbound or outbound FK constraints anchor it to the core order and batch masters, it is best treated as an independent work-item queue rather than a fully integrated hub or satellite. That classification is a modeling suggestion only; the physical schema remains a conventional relational table.

Key Information Stored

The documented physical schema contains 14 columns. The most significant are summarized below.

• WF_ITEM_ID — the surrogate primary key, defined by the GML_BATCH_SO_WORKFLOW_PK unique index. It is also the only documented business-key candidate, since no other unique index is reported.
• WF_ITEM_TYPE and WF_ITEM_KEY — identify the Oracle Workflow item being processed. These columns tie each reservation request to the standard workflow runtime tables, allowing the workflow engine to correlate the record with its activity history.
• SO_HEADER_ID — the sales order header being fulfilled; the top-level order reference for the reservation.
• SO_LINE_ID — the specific order line against which the batch is to be reserved.
• BATCH_ID and BATCH_LINE_ID — the process manufacturing batch (and its line detail) nominated for reservation. These link the workflow item to the GME/GMD batch inventory model.
• ACTION_CODE — the operation the workflow should perform, used to distinguish reservation, un-reservation, or similar batch-processing actions.
• CREATION_DATE, CREATED_BY, PROGRAM_APPLICATION_ID, PROGRAM_ID, LAST_UPDATED_BY, and LAST_UPDATE_DATE — standard audit and concurrent-program context columns indicating who or what created and last touched each work item.

Common Use Cases and Queries

Typical usage centers on diagnosing stuck or failed batch reservations. Support and functional analysts query the table to find work items for a given order, batch, or date window, and reporting teams use it to measure reservation throughput and pending backlog.

SELECT wf_item_id, wf_item_type, wf_item_key,
       so_header_id, so_line_id,
       batch_id, batch_line_id, action_code,
       creation_date, last_update_date
FROM   gml.gml_batch_so_workflow
WHERE  so_header_id = :p_order_header_id;

To locate work items created but not yet actioned, filter on the creation window and compare against workflow status. To audit activity by program, group on program_id and program_application_id. Because the table is small and queue-like, heavy joins to order and batch masters are usually performed on the ID columns rather than through enforced FKs.

Related Objects

The documented relationship data identifies one inbound foreign key: AMS_TCOP_REQUESTS.WF_ITEM_ID references this table's WF_ITEM_ID, linking CRM/telemarketing campaign requests to batch reservation work items. Beyond that, the table integrates conceptually with the following objects through its documented columns:

• AMS_TCOP_REQUESTS — references GML_BATCH_SO_WORKFLOW.WF_ITEM_ID via its own WF_ITEM_ID column.
• OE_ORDER_HEADERS_ALL — joined on SO_HEADER_ID to resolve order context.
• OE_ORDER_LINES_ALL — joined on SO_LINE_ID to resolve line-level detail.
• GME_BATCH_HEADERS and GME_BATCH_LINES — joined on BATCH_ID and BATCH_LINE_ID to resolve batch identity.
• WF_ITEMS / WF_ITEM_ACTIVITY_STATUSES — correlated via WF_ITEM_TYPE and WF_ITEM_KEY to inspect workflow progress.
• Oracle Workflow APIs (WF_ENGINE) and the OM batch reservation concurrent programs that populate and consume this queue.

Together these relationships position GML_BATCH_SO_WORKFLOW as the operational bridge between order management demand and process manufacturing batch supply.