Human Capital Management Blogs by Members
Gain valuable knowledge and tips on SAP SuccessFactors HCM suite and human capital management market from member blog posts. Share your insights with a post of your own.
cancel
Showing results for 
Search instead for 
Did you mean: 
supriyalanka
Discoverer
923
The SAP Success Factors brought a new enhancement in recent past; it replaced old Benefit auto enrolment job (Deprecates from 2H 2023) with two new jobs.

  • Create or Update Benefit Enrollments for Benefit Master Data Changes

  • Create or Update Benefit Enrollments for Employee Master Data Changes


Old Benefit Auto enrolment Job was considering all employees in each run, unless old job, “Create or Update Benefit Enrollments for Employee Master Data Changes” job queries Benefits Employee Master Data Change Tracker Object and evaluate only those employees’ benefits.

Business Scenario: When there is a Benefit eligibility/ Coverage depends on Employee Age, we should have a tracker record for those dates to evaluate employee benefit eligibility accordingly.

In the below business scenario, one of our legal entities has “Life Insurance – Basic Employee” as an automatic enrolment type Benefit plan, with 3 different coverages based on Age.



We create 3 different benefits with different coverages. Below is the Eligibility rule defined on employee’s age for first benefit. In the same way other two benefits eligibility rules are also factored using Age condition.



Our old Benefit auto enrolment job was running on daily basis, As and when employee’s age turns 65, current enrolled benefit will get delimited, and employee will get enrolled into other life insurance basic (ABC1005B) Benefit with 1x coverage amount.

With newly “Create or Update Benefit Enrollments for Employee Master Data Changes job” in place system will look for Tracker object and evaluate those employee benefits only in each run.

To accommodate this requirement with new employee master data job, we need to rely on “Benefit Eligibility Date configuration” to create tracker record automatically as and when employee enrolled into this particular benefit either automatic (ISC/Job) or manually.

We need to create Benefits Eligibility Date configuration as below.




For Testing purpose, we hired an employee with 64 years of age who turn 65 tomorrow. He got enrolled in to ABC1005A benefit, and two tracker records got created one with tomorrow’s date where employee turns 65 years and one more with rate chart rate chart end of the year (specified in “Age to” field).


Two tracker records got created as below.

 




“Create or update benefit Enrollments for Employee Master data changes” Job executed on November 5th successfully and Benefit enrolment updated to ABC1005B.



After Successful execution, system created one more tracker record for next 5 years.

 


Tracker record creation using “Create or Update Benefit Enrollments for Benefit master data changes” job:

 

Create or Update Benefit Enrollments for Benefit Master Data Changes Job should be created and run with “Job Run context” as “Determine Next Job Run Date for Enrollments”.

 

Determine Next Job Run Date for Enrollments: This option is required when you migrate from the Benefits Auto Enrollments Job to the Create or Update Benefit Enrollments for Benefit Master Data Changes job and you already have Enrollments created using the old job.

The job will determine the next run date based on the configuration in the Benefit Eligibility Date Configuration object for the selected benefit.
3 Comments
Labels in this area