EEX 9.2: Risk Templates Multiple Per Diem Under Same Day Validation Is Ignored in Fluid Approvals for Travel Authorizations
(Doc ID 2854801.1)
Last updated on MARCH 09, 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 during Fluid Travel Authorization Approvals, where the defined Risk Template configuration of 'Multiple Per Diem Exist Per Day' is being completely ignored, and the system validations are not marking any Transaction Lines as duplicates, or with exceptions.
The submitted Travel Authorization has the exact same expense listed multiple times in several rows, with the same Expense Date, Per Diem Expense Type value, Transaction Amount, and Currency Code.
Testing the exact same scenario in an Expense Report, with similar Per Diem Lines, the Fluid Approvals correctly flags all affected rows with the Risk Details of 'Multiple Per Diem Exists Per Day' message, and displaying the 'Exceptions and Risks' link at the main approval page.
1.- Define a Risk Template for Travel Authorizations, making sure the 'Multip Per Diem Exist Per Day' flag is selected
2.- Link this new Risk Template into the Travel Authorization row for the active Approver Profile
3.- Configure an Expense Type for Per Diem, and set up the Expense Location Amounts in the Per Diem Table
4.- Log into the FSCM Online Application as an Expenses Employee
5.- Proceed to create a new Travel Authorization transaction, with 4 lines, each having the same values on the below fields:
a) Expense Date
b) Expense Type Per Diem
c) Expense Amount
d) Expense Location
e) Currency Code
6.- Submit the Travel Authorization
7.- Log into the FSCM Online Application as an Expenses Approver
8.- Open the submitted Travel Authorization in Fluid Approvals
9.- Confirm that there is no 'Exceptions and Risks' link available, and that none of the Transaction Lines are flagged as duplicates, or with Risk Details mentioning multiple Per Diem expenses in the same day
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.
Bypassing the Risk Template configuration, the submitted Travel Authorizations do not offer all the possible information to the Approver Users, who may potentially miss the risks, and the violations taking place, and approve the transaction.
The Fluid Approvals functionality should be working in Travel Authorizations the same way it already does with Expense Reports, ensuring that Risk Template validations are properly triggered, and offending Transaction Lines marked accordingly.
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