SAP Knowledge Base Article - Public

3589264 - onChange Rule Doesn't Set Field on Import - Employee Central

Symptom

Business rule is not setting value for a field when importing employee data. There is a onChange rule assigned to a field in the BCUI to set value to another field in the same HRIS element.

"Image/data in this KBA is from SAP internal systems, sample data, or demo systems. Any resemblance to real data is purely coincidental."

Environment

SAP SuccessFactors HCM Suite

Reproducing the Issue

  1. Assign onChange rule to a field A that will set value for a field B;
  2. Import Employee Data with field A;
  3. Check employee profile;
  4. Field A was changed according to the import file but field B stays the same;

Cause

Both fields need to be in the import file. When trying to set B with an onChange rule assign to A, a column for field B needs to be in the import file with no value as system design.

If the column for field B is not in the import file, the rule will trigger but nothing will change in the profile for field B.

Resolution

Add a column for for both fields in the import file and leave the target field with not value. 

Note: To ensure the import file is classified as a change in field A, you must add a value to field A that is different from the existing value in the profile. Otherwise, the rule will not be triggered.

Incorrect: 

Correct: 

Keywords

 Assign onChange rule, set value, Import Employee Data, onChange rule, column, import file, rule trigger, changes in profile, rule not triggered, employee central, successfactors, import error, onchange , KBA , LOD-SF-EC-EDP , Import Employee Data (EC Core only) , Problem

Product

SAP SuccessFactors HCM Core 2411