EEX 9.2: Receiving Invalid Row Number Error Message When Adding a New Transaction Line at Fluid Expense Report Having Used the Copy Expense Report Feature
(Doc ID 2827610.1)
Last updated on DECEMBER 17, 2021
Applies to:PeopleSoft Enterprise FIN Expenses - Version 9.2 to 9.2 [Release 9]
Information in this document applies to any platform.
The system is throwing a PeopleCode Error Message when manually adding a new Expense Report Line on Fluid User Interface, on an Expense Report that has been created from a Copy From Existing Report.
1.- Navigate to: Employee Self-Service Fluid Homepage > Expenses Tile > Create Expense Report Tile
2.- Select the Down Arrow in the Business Purpose Field.
3.- Click on 'Miscellaneous' Business Purpose.
4.- Enter 'Test' in the Description field.
5.- Click the down arrow in the Expense Report Action Field and select Copy Expense Report
6.- In the Expense Report Copy Option Field, Select 'Full Expense Report'.
7.- Click on the calendar icon to the right of the From Date Field. "
8.- Keep the current month displayed, and change the year to 2 years prior and select the 1st day of the month.
9.- Click the Search button.
10.- Select one of the Expense Reports listed by clicking in the round box to the left of the listed report.
11.- Click the Copy Expense Report button.
12.- Click on the Update Details button
13.- Add a new Expense Line to the report by clicking on the Add icon on the top left of the screen, in the item summary section.
14.- Error Message is triggered
Users are unable to complete the needed changes on a copied Expense Report transaction in Fluid User Interface, and this delays data entry tasks. This in its turn can delay the reimbursements to be paid to Employees or Credit Card Suppliers.
The system should not trigger such Error Message when creating a brand new Expense Report Line on a saved Expense Report created from a copy on an existing one.
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