How To Fix CNV20200372 - Assigned &1 &2 are not merged

SAP Error Message - Details

• Message type: E = Error

• Message class: CNV20200 - Messages for development class CNV_20200

• Message number: 372

• Message text: Assigned &1 &2 are not merged

What causes this issue?

Company codes &V3& are merged.
Assigned &V1& &V2& are not merged.

System Response

Either error or warning (depending on scenario).

How to fix this error?

Check the mapping and correct it if necessary.
As a rule, it is mandatory to merge assigned objects as well.
However there are the following exceptions from this rule:
For company codes for number assignment:
Find out if it is really correct that the company codes should be merged
without merging the company codes for number assignment (domain BURKSN),
and if any accompanying activities are required.
For credit control areas:
Find out if it is really correct that the company codes should be merged
without merging the credit control areas, and if any accompanying
activities are required with regard to credit management.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message CNV20200372 - Assigned &1 &2 are not merged ?

  The SAP error message CNV20200372, which states "Assigned &1 &2 are not merged," typically occurs during data migration or conversion processes, particularly when using the SAP S/4HANA Migration Cockpit or similar tools. This error indicates that there are issues with the merging of data records, often related to master data or transactional data that should be consolidated but are not due to inconsistencies or conflicts.
  Cause:
  
  Data Inconsistencies: The records that are supposed to be merged may have conflicting or inconsistent data, such as different values in key fields.
  Missing Relationships: There may be missing relationships or dependencies between the records that need to be merged.
  Incorrect Mapping: The mapping configuration for the data migration may not be set up correctly, leading to issues in identifying which records should be merged.
  Duplicate Records: There may be duplicate records in the source data that are not being recognized as duplicates due to differences in key fields or other attributes.
  
  Solution:
  
  Review Data Records: Check the records that are supposed to be merged. Look for inconsistencies in key fields or other attributes that may prevent merging.
  Adjust Mapping Configuration: Ensure that the mapping configuration in the migration tool is set up correctly. Verify that the correct fields are being used for merging.
  Clean Up Data: If there are duplicates or inconsistencies, clean up the data in the source system before migration. This may involve standardizing values, removing duplicates, or correcting errors.
  Check Relationships: Ensure that all necessary relationships between records are maintained and that there are no missing dependencies.
  Consult Documentation: Refer to the SAP documentation for the specific migration tool you are using. There may be specific guidelines or troubleshooting steps related to this error.
  Use SAP Notes: Check for any relevant SAP Notes that may address this specific error or provide additional guidance.
  
  Related Information:
  
  SAP Migration Cockpit: This tool is commonly used for data migration to SAP S/4HANA. Familiarize yourself with its functionalities and best practices.
  Data Quality Management: Implement data quality checks and validation processes to ensure that the data being migrated is clean and consistent.
  SAP Community: Engage with the SAP Community forums for insights and experiences from other users who may have encountered similar issues.
  
  If the problem persists after following these steps, consider reaching out to SAP support for further assistance.