/support/notes/service/sap_logo.png){kind=logo}
SAP Knowledge Base Article - PublicSymptom
This article provides steps required to prepare your system for Talent Intelligence Hub upgrade in the 1H 2023 Release, on instances using Job Description Manager solution (JDM).
If you are currently using Job Profile Builder to manage Families and Roles, and Center of Capabilities to manage competencies, the information here provided is not valid for your system, so check the KBA 3328015 - Migrating JPB data to Talent Intelligence Hub - 1H 2023.
Environment
- SAP SuccessFactors HXM Suite
- SAP SuccessFactors Job Description Manager (JDM)
- SAP SuccessFactors Talent Intelligence Hub (TIH)
Resolution
With Talent Intelligence Hub users can manage different attributes (competencies, skills and any other custom attribute configured in your instance that are important to your business) in a centralized placed called Growth Portfolio. For more information, check our Administration Guide in SAP SuccessFactors Platform > Using Talent Intelligence Hub.
Important Notes
- Before enabling Talent Intelligence Hub is important to be aware that you cannot revert back to manage competencies in Job Description Manager. Once your system is successfully migrated to Talent Intelligence Hub, competencies are managed under the new framework.
- Only competencies will be migrated to Talent Intelligence Hub framework. You will still be managing Families, Roles, and related mappings under Admin Center > Manage Families and Roles.
- There are no impact on other functionalities related to Job Description Manager (e.g. Writing Assistant, Coaching Advisor), other than competencies.
- Your JDM data for all libraries, competencies and behaviors must be maintained in all locales enabled for your instance, as Talent Intelligence Hub does not support the default locale context.
- Back up your JDM data before running the migration to Talent Intelligence Hub.
Migrating to Talent Intelligence Hub
To prepare your system and data for the enablement of Talent Intelligence Hub in the 1H 2023 Release, make sure to:
- Run JDM checks in Admin Center > Check Tool and fix any errors returned - Check the WIKI page JDM & JPB Check Tools for more details and help fixing the issues you may find;
- 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:
- Job is completed successfully - Go to step "4";
- Job fails - Run checks for Talent Intelligence Hub in Admin Center > Check Tool to verify what needs to be corrected for a successful migration.
- Set up Role-Based Permissions for Talent Intelligence Hub - Check the required permissions in the section Permissions Required for Using Talent Intelligence Hub of our Administration Guide.
For complete information on migrating data from JDM to the new framework, check the section Migrating from Job Description Manager to Talent Intelligence Hub in the Using Talent Intelligence Hub Guide.
Data Validation for Talent Intelligence Hub in Check Tool
After upgrading to Talent Intelligence Hub framework, it is important to run the new checks for the application in Admin Center > Check Tool, to ensure the data was migrated without issues, if the migration job was successful, or to correct any errors, if the migration job failed.
Here is the list of checks available for Talent Intelligence Hub in the Check Tool:
| Check Name | Check ID | Relevant for JDM instance | Description | Fixing Errors Found |
| User Profile UUIDs are valid | UserProfileUUIDValidationCheck | NO | The user profile UUIDs must be valid. The UUID must not be a null value. | Not relevant on JDM instances. Check will be successful with no errors. |
| Use Job Profiles in Requisitions is enabled | UseJobProfilesInReqCheck | NO | Validates prerequisites for enabling Talent Intelligence Hub. For a Job Description Manager 2.0-enabled instance, ensure the “Use Job Profiles in Requisitions” option is enabled in Admin Center > Manage Recruiting Settings. | Not relevant on JDM instances. Check will be successful with no errors. |
| Skills are not mapped to entities in Job Profile Builder | MustNotHaveSkillMappingsWithNullWsmIdCheck | NO | 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. | Not relevant on JDM instances. Check will be successful with no errors. |
| Job Profile Builder Enablement Status. | JPBNotMigratedMandatoryPreCheck | NO | 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 Porifle Builder. | Not relevant on JDM instances. Check will be successful with no errors. |
| SAP SuccessFactors Platform is successfully integrated with SAP SuccessFactors Learning | LMSTenantSealingStatusCheck | YES | 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. |
| Missing competencies data in the mapping table | MissingCompetencyJpbIdsInMappingEntityCheck | NO | 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. | Not relevant on JDM instances. Check will be successful with no errors. |
| Behavior names do not exceed 236 characters | BehaviorNameLengthCheck | YES | 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. Similar to quick fix introduced for Sequence Issue documented in the KBA 2993636. NOTE: Keep a back up of your JDM data before using the Quick Fix option to correct this issue. Alternatively, you can fix the name length issues for the pointed behaviors in your instance by changing them in Admin Center > Manage Competencies, or using the import functionality. |
| Competency names do not exceed 236 characters | CompetencyNameLengthCheck | YES | 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. Similar to quick fix introduced for Sequence Issue documented in the KBA 2993636. NOTE: Keep a backup of your JDM data before using the Quick Fix option to correct this issue. Alternatively, you can fix the name length issues for the pointed competencies in your instance by changing them in Admin Center > Manage Competencies, or using the import functionality. |
| Migration of competencies in job requisitions from Job Description Manager 1.0 to Job Description Manager 2.0 is complete | MigrateJDM1CompetenciesJobCompleted | NO | Validates if the “Migrate Competencies in Job Requisitions from JDM1.0 to JDM2.0” Job is running. | Not relevant on JDM instances. Check will be successful with no errors. |
| Missing Job Description Manager data reference in the mapping entity | MissingJdmIdsInMappingEntityCheck | NO | 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. | Not relevant on JDM instances. Check will be successful with no errors. |
NOTE: the solution here presented is an overall representation of the target data, you may have a more complex and specific scenario in your system that will require your attention to apply the potential solution presented here.
See Also
Keywords
2305, release, 1H 2023, TIH, WSM, JDM, JDM1.0, migrate, upgrade, enablement, preparing, readiness , KBA , LOD-SF-TIH-JDM , Job Description Manager , How To