How To Fix CNV_CMIS_U_20066 - BC Set information already exists in central system

SAP Error Message - Details

• Message type: E = Error

• Message class: CNV_CMIS_U_20 - CMIS Upg: Messages from XPRA functions

• Message number: 066

• Message text: BC Set information already exists in central system

What causes this issue?

One step within the BC Set activation is to determine the active BC Sets
in the receiver system and store it temporarily in the central system.
The program determined that there already exists some BC Set information
in the central system which could mean that a parallel project is
ongoing.

System Response

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

How to fix this error?

Check if there is a parallel project (CMIS or any other migration
project with an integrated upgrade) in process. If yes, you must ensure
that the BC Set activation is executed one after the other. The
information of the BC Sets is only stored once in the central system.
If you are sure that you are the only project that is going to
subsequently activate the BC Sets, you can use the troubleshooting
functionality, assigned to this activity, to initialize the BC Set
information in the central system at first. After the initialization,
you can start the activation of the BC Sets again.

Procedure for System Administrators

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message CNV_CMIS_U_20066 - BC Set information already exists in central system ?

  The SAP error message CNV_CMIS_U_20066 indicates that there is an issue with the Business Configuration Set (BC Set) information already existing in the central system. This typically occurs during the process of data migration or configuration where the system is trying to create or import a BC Set that already exists.
  Cause:
  
  Duplicate BC Set: The error is primarily caused by an attempt to create or import a BC Set that has already been defined in the system.
  Incorrect Configuration: There may be a misconfiguration in the migration or import process that leads to the system trying to create a BC Set that is already present.
  Transport Issues: If the BC Set was transported from another system, it might already exist in the target system.
  
  Solution:
  
  
  Check Existing BC Sets: 
  
  Use transaction code SIMG or SPRO to navigate to the relevant configuration area and check if the BC Set already exists.
  If it does exist, you may need to modify or delete the existing BC Set if it is not needed.
  
  
  
  Adjust Import Process:
  
  If you are importing data, ensure that the import process is correctly configured to avoid attempting to create existing BC Sets.
  Review the import logs to identify any discrepancies.
  
  
  
  Use Transaction Code:
  
  You can use transaction code CNV_MBT to manage BC Sets and check for existing entries.
  
  
  
  Consult Documentation:
  
  Review the SAP documentation related to the specific BC Set you are working with to understand its requirements and constraints.
  
  
  
  Contact SAP Support:
  
  If the issue persists and you cannot resolve it, consider reaching out to SAP support for further assistance. They may provide insights specific to your system configuration.
  
  
  
  Related Information:
  
  BC Sets: Business Configuration Sets are used in SAP to manage configuration settings in a structured way, allowing for easier transport and management of settings across different systems.
  Data Migration: This error often arises during data migration projects, especially when using tools like SAP S/4HANA Migration Cockpit or SAP Data Services.
  Transaction Codes: Familiarize yourself with relevant transaction codes such as SIMG, SPRO, and CNV_MBT for managing configurations and BC Sets.
  
  By following these steps, you should be able to identify the cause of the error and implement a solution to resolve it.