The Timesheet Interpreter Manual Item Import module allows time and attendance feature allows manual item information that is captured outside of the FastTrack360 system to be imported into the system so that electronic timesheets can be created, approved, paid and billedinterpreted timesheets.
The Timesheet Import module imports timesheets manual items are imported via an import batch process, which groups together a collection of timesheet data that is processed together to create applies the manual item data to identified interpreted timesheets within the FastTrack360 Time and Attendance Interpreter Review module. The timesheet import batch process consists of the following general steps:
Uploading the timesheet import file.
Defining the field mapping.
Queuing the timesheet import batch for processing. Each of these steps is described in more detail below.
...
.
Uploading the
...
Manual Item Import File
The import batch process is initiated by uploading a timesheet an import file, which contains the data that will be used to create timesheets and to populate information on each timesheet. The timesheet manual items in interpreted timesheets that have not been reviewed. The import file must be formatted such that Timesheet Import so the system can read the import file and its content. For example, the first row of the import file must contain column headers that can be mapped to FastTrack interpreted timesheet fieldsmanual item. For more information, see Import File Format Validation.
Defining the Field Mapping
If the format of the import file format is valid the system will read and display the column headers from the import file. The column headers must be mapped to the corresponding Time and Attendance interpreted timesheet manual item fields to inform the system what data is supplied in the import file and what that data corresponds to within the FastTrack system.
A set of field mappings that are configured when importing a timesheet an import file can be saved as a template, which can be applied whenever an import file that originates from the same source is processed in the future. This prevents the need to manually configure the field mapping each time an import is processed. For more information, see Saving Field Mapping Templates.
Queuing the Import Batch for Processing
Once the field mapping has been configured it is possible to queue the timesheet interpreter manual import batch for processing. On attempting to queue an import batch for processing, the system performs field mapping and data type validation to ensure that timesheets and timesheet manual items can be theoretically created based on the mapping and types of data provided within the import file. For more information, see Field Mapping & Data Type Validation.
If the validation succeeds the import batch is sent to the Process Queue, where the batch undergoes processing. The amount of time that it takes for a queued batch to complete processing depends on a number of factors such as the following:
the number of prior import batches already queued for processing the number of individual rows within the import file.
When processing of an import batch is completed, the following occurs:
any timesheets manual items that can be successfully created based on the data in the import file are created in the Time and Attendance module and the status of the timesheets is set to Submittedrelated interpreted timesheet where the timesheet is ‘Not Reviewed’.
the status of the batch is set to Completed or Completed with Exceptions.
...
If a system error occurs when an import batch is queued for processing the status of the batch will be set to Failed and no timesheets manual items will be created in Time and Attendancein interpreted timesheets in Interpreter Review. If this occurs, you will need to process the original import file as part of a new timesheet import batchmanual item import batch.
| Info |
|---|
Where the same information is imported via two different import batches, the manual item will display as two different items in the Interpreter Review > Interpreter Timesheet Details screen. However, if you edit any of the items within the Interpreted Timesheet, the system will consolidate any transactions where the same item/date/values etc exist, so the two imported items will be combined. This is standard behaviour even where a user enters the same information twice via the UI. In the Audit Tab however, the two separate transitions will display. Where the manual item is imported via an API call, if the same scenario exists (same item/date/values), the API import will call the UI logic and automatically combine the two separate call items. |
| Child pages (Children Display) |
|---|
...