How To Fix CNV_20200_CHECK211 - Merge into (CoCd &1, CJ &2) with same customizing and allowed postings

SAP Error Message - Details

• Message type: E = Error

• Message class: CNV_20200_CHECK - Messages for check functions (company code merge)

• Message number: 211

• Message text: Merge into (CoCd &1, CJ &2) with same customizing and allowed postings

What causes this issue?

Merge of cash journals into (Company code &V1&, Cash Journal Number &V2&
) for which the source cash journals have the same customizing and in
addition either no postings exist, or postings exist only in one company
code.

System Response

Warning

How to fix this error?

Check whether you want to merge these cash journals. If you do not want
to merge them, provide a suitable mapping for cash journals.

Procedure for System Administrators

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

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message CNV_20200_CHECK211 - Merge into (CoCd &1, CJ &2) with same customizing and allowed postings ?

  The SAP error message CNV_20200_CHECK211 typically occurs during a data migration or conversion process, particularly when using the SAP S/4HANA Migration Cockpit or similar tools. This error indicates that there is an attempt to merge two entries in the system that have the same customizing settings and allowed postings, which is not permitted.
  Cause:
  
  Duplicate Entries: The error arises when there are two or more entries (e.g., cost centers, internal orders) in the system that have identical characteristics (customizing settings) and are set up to allow postings. The system does not allow merging of such entries to avoid data integrity issues.
  Configuration Issues: There may be a misconfiguration in the customizing settings for the entries being merged, leading to conflicts.
  Data Migration Issues: During data migration, if the source data contains duplicates or conflicts, this error can occur.
  
  Solution:
  
  Identify Duplicates: Check the entries that are being merged (CoCd &1, CJ &2) to identify if they are indeed duplicates. You can use transaction codes like SE16 or SE11 to view the relevant tables.
  Review Customizing Settings: Ensure that the customizing settings for the entries are not identical. If they are, you may need to adjust the settings to make them unique.
  Adjust Allowed Postings: If the allowed postings for the entries are the same, consider modifying them to ensure that they can be merged without conflicts.
  Data Cleansing: If this error occurs during a data migration process, perform data cleansing to remove or consolidate duplicate entries before attempting the migration again.
  Consult Documentation: Refer to SAP documentation or notes related to the specific migration or conversion process you are using for additional guidance.
  
  Related Information:
  
  Transaction Codes: Use transaction codes like SE16 (Data Browser) or SE11 (Data Dictionary) to analyze the relevant tables and entries.
  SAP Notes: Check for any relevant SAP Notes that may provide additional insights or solutions for this specific error message.
  Migration Cockpit: If you are using the SAP S/4HANA Migration Cockpit, review the migration objects and mappings to ensure that there are no conflicts in the data being migrated.
  
  If the issue persists after following these steps, it may be beneficial to consult with your SAP support team or reach out to SAP support for further assistance.