EEX 9.2: Classic Online Expense Report Approvals No Longer Displays Expense Report ID Value on View Exception Comments and Risks Page for Potential Duplicate Lines
(Doc ID 2855806.1)
Last updated on SEPTEMBER 12, 2022
Applies to:PeopleSoft Enterprise FIN Expenses - Version 9.2 to 9.2 [Release 9]
Information in this document applies to any platform.
A difference in system behavior has been detected with Online Classic Approvals for Expense Reports, where the Potential Duplicates Exist validation is no longer providing all needed detailed information to be able to easily identify the rows that are being listed in the Exception Comments and Risks page. While the system provides the Expense Date, Expense Amount, Line Number, and the Exception Comment entered by the User while creating the transaction, the system is no longer containing the Expense Report ID where the identified Line belongs to.
1.- Log into the FSCM Online Application as a System Administrator
2.- Make sure that at the Overall User Preferences settings level, the Set ID field is populated (Navigation Path: Set Up Financials/Supply Chain > Common Definitions > User Preferences > Define User Preferences > Overall Preferences tab)
3.- At the Expenses Installation Options level, select the 'Duplicate Review Required' check-box (Navigation Path: Set Up Financials/Supply Chain > Install > Installation Options > Expenses)
4.- In the Expense Report Transaction Definition set up page, enable HR Supervisor approval level (Navigation Path: Set Up Financials/Supply Chain > Product Related > Expenses > Management > Approval Setup > Map Approval Trans Definition)
5.- Create a Risk Template for Expense Report transaction type where the 'Duplicates Exist' check-box is selected, and link it to the Approver Profile for HR Supervisor (Navigation Path: Set Up Financials/Supply Chain > Product Related > Expenses > Management > Approval Setup > Define Risk Template Details)
6.- Define a new Reason Code to be used in this test, with Reason Type of 'Expense Duplicate Line' (Navigation Path: Set Up Financials/Supply Chain > Common Definitions > Codes and Auto Numbering > Create Reason Code)
7.- Remove the delivered Approvals Fluid Role for the User acting as HR Supervisor approver, at the PeopleTools Profile level (Navigation Path: PeopleTools > Security > User Profiles > User Profiles > Roles tab)
8.- Log into the FSCM Online Application as an Expenses User
9.- Using Fluid functionality, create a new Expense Report with two identical Transaction Lines (Same Expense Type, Expense Date, and Expensed Amount), and save the changes (Navigation Path: Employee Self Service Fluid Homepage > Expenses Tile > Create Expense Report Tile)
10.- At this stage, the system will flag the 2 Transaction Lines as Duplicates, and the 'Review Duplicate Lines' message/button will be displayed
11.- Open the 'Possible Duplicates Exist' page for each of the 2 Expense Lines, and mark them as Reviewed, as well as enter the previously created Reason Code
12.- Back at the Expense Entry main page, enter a justification for the Duplicate Expense at the Exception Comment section on each of the 2 Transaction Lines
13.- Proceed with the submission for approvals of the Expense Report
14.- Confirm the Expense Report is in Submitted For Approval status, and workflow has routed the transaction to the HR Supervisor
15.- Log into the FSCM Online Application as the HR Supervisor Approver
16.- Go to the Online Classic Approval pages for Expense Reports, and open the routed transaction (Navigation Path: Manager Self Service > Manager Travel and Exp Center > Approvals > Approve Expense Transactions)
17.- Confirm that the Risk and Exception alert icon is displayed on each of the 2 Expense Report Lines
18.- ISSUE: Go to the 'View Exception Comments and Risks' page, and confirm that the Exception Information Comments for the 2 identified Transaction Lines do not contain the Expense Report ID value
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 fact that the Expense Report ID information is missing at the Online Classic Approvals View Exception Comments and Risks page, makes it the more difficult for the Approver User to identify the potential duplicate expense line, and this may delay approvals, or enable the mistake of approving the submitted transaction if proper review cannot be performed.
The Online Classic Approvals functionality should once again include Expense Report ID information within the Comments field of the View Exception Comments and Risks page for those identified potential duplicate expenses.
This seems to be taking place after applying the Enhancement Request delivered via <Bug 32805464> - (ENH PSFTEXP-1054 ENHANCE MULTIPLE DUPLICATE TRACKING EXCEPTIONS - MAIN) on PeopleSoft Enterprise FSCM 9.2 Image #41,
Prior to FSCM 9.2 Image #41, the Exception Comments and Risks page would display the below detailed message:
" Expense Line is a duplicate of Line #XX, Sheet ID XXXXXXXXXX. Date YYYY-MM-DD, and Amount Spent XXX USD. "
Starting with PeopleSoft Enterprise FSCM 9.2 Image #41, the Exception Comments and Risks page would display the below message instead:
" Employee entered Exception Comments for duplicates. Date YYYY-MM-DD, and Amount Spent XXX USD. "
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