This article lists recommendations for Benefits Auto Enrollment Jobs in Provisioning and the eligibility rule set up.
- SAP SuccessFactors HXM Suite
- SAP SuccessFactors Employee Central - Global Benefits
SAP SuccessFactors is offering Employee Central Benefits customers a new, lightweight solution for updating benefit records in real time when changes are made in Employee Central master data due to work events. This solution involves listening for the Intelligent Services Events (ISEs) that are available in Employee Central and having them trigger the desired changes to benefits records. Today ISE listening for Benefits is available for automating the new hire event (creation of exceptions automatically), and for employee termination. The roadmap is planned to extend this model to other events such as transfer, salary change, and job changes etc.
Real time benefits processing reduces customers’ reliance on the Benefits Auto Enrollment job, which uses the older technology of batch mode processing. To ensure a smooth transition to real time benefits processing, we are also making changes to the Auto Enrollment Job, enabling work event automation and jobs to work symbiotically in updating the system.
Because jobs will continue to be an integral part of the benefits landscape, with this KBA we are sharing leading practices to enable optimized job execution time. The goal is for jobs to execute in two hours or less. Based on the setup of benefits (number of eligible employees, complexity of rules etc.) this could result in configuring either one job with single or multiple benefits.
You can chck in our guide Create Job for Auto Enrollment Benefit all the needed configurations for this and some scenarios are explained below on how the jobs can be split for efficient execution time.
Scenario 1: One job for Benefit across different legal entities
If a single benefit is applicable for more than one legal entity and this job takes more than 2 hours for execution; then instead of one job that is configured at the benefit level; split this into 2 separate jobs:
Example: Medical benefit is applicable for legal entities: LE1 and LE2, then:
Job 1: Medical benefit for LE1
Job 2: Medical benefit for LE2
Scenario 2: One job for all benefits across the same benefit type
If a single job is scheduled for all benefits of type “Allowances” that has an approximate execution time of more than two hours, then please split the job such that the execution time for each job is reduced.
Scenario 3: One job for all benefits across different benefit types
If a single Job is scheduled for all benefits across different benefit types “Allowances”, “Insurances” and “Pensions” that has an approximate execution time of more than two hours, then please split the job with a combination of benefits such that the execution time for each job is reduced. As much as possible, avoid configuring one job that contains benefits across different benefit types.
Scenario 4: Review of the rule’s setup
The way eligibility rules are configured has an impact on the performance. Hence please refer to the Rules implementation guide to follow the best practice.
Scenario 5: Recurrence of the job
Please ensure that the recurrence of job doesn’t fall in a frequency less than daily, unless needed. The dependency on recurrence can be avoided by adopting the event-based handling model. For e.g.: The recurring jobs scheduled for enrolling new hires maybe reviewed by exploring this new approach for your requirements.
As mentioned earlier, the event-based handling will be enhanced phase wise to cover other work events.
*Note* The effective date of the benefit enrollment of a user enrolled into a benefit by the auto enrollment job will be the date of the runtime of the job.
Best Practices, Interrupt, Restart, Interrupted, Restarted, Stopped, Performance, Schedule, Dashboard, Execution Manager Dashboard, Intelligent Services Center, ISC, Event, Subscriber, Publisher, Activity, ben, GBF, enrol, enrolling, enrolment , KBA , LOD-SF-EC-GBF , Global Benefits , How To