You can troubleshoot and fix issues where hours are not calculating for one or more employees in Maintain Hours by understanding potential causes and applying the correct resolutions. This article outlines ten common reasons for calculation failures and provides step-by-step solutions. Common causes and resolutions.
Cause 1: Scheduled overnight calculation did not run for employees
Resolution:
Manually run a calculation and confirm hours have calculated.
If the overnight job failed, contact Support by raising a case online with this article’s title for database script investigation.
See also: How to run a manual calculation for multiple employees.
Cause 2: System Calendar and Control Parameters current period are out of sync
Resolution:
Update the System Calendar or Control Parameters to ensure both are in sync.
See: How to advance the System Calendar without using Advance Period.
Cause 3: System Calendar has not been extended
Resolution:
Extend the T&A system calendar as required.
Cause 4: Calendar-based Shift Types have not been extended
Resolution:
Extend the relevant standard Shift Types.
See: How to extend a standard Shift Type.
Cause 5: Work Group(s) do not have the 'Calculate Clockings' parameter configured
Resolution:
Go to CoreTime > System Params > Work Groups > General Parameters -2.
Tick the Calculate Clockings checkbox.
Click Save.
Cause 6: Overnight jobs are scheduled too close together and interfere
Resolution:
Contact Support by raising a case online referencing this article for further investigation.
Cause 7: Overnight jobs scheduled via Batch Jobs are hanging
Resolution:
Contact Support by raising a case online referencing this article for resolution.
Cause 8: Employee(s) have incorrect start dates set up
Resolution:
Review and update the employee’s original and latest start dates.
See: How to change an employee's original Start Date and Latest Start Date in CorePersonnel.
Cause 9: Calculation is outside Back Office default 42-day period
Resolution:
Ensure the calendar is up to date.
Note: From Back Office version 24+, calculations only run back 42 days; from version 26 onwards, this extends to 90 days.
Cause 10: 'Calculate to' parameter set to 'End of Input Period'
Resolution:
Navigate to CoreTime > System Params > Reference A-C > Control Parameters > General Parameters -1.
Set the Calculate to field to Yesterday or Today.