For dual HRM/Financial sites (DUAL_HRM_FIN_SITE parameter is set to True on the Application Parameter (APPCTRL) page), in order to determine the validity of a travel expense, it is necessary to determine whether or not a traveler was on leave during the travel period specified on the travel transaction.
The determination of the traveler’s leave status for the travel period specified is performed by the system as follows:
The system evaluates the Employment Status value within the Employee Assignment records in Advantage HRM to determine if the traveler is/was on extended leave during any part of the travel period (which is specified by the Travel Start Date and Travel End Date field values in the Travel transaction’s Header). If the traveler is found to have been on extended leave, the system issues an error within the Travel transaction.
If the traveler was not found to be on extended leave, the system then evaluates the Leave Detail table in Advantage HRM to determine if the traveler was on another type of leave during any part of the travel period. If the traveler is found to have been on another type of leave during the travel period, the system then determines if the leave is a type that allows the employee to still claim expenses while on leave. If the employee is determined to be on leave during the travel period and is eligible to claim expenses, the system does not issue an error within the Travel transaction. However, if the employee is determined to be on leave during the travel period but is ineligible to claim expenses, the system issues an error within the Travel transaction.
Note: for those dual HRM/Financial sites that do not use Advantage HRM to record time and leave (e.g. if the site uses a third-party tool like KRONOS), there is no additional logic to account for these sites. The system still performs the above edits within the Travel transactions but just does not issue an error message if there are no records found in the Leave Detail table.