My Oracle Support Banner

EEX 9.2: Fluid Travel Authorization Per Diem Line Amount Not Defaulting Unless Date From and Date to Fields Populated at Header Level (Doc ID 2830774.1)

Last updated on DECEMBER 27, 2021

Applies to:

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


It has been detected that when a new Travel Authorization is being created online via the Fluid User Interface pages, the Date From and Date To fields located at the Header level are a major drive, along with the Travel From and Travel To fields, to default into the Line Amount field the Per Diem Amounts should any Line contain a Per Diem related Expense Type.

Note as well that at the Fluid Travel Authorization Expense Type mapping configuration page, it is possible to select Per Diem related Expense Types. If done so, the delivered codeline will ensure that those Expense Types defined and active will automatically get added into the Travel Authorization as new Lines upon the page being loaded.

The problem that has been detected is that when adding a new Travel Authorization in Fluid User Interface, the Header Level Fields listed below will be blank:

    - Travel From
    - Travel To
    - Date From
    - Date To

As such, the Per Diem related rows will not have the Line Amount field pre-populated, which is understandable. However, after populating the 4 Fields listed above, and have them defaulted into the existing Travel Authorization Lines, (via saving, or manually entering such values online, in the Details page), the Line Amount field is still kept blank, and not re-calculated by the system.

Only when the 4 aforementioned Fields are populated, and a brand new Travel Authorization Line is created, with a Per Diem Expense Type selected, would the system default the value into the Line Amount field from the Per Diem Location Amount tables.

At the same time, the system allows the saving of a Travel Authorization in Fluid, with the From Date and To Date fields being blank, which is confusing, as they are marked as required.


    1.- Define a new Per Diem Expense Type, and ensure it retrieves its amounts from the Per Diem Location Amount table
    2.- Define an amount value for the Expense Type selected, and a specific Location
    3.- At the Fluid Travel Authorization Expense Type mapping set up page, ensure the Per Diem Expense Type is selected, and active
    4.- Proceed to create a new Travel Authorization via Fluid User Interface
    5.- Confirm that upon loading the Fluid Travel Authorization creation page the below Fields are blank by default:
               - Travel From
               - Travel To
               - Date From
               - Date To
    6.- Confirm as well that there is already a Travel Authorization Line with the Per Diem Expense Type present in the transaction, with the Line Amount field empty
    7.- Continue by populating the 4 aforementioned fields at the Header level
    8.- Click on the Details button of the Travel Authorization Line where the Per Diem Expense Type is defined
    9.- Ensure that an Expense Date is present, and if not, manually enter it
    10.- Try to save the changes of the Travel Authorization
    11.- Confirm that the system triggers a message stating that the existing Per Diem Travel Authorization Line needs to have a value entered into the Amount field
    12.- Add a second Travel Authorization Line, and select the same Per Diem Expense Type
    13.- Confirm that this time, the Line Amount is populated with the value defined at the Per Diem Location Amount tables, but only for the newly created line, and not the original one

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.

Employees are not always knowledgeable of what Amount Limits are defined by the company for each Location when using Per Diem Expense Types, so if the system is not going to validate the amounts, nor default them, then mistakes can be done, and wrong amount entered, approved, and even paid to the Employees, bypassing all the Per Diem Location Amounts configured.

The system should not allow an Employee to successfully save a Travel Authorization in Fluid is the Date From and Date To fields are not populated. At the same time, when those fields are defined by the User, the system should trigger validations for any Lines using Per DIEM Expense Types, and default the Per Diem defined amounts to the Line Amount rows, (new and existing ones), should the Line Amount be empty.

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.




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

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