When an Interpreter Manual Item Import batch has been processed successfully the original import file is saved with the batch and can be downloaded for viewing or saving to an external location.
In addition to the original import file, an exception report and a validation report is generated and saved with a batch depending on the final status of the batch. These reports are described in detail below.
The import file, exception report and validation report are saved as comma separated files (.CSV file extension).
Exception and validation reports are not generated if a batch fails to be processed successfully due to a system error and therefore its status is Failed. In such circumstances, you can download the import file and attempt to import the file again as part of a new Manual Item Import batch.
Exception Reports
An exception report is generated and saved with a Manual Item Import batch whenever a batch completes processing successfully and one or more manual item exceptions were encountered during the processing of the batch. That is, an exception report is generated for a batch if the final status of the batch is Completed with Exceptions.
A manual item exception occurs when Interpreter Manual Item Import is unable to create a manual item based on the data contained in a row of the import file. For example, if a row in the import file references a Timesheet ID number that does not exist then it will not be possible to create the corresponding manual item in the interpreted timesheet. In such cases, the corresponding manual item is not created and the offending row is written to the exception report.
An import file can contain data for any number of individual interpreted timesheets. An exception error that affects one interpreted timesheet does not prevent the successful importing and creation of any manual items in other interpreted timesheets included in the import file.
The import exception report is structured as follows:
the first row of the report lists the column header names from the original import file
subsequent rows in the report list each row from the original import file that failed to be imported (failed rows)
to the right of each failed row is an exception/error message that applies to the failed row.
An example of the format of the exception report file is shown below.
You can refer to the exception/error message for each row in the report to determine why the corresponding row failed to be imported. You can then correct each offending row, delete the corresponding exception message and then save the corrected exception report as a new import file. This allows you to create a new import file for the manual items that failed to be imported and created successfully.
A comprehensive list of exceptions is generated and is written to the exception report based on the data that can be validated during the processing of a batch. It is possible that further exceptions can occur when you attempt to import a corrected exception report. For example, if rows in the original import file fail to import because they reference an interpreted timesheet that does not exist, Interpreter Manual Item Import will be unable to verify if the timesheet item dates specified in those rows are valid because the date range of the timesheet cannot be established. Therefore, if you correct the Timesheet ID for the offending rows and attempt to import the corrected exception report, further exceptions may be encountered if, for example, item dates specified against the corrected rows reference a date that is outside the date range of the interpreted timesheet.
For more information about exception errors that may be logged to the exception report, see Data Validation.
Validation Reports
A validation report lists each row from the original import file that was imported successfully. If a batch is imported without any exceptions, the validation report for the batch will effectively be identical to the original import file. However, if any exceptions are encountered during the processing of a batch, the validation report will list the rows that were processed without exceptions only.
A validation report can be downloaded and used to cross-check against the corresponding manual item rows that have been created in the interpreted timesheet if necessary.