My Oracle Support Banner

EAM: The Transaction Reversal Page Displays Error “Data Being Added Conflicts With Existing Data. (18,2)” While Saving if There Are Two or More Comments Added to the Reversal Transaction. (Doc ID 2971951.1)

Last updated on SEPTEMBER 03, 2023

Applies to:

PeopleSoft Enterprise FIN Asset Management - Version 9.2 to 9.2 [Release 9]
Information in this document applies to any platform.


 The below error message is displayed on the Transaction Reversal page upon saving if there are two or more comments added to the reversal transaction.

"Data being added conflicts with existing data. (18,2)

When adding a new item to the database, the system found a conflicting item already exists.

This problem can happen if another user has entered similar information at the same time as you. Note the changes you have made, cancel the page, then retry your changes.

If the problem persists, it may be because of an application or other programming error and should be reported to technical support staff.

This error occurs when the keys on the record being inserted match a record that is already in the database. The application must ensure that each inserted record has unique keys."

*The error message is presented as a pop-up message

The issue can be reproduced at will with the following steps:

1. Create a Generic Asset(1) and Calculate the Depreciation(2)
Navigation(1): Asset Management > Asset Transactions > Owned Assets > Express Add
Navigation(2): Asset Management > Depreciation > Processing > Calculate Depreciation
2. Perform a reversible transaction (Transfer the cost to a different chartfield)
Navigation: Asset Management > Asset Transactions > Financial Transactions > Cost Adjust/Transfer Asset
3. Calculate the Depreciation
Navigation: Asset Management > Depreciation > Processing > Calculate Depreciation
4. Open the Transaction Reversal Page and search for the Asset in question
Navigation: Asset Management > Asset Transactions > Financial Transactions > Transaction Reversal
5. Add two or more comments using the + (Plus) sign and hit the OK button
6. Attempt to save the transaction
Note that the error message is shown as soon as the Save button is pressed

Detailed DEMO Replication Steps Attached


 The reported issue occured after applying several fixes from FSCM 9.2 PUM Image 33, 34, and 36.


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

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.