EEX 9.2: The Merchant Name of a My Wallet Transaction (Record Field PS_EX_TRANS.MERCHANT) Gets Blanked out if Expense Type Is Changed in Fluid and Online Classic My Wallet Page
(Doc ID 2682600.1)
Last updated on JUNE 19, 2020
Applies to:PeopleSoft Enterprise FIN Expenses - Version 9.2 to 9.2 [Release 9]
Information in this document applies to any platform.
The Merchant Name from a My Wallet item (Record Field PS_EX_TRANS.MERCHANT) is being deleted if the User manually changes the Expense Type value of the Credit Card Transaction at the Fluid My Wallet pages, as well as Online Classic pages.
Credit Card flat files from Banks may contain much more detailed information than what the Expense Type configuration currently requires, and that is OK. All transaction data that is provided impacts correctly on the My Wallet table (Record PS_EX_TRANS). Such transaction data should not be lost.
1.- Log into the FSCM Online Application as User ID EXS1
2.- Go to the Fluid Employee Self-Service Homepage
3.- Click on the Expenses Tile
4.- Click on the My Wallet Tile
5.- Select the existing Meals and Incidental Expenses credit card transaction
6.- Query the My Wallet table (Record PS_EX_TRANS) for that transaction, and confirm that Field MERCHANT is populated
7.- Back online, modify the Expense Type to 'Membership Fees' and save the changes
8.- Query the My Wallet table (Record PS_EX_TRANS) for that transaction once again, and confirm that Field MERCHANT is still populated
9.- Proceed to change once again the Expense Type of this My Wallet transaction, returning to the original value of 'Meals and Incidental Expenses' Expense Type, and save the changes
10.- Finally, query the My Wallet table (Record PS_EX_TRANS) for that transaction one last time, and confirm that Field MERCHANT is now 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 issue, (Note the PDF contains steps on Fluid User Interface, but same steps in Online Classic return the same results).
The My Wallet table, (Record PS_EX_TRANS), loses important transaction data, which cannot be manually entered online anymore. If the transaction is later in need of modification once again, to an Expense Type that requires Merchant information, that data has been lost. This could affect data audits.
Regardless of whether the Expense Type selected requires, or not, the Merchant field, if the Record Field PS_EX_TRANS.MERCHANT is populated from the Credit Card electronic flat file, the value should be respected at all times, unless a User manually changes it using the online functionality to override the existing value.
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