How To Fix CNV_20200_CHECK170 - Ledger &1/Activity &2:diff. settings and not present in all part. CoCds

CNV_20200_CHECK170 - Overview

• Message type: E = Error

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

• Message number: 170

• Message text: Ledger &1/Activity &2:diff. settings and not present in all part. CoCds

What causes this issue?

FI-SL ledger &V1& / activity &V2& has different settings in the
participating company codes and does not occur in all participating
company codes.

System Response

Error

How to fix this error?

A company code merge will result in inconsistencies on special ledger
level. A company code merge can be done only when all participating
company codes have the same settings. We recommend that you contact your
special ledger consultant in order to identify additional activities.

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_CHECK170 - Details

• The SAP error message CNV_20200_CHECK170 typically arises during the data migration process, particularly when using the SAP S/4HANA Migration Cockpit or similar tools. This error indicates that there are discrepancies in the configuration settings for a specific ledger and activity across different company codes (CoCds) in your system.
  
  Cause:
  The error message suggests that the ledger and activity specified (denoted by &1 for the ledger and &2 for the activity) have different settings in the system and are not uniformly configured across all participating company codes. This can happen due to:
  
  Inconsistent Configuration: Different company codes may have different settings for the same ledger or activity, leading to inconsistencies.
  Missing Configuration: The ledger or activity may not be defined in all company codes, which is required for the migration process.
  Data Migration Issues: During the migration, if the source data does not match the expected configuration in the target system, this error can occur.
  
  
  Solution:
  To resolve