System is Creating Duplicate Approval Transaction Ids
(Doc ID 2355920.1)
Last updated on FEBRUARY 07, 2018
Applies to:Oracle Financial Services Revenue Management and Billing - Version 184.108.40.206.0 and later
Information in this document applies to any platform.
Oracle Revenue Management and Billing (ORMB) v220.127.116.11.0 with Oracle Utilities Application Framework (OUAF) v18.104.22.168, instead of throwing an error, the system is creating a duplicate Approval Transaction Id.
Price assignments are automatically duplicated in the system. The users confirmed that they did not try to assign pricing twice and nothing unusual happened when they were working on it. Every account they worked on was duplicated. The issue was also reproduced in the DEV environment. The screens 'Edit PriceList Assignment', 'Edit Product', 'Add Product', and 'Add Transaction Details', generated the error message "You Cannot Edit or Delete object; another Transaction for the same object is in approval workflow". However, in the back end a new Approval Transaction ID was created by the system. The basic issue is that the system is not validating whether an APP TXN ID is already present. Additionally, if a user clicks 'Save' on the screen twice, it should provide an error message instead of providing a new approval for the same request.
System should validate and avoid creating duplicate records and show relevant error message on UI.
The issue can be reproduced at will with the following steps:
-- Rules Issue --
1. User navigates to Rule.
2. Modifies Rule.
3. Clicks Save and receive following message on UI:
"You Cannot Edit or Delete object; another Transaction for the same object is in approval workflow"
-- Pricelist Issue –
1. User navigates to account -> effective pricing.
2. Overrides pricing.
3. Click on 'Save' and the following error is displayed on the UI:
"Approval Transaction with same key pending approval."
– Pricelist Approval Transaction –
Please note that there are two transactions with the same ID.
The issue has the following business impact:
Due to this issue, users find many invalid records in the back end.
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