Troubleshooting
Problem
Error 'WMS00144 - Summary Task is not the latest summary task' seen from acceptVariance API even when task ID passed in the input xml is the latest summary task
Environment
Consider a scenario where user manually completes the count and then feeds the information into Sterling Warehouse Management System. To be able to feed this data into the system, customer creates a Custom API which creates count task, completes them and creates variances tasks within the same flow
In such a scenario, in case the count task completing takes less than a milisecond to complete, it is possible that the Count summary task and the Variance summary task are created exactly at the same time (within the same milisecond)
Sample input xml for acceptVariance API :
<CountRequest AcceptAllVariances="Y"
CountRequestKey="<count req key>" IgnoreOrdering="Y"
Node="<node>" ReasonCode="<reason_code>"
ReasonText="" SummaryTaskId="<summary_task_id>"/>
Diagnosing The Problem
The query run by our system(in acceptVariance API) to get the latest summary task is :
SELECT YFS_TASK.* FROM YFS_TASK YFS_TASK WHERE COUNT_REQUEST_KEY = '<count req key>' AND IS_SUMMARY_TASK = 'Y' ORDER BY CREATETS DESC
The first row of the result is considered as the latest summary task
Since the above query is based on create time stamp and in this scenario the Createts of both count and variance task are the same, the system may recognize an incorrect task as the summary task and result in error 'WMS00144 - Summary Task is not the latest summary task' when acceptVariance API is run with task ID which is infact the latest
Resolving The Problem
1) Introduce a delay of a milisecond between creating count tasks and creating variance tasks so the Database Query correctly identifies the latest summary task
2) Use paper based counting solution provided by our product
Was this topic helpful?
Document Information
Modified date:
16 June 2018
UID
swg21977648