When you attempt to queue an import batch for processing the system will perform validation of the field mapping that has been applied to ensure that fields that have been mapped are sufficient to theoretically create manual items in interpreted timesheets within Interpreter Review. These validations are described below.
If any of the field mapping or data type validation checks fail, the Import batch will not be queued for processing and an error message will be displayed to identify the reason why the validation failed.
For a full list and description of the fields that can be mapped and the applicable data type of each field, see Mapping Fields.
Field Mapping Validation
When you attempt to queue a Timesheet Import batch for processing, the system will first check if fields have been mapped to identify the FastTrack job order to which each row in the import file corresponds. Specifically, the system will check if any of the following fields have been mapped:
Job ID
Job Alt No
Purchase Order Number
If none of the abovementioned fields have been mapped, Timesheet Import will check if all of the following combinations of fields have been mapped:
Candidate ID or Candidate Alt No or Candidate Full Name or (Candidate Firstname + Candidate Surname)
Item Date or Week Ending Date.
Next, Timesheet Import will check if the following fields, which are required to identify attendance items, have been mapped:
Start Time 1
End Time 1
Standard rates timesheets may not have shift start and end times and therefore it is not mandatory to map the Start Time 1 and E nd Time 1 fields. However, if a start time field is mapped, the corresponding end time field must also be mapped.
If the Start Time 1 and End Time 1 fields have been mapped the system will then check if the following fields have been mapped:
Item Date
Attendance Item Name, Attendance Item Import Code, Pay Code Name or Pay Code Import Code.
If neither Start Time 1 nor End Time 1 fields have been mapped the system will check if all of the following fields have been mapped:
Item Date
Pay Code Name or Pay Code Import Code
Quantity
Fields Required to Identify Additional Shift Start & End Times
If the Start Time 1 and End Time 1 fields have been mapped, the system will check if the Start Time 2 – Start Time 10 fields and the End Time 2 – End Time 10 fields have been mapped. Where any of those fields have been mapped, the system will check that corresponding start/end time field has also been mapped.
For example, if Start Time 2 has been mapped the system must check that End Time 2 has also been mapped. If End Time 10 has been mapped the system must check that Start Time 10 has also been mapped and so on.
Fields Required to Identify Unpaid Breaks
If the Start Time 1 and End Time 1 fields have been mapped, the system will check if any of the Break Start 1 – Break Start 10 and Break End 1 – Break End 10 fields have been mapped. If any one of these fields is mapped, the system will check that the corresponding start/end field has also been mapped.
For example, if Break Start 1 has been mapped the system must check that Break End 1 has also been mapped. If Break End 10 has been mapped the system must check that Break Start 10 has also been mapped and so on.
Data Type Validation
When you attempt to queue a Timesheet Import batch for processing the system also checks that the type of data that is provided in each mapped column within the import file matches the data type of FastTrack field to which that column is mapped. For example, if a column header is mapped to a field that must contain a date value, Timesheet Import will check that the corresponding column contains dates and not any other type of data. For example if the date is not the correct format a pop up message will display 'Error: Date contains an invalid format type for the field mapping. Required date format is DD/MM/YYYY.’