My Oracle Support Banner

EEX 9.2: Credit Card Transaction Defaulted Into Fluid Expense Report Becomes Disassociated From My Wallet Respective Row, Which Is Once Again Eligible for Employees To Re-Use (Doc ID 2895346.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.

Symptoms

Users are able to break the link and disassociate a My Wallet Credit Card transaction from the Expense Report it has been defaulted in, and re-use it into new Expense Reports. This takes place when the Expense Type value present in the My Wallet pages is blanked out from the transaction at hand, and then defaulted into a new Expense Report. If the Employee selects a different Expense Type value, the Fields of SHEET_ID, SHEET_NAME, LINE_NGR from Record PS_EX_TRANS get blanked out, while the Field TXN_STATUS is changed from 'A' (Assigned), to 'U' (Unassigned).

This takes place only when the Expense Type look-up feature, and its pop up window, are used to select the new value at the Fluid Expense Report Line details page level.

REPLICATION STEPS:

    1.- Log into the FSCM Online Application as an Expenses User
    2.- Navigate to: Set Up Financials/Supply Chain > Business Unit Related > Expenses > Expenses Definition
    3.- Open Business Unit US001
    4.- At the Business Unit 1 tab, select the check-box for 'Allow Changes to Expense Type', but leave un-selected the 'Require a Reason Code' flag
    5.- Go to the Employee Self Service Fluid Homepage
    6.- Click on the Expenses Tile
    7.- Click on the My Wallet Tile
    8.- Create a new Credit Card Transaction with Expense Type GRCRIES, select a Credit Card related Payment Type, such as MC, and the respective Credit Card Account Number
    9.- SQL Update PS_EX_TRANS.DATA_SOURCE_EX to a value of 'MC' instead of current 'USR' to make it a Credit Card Transaction (This is to bypass having to upload an electronic flat file via EX_DATA_LOAD AE Program)
    10.- Proceed to blank out the Expense Type value of the transaction in My Wallet, and save the changes
    11.- Click on the MORE button
    12.- Select the Credit Card Transaction
    13.- Click on REPORT button
    14.- At this stage, the system brings the User to the Fluid Expense Report Line Details level (Expense Entry page)
    15.- Query PS_EX_TRANS Record for the Credit Card Transaction at hand, and confirm that Fields SHEET_ID, SHEET_NAME, and LINE_NBR are populated, and Field TXN_STATUS is 'A' (Assigned)
    16.- At the Fluid Expense Entry page, click on the magnifying glass icon from the Expense Type field
    17.- On the Expense Type Search pop up window, select the Expense Type MEETING
    18.- Once back at the Fluid Expense Entry page, click on the REVIEW & SUBMIT button
    19.- At this stage, on the Fluid Expense Summary page, the system displays an Error that has flagged the Expense Report Line
    20.- ISSUE: Query PS_EX_TRANS Record again, and confirm that for the Credit Card Transaction at hand, the Fields SHEET_ID, SHEET_NAME, and LINE_NBR have been blanked out, and Field TXN_STATUS is 'U' (Unassigned)
    21.- At the Fluid Expense Summary page, click on the EXPENSE ENTRY back button
    22.- At the Fluid Expense Entry page, confirm that the Wallet icon is displaying a count of 1, suggesting that the Credit Card Transaction is once again available for default into a new Expense Report

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.

With this scenario, a single Credit Card Transaction can be repeatedly used into multiple Expense Reports, causing the company to overpay the Credit Card Supplier, and generating orphan Credit Card Transactions in Expense Reports that no longer have their associated row in My Wallet Record.

A Credit Card Transaction that has been defaulted from My Wallet and into an Expense Report should remain associated at all times, with the Fields on PS_EX_TRANS Record being properly pointing to the Expense Report Line it has generated.

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.