WIP Move Transaction Workers (WICTWS) Performance Issue
(Doc ID 559935.1)
Last updated on SEPTEMBER 04, 2017
Applies to:Oracle Work in Process - Version 220.127.116.11 to 18.104.22.168 [Release 11.5]
Information in this document applies to any platform.
On 11.5.10 there is inconsistent performance for WIP Move Transaction Workers (WICTWS) requests: WIP Move Transaction Manager (WICTMS) is scheduled to run every 1.5 minute. and spawns one or more WIP Move Transaction Workers (WICTWS) requests.
About 60 to 70% of the WICTWS requests show reasonable performance (completes in 30 seconds or less) but in between, a few of the WICTWS requests take too much time for completion (ranging from 60 seconds to 600 seconds). Since WICTWS is a single threaded process, only one can run at a time and because of these performance issues of WICTWS, you have a big queue of WICTWS in Pending status.
Expect consistently timely performance of the WICTWS module.
Steps To Reproduce:
The issue can be reproduced at will with the following steps:
1. Inventory Responsibility -->> Set up -->> Transactions -->> Interface Manager
2. Launch "Move transaction" Manager to run every 90 seconds after completion. This will process
pending WIP Move Transactions and submits one or more WIP Move Transaction Workers (WICTWS).
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!