Actually if i do so, the system will calculate retro, which the client don't want.
Please consider the scenario below.
An employee avail the causal leave in Aug and the end user deduct his/her annual leave by mistake. At the end of the year, lets say in December, the employee came to correct the quota that he availed his Casual leave instead of Annual leave. In this case, if i delete the record from IT2001, the system will calculate the retro from Aug.
See both are paid leaves right. you can delete the wrong entry and correct the abs type. To not process to retro you can delete the retro periods in PU03 of the Employee. then system will not run the retro from august month on-wards.
Since you can see that both are paid leave. If you will not do any changes then it will be show as a mismatch between two quotas value and user will be in a dilemma about his quota.
So if you will change in the quota value by deleting and updating new quota it will trigger to retro but it will not bring any mismatch amount or retro amount for current period. Overall quota amount will be correct in system as well,as user will be in clear picture.
What you do is create 2 more absence types to handle such cases and according to the requirement configure a counting rule and decide that whether to assign it to absence type i.e annual leave is deducted but now it should be replaced and added to existing quota so that it can be encashed in such cases maintain absence type but quota should not get deducted it should get added with number of absence days.
Similarly Casual leave it is not deducted since maintain it accordingly it gets deducted from casual leave.
Further more consider payroll calculations as well.
What we can suggest is some how we can adjust with work arounds.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.