EEX 9.2: Distance Varied Rate Blanked Out In Fluid Expense Report Line If Miles Value Is Minored, Throwing Error Message
(Doc ID 2587695.1)
Last updated on SEPTEMBER 11, 2019
Applies to:PeopleSoft Enterprise FIN Expenses - Version 9.2 to 9.2 [Release 9]
Information in this document applies to any platform.
A problem has been detected at the Expense Report creation pages with Fluid User Interface (Page EX_SHEET_LN_FL), when using Expense Type of Automobile with Mileage, linked to Transportation Types. If the Miles/Kilometers previously entered value at the Expense Report Line level gets modified by an Employee at a later stage, while the Expense Report is still in Pending status, should that change mean a lower amount of Miles/Kilometers, the system triggers an Error Message, and the Transaction Amount is not calculated.
The primary issue is that with this change, the Distance Rate is blank out to 0.00, as the code fails to retrieve the proper Variable Rate. As a result, the Transaction Amount is set to 0 as well.
Modifying the amount of Miles/Kilometers to a higher value than that initially entered, seems to be working fine. The problem is when the value is lowered.
1.- Create a new Transportation Type
2.- Create a new Expense Type flagged for Transportation Type, and Automobile
3.- Define a new Distance Rate for the Expense Type, and Transportation Type combination, and define it as Varied Rate
4.- Link this Transportation Type to the Expenses Profile of an Employee
5.- Create a new Expense Report for the involved Employee, adding two lines, both using the Expense Type previously created. Use Fluid User Interface to create the transaction
6.- After adding the 2 Expense Lines, with the Miles needed, and amount calculated, save the changes
7.- Go out of the component
8.- Come back, and open again this Expense Report under Fluid pages
9.- Go to one of the Expense Report Lines, and modify the Miles value from the current one, to a lesser value
10.- Upon tabbing out of the field, the system throws an Error Message
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.
" There is no distance rate of transportation type XXX for the total accumulated distance -XX.
The total accumulated distance exceeds the highest band of varied distance rates. Please check your Distance Rate configuration. "
From this moment on, the Employee is unable to correct the Expense Report Line anymore. The Distance Rate is set to 0.00, unless the change is reverted. Users are forced to delete the whole Expense Report Line, and start from scratch, which is task intensive, and User not friendly.
If the amount of Miles/Kilometers entered as distance is modified, the system should still be able to default the proper Distance Rate (using the Varied Rate configuration), and calculate the new Transaction Amount for the line at hand.
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