Last updated on OCTOBER 28, 2016
Applies to:PeopleSoft Enterprise FIN Receivables - Version 9.2 to 9.2 [Release 9]
Information in this document applies to any platform.
Users are receiving an Error Message of " Page data is inconsistent with database. (18,1) " at the Create Accounting Entries page (PAYMENT_MISC_DST) for Direct Journal Payments, once the 'Next In List', 'Previous in List', or 'Return to Search' buttons are clicked, just after Budget Checking has been run to Success, and Budget Status of the transaction has been updated to Valid.
1.- Enable Commitment Control functionality for Accounts Receivable module
2.- Navigate to: Accounts Receivable > Payments > Online Payments > Regular Deposit
3.- Create multiple Deposit Groups, each with one Payment, marked as 'Direct Journal', for the Business Unit enabled on Commitment Control
4.- Navigate to: Accounts Receivable > Payments > Direct Journal Payments > Create Accounting Entries
5.- Perform a search on the Deposit Unit, in order to retrieve a list of at least 3 of the above created Deposit IDs
6.- Select from the displayed list, a Deposit/Payment that is in the middle of the retrieved values
7.- At the Accounting Entries tab, fill in the needed ChartFields for the User entered Accounting Line
8.- Click on the lightning bolt icon to generate the proper balancing accounting entry line
9.- Select the Complete check-box
10.- Save the changes
11.- Click on the Budget Check icon recently displayed
12.- Once Budget Check has finished, and the Budget Status of the transaction shows as Valid, click on 'Next In List' button
13.- A pop up message will appear, click on YES button
14. Click on SAVE button
15.- The Error Message is triggered
To gather more information concerning this scenario and its related problem, refer to the available Replication Steps Word Document here linked containing the complete configuration and the replication steps necessary to reproduce the issue.
" 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 Budget Checking verification at the Create Accounting Entries for Direct Journal Payments prevents the Users from saving any further changes performed.
The User should be able to save any changes performed at the Create Accounting Entries page for Direct Journal Payments.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms