2336779 - Invalid HRIS Sync Mapping Configuration "HRIS Sync Job Failure"

Symptom

Daily or Full HRIS Sync Job is not working
Daily or Full HRIS Sync Job failure with KB-1
Invalid HRIS Sync Mapping Configuration

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
SAP Successfactors Employee Central - HRIS Sync

Resolution

Summary on HRIS sync

Employee Central (EC) provides an effectively dated data repository to house employee’s HR information like Job, Salary, etc. This will gradually become the centralized data repository. At the same time, EC uses the HRIS Synch mechanism to sync data stored in EC tables back to user directory tables. The sync from EC tables to legacy tables is one-way.

Also, there are 3 ways to trigger HRIS sync.

Real-time sync integration by UI operation

Most EC UI operations have integrated with HRIS sync such as new hire, MSS job change, personal info change, etc. to real-time sync the specific HRIS data from the UI to user directory tables.
Notes: For effective dated objects, only past day’s records / current day’s records will be synced by real-time sync integration. Future day’s records will be synced when the future day becomes current in running HRIS sync job.

HRIS Sync Job

User can schedule a regular (i.e. daily) HRIS sync job in ‘Manage Scheduled Jobs’ in provision and then the HRIS sync job will run as scheduled.

EC data import

When HRIS Element (Employee Central data) is imported, it will also trigger HRIS sync job run if there is at least one HRIS Sync Job configuration in ‘Manage Scheduled Jobs’ and the status is submitted.
Only one HRIS sync job can run at a time. It means if there is in-progress HRIS sync job, another HRIS sync job won't be triggered before the running HRIS sync completes.

Example of Invalid HRIS Sync Mapping configuration

Please View This KBA: 2172427 - HRIS Sync - Data Synchronization From EC to EP - Hard Coded Sync Mappings

2493579 - Employee Central: Person/User IDs Used Within Employee Central - SuccessFactors Employee Profile
Chapter: Differentiating Between Person ID, User ID, and User Name in Employee Central

To avoid issues in the system, do not map HRIS fields to the following standard elements:

loginMethod
managerId
username
userId
jobCode
hireDate

Map custom field to username

username should be unique. If there is duplicated custom-string2 values, Hris Sync Job will fail.

Example: Below configuration will cause job failure.

PersonInfo:

<hris-element-ref refid="personInfo">

<hris-mapping >

<hris-field-ref refid="custom-string2"/>

<standard-element-ref refid="username"/>

</hris-mapping>

</hris-element-ref>

</hris-sync-mappings>

EmailInfo:

Please do not configure/map the email-address of any type to the "username" field in Employee Profile

As there is no "uniqueness" check available on EC side, the system can try to pass non-unique values to "username" which would result in UI/Import errors when attempting to do so
2336779 - Invalid HRIS Sync Mapping Configuration " HRIS Sync Job Failure"

<hris-element-ref refid="emailInfo">

<hris-mapping entity-type="B" >

<hris-field-ref refid="email-address"/>

<standard-element-ref refid="username"/>

</hris-mapping>

</hris-element-ref>

<hris-element-ref refid="personInfo">

<hris-mapping>
<hris-field-ref refid="person-id-external"/>
<standard-element-ref refid="username"/>
</hris-mapping>

Note:

Do NOT configure username as a standard-element-ref. View Guide: Fields Hard-Coded for Syncing
Do NOT map the standard elements userId, managerId, jobCode, and hireDate. Doing so causes issues in the system.
View: 2328243 - HRIS Sync: Configuring a sync-mapping from an EC field to username (EP)

Map phone-number field with self-defined phone type.

Hris Sync syncs phone number by picklist option external code.
Otherwise, phone number will not by synced.

Here are the expected external code：

Homephone: H
Businessphone: B
Cellphone: C
Fax: F

Example: Below configuration will cause job failure.

<hris-element-ref refid="phoneInfo">

<hris-mapping entity-type="M" >

<hris-field-ref refid="phone-number"/>

<standard-element-ref refid="cellPhone"/>

</hris-mapping>

<hris-mapping entity-type="W1" >

<hris-field-ref refid="phone-number"/>

<standard-element-ref refid="businessPhone"/>

</hris-mapping>

</hris-element-ref>

Map field to userId

Should not map any field to userId.

Example: Below configuration will cause job failure.

<hris-element-ref refid="personInfo">

<hris-mapping >

<hris-field-ref refid="person-id-external"/>

<standard-element-ref refid="userId"/>

</hris-mapping>

Please refer to KBA 2512703 - HRIS Sync: Biographical Info Sync FAQ - for further information

person-id-external : Although when hiring a new employee, the Person ID is also used by Employee Central to create the System UserID, this is not handled by the HRIS Sync feature.

Once the UserID is created it cannot be changed (where as Person ID can be). Therefore there is a mapping of sorts, but it is not handled by the HRIS Sync. This is instead hard-coded into the application and only comes into effect when creating the new employee.

Please note that it is not nessecary, nor is it recommended to map "person-id-external" with the userId field. For example - do not do this -:

<hris-mapping >
<hris-field-ref refid="person-id-external"/>
<standard-element-ref refid="userId"/>
</hris-mapping>

For a more comprehensive overview of what to do and not to do, please refer to KBA 2512703

<hris-element-ref refid="personInfo">

<hris-mapping>
<hris-field-ref refid="person-id-external"/>
<standard-element-ref refid="empId"/>
</hris-mapping>

Please Note: This mapping should not be used if you use sm-mapping in candidate template. More information can be found on KBA: 3033802

Map multiple EC fields to one EP field

Should not map multiple EC fields (EC hris-element-ref) to one standard-element field.
View : To avoid data inconsistency, don't map multiple HRIS fields to the same Employee Profile field.

Example: Below configuration will cause job failure.

<hris-element-ref refid="employmentInfo">

<hris-mapping >

<hris-field-ref refid="start-date"/>

<standard-element-ref refid="custom15"/>

</hris-mapping>

</hris-element-ref>

<hris-element-ref refid="emailInfo">

<hris-mapping entity-type="P" >

<hris-field-ref refid="email-address"/>

<standard-element-ref refid="custom15"/>

</hris-mapping>

</hris-element-ref>

Map field to loginMethod

loginMethod is an internal field and It is not allowed to be synced from EC. View: 2806846 - Unable to update the Login Method field in People Profile
Login Method field in People Profile is not recommended, because to maintain a value in Employee Central and update the same value (login method) in UDF a custom HRIS Sync Mapping would need to be maintained. We currently do not support any HRIS Sync Mappings for the loginMethod field.

Example: Below configuration will cause job failure. <hris-mapping >

<hris-field-ref refid="custom-string52"/>

<standard-element-ref refid="loginMethod"/>

</hris-mapping>

FAQ - Additional Information

Q) Where can I get information on this from the Guide?

A) Guide: Implementing Employee Central Core

Chapter: Human Resource Information System (HRIS) Synchronization

Q) How can I conduct Hris sync overriding?

A) Chapter: Overriding Hard-Coded Sync Mappings

We strongly recommend that you do not override hard-coded HRIS Sync mappings in the Succession Data Model. But if your business processes require the override, note the cautions and rules while adding custom HRIS Sync mappings.

Keywords

HRIS Sync Mapping, Full HRIS Sync, Daily HRIS Sync, loginMethod, userId, username, invalid, KB-1, Failure, failed, Invalid HRIS , KBA , LOD-SF-EC-HRS , HRIS Sync , How To

Product

SAP SuccessFactors Employee Central all versions ; SAP SuccessFactors HCM suite all versions

2336779 - Invalid HRIS Sync Mapping Configuration "HRIS Sync Job Failure"

Symptom

Environment

Resolution

See Also

Keywords

Product

Legal

Follow