My Oracle Support Banner

EEX 9.2: Fluid Expense Report Review Duplicate Lines Page Displays Incorrect Expense Date and Expense Type From Modified Transaction Line Instead of True Duplicate Values (Doc ID 2958994.1)

Last updated on JULY 02, 2023

Applies to:

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

Symptoms

Having entered multiple Expense Report Line transactions with the same values on the Expense Date, Expense Type, Expense Amount, and Transaction Currency Code fields, the system correctly flags the rows as potential duplicate expenses. However, when clicking to the Transaction Line's 'Review Duplicate Expenses' button, and loading the Possible Duplicates Exist page (Panel EX_SHEET_DUP_SCF), the listed and identified Expense Report Line is displaying the incorrect Expense Date and Expense Type values.

This is taking place if the original Transaction Line has different values, but got later updated on Expense Date and Expense Type fields to match another Expense Report Line. Somehow, the Duplicates Message will reflect the old unique values, instead of contain the values that make the expense duplicate of one another.

REPLICATION STEPS:

    1.- Log into the FSCM Online Application as a System Administrator
    2.- Navigate to: Set Up Financials/Supply Chain > Install > Installation Options > Expenses
    3.- Ensure that the 'Duplicate Review Required' check-box is not selected
    4.- Log into the FSCM Online Application as an Expenses User
    5.- Go to the Employee Self Service Fluid Homepage
    6.- Click on the Expenses Tile
    7.- Click on the Create Expense Report Tile
    8.- Enter the needed values at the Expense Report Header level (Business Purpose, Description, Default Location)
    9.- Select the Expense Report Action of 'Add Expense Lines'
    10.- The system loads the Fluid Expense Entry page with almost all fields in blank
    11.- Manually add Expense Report Line #1 with the below values:
         a) Expense Date = 04/24/2023
         b) Expense Type = GROCERIES
         c) Amount = 7.00
         d) Currency Code = USD
    12.- Save the transaction
    13.- Manually add Expense Report Line #2 with the some different values on Expense Date and Expense Type fields:
         a) Expense Date = 04/23/2023
         b) Expense Type = SUPPLY
         c) Amount = 7.00
         d) Currency Code = USD
    14.- Save the changes
    15.- Proceed to modify the Expense Report Line #2 with new values for the following fields:
         a) Expense Date = 04/24/2023     (From original 04/23/2023 value date)
         b) Expense Type = GROCERIES     (From original SUPPLY value date)
    16.- Save the changes
    17.- Confirm that on both Expense Report Lines, #1 and #2, the 'Review Duplicate Lines' button is now displayed
    18.- Go to the Expense Report Line #2, and click on the 'Review Duplicate Lines' button
    19.- The system loads the Possible Duplicates Exist modal page
    20.- PROBLEM: The system lists Expense Report Line #1, but the Expense Date and Expense Type values are wrong, as they correspond to those of Expense Report Line #2 before the changes were made

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 Employees are getting confused with the current system behavior, because while the Expense Report Lines have been correctly flagged as potential duplicates, the Expense Date and Expense Type values displayed are incorrect. Comparing the values, one would easily think that the two transactions are not the same, while in fact, they are.

If the system has detected any potential duplicates, whether the 'Duplicate Review Required' new functionality is enabled, or not, at the Expenses Installation Options level, the Possible Duplicates Exist page (Panel EX_SHEET_DUP_SCF) should display the proper Expense Date and Expense Type values at all times, not the old changed ones.

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.

Changes

 

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
Changes
Cause
Solution
References


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