When generating limit year, initial value field is not available to enter if we use Carried Forward Absence type.
However, sometimes for some employees it is other way around that allows a Carry Forward absence type to limit generate but it does not allow normal absence type to limit generate where initial value field is blank.
What is the logic behind? Why ‘Carry forward type’ some times allows to enter initial value field and sometimes not allow? Where to fix it?
Please advise.
Thanks in advance
Regards
Nimesh
Best answer by Shehan Almeida
@nimesh
It is not possible to define a carry forward absence type in Limit Definition tab. Therefore it is not possible to have the ‘Absence Editable’ check box also be checked for this type of absence types. E.g. for absence type CARRY in your example.
The carry forward absence types get their limits from the unused absence of the main absence type in previous year. e.g. CETRTT in your example.
What you have to do is just generating limits for the given period and there is no need to edit Initial Value field there.
Yes and then even for main absence type you need to have the ‘Absence Editable’ check box ticked to manually enter a value in the ‘Initial Value’ field at limit generation. Otherwise manual entry is not allowed in the system.
It is not possible to define a carry forward absence type in Limit Definition tab. Therefore it is not possible to have the ‘Absence Editable’ check box also be checked for this type of absence types. E.g. for absence type CARRY in your example.
The carry forward absence types get their limits from the unused absence of the main absence type in previous year. e.g. CETRTT in your example.
What you have to do is just generating limits for the given period and there is no need to edit Initial Value field there.
We use 3 different kinds of cookies. You can choose which cookies you want to accept. We need basic cookies to make this site work, therefore these are the minimum you can select. Learn more about our cookies.
