Error messages

You can view the logs in the Job Scheduler or the Import Transactions page for errors during a Clock Transaction Import. See "Job Scheduler" in the Infor Workforce Management Time and Attendance Implementation and Administration Guide.

This table lists the possible error messages from the Message column in the Import Transactions page for a Clock Transaction Import.

Error Message Description
No rows were added for Employee {Employee Name} because it is a pending employee. Please use the ION processor to complete the initial employee creation to mark this employee as non-pending This update was for an employee in pending status. Use the ION processor to complete the initial employee creation to mark the employee as not pending.
No rows were added for Employee {Employee Name} because it is a pending employee with pre-existing rows, existing rows will be updated Although the ION process was used, the rows were already created for the pending employee. In this instance, only updates are allowed.
(CTPJ_IDENTIFIER/CTPJ_IDENT_TYPE/CTPJ_TYPE/CTPJ_TIME/Reader Name) cannot be empty. Required fields cannot be null.
Transaction Type has an invalid value [value from import file]. It should be a valid transaction type.

Transaction Type value needs to validate against the Swipe Type and Clock Presets.

If a clock preset is sent, then it needs to transform that to a swipe type.

Transaction Time [value from import file] is an invalid value. Date/Time should be in the format: YYYY-MM-DDTHH:MM:SSZ

Invalid clock time value.

For a number:

(Field Name) has an invalid value <from import value>. It should be a valid number.
The data does not match the field type value.
Identifier Type has an invalid value [value from import file]. It should be B for badge, or N for name. Invalid identifier type.
Invalid clock transaction status (Swipe Status). Value must be A for accepted, or R for rejected. Invalid status.
Invalid time zone name %1$s", timeZoneName Invalid timezone.
Note: Similar validations and error messages are used for the generic clocks import. However, it is highly recommended that you use the Clock Transactions Import if you are importing clock transactions.