Recently I got to work on an interesting client requirement and realized this was becoming common practice. The requirement is to pay Holiday Pay only if the employee works both the day before and the day after a holiday. This can be a complicated matter and often implementers will resort to custom code to resolve this requirement.

SCENARIO

Holiday pay is to be generated automatically via time evaluation for your employees on company holidays. Your company also has a holiday policy that states that employees will not get holiday pay hours in case of unexcused absence time before or after a company holiday.

The challenge here is that you do not know if the person will work the next day when the Holiday occurs. In addition, the day before or after the Holiday may not be a scheduled working day. Instead, it could be another Holiday or a weekend as well. Given this scenario, there may be certain instances where you need to look back in time, especially when unexcused time occurs after the company holiday. In this case, you would have already generated holiday hours so you need to correct them.

I have regularly solved this issue using a series of Personnel Calculation Rules in the Time Evaluation Schema. This solution allows the entire scenario to be created purely in configuration and has no reliance on custom operations or custom code. This makes changes and updates less of a maintenance issue.

SOLUTION

Using a time type to store time paid is a simple method to check previous days after the fact and make decisions on this data. I create a time type to store worked time before the holiday, the holiday hours paid (if Paid), and roll these forward to the day after the holiday.

Step 1) Set a counter if worked or approved absence before the Holiday:

This rule runs every day and adds a “1” into customer time type ZWRK to indicate our criteria for “worked the day before” in this case it also sets a True/False indicator so we know if we bother to pay the holiday time at all.

Step 2) On the Holiday, add the paid hours to a custom time type ZHOL:

This rule runs on the holiday and confirms that we paid the holiday. This is for later use in case we have an employee who does not work the day after. This amount of holiday hours would then be reversed.

Step 3) On the days after the Holiday, we determine if we should have paid the holiday or not:

This combination of rules runs every day to see if the day before was a paid holiday or not and whether we worked the day after. Specifically; 

CONCLUSION

This requirement is becoming more commonplace. This solution is flexible enough that any change in company policy can be configured, such as change in Absence Codes that are considered “approved”. Standard SAP configuration, including operations and functions in the Personnel Calculation Rules, is used. This makes maintenance more feasible since any SAP Time Management expert can understand and maintain these rules.

ABOUT HR FOCAL POINT

  • When time, accuracy and high-quality support are essential, HR Focal Point's precision approach to SAP HCM solutions is the clear choice. 
  • HR Focal Point has been the SAP HCM expert since 2004 with hundreds of years of combined consulting experience its team.
  • HR Focal Point has the SAP HCM experts that will allow you to achieve your goals on time, on point and on budget, thus maximizing your ROI.
  • HR Focal Point offers a flexible engagement model so you only pay for the services you require, when you require them.
  • As an SAP Services Partner, HR Focal Point is known for delivering high-quality solutions, in support of SAP HCM, that are completed accurately and on schedule.
  • HR Focal Point has partnered with SuccessFactors to develop and deliver innovative Cloud solutions, including Employee Central Payroll, for their clients.

FOR MORE INFORMATION

HR Focal Point
Telephone: +1 855.464.4737
Email: solutions@hrfocalpoint.com

 

Comment