EEX 9.2: Able To Submit for Approval an Expense Report in Fluid Containing a Zero Line Amount, and Triggering 'Page Data Inconsistent With Database' Error Message When Trying To Correct It
(Doc ID 2986281.1)
Last updated on NOVEMBER 15, 2023
Applies to:
PeopleSoft Enterprise FIN Expenses - Version 9.2 to 9.2 [Release 9]Information in this document applies to any platform.
Symptoms
The Fluid Expense Report component is allowing the submission for approval of a zero amount transaction, without flagging it in Error, if an Employee blanks out the Expense Line Amount field to 0.00 right before clicking the Review and Submit button, and after a Save has been performed.
Upon further reviewing the transaction, the system correctly flags it in Error due to missing blank amount, although it is already in Submission In Process status. While all Expense Entry page fields are editable, if the Expense Amount is populated, the system will throw a 'Page Data Inconsistent With Database' Error Message when trying to Save or Submit.
REPLICATION STEPS:
1.- Log into the FSCM Online Application as an Expenses User
2.- Go to the Employee Self Service Fluid Homepage
3.- Click on the Expenses Tile
4.- Click on the Create Expense Report Tile
5.- Fill in the details of the Expense Report Header
6.- Select the Expense Report Action of 'Add Expense Lines'
7.- Fill in the Expense Entry page with all fields being populated, except for the Amount Field
8.- Click on the Review and Submit button
9.- At the Expense Summary page, confirm that the system has displayed the Error Message about Zero Amount, and the Submit button is grayed out
10.- Click on the Update Details button
11.- Back at the Expense Entry page, confirm that the system is displaying the Error Messages referring to a blank Amount on Expense Report Line and Distribution Accounting levels
12.- Fill in the Amount field with a value, and click on Save button
13.- Confirm that the Error Message is being cleared up
14.- At this stage, blank out the Expense Amount field once again
15.- Click on the Review and Submit button
16.- PROBLEM: The Expense Summary page is loaded, but no Error Message is displayed this time, while the Submit button is clickable
17.- Click on Submit button
18.- Click on Submit button on the confirmation message pop up
19.- The Expense Report is now in a status of 'Submission In Process'
20.- Click on the Update Details button
21.- PROBLEM: Back on the Expense Entry page, notice that all Fields are editable
22.- Click on the Review and Submit button again
23.- At the Expense Summary page, now confirm that the Error Message is displayed again
24.- Click on the View Details button
25.- Back at the Expense Entry page, confirm that the system is displaying the Error Messages referring to a blank Amount on Expense Report Line and Distribution Accounting levels
26.- Fill in the Amount field with a value, and click on either Save button, or Review and Submit button
27.- PROBLEM: The system throws an Error Message
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 problem.
ERROR MESSAGE:
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. "
Employees are able to submit for approval Expense Report transactions containing an amount of 0.00 at the Transaction Line and Accounting Distribution Line levels.
Whenever the Employee sets the Expense Report Line to an Expense Amount of 0 (blank, zero), the system should flag the Transaction Line in Error, and prevent the submission of the same through approval workflow until the inconsistency is addressed.
Changes
Cause
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
Symptoms |
Changes |
Cause |
Solution |
References |