Timesheet exceptions occur when a row in the timesheet import file contains missing or invalid data that the system cannot use to create a timesheet or timesheet items. This article explains how those rows are treated during import and where you can review them in the Exception Report.
Understand Timesheet Exceptions
Timesheet exceptions are created during the timesheet import process when the system finds a problem with a row in the import file. If the data in that row is incomplete or incorrect, the system cannot use it to create a timesheet or any associated timesheet items.
Typical examples include:
The import file references a job order number that does not exist in the system, so there is no job to match the timesheet to.
Required fields are missing, empty, or contain values in an invalid format.
Key references in the row do not match existing records in the Time and Attendance module.
When this happens, the system does not create a timesheet for that row. Instead, the row is treated as an exception and is captured in the Exception Report for the import batch.
Use the Timesheet Exception Report
Rows that could not be imported because of exception errors are written to an Exception Report for the relevant timesheet import batch. You can review this report after the batch has finished processing.
Run the timesheet import so that the system processes the rows in your timesheet import file.
After the Timesheet Import batch has completed processing, download the Exception Report for that batch.
Open the Exception Report to see each row that failed with an exception and review the details so you understand which data was missing or invalid.
Use the information in the Exception Report to identify problem rows in your original timesheet import file. Once you have reviewed the exceptions, you can decide how to correct the underlying data in your source file or other records before attempting another import.