![]() |
![]() |
|
The following table explains the validation messages that may occur when you import a CSV file.
Validation Messages |
Details |
Employee code is blank. |
Employee Code field is empty. |
Employee [Employee] is not a valid active employee. |
Employee Code is not valid. |
Employee [Employee] does not have a current active default appointment. |
Employee is not associated with a valid WAP. |
Employee [EmployeeCode] leave request for [StartDate] to [EndDate] does not contain any working days. |
Leave request is not during profiled hours, or is already a public holiday. |
End date is blank. |
End date is empty (blank). |
End date [EndDate] is an invalid date or is in an incorrect format. The only supported format is dd/mm/yyyy. |
Date format is incorrect or date is invalid. For example, 29/02/2009. |
End date [EndDate] cannot be less than start date [StartDate]. |
End date is less than the start date. |
Expected 4 columns, but given [NumberOfColumns]. |
CSV file has more or less than 4 columns. |
Reason code is blank. |
Reason Code is empty (blank). |
Reason code [ReasonCode] does not exist. |
Reason Code does not exist in PayGlobal. |
Reason code [ReasonCode] is not a valid leave reason for employee code [EmployeeCode]. |
Reason Code is not valid for the employee. |
Start date is blank. |
Start date is empty. (blank). |
Start date [StartDate] is an invalid date or is in an incorrect format. The only supported format is dd/mm/yyyy. |
Date format is incorrect or date is invalid. |
Successfully validated [TotalRows] records. |
Output to log file. |
The file is blank. |
CSV file contains no records. |
The end date [EndDate] does not fall within a valid pay period calendar for employee [EmployeeCode]. |
End date is not in a valid pay period. For example, pay period does not exist. |
The start date [StartDate] does not fall within a valid pay period calendar for employee [EmployeeCode]. |
Start date is not in a valid pay period. For example, pay period does not exist. |
Employee [EmployeeCode] has an overlapping approved leave request in Self-Service with start date of [StartDate] and an end date of [EndDate]. |
An approved leave request already exists in ESS for the same period. |
Employee [EmployeeCode] has an overlapping unapproved leave request in ESS with start date of [StartDate] and an end date of [EndDate]. |
An unapproved leave request already exists in ESS for the same period. |
Employee [EmployeeCode] has an overlapping leave request in the upload CSV with leave reason [ReasonCode] for start date [StartDate] and end date [EndDate]. |
A leave request already exists in the import file for the same period. |
Validation failed for line [LineNumber] - [ValidationMessage]. |
Output to log file on error. |
You cannot upload leave for [EmployeeCode] for the period [StartDate] to [EndDate]. The employee cannot use self-service during this period. |
The employee was set up with a Leave unit source of “None”, so they cannot use ESS to enter leave requests. |
You cannot upload leave for [EmployeeCode] for the period [StartDate] to [EndDate]. This employee must key their required units in self-service during this period. |
The employee was set up with a Leave unit source of “Keyed”, so they must use ESS to key their leave requests. |
Employee [EmployeeCode] has an overlapping leave timeband in PayGlobal for the period [StartDate] to [EndDate]. |
The employee has a timeband in Daily View that has a leave reason for this period of leave. |
Employee [EmployeeCode] has an overlapping leave request in PayGlobal for the period [StartDate] to [EndDate]. |
The employee has a leave request in PayGlobal for this period of leave. |
You cannot upload leave for employee [EmployeeCode] for the period [StartDate] to [EndDate] as the leave start date is after their last available leave date [LastAvailableLeaveDate]. |
Start date is after the employee's last available leave date. For example, the period calendar is not set up or the employee has a termination date. |
|
|
Topic: 7903