SAP Knowledge Base Article - Public

2510530 - Employee Central - Job Info HRIS Sync

Symptom

This article explains how HRIS Sync works for jobInfo in EC.

"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 HXM Suite
  • SAP SuccessFactors Employee Central

Resolution

Hard-Coded Sync

The synchronization of jobInfo data to EP works as such. Currently there are 8 fields in the jobInfo hris-element which have hard-coded sync mappings -:

HRIS Element EC Fields Sync Order 
jobInfo
  • emplStatus (hidden in XML)

9
  •  manager-id

10
  • job-code
  • job-title
  • department
  • division
  • location
  • timezone

11

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?

These fields have a hard-coded sync mapping because they all have Downstream Impacts to other areas of the SAP SuccessFactors HCM Suite. Some of the fields can be overridden in sync-mapping configuration, and others cannot.

Custom Sync Mappings for jobInfo (overriding the hard-coded mappings) View Guide:Hard-Coded for Syncing

Some hard-coded mappings can be overridden but not all. The ones you can over-ride are -:

 EC Job Info Source Field ID EP (standard-element) Destination Field ID Example XML of what you can do Comments
department department

<hris-mapping>
    <hris-field-ref refid="company"/>
    <standard-element-ref refid="department"/>
</hris-mapping>

<hris-mapping>
    <hris-field-ref refid="department"/>
    <standard-element-ref refid="custom10"/>
</hris-mapping>

If you are overriding a hard-coded sync mapping, it is wise to ensure that you are still synchronizing the original source to another field. As per the example on the left -:

  • EC "company" field is sync'ed to EP "department"
  • EC "department" field is sync'ed to EP "custom10"
division division

<hris-mapping>
    <hris-field-ref refid="business-unit"/>
    <standard-element-ref refid="division"/>
</hris-mapping>

<hris-mapping>
    <hris-field-ref refid="division"/>
    <standard-element-ref refid="custom11"/>
</hris-mapping>

If you are overriding a hard-coded sync mapping, it is wise to ensure that you are still synchronizing the original source to another field. As per the example on the left -:

  • EC "business-unit" field is sync'ed to EP "division"
  • EC "division" field is sync'ed to EP "custom11"
location location

<hris-mapping>
    <hris-field-ref refid="cost-center"/>
    <standard-element-ref refid="location"/>
</hris-mapping>

<hris-mapping>
    <hris-field-ref refid="location"/>
    <standard-element-ref refid="custom12"/>
</hris-mapping>

If you are overriding a hard-coded sync mapping, it is wise to ensure that you are still synchronizing the original source to another field. As per the example on the left -:

  • EC "cost-center" field is sync'ed to EP "location"
  • EC "location" field is sync'ed to EP "custom12"
job-title title

<hris-mapping>
    <hris-field-ref refid="local-job-title"/>
    <standard-element-ref refid="title"/>
</hris-mapping>

<hris-mapping>
    <hris-field-ref refid="job-title"/>
    <standard-element-ref refid="custom13"/>
</hris-mapping>

Please note that in multiple UI's (such as My Employee Files, People Search > Quick Card and Org Chart) will use the "title" standard-element to display the persons Job Title. By default "job-title" is synchronized here, but this can be over-ridden if you require a different value other than job-title to be used to define the "title" of the employee

Note that is no recommended to override this the standard 'job-title' to 'title' mapping with 'position' to 'title' as this can lead to not sync to employee profile as expected.
location.corporateAddress.country country

<hris-mapping>
    <hris-field-ref refid="country-of-company"/>
    <standard-element-ref refid="country"/>
</hris-mapping>

There is a hard-coded synchronization between Location > Corporate Address > Country and the Country. You can over-ride this but only with a valid source field (not a custom picklist or such). Therefore in this scenario we would only recommend over-riding the standard-element "country" with the value from Job Info "country-of-company" (which is a value typically set by Legal Entity > countryOfRegistration). Please refer to article 2618726

Which fields should I not override?

There are 2 sync-mappings that you should never over-ride or duplicate. The reason is that doing so will cause data not to synchronize correctly and will lead to further Downstream Impacts - again refer to 2507190 - HRIS Sync: Downstream Impacts - for guidance

EP (standard-element) Destination Field Example XML of what not to do Comments
managerId

<hris-mapping >
    <hris-field-ref refid="manager-id"/>
    <standard-element-ref refid="managerId"/>
</hris-mapping>

OR

<hris-mapping >
    <hris-field-ref refid="custom-string29"/>
    <standard-element-ref refid="managerId"/>
</hris-mapping>

This will lead to invalid data being set in the managerId field in EP, which will potentially lead to

  • User is unable to log in - Invalid Manager
  • Performance Forms do not move to new Manager assigned in EC Job Information
  • Please refer to KBA 2174070 for further information
    • Do NOT map the standard elements userId, managerId, jobCode, and hireDate. Doing so causes issues in the system.
jobCode

<hris-mapping >
   <hris-field-ref refid="job-code"/>
   <standard-element-ref refid="jobCode"/>
</hris-mapping>

OR

<hris-mapping >
   <hris-field-ref refid="custom-string27"/>
   <standard-element-ref refid="jobCode"/>
</hris-mapping>

If you map a different field (or even duplicate the same mapping) to jobCode in EP, then this will cause the job-code from EC not to map to jobCode field in EP

The downstream impacts are -:

  • Performance Management: Performance Forms will not populate the correct Competency (or will not populate the Competencies at all)
    • When Employee Central is enabled, all of the Families and Roles (the Roles) will need to be re-mapped to EC Job Classifications.
    • If the full string ("Name (Code)") is not passed to EP field jobCode, then the system will not match the jobCode with a Role in Families and Roles.
    • Please refer to KBA 2080013 for further information
      • Do NOT map the standard elements userId, managerId, jobCode, and hireDate. Doing so causes issues in the system.
emplStatus

<hris-mapping >
   <hris-field-ref refid="emplStatus"/>
   <standard-element-ref refid="status"/>
</hris-mapping>
  • Do not map jobInfo field "emplStatus" to another standard-element field

This is because this hard-coded mapping controls whether the Basic User Data (the User Account) is "active" or "inactive".

For more information on the "Status" sync, please refer to KBA 2505526 for further guidance

Best Practice Recommendations

Please plan any mappings from Job Information carefully. As Job Information is updated more often then most other Employee Central data, any standard-elements which are hard-coded or have custom-mapings defined from jobInfo will be updated more often.

These are typically used to grant Permissions or build Reports, Launch Performance or Compensation forms, therefore any changes to these mappings should be carefully considered as there might be further Downstream Impacts.

 

Frequently Asked Questions

Q) Which fields are hardcoded to be synchronized?
A) See the table above for the list of Hard-Coded Sync Mappings

View: Hard-Coded for Syncing

  • Use the table here to determine which fields are hard-coded to be synced by the system.
  • HRIS fields with visibility="none"aren’t synced. The rule applies to both hard-coded (exceptions are noted where relevant) and configurable sync mapping.

Caution

  • Do NOT configure username as a standard-element-ref.
  • Do NOT map the national ID or minority fields to custom fields.
  • Do NOT map the standard elements userId, managerId, jobCode, and hireDate. Doing so causes issues in the system.

See Also

  • 2080728 - Employee Central: What is HRIS Sync?
  • 2328243 - HRIS Sync: Configuring a sync-mapping from an EC field to username (EP)
  • 2172427 - HRIS Sync - Data Synchronization From EC to EP - Hard Coded Sync Mappings
  • 2080730 - Employee Central: HRIS Sync - Troubleshooting Guide
  • 2336779 - Invalid HRIS Sync Mapping Configuration "HRIS Sync Job Failure"
  • 2505747 - HRIS Sync - HRIS Sync Job - Order in which Elements are Synchronized
  • 2507190 - HRIS Sync: Downstream Impacts
  • 3210602 - Hourly Daily Hris Sync casing Importing employee data such us causing Job Information failure
  • 2512703 - Employee Central - Biographical Info HRIS Sync 

Keywords

jobInfo, hris sync, ec sync, sync, synchronization, hris-mapping, hris-sync-mappings, hris sync, succession data model, xml, sdm, employee central, ec, sync, job information, FAQ , KBA , LOD-SF-EC-HRS , HRIS Sync , LOD-SF-EC-JOB , Job Information , Problem

Product

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