How To Fix CNV_20200_CHECK023 - Company codes are merged but not their associated credit control areas

CNV_20200_CHECK023 - Overview

• Message type: E = Error

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

• Message number: 023

• Message text: Company codes are merged but not their associated credit control areas

What causes this issue?

The participating company codes use different credit control areas.
Company codes are merged but not their associated credit control areas.

System Response

Warning.

How to fix this error?

The participating company codes use different default credit control
areas. The usual procedure would be to then merge the credit control
areas. You can specify mapping values to do this. If you do not want to
merge the credit control areas (for example if you use table T001CM -
Permitted Credit Control Areas per Company Code), it is important to
note that the system uses the settings from the reference company code
during the company code merge. After the company code merge, you have to
check your Customizing settings for the credit control areas (tables
T001, T001CM, and T014). In addition, you have to check whether you need
to recreate the credit control data after the merge (by using report
RFDKLI20 during system downtime).

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.

CNV_20200_CHECK023 - Details

• The SAP error message CNV_20200_CHECK023 indicates that there is an issue related to the merging of company codes and their associated credit control areas during a data migration or system conversion process. Specifically, this error arises when company codes are merged, but their corresponding credit control areas have not been merged or aligned accordingly.
  
  Cause:
  
  Mismatched Credit Control Areas: When two or more company codes are merged, they should ideally share the same credit control area. If the credit control areas are different or not properly aligned, this error will occur.
  Data Inconsistency: There may be inconsistencies in the configuration or master data related to credit control areas and company codes.
  Incomplete Migration Steps: The migration process may not have included all necessary steps to ensure that credit control areas are merged or reassigned correctly.
  
  
  Solution:
  
  
  Review Credit Control Area Assignments:
  
  Check the credit control area assignments for the company codes involved in the merge. Ensure that