2510653 - HRIS Sync: What Value is sent depending on Source / Destination Field Configuration

Symptom

This article explains the different behaviours of the HRIS Sync based on the Source / Destination field type/configuration.

Environment

SAP Successfactors HCM Suite
SAP Successfactors Employee Central

Resolution

HRIS Sync Mapping - Value Output

The system will derive different values depending on the Source and Destination field configuration. Please refer to the below table for further information -:

EC Source Field Configuration	EP Destination Field Configuration	Value in Employee Export	Comments
STRING (Text) Field	STRING (Text) Field	STRING (Text) Value	STRING Value is mapped
Foundation/Custom Object Field	STRING (Text) Field	STRING (Text) Value - "Name (Code)" of the Object value	This is expected behaviour. If you wish to synchronize just the "Name" or "Code" of an Object value (such as the "Code" of the Legal Entity), you will need to implement a custom-string field (as a regular string) in the corresponding HRIS Element (in this example - in jobInfo) and then use a onChange (set on the object field in jobInfo) & onSave Business Rule (set on jobInfo) to set the custom-string field value in jobInfo to be equal to the Name or Code field of the desired Object. Then you can map the custom-string field in the sync-mappings, to the EP field.
Picklist Field	STRING (Text) Field	Picklist Label	The label of the value is synchronized. So in the EP Destination field, the value is static and will not change based on logged in users locale
Picklist Field	Picklist Field	Picklist Option ID	This is expected behaviour - if the destination is also picklist, then the Option ID of the Picklist value will be used instead The benefit of this is that in the EP UI, the value will display in the locale users language. Down side is that in the Employee Export file you will see Option ID and not a label
Date Field	STRING (Text) Field	STRING (Text) Value - Extra Configuration is needed	You can define the format in which the data is converted into a STRING. For example -: <hris-mapping> <hris-field-ref refid=”date-of-birth” date-format=”dd/MMM”/> <standard-element-ref refid=”custom02” /> </hris-mapping> Please refer to article 2386939 - HRIS Sync - Date field
Date Field	Date Field	Date Value (on DB level is stored as YYYY-MM-DD)	Date Value is mapped
Decimal Field	STRING (Text) Field	STRING (Text) Value	Stored as STRING
Numeric Field	STRING (Text) Field	STRING (Text) Value	Stored as STRING
Worker Type Field	STRING (Text) Field	NOT SUPPORTED	Do not map type="worker" fields from EC to EP STRING fields. This is not supported
Worker Type Field	"Role" field (such as hrId, matrixManager, etc)	NOT SUPPORTED	Do not map type="worker" fields from EC to EP Role fields. This is not supported
EC Field	userinfo-element field	SUPPORTED	Please refer to article 2079942 - How to sync Employee Central data to Userinfo Element Fields - Employee Central

PS: If no value is sent from EC to EP for custom mapping (mapping is overriding harcoded sync mapping), then hardcoded sync will happen and value from relevant EC hardcoded mapped field will be synced onto EP hardcoded mapped field. You cannot disable the hardcoded sync unless you overwrite it with a non-null data from EC.

More information can be found in the Employee Central Master implementation guide

Keywords

HRIS Sync, hris sync, hris-sync, HRIS sync, hrissync, Sync, synchronization, EC to EP, EC, EP, hris-mapping, <hris-mapping>, hris-sync-mappings, hris-element-ref, succession-data-model, succession data model, field types , KBA , LOD-SF-EC-HRS , HRIS Sync , LOD-SF-EC , Employee Central , How To

Product

SAP SuccessFactors Employee Central all versions