Symptom
This article explains how HRIS Sync works for compInfo in EC.
Environment
SAP SuccessFactors Employee Central
Resolution
Hard-Coded Sync
The synchronization of compInfo data to EP works as such. Currently there are 4 fields in the compInfo hris-element which have hard-coded sync mappings -:
HRIS Element | EC Fields |
compInfo |
|
Form more information on the order in which data is synchronized, please refer to KBA 2505747 - HRIS Sync - HRIS Sync Job - Order in which Elements are Synchronized
What is the purpose of these Hard-Coded Sync Mappings?
Compensation Management and Variable Pay modules both have a direct integration with Employee Central, so Compensation Info data does not typically flow from Compensation Information > Basic User Data (UDF) > Compensation, but instead goes from EC > Compensation Management (for example). That being said, you may still want certain data to synchronize (via HRIS Sync) from compInfo to the SAP SuccessFactors HCM Suite.
-
For more information please review the article 2507190 - HRIS Sync: Downstream Impacts
Custom Sync Mappings for compInfo (overriding the hard-coded mappings)
Some hard-coded mappings can be overridden but not all. The ones you can over-ride are as follows (but please be aware of the mentioned caveats if you do) -:
EC Job Info Source Field ID | EP (standard-element) Destination Field ID | Example XML of what you can do | Comments |
pay-grade | payGrade |
<hris-element-ref refid="jobInfo"> <hris-mapping> |
The field "compInfo.pay-grade" is deprecated in Employee Central 2.0. Instead Pay Grade information is now captured in Job Information (the jobInfo hris-element) Therefore, overriding the hard-coded mapping may be needed |
salary | salary |
N/A |
Salary information is captued in the "payComponentRecurring" hris-element. Therefore this mapping is obsolete. Employee Central to Compensation & Variable Pay modules is handled with a direct integration. Please refer to the implementation guides for each -: |
job-level | jobLevel |
<hris-element-ref refid="jobInfo"> <hris-mapping> |
The field "compInfo.job-level" is is not often used in Employee Central 2.0. Instead Job Level information is typically captured in Job Information (the jobInfo hris-element) as a STRING value. The STRING field used to capture this value in EC is usually set from the "Pay Grade Level" field on the Pay Grade object using Propagation XML. |
bonus-target | bonusTarget |
N/A |
Salary information is captued in the "payComponentRecurring" hris-element. Therefore this mapping is obsolete. Employee Central to Compensation & Variable Pay modules is handled with a direct integration. Please refer to the implementation guides for each -: |
Which fields should I not override?
There arent any fields that specifically you should not override in compInfo. But as per the above table, you will want to plan your Compensation Management and Varliabe Pay integration carefully, given the above caveats. For Downstream Impacts - again refer to 2507190 - HRIS Sync: Downstream Impacts - for guidance
Best Practice Recommendations
Please plan any mappings from Compensation Information carefully. Though it is true that Compensation Management has a direct integration with Employee Central, the data is only sent from EC to the Compensation form when it is created. After that point the only updates that would occur are those fields that are mapped via HRIS Sync.
For more information on the integration between Employee Centra and Compensation/Variable Pay, please refer to the implementation guides -:
You may also want to review the content in the article - 2507190 - HRIS Sync: Downstream Impacts
More information can be found in the Employee Central Master implementation guide
See Also
Keywords
compInfo, hris sync, ec sync, sync, synchronization, hris-mapping, hris-sync-mappings, hris sync, succession data model, xml, sdm, employee central, ec, sync, compensation information, FAQ , KBA , LOD-SF-EC-HRS , HRIS Sync , LOD-SF-EC-CMP , Compensation Information & One-Time Bonus , How To