Pay scale progression mechanism should allow employers to automatically move employees to the next higher pay scale level based on eligibility rules governed based on Pay scale membership period, Actual Hours Worked by an employee and Employee’s Age.
In this blog, we are covering based on the employee’s Age – How the Pay Scale progression will be managed in the Employee Central.
The term grade step progression and pay scale progression have the similar meaning.
Configuration steps:
- Custom field in the Pay Scale Level object.
- Pay Scale Level with Pay Component assignment.
- Rules to derive the Employee’s age and pay scale progression.
- Off-Cycle Event Batch setup.
This is not a very common use case however certain countries like Netherlands do use employee’s age for eligibility to progress to the next pay scale level or determine a portion of the compensation based on age.
Custom field in the Pay Scale Level object
In the Pay Scale Level object, I’m enabling the custom field “Age” to capture the eligibility criteria at the Pay Scale Level. This will be used in the business rule to check if employees have met the criteria and are eligible for progression.
Pay Scale Level with Pay Component assignment
On the next step, the pay component needs to be maintained under each pay scale level based on the requirement.
Rules to derive the Employee’s age and pay scale progression
Business rules will play a major role in running the pay scale progression, I’m configuring two business rules.
- Rule 1: To process the pay scale level changes by Off Cycle Event Batch
- Rule 2: For updating the salary change in the compensation portlet based on the pay scale level.
Rule 1: Below is the snapshot of the rule.
Use the application-specific rule scenario: Trigger Rules for Off Cycle Event Batch
Note: Associate the rule in the “Manage data > Off Cycle Event Batch object”.
Rule 2: Below is the snapshot of the rule.
Use application-specific rule scenario Trigger Cross-Entity Rules.
Note: Associate the rule in the “Manage Business Configuration > Job Information > On save”.
Off-Cycle Event Batch setup
Create the off-cycle event batch object.
- Set base object as Job information.
- Associate the above rule and assign the employee group created.
- Set the flags: Include all matched records in every run to No – See appendix for more detailed information on how this flag works Include inactive records to No.
Limitation: Even though it is recommended to define a ‘toFilter’ for better performance, ‘toFilter’ is optional as mentioned in the implementation guide. However, when Job Information is used as the base object, not defining the ‘toFilter’ results in no records being filtered for processing by the rule. A dummy ‘toFilter’ can be setup as a workaround to the problem. Below is a sample dummy filter criteria.
- Create the “Off Cycle Event Batch” job in the instance under “Scheduled Job Manager”.
Scheduled Job Manager
Outcome
Scenario: I’ve picked an employee who's age is "18" with pay scale level “NLD/WEST/PLANT/TRAINEE/L1” and turned to “19” the system has to be automatically move to next pay scale level “NLD/WEST/PLANT/TRAINEE/L2”.
Pay Scale Progression based on Service Period
All the above steps will be followed the same expect the business rules (For updating the salary change in the compensation portlet based on the pay scale level).
Read other SAP SuccessFactors Employee Central blog posts and follow SAP SuccessFactors Employee Central
Please follow my profile for future posts Narendra Prasath Parthiban
It would be appreciated if you could Like and Share your valuable feedback in the comment section.
- SAP Managed Tags:
| User | Count |
|---|---|
| 13 | |
| 12 | |
| 3 | |
| 3 | |
| 3 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 |
