EEX 9.2: The Fluid Travel Authorization Component Only Sets PS_EX_TAUTH_LINE.OUT_OF_POLICY Record Field Value Correct After Second Save Issuing the Location Amount Error Message On The Wrong Time
(Doc ID 2876728.1)
Last updated on JULY 06, 2022
Applies to:PeopleSoft Enterprise FIN Expenses - Version 9.2 to 9.2 [Release 9]
Information in this document applies to any platform.
A problem has been detected with the Fluid Travel Authorization component, where the system requires the transaction to be saved at least a couple of times, before the delivered validation logic sets a Transaction Line with an Expense Amount far greater than the Location Amount defined limit, with an Out Of Policy flag set to Yes, displaying the Error Flag and Amount Comments icons.
1.- Log into the FSCM Online Application as an Expenses User
2.- Navigate to: Set Up Financials/Supply Chain > Product Related > Expenses > Location > Expense Location Amount
3.- For Expense Type LODGING, Currency Code USD, and Location NWYK, set an amount of 300 USD
4.- Go to the Employee Self Service Fluid Homepage
5.- Click on the Travel Authorizations Tile
6.- Click on the 'Add Travel Authorization' button
7.- Manually enter all the Travel Authorization Header values, as below:
- Travel From = NWYK
- Travel To = NWYK
- Date From = November 30th 2021
- Date From = December 30th 2021
8.- Manually enter all the Travel Authorization Line values, as below:
- Expense Type = LODGING
- Expense Amount = 300.00 USD
- Number of Nights = 30
9.- Save the changes
10.- Query Record PS_EX_TAUTH_LINE and confirm that Field OUT_OF_POLICY is set to 'N'
11.- Proceed to change the Date To value to December 1st 2021, which automatically sets the trip to only one day duration
12.- Click on SAVE button
13.- Query Record PS_EX_TAUTH_LINE, and confirm that Field NBR_NIGHTS is automatically changed from '30' to '1', which is expected, but the Field OUT_OF_POLICY is still storing a value of 'N', when it is expected to have the value of 'Y' instead
14.- At the Fluid Travel Authorization main page again, click on SAVE button a second time
15.- Query Record PS_EX_TAUTH_LINE, and confirm that Field OUT_OF_POLICY is now storing the correct value of 'Y'
16.- However, the system has not displayed the Error Flag on the Travel Authorization Line, nor requested Justification Comments to be entered by the User
17.- Click on the SUBMIT button
18.- It is only now that the Travel Authorization Line is flagged in Error, and the Amount Comments icon is displayed
19.- When clicking the Error Flag at the Line level, the message doe snot seem to be complete, it is cut off.
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.
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