Skip to Content
Product Information
Author's profile photo Bijolesly Kurian

Create or Update Benefit Enrollments for Employee Master Data Changes Job

The SAP SuccessFactors H2 2020 Release brings with it a new enhancement that allows admins to set up a new type of job (Create or Update Benefit Enrollments for Employee Master Data changes) to create or update enrollment records whenever there is a change in Employee master data.

Reason for introducing this new job

The ‘Benefits Auto Enrollment’ Job analyzes all employee records with each run, even those records where there are no changes as per the eligibility rule.

This approach slows down jobs, affecting the performance with respect to time. Occasionally, it also makes the job fail due to memory consumption issues if the volume to be processed is too high for some customers based on their setup and number of employees.

How does this new job work?

During the ‘Create or Update Benefit Enrollments for Employee Master Data Changes’ job run, a new ‘Benefits Employee Master Data Change Tracker’ object is queried to find the employees with master data changes:

  • If the system doesn’t find any records of any such employees belonging to the selected legal entity, the job will log the result and exit.
  • If it finds records, it processes only those employees. After the execution, the job will update the status in the tracker object whether the job has processed successfully or not.

As this job processes only those employees with master data changes, it reduces the volume that needs to be processed and increases the processing efficiency of the job.

Note: The records will be created in ‘Benefits Employee Master Data Change Tracker’ object when there is a change in employee master data. We use rules to trigger such changes, and this is explained in the additional configurations section below.

Use cases addressed by this Job

Whenever there is a change in employee master data, this job will perform the below mentioned actions on the benefits as per the eligibility rule defined in the Benefit.

  • Create enrollment
  • Update enrollment

For example:

  • If an employee becomes newly eligible for a benefit due to change in Department, then the job will create an enrollment record.
  • If an employee becomes eligible for a benefit with higher entitlement amount due to change in Pay grade, then the job will update the enrollment record with the new amount.

If an employee loses eligibility for a benefit due to change in Job classification, then the job will terminate/delimit the enrollment record.

Are there any limitations with this job?

Yes, currently there is a limitation and if it is not acceptable in your business scenario you must continue to use the Benefits Auto Enrollment job for the following scenario:

Subsequent auto updates to the enrollments based on custom date related eligibility changes are not supported.

For example:

If the eligibility rule of the benefit is defined based on any custom date field or any other date fields that we have not listed in the ‘Create Benefits Eligibility Date Configuration’.

What additional configurations are introduced to set up this job?

1. Configure rules for the master data objects:

New approach works solely based on identifying that there is a master data change for employee. This is done by using business rule. Rules must be configured using the rule functions listed below for the master data objects maintained in the benefit eligibility rules.

For example, if your eligibility rule is defined based on the parameters Job Information, Biographical Information, Personal Information then create the rules using the below rule functions and attach to the mentioned parameters as a ‘Post save’ or ‘On save’ rule for all three entities (Job Information, Biographical Information, Personal Information)

  • Create Benefit Tracker for Employment Info Changes ()
  • Create Benefit Tracker for Employment Info Changes with Effective Date ()
  • Create Benefit Tracker for Personal Info Changes ()
  • Create Benefit Tracker for Personal Info Changes with Effective Date ()

When there is a change to any of the fields in these parameters (Job information, Biographical Information, Personal Information etc.), this rule will trigger and create an entry into the ‘Benefits Employee Master Data Change Tracker’ object.

2. Configure Benefit Eligibility Dates:

If the Benefit eligibility rules are defined on certain dates, such as Date of Birth, Date of Hire, Probation Date, and so on, you should create the Benefits Eligibility Date Configuration object. The object will determine the date on which the benefit eligibility of the employee changes and will create tracker records for the determined dates. On those dates the jobs will evaluate the employee for the specific benefit.


Employees of a company are eligible for ‘Fuel Allowance’ benefit only if they complete 3 years in the organization. Let us consider two employees Steve and Jason have hire dates as July 15, 2018 and August 1, 2019 respectively. The Benefit Eligibility Date Configuration object should be created as below for this requirement.

  • Base Date: Employee Hire Date
  • As of Day: No Selection
  • As of Month: No Selection
  • As of Year: No Selection
  • Recurring: No
  • Offset Value: 3 Year

The job is run on August 1st, 2021. On this date, Steve is eligible for the benefit, so enrollment records will be created for Steve.

However, Jason is not eligible for the benefit as he has not completed three years in the company.

A tracker record will be created for Jason with the planned job run date as August 1st, 2022.

When the job runs on August 1st, 2022, it will create the required enrollment records for Jason. If there are no more changes to employee master data of Jason until August 1st, 2022, then this job will execute only on August 1st, 2022 for employee Jason and in all the previous runs it will not execute for this user as there are no changes expected to his enrollment record

End to End setup of ‘Create or Update Benefit Enrollments for Employee Master Data Changes’ Job

1. Setup the Benefit

  1. Create Benefits with eligibility rules (This job is supported only for Allowance, Pension, and Insurance type Benefits)
  2. While creating benefits, please note the below points.
    • Select the Enrollment type as ‘Automatic’. Note: Enrollment type ‘Manual’ is also supported but only for ‘Insurance’ type benefit. The first enrollment must be done manually, and job is used for any updates.
    • Choose ‘Allow automatic updates’ field to ‘Yes’ to enable updates to enrollment records through jobs. Please note, from b2011 release ‘Allow automatic updates’ filed is available for ‘Manual’ type benefit as well.
  3. Below is a sample eligibility rule used in the benefit (we can use this rule as a base to complete the sample scenario in the coming sections)

2. Set Up the Rules for Parameters Used in the Eligibility Rule

  1. Navigate to Admin Center –> Manage Business Configuration.
  2. Choose the object that you need to assign the rule. If the eligibility rule is created with the fields in ‘Job information’ then choose the ‘Job Information’ object.

  1. Create a rule and assign it under the ‘Trigger rules’ section

           Below is the sample rule

  1. Save the configuration

3. Create Benefits Eligibility Date Configuration

If the benefit eligibility rule is defined on any date specific fields, please create the below configuration. If no date specific fields are defined in the eligibility rule, then you can skip this set up.

  1. Go to Admin Center–>Benefits Admin Overview–>Create New–>Benefits Eligibility Date Configuration.
  2. Choose Base Date based on the type of date used in the benefit eligibility configuration. The system supports most standard dates, such as Employee Hire DateEmployee Date of BirthDependent Date of Birth, and so on. However, if you use custom date or any date that is not available in the Base Date field, you should use the Benefits Auto Enrollment Job for benefit enrollment update scenarios.
  3. The fields As of DayAs of Month, and As of Year are optional. Choose these fields if you want to evaluate Base Date of an employee on a specific date and not on the job execution date. If these fields are not selected, the Base Date is evaluated on the job execution date and appropriate enrollment records or tracker records are created.
  4. Choose Recurring as Yes if the benefit needs to be evaluated on a recurring basis.

For example, if the base date is Employee Date of Birth and the benefit need to be evaluated             on every year on employee’s birth date.

  1. In the Set Duration from Base Date section, set the value and units to be added to the base date.
  2. Select the benefits that should be evaluated by the job on the determined dates of benefit eligibility change.
  3. Choose Save.

4. Set up the job in Provisioning:

  1. Login to Provisioning and select the Company
  2. Choose ‘Manage scheduled Jobs’ from ‘Manage Job Scheduler’
  3. Click on ‘Create New Job’
  4. Enter the Job name and Job owner
  5. Choose the Job type ‘Create or Update Benefit Enrollments for Employee Master Data Changes


  1. Choose the Legal entities. Please note, in this job Benefit selection is not available.
  2. Enable ‘Show response in execution manager dashboard’ checkboxes to view the execution results in ‘Execution manager dashboard’ once the job is completed.
  3. Save the job

How does the new job create or update the enrollment records?

  1. Employee ‘Rick Smolla’ was already enrolled in an allowance benefit with 500 USD per month (As per the eligibility rule defined in the benefit, refer the eligibility rule screenshot in the Benefit set up section)
  2. The Admin/HR Manager has changed Rick Smolla’s pay grade to ‘H-07’ in the Job information portlet.

  1. This change will create an entry in ‘Benefits Employee Master Data Change Tracker’ object. Also note that the field ‘Job processed status’ will be set to ‘Not Processed’. This status will be changed once job process this record.

  1. Now when the job runs as per the schedule, it will look for the ‘Benefits Employee Master Data Change Tracker’ object and executes the eligibility rule for the employee ‘Rick Smolla’ and not for any other employees. Because there are no changes to other employees’ master data.
  2. As a result, the enrollment record will get updated with the new amount 1000 USD.
  3. Since the job ran successfully and updated the enrolment record, the ‘Job Processed Status’ in ‘Benefits Employee Master Data Change Tracker’ object will get updated with ‘Success’.

Frequently Asked Questions:

1.What is the significance of the field ‘Job Processed Status’ in ‘Benefits Employee Master Data Change Tracker’?

Answer: When there is any change to the employee master data like Job information or Personal information, it will create an entry in the ‘Benefits Employee Master Data Change tracker’ object with the ‘Job Processed Status’ as ‘Not processed’.

Once the job runs successfully, the status will be changed to ‘Success’.

Due to any reason if job fails, the status will be marked as ‘Failed’ and when the job run next time it will reconsider this entry for execution.

Note: Please note if the job failed yesterday and when the job runs today, it will execute the eligibility rule as of today only and not as of yesterday.

2.I do not see the Benefit selection in ‘Create or Update Benefit Enrollments for Employee Master Data Changes’, which benefits will be considered for Job processing?

Answer: This job is based on Legal entity selection. Since this job updates enrollment records based on employee master data changes, those changes should be applicable for all relevant benefits. Hence the benefit selection is not required, system updates the enrollment records for all applicable benefits of type Allowance, Pension, and Insurance.

3.The ‘Benefit Auto Enrollment’ job works only for Allowance, Pension and Insurance type benefits, how about the ‘Create or Update Benefit Enrollments for Employee Master Data Changes‘ job?

Answer: This job also will create or update the enrollment records for Allowance, Pension and Insurance Benefits only.

4.When an employee is terminated, the Benefits auto enrollment job delimits the enrollment record once the job runs. Why is the new job not delimiting the enrollment record?

Answer: As a leading practice we recommend that customers use the Termination Intelligent Service event for delimiting the enrollment records as it has the flexibility to set up the effective dates (back dated or future dated) while delimiting the enrollment and deduction records.

5.I created my initial enrollments using Benefit auto enrollment job and using the ‘Create or Update Benefit Enrollments for Employee Master Data Changes’ for updates. Now if an employee becomes newly eligible due to a change in pay grade or due to a change in marital status, can this job create enrollment for this employee?

Answer: Yes, ‘Create or Update Benefit Enrollments for Employee Master Data Changes’ job will create enrollments. The change in Job information (Pay grade) or the change in Personal information (Marital status) will be recorded in Benefits employee master data change tracker object (if the rules are configured in Job information and Personal information).

Job will run the eligibility rule for the employee as it finds an entry in the ‘Benefits Employee Master Data Change Tracker’ object and creates enrollment record.

6.Where do I need to assign the rules for the parameters used in eligibility rule?

Answer: Assign the rule at ‘OnPostSave’ for ‘Job information’ parameter and for any MDF object. For all other parameters assign it at ‘OnSave’. For the rules assigned at ‘OnSave’, please make sure this rule is assigned as the last rule in sequence.

7.The ‘Allow automatic updates’ field was not available for manual type Insurance benefit previously but with the H2 2020 release I see this field. Why this change? And is this selection applicable for both jobs?

Answer: Yes, you need to set the ‘Allow Automatic Updates’ field to ‘Yes’ in the benefit for any updates to the enrollment records. This is applicable for both the jobs (‘Benefit Auto Enrollment’ and ‘Create or Update Benefit Enrollments for Employee Master Data Changes’ jobs).

Since we don’t have the Benefits selection in the new job, this job will process the manual insurance benefits for any updates only if the field ‘Allow Automatic Updates’ is enabled.


Thank you.


Global Benefits Product Management

Assigned Tags

      You must be Logged on to comment or reply to a post.
      Author's profile photo Jorge Alberto Diaz Casique
      Jorge Alberto Diaz Casique

      Excellent blog! Congrats and thanks by sharing information! Does It work if employee is transfering since a benefit legal entity to other? for example... Benefit legal entity A has insurance plan Z and employee is transfering to Benefit legal entity B but this Benefit legal entity dont has insurance plan Z, benefit legal entity has insurance plan Y.



      Author's profile photo Bijolesly Kurian
      Bijolesly Kurian
      Blog Post Author

      Hi Jorge Alberto Diaz Casique ,

      Thank you so much for showing interest on this topic. The transfer scenarios across legal entity is not handled with this job. That said, as this is an identified gap, we are working on Intelligent service event for Transfer in H1 2021 release, using this feature the transfer use cases can be achieved (including the transfer from one legal entity to another).

      Please note that the H1 2021 development is not yet complete, and so this feature is not 100% ready and available. As with any development, there is always the chance that we may find something in our testing cycle that would prevent the release. The release information notes are scheduled to come out on April 9th, with our tentative external Q&A session dates on May 5th. I strongly encourage you to use the Q&A forum once ready to dive into more specifics on this enhancement.

      Best Regards,


      Author's profile photo Jorge Alberto Diaz Casique
      Jorge Alberto Diaz Casique

      Hello! Thanks for update! They are excellent news for me! We are implementing global benefit and from june to august We are in configuration phase. I am following your steps!!!!

      Author's profile photo Paco Adrian Paul Pascua
      Paco Adrian Paul Pascua

      As alwasys bijo excelleng blog.

      Author's profile photo Rajesh Babu Narasipudi
      Rajesh Babu Narasipudi

      Hello Bijo,


      Thanks for in-details explanation about Benefit eligibility.

      We have an issue at "Open Enrollment ends"

      Actually, we have configured the Open enrollment ends at 90 days from hire date.

      But it is showing only one month.

      I don't know where we have done wrong.

      But in Employee details the benefits start date showing as 90 days

      Could you please help me out




      Author's profile photo Ahmed Rady
      Ahmed Rady

      Hi Bijo,


      Thank you so much for the great information. I just have a question. If we have retired employees who are eligible for medical/dental/life insurance. The rate charts could change every year and therefor we need the job to consider the retired inactive employee however this is not the case right now. Is there any solution to consider the retired employees in this case so the job can check and update the enrollment instead of delimiting the records?



      Author's profile photo Bijolesly Kurian
      Bijolesly Kurian
      Blog Post Author

      Hi Ahmed Rady ,

      First of all let me clarify one thing, this is not a gap in new jobs. Even in the old job (Benefits auto enrollment) , this use case is not covered.

      You can stop delimiting the enrollment records by skipping it for retirees in the ISC termination event rules. But the rates will not get updated as the jobs process only for active employees. As a workaround, you can use imports to update the enrollments, i believe this activity may require once in a year. You can also submit an influence request with the detailed requirement.



      Author's profile photo Paco Adrian Paul Pascua
      Paco Adrian Paul Pascua

      Hi Bijo,


      This is Paco (Previously from Support), I noticed that the depreciation of the new job was moved from H1 to H2 release, is there a specific reason for this? are there limitations in the new job that might have caused the delay of the depreciation, would love to hear from you again.

      Author's profile photo Bijolesly Kurian
      Bijolesly Kurian
      Blog Post Author

      Hi Paco,

      We see that there are many customers still testing the new jobs and not yet ready in production. So based on customers feedback, we have decided to extend it for one more release.



      Author's profile photo Paco Adrian Paul Pascua
      Paco Adrian Paul Pascua

      Thanks Bijo!

      Author's profile photo Paco Adrian Paul Pascua
      Paco Adrian Paul Pascua

      Hi Bijo


      It seems that if the enrollment type is Manual we are not allowed to set “allow automatic updates to yes” for pension and allowances

      But what if there is a scenario wherein the employee is enrolled in an allowance and suddenly after a data change they become ineligible? I would assume that since allow automatic updates is set to

      No the new tracker job will not make the employee ineligible or will not delimit the benefit enrollment, is this by design?


      Author's profile photo Madhusudan Reddy
      Madhusudan Reddy

      Hi Bijo,

      Thank you so much for the great information.

      We have implemented Benefit auto-enrollment through ISC for hire and rehire and its working great.

      However, the daily scheduled job in provisionig Create or Update Benefit Enrollments for Employee for Master Data Changes is not working as per the client needs.

      Example: We have pay rate changes for employees with Past, Current and future effective dated.  The daily scheduled job working great for Current and future effective dated pay rate changes. But for the past dated changes, the daily Job inserting a new record with the todays date (Job run date) instead of Pay rate change effective date.

      Is there any reason for not considering the Past dated Pay rate effective date and considering the Job run date?

      Any plan to provide the patch/Fix to consider the above scenario?