EAR 9.2: Collections Workbench Issues A Data Inconsistency Error Message (18,1) When Adding Conversations On Existing Customer Items
(Doc ID 2407829.1)
Last updated on FEBRUARY 03, 2019
Applies to:PeopleSoft Enterprise FIN Receivables - Version 9.2 to 9.2 [Release 9]
Information in this document applies to any platform.
A problem has been detected when Functional Users try to add new Item Conversations via the Collections Workbench. Upon trying to save the newly entered conversation into an existing Item transaction, the system is issuing an Error Message stating that there is a data inconsistency problem.
1.- Log into the FSCM Online Application as Receivables User
2.- Navigate to: Accounts Receivable > Collections Workbench
3.- Set the below search criteria values:
a) Set ID = SHARE
b) Unit = US001
c) Customer = 1001
4.- Click on the SEARCH button
5.- From the displayed list of available transactions, click on the Item ID link of one of them
6.- The system displays the Item Maintenance page, where the 'Add Conversations' link should be clicked
7.- Enter a new value in the Description field, as well as within the Comments box under the Conversation Entries section
8.- Click on the OK button
9.- Back on the Item Maintenance page, click once again on the OK button
10.- The system throws an Error Message due to data inconsistency
" Page data is inconsistent with database. (18,1)
When trying to save your page data, the system found that the information currently in the database did not match what was expected.
This problem can happen if another user has changed the same information while you were making your changes. Note the changes you have made, then cancel the page. Reload the page and view any changes made by the other user. Ensure your changes are compatible and retry, if appropriate.
If the problem persists, it may be a result of an application or other programming error and should be reported to technical support staff.
Possible application errors that can cause this message include:
- changing page data from SavePostChange PeopleCode, without making a corresponding change to the database.
- changing the database via SqlExec at various points, for data that is also in the component buffers.
- database auto-update fields maintained by triggers didn't get defined correctly in Record Field definition or in Record Properties definition. "
The Receivables Users are unable to successfully post a new conversation on an existing Item via the Collections Workbench functionality.
Whenever a new Conversation is added at the Item level through the Collections Workbench, the system should be able to store the new information into the proper transaction tables, and not issue any Error Messages.
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