3357239 - Error with Every competency name in Center of Capabilities is unique (Check ID: CoCDuplicateCompetenciesMappedToSameJdmId) - Talent Intelligence Hub

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.

• SAP SuccessFactors Talent Intelligence Hub
• SAP SuccessFactors Center of Capabilities
• SAP SuccessFactors Job Description Manager
• SAP SuccessFactors Job Profile Builder

1. Navigate to Admin Center > Tools > Check Tool
2. Select the Migration tab
3. See entities pending migration

The system created 2 mappings for the same JDM ID

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:

1. Navigate to Admin Center > Import and Export Data
2. In the Select the action to perform dropdown, select Export Data
3. Select the below options:
   
   • Select Generic Object: JdmJpBMappingEntity
   • Include Inactive Records: Yes
4. Select Export
5. Select View Result
6. Locate the job and select View Details
7. Select Download Status to download the file
8. Reference the JDM ID from your Check Tool file (e.g., 14507)
9. Open the JdmJpBMappingEntity file you downloaded from step 8
10. In Column C of the JdmJpBMappingEntity file, filter for the JDM ID from the Check Tool file (e.g., 14507)
11. 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

1. Navigate to Admin Center > Import and Export Data
2. In the Select the action to perform dropdown, select Export Data
3. Select the below options:
   
   • Select Generic Object: Role-Mapped Competencies
   • Include Inactive Records: Yes
4. Select Export
5. Select View Result
6. Locate the job and select View Details
7. Select Download Status to download the file
8. Open the Role-Mapped Competencies file
9. 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

Engineering can process a script to remove the incorrect mappings only in case the Customer would like to keep the competency used.

Otherwise Customer can remove the competency via Manage data tool.

In case the script is necessary, the process is as follows:

1. 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 described above
2. Customer will add an identifier to the unused competency name (e.g., n/a at the end)
3. Engineering will create a script to delete the mapping for the unused competency from the mapping table
4. Support will create an engineering ticket
5. Engineering will process a script to identify the impacted competencies
6. Support will rename the competency in JDM to the original one via Provisioning:
   1. Provisioning > Competency Libraries
   2. Select the specific competency with n/a and rename it to correct used one.
7. Support can update the correct used competency in CoC by appending a dot to description

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-COC-ADM , Admin Center, Settings, Permissions , LOD-SF-TIH-JPB-MIG , Migration to Job Profile Builder , Problem