- This article discusses how to further troubleshoot Accrual issues. More troubleshooting information can be found in the Time-Off User Handbook.
- We ran the Accruals Calendar job via Admin Tools > Manage Time Off Calendars, but some/all of the employees of that Time Account Type did not get their accruals for the period set in the Accruals Calendar job.
- Employee Central 2.0
It is possible to re-run an Accrual Calendar job at any point, but creating a new Accruals Calendar run via Admin Tools > Manage Time Off Calendars. The system will not add more accruals to employees who already have accrued time off for the date period specified in the Accruals Calendar job will not receive more accrued time, only users who have not accrued time for that date period will be updated.
- Ensure that the start and end date of the accrual period is exactly the same as the previous job you had run. Then also ensure that only 1 Time Account Type per accrual job is set (do not have multiple Time Account Types in 1 Calendar Run job). As of b1402, you will only be able to run 1 accrual job per Time Account Type (so you will need multiple accrual jobs if you have multiple Time Account Types).
Reasons why certain employees did not get their accruals after the Accruals Calendar job has completed -:
1) You have configured Accruals based on Seniority – you need to check and ensure the affected users Employment Information data that is used to calculate Seniority is actually defined for that employee. If the value is missing from the employees Employee Central data, then their accrual will fail to calculate.
2) Incorrectly configured Seniority Lookup table - Verify that the Seniority Lookup Table has its ranges set correctly. Each Seniority Lookup Table that you use should have one record with a “Seniority From” value of 0 and one with “Seniority To” value of 100 (the range must add up from 0 to 100). If the table does not have an ending value of 100 then there will be errors when calculating accruals for employees who’s accruals are calculated using that lookup table.
3) Another thing to note is that the From and To values should never overlap. For example you should not have -:
- From 0 to 2
- From 2 to 4
- From 4 to 6
As the system will not know where one ends and the other begins. A correct example would be as follows (the From / To gap is up to you, ust make sure the values do not over lap) -:
- From 0 to 1
- From 2 to 3
- From 4 to 5
- From 6 to 7
- and so on
If you are basing you accruals on "Difference in Calendar Years()" then you should be using one of the rounding based versions of this rule function to Round Up or Round Down, so the system can further determine which Seniority bracket the employee falls into. Rounding Up or Down is entirely up to customer requirements in this respect. The most important is that the Lookup Table does not have value overlaps so the rule can correctly determine the accrual amount.
An example of a correctly configured accrual lookup is shown -:
As of the b1402 release, you will also be able to use “Simulation” mode to simulate accruals, so further troubleshooting can be performed. Simulation mode will run the accruals and provide a status report once the job completes, but the accruals will not be saved against employees Time Account.
- Further troubleshooting information regarding accruals can be found in the Time Off User Handbook. If you do not have a copy of this guide book, please reach out to Customer Success by creating a Support Ticket, and requesting the latest version.
KBA , sf employee central , LOD-SF-EC , Employee Central , LOD-SF-EC-TIM , Time-Off , How To