Troubleshooting
Problem
Attempts to run Schedule Order agent raises events for the order which is already scheduled by scheduleOrder API in IBM Sterling Order Management.
Symptom
Schedule transaction has event configured (for example ON_SUCCESS). Now Schedule Order agent is running on background. However an order is created and scheduled from application console/API call. During which scheduleOrder.ON_SUCCESS event is raised. Now when schedule agent process this order then the same event is raised again.
Cause
This is working as designed.
Resolving The Problem
Entries in the yfs_task_q table are created for task q based agents. Corresponding agent will pick up records from this table and perform the applicable functionality on the record. These agents will also have corresponding API, which can perform same functionality. However, API does not work through yfs_task_q table, API input will have all the required information. API will also not delete or update records present in yfs_task_q table.
In case, Order is processed by API call then the corresponding entry in yfs_task_q table will not get processed/updated during API call. And when the agent is run it will pick up this yfs_task_q table and delete/update it as no processing is required. It should be noted that internal Transaction processing will not happen but the events configured will be invoked during agent run as well.
For example:
Order is getting scheduled from API, so entry in yfs_task_q remains. These entries will be picked up by scheduleOrder agent and it will delete them. Sourcing/scheduling logic will not be invoked but events(if configured), like ON_SUCCESS will be invoked.
Was this topic helpful?
Document Information
Modified date:
16 June 2018
UID
swg22011580