/support/notes/service/sap_logo.png){kind=logo}
SAP Knowledge Base Article - PublicSymptom
This article provides steps required to prepare your Job Profile Builder (JPB) system for the Talent Intelligence Hub upgrade.
If you are currently using Job Description Manager to manage Families, Roles, and Competencies, the information here provided is not valid for your system, so check the KBA 3327912 - Migrating JDM data to Talent Intelligence Hub - 1H 2023.
Environment
- SAP SuccessFactors Job Profile Builder
- SAP SuccessFactors Talent Intelligence Hub
Resolution
With Talent Intelligence Hub (TIH), users can manage different attributes (competencies, skills and any other custom attribute) that are important to your business in a centralized place called Growth Portfolio. For more information, check our Administration Guide in SAP SuccessFactors Platform > Using Talent Intelligence Hub.
Important Notes
- Before enabling TIH, please be aware that you cannot revert back to Manage Competencies in Job Profile Builder (JPB). Once your system is successfully migrated to TIH, competencies are managed under the new framework.
- Only competencies will be migrated to the TIH framework. You will still manage Job Profiles, Families, Roles, and related mappings under Admin Center > Manage Job Profile and Manage Job Profile Content.
- At this time, Skills cannot be migrated to TIH. Check the Restrictions column in Decision Matrix for Job Profile Builder to Talent Intelligence Hub Migration.
- There are no impacts on other functionalities related to JPB (e.g. Writing Assistant, Coaching Advisor) other than competency entity.
- Your JPB data for all libraries, competencies, behaviors, categories, and groups must be maintained in all locales enabled for your instance. TIH does not support the default locale context.
- Back up your JPB data before running the migration to TIH.
Still Need Help? If you need assistance with the migration, customers can exchange experiences with each other and ask questions of our migration and adoption experts in a new Work Zone group. In order to be admitted into the group, please send an email to SAP_SF_Product_Advisory@sap.com. All group members will also be invited to Office Hours calls, that will take place from time to time, and according to necessity. More information is posted in Everything you need to know about: SAP SuccessFactors Talent Intelligence Hub.
Migrating to Talent Intelligence Hub
To prepare your system and data for the enablement of Talent Intelligence Hub, follow the below steps:
- Migration from JDM to JPB was completed successfully for instances using JDM and had pre-existing data. Please review JDM to JPB Migration Scenarios and Best Practices for more details and help migrating JDM data to JPB.
- Run JPB checks in Admin Center > Check Tool and fix any errors returned. Please review JDM & JPB Check Tools for more details on fixing the issues you may find.
- Run the TIH checks below in Admin Center > Check Tool and fix any errors returned
- Enable Talent Intelligence Hub in Admin Center > Upgrade Center. Carefully read the information for the Talent Intelligence Hub upgrade.
- Check if migration job is completed successfully. If the job fails, run checks for Talent Intelligence Hub in Admin Center > Check Tool to verify what needs to be corrected.
- Set up Role-Based Permissions for Talent Intelligence Hub. Check the required permissions in the section Permissions Required for Using Talent Intelligence Hub.
For complete information on migrating data from JPB to the new framework and conditions for migrating competencies maintained in Center of Capabilities, check the section Migrating from Job Profile Builder to Talent Intelligence Hub in the Using Talent Intelligence Hub Guide.
Data Validation for Talent Intelligence Hub in Check Tool
Before upgrading to the Talent Intelligence Hub framework, it is important to run the checks in Admin Center > Check Tool to ensure the data will be migrated without issues. Here is the list of checks available for Talent Intelligence Hub in the Check Tool:
| Check Name | Check ID | Description | Fixing Errors Found |
| Competency names do not exceed 236 characters | CompetencyNameLengthCheck | The competency names have an upper limit of 236 characters. The competencies that exceed 236 characters will not be migrated from Center of Capabilities. |
Quick Fix option is available for this check, and users with granted permission for the action can correct the issue completing the steps on the Check Tool screen for the check. Competency Names will be truncated to 236 characters automatically. Supporting KBA: |
| Missing Job Description Manager data reference in the mapping entity | MissingJdmIdsInMappingEntityCheck | During Job Description Manager to Job Profile Builder migration, a mapping entity is created to store the Job Description Manager and Job Profile Builder reference IDs. Sometimes, due to technical issues, mapping for some of the Job Description Manager references is not created in the system. |
The data was missed during JDM to JPB migration job. Supporting KBA: |
| Migration of competencies in job requisitions from Job Description Manager 1.0 to Job Description Manager 2.0 is complete | MigrateJDM1CompetenciesJobCompleted | Validates if the “Migrate Competencies in Job Requisitions from JDM1.0 to JDM2.0” Job is running. |
When you enable the setting "Use Job Profiles in Requisitions" in Admin Center > Manage Recruiting Settings, the action triggers the background job "Migrate Competencies in Job Requisitions from JDM1.0 to JDM2.0", to bring in the competencies from JDM to JPB. Supporting KBA: |
| Missing competencies data in the mapping table | MissingCompetencyJpbIdsInMappingEntityCheck | During Center of Capabilities to Talent Intelligence Hub migration, a mapping entity is created to store the Center of Capabilities and Talent Intelligence Hub reference IDs. Sometimes, due to technical issues, mapping for some of the competency references from Center of Capabilities is not created in the system. |
Quick Fix option is available for this check, and users with granted permission for the action can correct the issue completing the steps on the Check Tool screen for the check. Competency mapping entries will be automatically populated for missing ones in JdmJpbMapping table. Supporting KBA: |
| Use Job Profiles in Requisitions is enabled | UseJobProfilesInReqCheck | Validates prerequisites for enabling Talent Intelligence Hub in JPB instances using Job Requisitions (RCM). |
If it returns with an error, the setting “Use Job Profiles in Requisitions” is not enabled in Admin Center > Manage Recruiting Settings. Supporting KBA: |
| SAP SuccessFactors Platform is successfully integrated with SAP SuccessFactors Learning | LMSTenantSealingStatusCheck | This check is visible only for Learning enabled instances. By default, any newly provisioned SAP SuccessFactors Learning tenants will be pre-integrated with an SAP SuccessFactors Platform tenant. However, the integration configurations in the tenant will be read-only. |
Ensure that the integration between SAP SuccessFactors Platform and SAP SuccessFactors Learning is successful. Supporting KBAs: |
| Behavior names do not exceed 236 characters | BehaviorNameLengthCheck | The behavior names have an upper limit of 236 characters. The behaviors that exceed 236 characters will not be migrated from Center of Capabilities. |
Quick Fix option is available for this check, and users with granted permission for the action can correct the issue completing the steps on the Check Tool screen for the check. Behaviors Names will be truncated to 236 characters automatically. Supporting KBA: |
| Job Profile Builder Enablement Status. | The migration status of Job Profile Builder is different from the migration status. Job Profile Builder can be enabled even before the migration to Job Profile Builder succeeds. This check validates the status of the migration and enablement of Job Profile Builder. |
JDM to JPB migration is not successful in your instance, although JPB is enabled and being used already. Supporting KBA: | |
| Skills are not mapped to entities in Job Profile Builder | MustNotHaveSkillMappingsWithNullWsmIdCheck | In Job Profile Builder, skills can be mapped to entities such as roles, families, or positions. This check validates whether a mapping exists for skills or not. If the skill is not mapped to any entities in Job Profile Builder, the check passes without an error. |
The migration of skills and skill mappings, from Job Profile Builder to Talent Intelligence Hub is not supported. Supporting KBA: |
| User Profile UUIDs are valid |
| The user profile UUIDs must be valid. The UUID must not be a null value. |
This is an ID generated by the system. It can't be changed and ensures that the object has a stable ID for integration purposes. UUID stands for "Universally Unique Identifier". Supporting KBA: |
See Also
Keywords
release, TIH, WSM, JPB, JDM2.0, migrate, upgrade, enablement, preparing, readiness, checks, errors, migrating, preparing , KBA , LOD-SF-TIH-MIG , Migration to Talent Intelligence Hub , LOD-SF-TIH-JPB-MIG , Migration to Job Profile Builder , How To
/support/notes/service/facebook.svg)
/support/notes/service/twitter.svg)
/support/notes/service/youtube.svg)
/support/notes/service/linkedin.svg)
/support/notes/service/instagram2.svg)