EEX 9.2: Deleting Duplicate Expense Report in Online Classic Page Does Not Purge the Related Rows From Record PS_EX_SHEET_DUP (Doc ID 3015510.1)

Last updated on APRIL 09, 2024

Applies to:

Symptoms

A problem has been detected with the Expense Report Line Duplicate checking functionality, where the validations do not seem to be triggered again once one of the flagged duplicate Expense Reports is deleted in Online Classic page. This is leaving orphan rows in Record PS_EX_SHEET_DUP for the deleted transaction, while affecting the remainder, as they keep being flagged for Duplicate Exist exceptions when performing Workflow Approvals, both in Online Classic as well as Fluid.

This is similar to the already similar scenario raised via <Bug 34409527> - (EX: EXPENSE REPORT DUPLICATE LINE FLAG NOT REMOVED EVEN AFTER SIMILAR EXPENSE REPORT IS DELETED), whose solution was delivered within PeopleSoft Enterprise FIN 9.2 PUM Image #46, addressing the problem when the Expense Report is deleted in Fluid pages.

REPLICATION STEPS:

    1.- Log into the FSCM Online Application as a System Administrator (User ID VP1)
    2.- Navigate to: Set Up Financials/Supply Chain > Install > Installation Options > Expenses
    3.- At the Expenses Installation Options level, select the 'Duplicate Review Required' check-box
    4.- Navigate to: Set Up Financials/Supply Chain > Common Definitions > User Preferences > Define User Preference
    5.- Open User ID EXA1
    6.- Go to the Overall Preferences tab, and define the below values:
           - Business Unit = US001
           - SetID = SHARE
    7.- Navigate to: PeopleTools > Security > User Profiles > User Profiles
    8.- Open User ID EXA1, and go to the ID tab, to link it to Employee ID KU0021
    9.- Navigate to: Travel and Expenses > Manage Expenses Security > Authorize Expense Users
    10.- Open Employee ID KU0021, and define User ID EXA1 with Authorization Level of 'Edit & Submit'
    11.- Navigate to: Set Up Financials/Supply Chain > Common Definitions > Codes and Auto Numbering > Create Reason Code
    12.- Under Set ID SHARE, confirm there is already a Reason Code with Reason Type 'Expense Duplicate Line', and if none exists, create one
    13.- Navigate to: Set Up Financials/Supply Chain > Product Related > Expenses > Management > Approval Setup > Map Approval Trans Definition
    14.- Open the configuration for Expense Reports, and ensure to activate the HR Supervisor approval level
    15.- Navigate to: PeopleTools > Security > User Profiles > User Profiles
    16.- Open User ID EXS1, and make the below configuration changes:
           - At the ID tab, link it to Employee ID KU0005 (Expenses HR Supervisor for Employee iD KU0021)
           - At the Roles tab, define delivered Role 'Approvals Fluid'
    17.- Log into the FSCM Online Application as an Expenses User (User ID EXA1)
    18.- Go to the Employee Self Service Fluid Homepage
    19.- Click on the Expenses Tile
    20.- Click on Create Expense Report Tile
    21.- Define the values on the Expense Report Header, (Business Purpose, Description, and Default Location), and select the Expense Report Action of 'Add Expense Lines'
    22.- Proceed to create one Expense Report Line with the below values:
           - Expense Date = November 15th 2023
           - Expense Type = Supplies
           - Description = Expenses Test 1
           - Payment Method = Cash
           - Expense Amount = 15 USD
           - Billing Type = Internal
    23.- Save the changes
    24.- Submit the Expense Report for approval, and confirm it got routed to HR Supervisor (Employee ID KU0005)
    25.- Go back to the Employee Self Service Fluid Homepage
    26.- Click on the Expenses Tile
    27.- Click on Create Expense Report Tile
    28.- Define the values on the Expense Report Header for a second transaction, (Business Purpose, Description, and Default Location), and select the Expense Report Action of 'Add Expense Lines'
    29.- Proceed to create an Expense Report Line with the exact same values as the previous transaction:
           - Expense Date = November 15th 2023
           - Expense Type = Supplies
           - Description = Expenses Test 2
           - Payment Method = Cash
           - Expense Amount = 15 USD
           - Billing Type = Internal
    30.- Save the changes
    31.- Confirm that the system has displayed the 'Expense Entry Errors' section stating there are duplicate expenses
    32.- Click on the 'Review Duplicate Lines' button
    33.- Mark the identified transaction line as Reviewed, and define a Reason
    34.- Save the Expense Report again, and do not submit this transaction
    35.- Query Record PS_EX_SHEET_DUP, and confirm that it has been populated with two rows, one for each of the Expense Report transactions created (one in Submitted For Approval, the other in Pending)
    36.- Navigate to: Employee Self-Service > Employee Travel and Exp Center > Expense Reports > Delete
    37.- Now, at the Online Classic Delete Expense Report page, find the Transaction in Pending status, select it, and click on DELETE button
    38.- Confirm that the selected Expense Report has been successfully deleted
    39.- PROBLEM: Query Record PS_EX_SHEET_DUP once again, and confirm that it still has the 2 rows from the affected Expense Report transactions
    40.- Log into the FSCM Online Application as the Expense Approver (User ID EXS1)
    41.- Click on the Approvals Tile, and select the submitted Expense Report
    42.- At the Expense Report main page within Fluid Approvals, click on the 'Exceptions and Risks' link
    43.- PROBLEM: The system still is displaying the Duplicates Exist exception, flagging the original transaction, while its duplicate has already been deleted
    44.- PROBLEM: The same problem happens when accessing the submitted Expense Report in Online Classic Approvals page, where the Exception comments is displayed in full

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 problem.

EXCEPTION COMMENTS:

Expense Approvers get confused while reviewing submitted Expense Reports, because they are still flagged as duplicates, while the identified potential transaction no longer exists. This delays approvals, and the timely reimbursement to Employees and/or Credit Suppliers.

Deleting the Expense Report in Online Classic page (Panel TE_DEL_SHEET) should clear any of its related rows in PS_EX_SHEET_DUP Record, so any other flagged transactions get cleared from this Duplicates Exist exceptions when they no longer are.

Changes

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.