Transaction Is Been Saved With Duplicate Transaction Number
(Doc ID 2284995.1)
Last updated on MAY 26, 2020
Applies to:Oracle Receivables - Version 12.2.4 and later
Information in this document applies to any platform.
Document Number Generation is set System Options to "When Saved".
If there are 2 users trying to create the same transaction at the same time, the application let save both transaction, resulting in duplicate transaction number.
Customer will not be able to complete the transaction because an error message shows saying that a transaction number already exist (APP-AR-11450).
They cannot delete transaction because they don't have 'Allow Transaction Deletion' checked as per company policy, so a data fix has to be provided every time that this happens.
Currently the validation for unique transaction is done when you insert the transaction number, and at the moment when the transaction is completed.
Customer also needs the validation done when the transaction is Saved.
Steps To Reproduce:
- Have user A start creating a transaction number XXXX
- Have user B start creating a transaction number XXXX
- User A save the transaction XXXX
- User B save the transaction XXXX
- Duplicate transactions are created.
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
|Still Have Questions?|