1. TRC not mapped to a valid NA Earnings Code
2. Currency Code reported in Payable Time does not match to Currency Code of the employee's paygroup
3. Employee is not active in JOB (for example, Terminated or Leave of Absence).
4. Employee has changed paygroups in the pay period being processed. (Time will reject, and then load in the new paygroup unless the new paygroup is also in a different company.)
5. TRC in Payable Time is mapped to a NA Earnings Code that is not in the Employee's Earnings Program
6. You run PayUnsheet and all payable time is set to Rejected
7. You enter override state and locality which is not setup for the employee's Tax Data records
8. Employee has prior period adjustments when associated to a different paygroup (Changed in latest release, will now load time to current paygroup unless Company or currency code differences exist).
9. If the Time Reporting Code is Hours or Units and if the value is not between +/- 9,9999.99, the time is rejected by the Load Time And Labor with a error message # 000255. If the Time Reporting Code is Amount type and if the value is not between +/- 99,999,999.99 then time is rejected by Load Time And Labor with the same error message.
2. Currency Code reported in Payable Time does not match to Currency Code of the employee's paygroup
3. Employee is not active in JOB (for example, Terminated or Leave of Absence).
4. Employee has changed paygroups in the pay period being processed. (Time will reject, and then load in the new paygroup unless the new paygroup is also in a different company.)
5. TRC in Payable Time is mapped to a NA Earnings Code that is not in the Employee's Earnings Program
6. You run PayUnsheet and all payable time is set to Rejected
7. You enter override state and locality which is not setup for the employee's Tax Data records
8. Employee has prior period adjustments when associated to a different paygroup (Changed in latest release, will now load time to current paygroup unless Company or currency code differences exist).
9. If the Time Reporting Code is Hours or Units and if the value is not between +/- 9,9999.99, the time is rejected by the Load Time And Labor with a error message # 000255. If the Time Reporting Code is Amount type and if the value is not between +/- 99,999,999.99 then time is rejected by Load Time And Labor with the same error message.
Also, if the sum of the hours/units/amount for a payperiod exceeds +/-9,9999.99 in the case of hours/units and +/-99,999,999.99 in the case of amount the same error message is displayed and the employees, time for the entire payperiod is rejected.
10. The incoming rows from Payable Time have negative override rates (no message will be provided at this time). Update: This is no longer an issue in current releases, applies only to 8 SP1 release.
11. Employee had a job change since the last run of Load Time and Labor. Time for all jobs will reject and be reloaded.
12. The employee terminated prior to the Pay Period Begin Date, and there is unprocessed Payable Time. (Message 005019)10. The incoming rows from Payable Time have negative override rates (no message will be provided at this time). Update: This is no longer an issue in current releases, applies only to 8 SP1 release.
11. Employee had a job change since the last run of Load Time and Labor. Time for all jobs will reject and be reloaded.
13. The employee has too many prior period adjustments. (NOTE: In the delivered version, this will occur when an employee has 99 XREF_NUM's already loaded to paysheets from a previous run. For example, this could occur when there have been a large number of prior period adjustments.)
14. Final Calc and Confirm has been run which stops paysheets from being updated. In order to load more time after a final calc and confirm is done they need to run pre-calc again after unconfirming. This is only a problem when a pay unconfirm has been run - because pay unconfirm updates the pay_calendar status, but not the payline status on the individual rows of PS_PAY_EARNINGS. There is no message for a final calc because a final calc might have run, but time can still be loaded if there are employees with individual payline status <>'F' (allows clients to fix errors).
