Auto-Progression for Employees is set-up in the system via Off Cycle Event batch. However, eligible employee records are not being updated by the system.
Image/data in this KBA is from SAP internal systems, sample data, or demo systems. Any resemblance to real data is purely coincidental
SAP SuccessFactors Employee Central
Reproducing the Issue
- Configure a business rule for progression
- Create a Batch, associate the rule from step 1
- Set "Include All Matched Records in Every Run" to "No"
Result: Employee is eligible and meets the conditions configured on business rule. However, his record is not updated by the batch.
A common cause is the "Include All Matched Records in Every Run" parameter.
Set the "Include All Matched Records in Every Run" value to "Yes" to activate indexing of the records. Once that eligible employee is included, they don't need to be re-added. Employee will be picked-up by the batch.
If this parameter is set to "No", it filters as Date Field filter > Last Successful Run Date of Off Cycle.
Please Note: The Off Cycle Event Batch will only ever create 1 record. The "Include All Matched Records in Every Run" setting means when checking the data against the criteria of the off cycle, it will either check the current record or all records.
E.g.: if you have 2 records in your history, the first meets the criteria and the second does not. If you want to check only the current record, no action will be carried out for this user as the current record does not match the criteria. Where if you check all records then the record will be created by the off cycle. So depending on what is set, it will either check only the current record or all records which will culminate in different end results.
Off Cycle Event Batch Handbook
2719010 - Employee Central - Off Cycle Event Batch
Off Cycle Event Batch, OCEB, auto-progression, all matches, Include All Matched Records in Every Run, records index, record not updated, not updated by batch , KBA , LOD-SF-EC-EDP , Import Employee Data (EC Core only) , How To