Duplicate WIP Move Transactions Performed In The Discrete Workstation Created Duplicate BackFlush Transactions
(Doc ID 2913585.1)
Last updated on DECEMBER 12, 2022
Applies to:Oracle Work in Process - Version 12.2.6 to 12.2.10 [Release 12.2]
Information in this document applies to any platform.
Duplicate WIP transactions via the Discrete Workstation create Duplicate BackFlush Transactions
Users use the Discrete Workstation to record move transactions on Discrete Jobs.
But 2 users can be working on the same job at the same time and the move transaction can be recorded twice for the same job and the the same from/op operations.
When it happens, the backflushed components are issued twice. There is no warning or error message to avoid this scenario.
There should be no duplicate WIP transactions created via the Discrete Workstation even when concurrent users are simultaneously submitting move transactions against the same job/operation.
The issue can be reproduced at will with the following steps:
1. Responsibility: Work In Process.
2. Go to Discrete Workstation.
3. User A is working on job 2084997 operation 40.
4. User B can select the same job and the same operation on his session (without any warning message).
5. User A moves the wip quantity to the next operation (Complete Operation).
6. User B can moves the wip quantity for the same operation and the same job (Complete Operation). There is no error message to tell him this quantity was already moved.
7. We see in the Move Transaction View that the Move transaction is duplicated.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document