Symptom
The recurring scheduled job "Create or Update Benefit Enrollments for Employee Master Data Changes" shows multiple concurrent executions of the same request and jobs appear stuck/queued with recovery/reprocessing.
Environment
- SAP SuccessFactors HCM Suite
- SAP SuccessFactors Employee Central
Reproducing the Issue
Cause
- In the object "Recurring information for benefit integration" the enrollment data is missing(for example, empty or invalid benefitEnrollment.id).
- Orphan "recurring information for benefit integration" objects exist where the related enrollment was deleted but the integration record remained, leading to processing issues for the auto-enrollment job.
Resolution
- Retrieve the list of "recurring information for benefit integration" objects from the system (for example, via export or object data reports).
- Identify records with empty or invalid benefitEnrollment.id, including cases where the linked enrollment no longer exists.
- For each affected record, either select a valid enrollment ID or delete the record according to your data governance rules.
- Save changes and ensure data consistency across related benefit enrollment entities.
- Allow the recurring job to run (or start it manually if appropriate) and verify that new executions no longer queue, remain In Progress, or fail.
See Also
Keywords
recurring job, scheduled job manager, benefit enrollments, employee master data changes, auto-enrollment job, insurance, stuck, queued, in progress, failed, reprocessed, recurring information for benefit integration, RIBI, missing benefitEnrollment.id, orphan enrollment, does not have, missing, empty, no value, benfit, GBF, , KBA , LOD-SF-EC-GBF , Global Benefits , Problem
Product
SAP SuccessFactors Employee Central all versions
SAP Knowledge Base Article - Public