EEX9.2: Error Appears On Copy Existing Expense Report When Accounting Details Default View Is Set On "Expanded" Under Employee Update Profile Page
Last updated on JANUARY 04, 2017
Applies to:PeopleSoft Enterprise FIN Expenses - Version 9.2 to 9.2 [Release 9]
Information in this document applies to any platform.
An error appears when user creates new Expense Report and is copying from an existing Expense Report or Travel Authorization, while Accounting Details Default View is set on "Expanded" under employee Update Profile page
Navigate to Travel and Expenses > Manage Employee Information > Update Profile - User Defaults tab and for Accounting Detail Default View set "Expanded"
The issue can be reproduced at will with the following steps:
1. Travel and Expenses > Expense Report > Create/Modify page
2. Travel and Expenses > Expense Report > Create/Modify page and in Quick start select "An Existing Report"
While user is creating an Expense Report by copying from an existing Expense Report and is having Extented Accounting Default option in Employee Profile, below error appears:
Invalid parameter 1 for function CurrentRowNumber. (2,116) EX_UI.EmployeePrivilege.EmployeePrivilege.OnExecute Name:FormatNewDistRow PCPC:1463 Statement:40
Called from:EX_UI.TxnExpenseReport.Accounting.LineAccounting.OnExecute Name:FormatCFsRow Statement:59
Called from:EX_UI.TxnExpenseReport.Accounting.LineAccounting.OnExecute Name:FormatCFs Statement:29
Called from:EX_UI.TxnExpenseReport.Accounting.LineAccounting.OnExecute Name:DisplayPage Statement:18
Called from:EX_LINE_WRK.EXPENSE_TYPE.FieldChange Name:display_line Statement:257
The specified parameter is not correct for the function. It may be the wrong type of parameter (string, number, record.field, etc) or an invalid value in this context.
Review the program for errors. If necessary, run a PeopleCode trace to determine the program that failed. Alternatively, for functions defined within PeopleCode, check the function declaration to verify that they are correct.
To gather more information concerning this scenario and its related problem, refer to the available Replication Steps containing the complete configuration and the replication steps necessary to reproduce the issue.
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