EEX 9.2: Expense Report Lines Remained Flagged As Duplicates Without Reason Even After Identified Similar Expense Report Transaction Is Deleted
(Doc ID 2895851.1)
Last updated on APRIL 08, 2024
Applies to:
PeopleSoft Enterprise FIN Expenses - Version 9.2 to 9.2 [Release 9]Information in this document applies to any platform.
Symptoms
A problem has been detected with the Expense Report Line Duplicate checking functionality, where the logic does not seem to be triggered again once one of the flagged duplicate expenses has been deleted. The system does not re-validate an already flagged Expense Report Lines upon saving any further changes, nor upon submission.
When an Expense Report that has been flagged as a potential duplicate is being deleted from the system, the transaction is physically deleted from the main Records (PS_EX_SHEET_HDR, PS_EX_SHEET_LINE, etc...), however, it leaves orphan transaction data into Record PS_EX_SHEET_DUP.
REPLICATION STEPS:
1.- Log into the FSCM Online Application as a System Administrator
2.- Navigate to: Set Up Financials/Supply Chain > Common Definitions > User Preferences > Define User P{references
3.- Open the configuration under User ID EXA1 (Expenses Employee)
4.- Go to the Overall Preferences tab, and ensure to populate the Business Unit US001, and Set ID SHARE
5.- Navigate to: Set Up Financials/Supply Chain > Install > Installation Options > Expenses
6.- Ensure to select the 'Duplicate Review Required' check-box
7.- Navigate to: Set Up Financials/Supply Chain > Common Definitions > Codes and Auto Numbering > Create Reason Code
8.- Define a new Reason Code under Set ID SHARE, and with Reason Type of 'Expense Duplicate Line'
9.- Navigate to: Travel and Expenses > Manage Employee Information > Update Employee Detail
10.- Open the Expenses Profile for Employee ID KU0021 (Linked to User ID EXA1)
11.- Go to the Organizational Data tab, and ensure that GL Unit is US001
12.- Log into the FSCM Online Application as User ID EXA1 (Expenses Employee)
13.- Go to the Employee Self Service Fluid Homepage, and click on the Expenses Tile
14.- Click on the Create Expense Report Tile
15.- Fill in all the Header details, and select the option of 'Add Expense Lines' action
16.- At the Expense Report Line level, create a couple of Transaction Lines:
a) Expense Report Line #1: Expense Date = July 20th 2022 , Expense Type = SUPPLY , Payment Method = Cash , Expense Amount = 70.00 USD
b) Expense Report Line #2: Expense Date = July 20th 2022 , Expense Type = GROCERIES , Payment Method = Cash , Expense Amount = 80.00 USD
17.- Save the Expense Report transaction, but do not submit it
18.- Go back to the Employee Self Service Fluid Homepage, and click again on the Expenses Tile
19.- Proceed to click on the Create Expense Report Tile for a second transaction
20.- Fill in all the Header details, and select the option of 'Add Expense Lines' action
21.- At the Expense Report Line level, create one Transaction Line that will match that of the first Expense Report:
a) Expense Report Line #1: Expense Date = July 20th 2022 , Expense Type = SUPPLY , Payment Method = Cash , Expense Amount = 70.00 USD
22.- Save the Expense Report transaction
23.- Confirm that the system has flagged the Expense Report Line as a potential duplicate, and the 'Review Duplicate Lines' button/message is getting displayed as per expected
24.- Query Record PS_EX_SHEET_LINE, and confirm that the 2 Expense Report transactions have the Field DUPLICATES_EXIST = 'Y' on the two identical lines
25.- Query Record PS_EX_SHEET_DUP, and confirm that it lists the 2 Expense Report transactions, on the duplicate detected lines
26.- Go back to the Employee Self Service Fluid Homepage, and click on the My Expense Reports Tile
27.- Find in the 'Not Submitted' section the first Expense Report with 2 lines, and proceed to delete it
28.- Query Record PS_EX_SHEET_LINE, and confirm that only the second Expense Report transaction is being listed now, (the first one got deleted), but the Field DUPLICATES_EXIST is still storing a value of 'Y'
29.- ISSUE: Query Record PS_EX_SHEET_DUP, and confirm that it still lists the 2 Expense Report transactions, on the duplicate detected lines. For the original Expense Report transaction, the row is now left orphan.
30.- Back at the My Expense Reports page, find the second Expense Report, and open it
31.- Confirm that the 'Review Duplicate Lines' button and message are still displayed at the Expense Entry page for the flagged transaction line
32.- Click on the 'Review Duplicate Lines' button, and see how the system displays the possible duplicate information
33.- Click on the link under the Report ID column (Expense Report ID and Line Number combination), and see how the system displays a new window, but there is no information on the transaction just clicked, as it has been deleted
34.- Proceed to click on Done or Cancel buttons
35.- Back at the Expense Entry page, click on the Save button
36.- ISSUE: The system has re-saved the transaction, but it has not triggered once again the validation of duplicates, and as such, the Duplicates Exist flag remains
37.- Perform a change at the affected Expense Report Line, such as modify the description, and save once again
38.- ISSUE: The system has re-saved the transaction once again, but it has not re-triggered the validation of duplicates, and as such, the Duplicates Exist flag remains
39.- Click on the 'Review and Submit' button
40.- ISSUE: At the Expense Summary page, the system is graying out the Submit button, so the Expense transaction cannot be submitted for approval
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.
ERROR MESSAGES:
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 |
Cause |
Solution |
References |