Symptom
After running the Migration Check for Talent Intelligence Hub, issues are found for the check "CoCDuplicateCompetenciesMappedToSameJdmId".
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 Talent Intelligence Hub
- SAP SuccessFactors Center of Capabilities
- SAP SuccessFactors Job Description Manager
- SAP SuccessFactors Job Profile Builder
Reproducing the Issue
- Navigate to Admin Center > Tools > Check Tool
- Select the Migration tab
- See entities pending migration
Cause
The system created 2 mappings for the same JDM ID
Resolution
Engineering can process a script to remove the incorrect mappings:
- Support will create an engineering ticket
- Engineering will process a script to identify the impacted competencies
- Customer will need to provide confirmation of which competency is no longer used. Some customers may have it marked as INACTIVE.
- Note: If you're unsure whether a competency has been used by any module, you can review Identify if Competency is Used in Another Module below Step 7
- Customer will add an identifier to the unused competency name (e.g., n/a at the end)
- Engineering will create a script to delete the mapping for the unused competency from the mapping table
- Support will rename the competency in JDM to the original one via Provisioning:
- Provisioning > Competency Libraries
- Select the specific competency with n/a and rename it to correct used one.
- Support can update the correct used competency in CoC by appending a dot to description
Identify if Competency is Used in Another Module
I. Locate the External ID of the Competencies
Prerequisite:
- Ensure you have a copy of the Check Tool CoCDuplicateCompetenciesMappedToSameJdmId results file (will be referred to as Check Tool file)
Procedure:
- Navigate to Admin Center > Import and Export Data
- In the Select the action to perform dropdown, select Export Data
- Select the below options:
- Select Generic Object: JdmJpBMappingEntity
- Include Inactive Records: Yes
- Select Export
- Select View Result
- Locate the job and select View Details
- Select Download Status to download the file
- Reference the JDM ID from your Check Tool file (e.g., 14507)
- Open the JdmJpBMappingEntity file you downloaded from step 8
- In Column C of the JdmJpBMappingEntity file, filter for the JDM ID from the Check Tool file (e.g., 14507)
- Once filtered, the External Code can be located under Column F and this is what you'll use for the next section (e.g., 1000076)
II. Identify If A Competency Is Used In Other Modules
- Navigate to Admin Center > Import and Export Data
- In the Select the action to perform dropdown, select Export Data
- Select the below options:
- Select Generic Object: Role-Mapped Competencies
- Include Inactive Records: Yes
- Select Export
- Select View Result
- Locate the job and select View Details
- Select Download Status to download the file
- Open the Role-Mapped Competencies file
- In Column D of the Role-Mapped Competencies file, filter for the External ID from the previous section (e.g., 1000076)
- If you do not have results, the competency has not been used in any module
- If you do have results, the competency has been used in at least one module
Keywords
success factors, SF, SFSF, COC, TIH, migrate, issues, PTCH-41572, WSM-21319 , KBA , LOD-SF-TIH-MIG , Migration to Talent Intelligence Hub , LOD-SF-TIH-JDM , Job Description Manager , LOD-SF-TIH-JPB-MIG , Migration to Job Profile Builder , LOD-SF-TIH-COC-ADM , Admin Center, Settings, Permissions , Problem
Product
Attachments
Pasted image.png |
Pasted image.png |
Pasted image.png |