At times in support projects, with change in business requirements or modifications we come across with high priority issues with strict deadlines. This could be due year-end or payroll period. During these difficult times we take more time than usually required due to stress. Hence I would like to discuss about a common issue / mistake with Groupings which I have come across during my project days.
Why do we need grouping?
In any project environment we will definitely have multiple levels of employee categories with different salary range, multiple shifts, multiple calculations on over time, leave encashment and different holiday calendars. Hence we need different groupings for different employees.
How do we end up with wrong grouping?
In few cases we will not be able to estimate or foresee the future requirements of client. In certain cases client could have demanded for a modified requirement at the final stages which would differ from the present configuration.
In one of my projects I came across a scenario where the requirement is stated as: “Leave Encashment to be calculated based the on the employee group i.e. Staff, Trainee and workmen. Also the calculation of leave encashment is mentioned below:
- For Staff: To be calculated on Basic pay, HRA, Conveyance, Education and Special Allowance.
- For Trainees: To be calculated only on Stipend.
- For Workmen: To be calculated on Basic pay, DA, HRA, Conveyance, Education, LTA.
If the Employee Sub-Group Grouping (ESG) are same and demands different calculations we can make use of the Operation called OUTWP – (Load Workplace and Basic Pay Data) using the field parameter PERSG. Please refer the below images for references.
Transaction Code: PE04 (Maintain Functions & Operations)