Introduction
In IBM Sterling OMS, task queue transaction entries are recorded in the YFS_TASK_Q table to manage order progression through the pipeline. These entries typically generate automatically when the processing transaction triggers the next time-based transaction.
When pipeline modifications occur — such as introducing new transactions — manually adding entries to YFS_TASK_Q becomes necessary for in-flight orders. IBM Sterling OMS provides the "Synchronize Task Queue" transaction: an out-of-the-box time-triggered feature designed to populate YFS_TASK_Q with updated time-triggered transactions.
Why Synchronize Task Queue is Needed
Pipeline modifications for active orders or shipments create inconsistencies, since in-flight items follow the previous pipeline version. Implementing the Synchronize Task Queue agent ensures YFS_TASK_Q records align with the latest pipeline transactions, keeping all orders synchronized.
Five different synchers exist in IBM Sterling OMS:
- Load execution task queue syncher
- Order delivery task queue syncher
- Order fulfillment task queue syncher
- Order negotiation task queue syncher
- Quote fulfillment task queue syncher
Example Scenario
The original Sales Order pipeline flows: Created → Scheduled → Released → Included in Shipment → Shipped.
After adding an "Order Validation" transaction between Create Order and Schedule Order, in-flight orders already in Created status will lack YFS_TASK_Q entries for this new transaction. Using Synchronize Task Queue creates the missing entries for all affected orders.
Implementation Steps
- Configure the Synchronize Task Queue Agent — Set up a new agent for the Synchronize Task Queue transaction at the DEFAULT level within the Order Fulfillment process type
- Create the new pipeline transaction — Add the Order Validation transaction at DEFAULT level under Order Fulfillment process type
- Modify the pipeline — Insert Order Validation between Create Order and Schedule Order transactions
- Trigger Synchronize Task Queue — Run the agent; it creates required
YFS_TASK_Qentries for newly added transactions on all in-flight orders - Orders resume processing — The Order Validation agent processes records, updates status to "Order Validated", and the Schedule agent proceeds normally
Conclusion
The Synchronize Task Queue Agent maintains consistent task queue execution based on the latest pipeline configuration. This ensures time-triggered transactions execute accurately for all orders — including those already in flight — without any missed transitions.