My Oracle Support Banner

EEX 9.2: Review Duplicate Expense Error Does Not Clear Up Easily, As Well as the Requirement to Exception Comments Duplicate Expense Is Being Bypassed Before Submission (Doc ID 2992258.1)

Last updated on DECEMBER 13, 2023

Applies to:

PeopleSoft Enterprise FIN Expenses - Version 9.2 to 9.2 [Release 9]
Information in this document applies to any platform.


A couple of problems have been detected when using the new Duplicate Review Required enhancement request in Fluid Expense Report interface:

    1) Having two identical Transaction Lines within an Expense Report, if the Employee marks one as reviewed, and enters a Reason, the system does not seem to clear out the Error Message flag on the the selected line

    2) While the Exception Comments section still displays the Duplicate Expense button, with a No Comments red flag within, denote that it is a required field to fill in, the system allows the Employee to submit the transaction for approval, even if the justification has been left blank


    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.- Log into the FSCM Online Application as an Expenses User (User ID EXA1)
    14.- Go to the Employee Self Service Fluid Homepage
    15.- Click on the Expenses Tile
    16.- Click on Create Expense Report Tile
    17.- Define the values on the Expense Report Header, (Business Purpose, Description, and Default Location), and select the Expense Report Action of 'Add Expense Lines'
    18.- Proceed to create one first Expense Report Line #1 with the below values:
           - Expense Date = November 14th 2023
           - Expense Type = Supplies
           - Description = Test AAA
           - Payment Method = Cash
           - Expense Amount = 20 USD
           - Billing Type = Internal
    19.- Click on the + button on the left panel to Expense Report Line #2, with the exact same values:
           - Expense Date = November 14th 2023
           - Expense Type = Supplies
           - Description = Test AAA
           - Payment Method = Cash
           - Expense Amount = 20 USD
           - Billing Type = Internal
    20.- Click on SAVE button
    21.- At this stage, the system has flagged both Expense Report Lines #1 and #2 for duplicate expenses
    22.- Click on the REVIEW DUPLICATE LINES button from Expense Report Line #2
    23.- The system loads the Possible Duplicates Exist modal window, listing Expense Report Line #1
    24.- Set the REVIEWED toggle/slide bar to YES, and define the REASON as OSS-DUPL previously created
    25.- Click on DONE button
    26.- Click on SAVE button
    27.- PROBLEM #1: The system has cleared up Expense Report Line #1 instead, and remains flagging Expense Report Line #2, which cannot be corrected/resolved
    28.- Click on the HOME button to get out of the component
    29.- Once back at the Employee Self Service Fluid Homepage, click on the Expenses Tile
    30.- Click on the My Expense Reports Tile
    31.- Find the recently created Expense Report transaction, and open it for further editing
    32.- Notice how now, both Expense Report Lines, #1 and #2, have no longer been marked with the Review Duplicate Lines error message (Problem #1 seems to have been mysteriously resolved by just getting out of the component, and re-opening the transaction, which should not be the needed in order to proceed)
    33.- Confirm though that both Expense Report Line #1 and #2 still have displayed the Exception Comments section, with the Duplicate Expense button showing a 'No Comments' red flag, which would signify it is required according to PeopleBooks
    34.- Click on REVIEW AND SUBMIT button
    35.- At the Expenses Summary page, the SUBMIT button is clickable. Click it.
    36.- PROBLEM #2: The system is allowing the Employee to submit the Expense Report for approval, even though the required comments justifying the duplicate expense, complimenting the Reason defined, have been left blank

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.

In order to clear out the Review Duplicate Lines Error Message from the affected Transaction Lines, the User must leave the Component, and re-open the transaction, which is unnecessary steps. Additionally, not all required information is available for the Approvers when reviewing the transaction submitted, delaying the reimbursement of the Employee, and/or Credit Supplier.

Once the Expense Report Line has been marked as reviewed, and the Reason defined, all potential duplicate Expense Report Lines should be validated, and cleared out, while at the same time, the submission of the transaction should be prevented until all required justification comments have been manually entered by the Employee at the Exception Comments section.


NOTE: In the images/screenshots/examples mentioned and/or the attached document, user details / company name / address / email / telephone number represent a fictitious sample (based upon made up data used in the Oracle Demo Vision instance). Any similarity to actual persons, living or dead, is purely coincidental and not intended in any manner.




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

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