Leave Deduction Policy change after Golive
This blog post explains you how to change the Deduction/ Counting method for time type post Go-live.
Business Requirement: Leave Deduction method changed from Work schedule
to Calendar days i.e including week off’s and Public Holidays.
As per the design of time type architecture, system will not allow to change the Counting method if there are Employee leave requests exist for the time type. This is quite common requirement from customers if leave deduction policy changed.
We proposed below solution to the customer:
Solution: We have create the new time type same as existing time type and assigned Counting method to consider all the days based on the client requirement and associate the existing Time account type to the new time type.
Below screenshot for counting method creation:
Assigning Counting method to Time Type:
Assign the new time type to the Time Profile:
Approve all the pending requests if any for the old time type and Disable the old time type from ESS view in Time profile and enable the new time type in Time Profile.
Note: Change the Old time type Name to Ex: “Sick Leave Do Not Use” as this is still be visible in the Admin screen & Admin should not use this time type by mistake & also you can take rule not to use this time type.
Hope this blog post helps you, in case if you have requirement of changing deduction method to the time type.
Good blog! This is a common requirement for a lot of customers since there are so many attributes of time changes that SF won't let you do if there are existing time-off requests. Wish that there are a better solution for this as the time profiles can get messy over time when requirements change
Hi Manjunath BK,
Thanks for the great blog on the leave policy changes, we also had the same type of request at a client and we followed a different approach.
The Time Type which we had to change was linked to a Time Account, and all we had to do was:
We followed the above approach because it allowed us to still report on the same "Time Type" without the need to recreate a new one and it did not impact on existing integrations.