JPB and JDM sync issues

Issue with JPB-JDM Sync?

In countries that use a language other than English (en_US) with the default, there may at some point have a synchronization problem between JPB and JDM, causing problems, for example when creating the PM or 360 forms, competencies and behaviors do not appear on the forms.

Some customers faced synchronization issue after changing the default language of their instances. These customers had a default language other than en_US. We couldn’t reproduce the non-sync, but we know how to resolve the issue.

The following are steps to identify where the problem is and how to fix it.

• Verification: The first check to be done is if the mapping of ROLE > “Mapped Job Codes” correctly considering the employee you are creating the form to.

Job Profile Content – Role – Mapping Job Codes

• Action: The job code / job classification mapped must be the job code of the employee generating the form.
  • If EC is not enabled, the mapping must be with the Job Code
  • If EC is enabled, the mapping must be with the Job Classification

Job Profile Content – Role – Mapping Job Codes

• Verification: check the default language of the customer instance (provisioning)

Provisioning – Company Settings > Default Language

• Verification: Identify the default language of the PM form / 360

XML – Form – Default Language

• Action: It is strongly recommended to use the same language for provisioning and forms

• Verification: Check in the instance the translations of competencies and behaviors in the center of capabilities. The same competencies and behaviors must appear in the provisioning with their respective translations.

Center of Capabilities – Translate Competencies

Provisioning – Competencies

• Action: If the translations do not appear identical in the instance (CofC) and provisioning (competencies), you must update the competence in the instance > center of capabilities
• Note: There is no need to duplicate information, just adjust and save to ensure the integration updates the data.

• Verification: Check if the translations appear in the mapping of families and roles in the instance, as well as in the provisioning

Job Profile Content – Families and Roles – Role

Job Profile Content – Role – Map Competencies

Provisioning – Families and Roles

• Action: If the translations do not appear identical in the instance (CofC) and provisioning (families and roles), you must update the Role in the instance > job profile content > families and roles
• Note: There is no need to duplicate information, just adjust and save to ensure the integration updates the data.

If all the checks were done correctly there should be no synchronization issue. To ensure that there are no more problems we suggest using the check tool.

Hope this can be useful and thanks for reading!

Last but not least, I would appreciate it if you could provide your feedback, and if you have any questions feel free to meet me in the comments. I have just started to share my knowledge on SAP SuccessFactors if you want to hear more follow my profile.

Claudia Costa

All images in this post are from SAP SuccessFactors Demo

Further information:

• BLOG – An Introduction to SAP SuccessFactors Platform Components
• BLOG – SAP SuccessFactors Platform Components – Part 2: Using Competencies in the HCM Suite
• BLOG – SAP SuccessFactors Platform Components – Part 3: Family, Roles, Competencies, and Job Codes
• BLOG – SAP SuccessFactors Platform Components – Part 4: Job Profile Builder
• Using Center of Capabilities
• Implementing and Managing Job Profile Builder
• KBA – 2885314 – JPB Data is not Consistent with legacy data
• KBA – 3064628 – JPB Migration Job is Successful but data is missing