EEX 9.2: Page Data Is Inconsistent Error Message When Deleting My Wallet Expense Line With Attachments in Fluid Expense Report
(Doc ID 2740448.1)
Last updated on DECEMBER 28, 2020
Applies to:PeopleSoft Enterprise FIN Expenses - Version 9.2 to 9.2 [Release 9]
Information in this document applies to any platform.
A 'Page Data Is Inconsistent With Database' Error Message is being triggered when trying to delete an Expense Report Line defaulted from My Wallet, and containing multiple uploaded attachments, when using the Fluid Expense Report component. The Attachments need to be uploaded from various locations: One at least from within Fluid My Wallet, and the other within Fluid Expense Report.
The Expense Report needs to have other My Wallet transactions, as well as a Credit Expense Line in order to replicate the problem.
1.- Log into the FSCM Online Application as an Expenses User
2.- Go to Fluid My Wallet functionality, and add several new transactions with Payment Type of Credit Card
3.- For one of the My Wallet transaction, upload a new attachment file
4.- Export this one My Wallet transaction with an attachment into a new Fluid Expense Report
5.- Once in Fluid Expense Report, upload a second attachment file into the defaulted My Wallet transaction
6.- Proceed to import the remaining 2 additional Credit Card transactions from My Wallet
7.- Continue by manually adding a new Expense Line, with a negative amount, and define a Credit Reference Comment
8.- At this stage, select the defaulted My Wallet expense line with the 2 attachments, and click on the Delete button
9.- On the pop-up message, select Yes button
10.- The system triggers an Error Message
" Page data is inconsistent with database.
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. "
To gather more information concerning this scenario and its related problem, refer to the available Replication Steps PDF Document here linked containing the complete configuration and the replication steps necessary to reproduce the issue.
The Employees are unable to successfully save the Expense Report changes, and as such, they will loose all the information/data entered/modified, and will have to start from scratch.
The system should be able to successfully delete the selected Credit Card Transaction, and release it back into My Wallet feature.
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