Users are able to book leave for the following year, even though there is no time account existing for that period.
This is only possible if the start date of the leave is in the current booking period.
Employee Central , Time Off
Reproducing the Issue
1. 2017 Vacation Time Account has a Account Validity Period and Booking Period of the 1/1/2017 - 31/12/2017. There is no 2018 time account.
2. Employee can request leave from the 2/12/17 - 3/1/2018, if there is enough balance on the 2017 account.
-> Customer wants to restrict users being able to extend the leave end date into the following year, when there is no valid time account.
Flexible requesting is enabled on the time type.
This means that full balance is booked on the leave start date.
1. Turn off flexible requesting
2. Create a take rule on the time type, that If the end date is in 2018 rasie error message stating that users cannot book leave for 2018 at this time.
Note: You would need to disable this rule once you create and start using the 2018 time accounts.
Flexible requesting, Future leave, no valid time account , KBA , LOD-SF-EC-TIM , Time Off , Problem