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

SAP Error Message - Details

• 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.

Smart SAP Assistant

• What is the cause and solution for SAP error message CNV_20200_CHECK170 - Ledger &1/Activity &2:diff. settings and not present in all part. CoCds ?

  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 this error, you can follow these steps:
  
  
  Check Configuration:
  
  Go to the configuration settings for the ledger and activity in question.
  Ensure that the settings are consistent across all relevant company codes. You can do this by navigating to the relevant configuration transaction (e.g., SPRO) and checking the settings under Financial Accounting (FI) or Controlling (CO).
  
  
  
  Define Missing Settings:
  
  If the ledger or activity is not defined in some company codes, you will need to create or adjust the configuration to ensure that it is present in all participating company codes.
  
  
  
  Review Migration Data:
  
  Check the data being migrated to ensure that it aligns with the configuration in the target system. This may involve reviewing the source data and making necessary adjustments.
  
  
  
  Use Transaction Codes:
  
  You can use transaction codes like OB22 (for ledgers) and OKKP (for controlling area settings) to review and adjust the settings.
  
  
  
  Consult Documentation:
  
  Refer to SAP documentation or notes related to the specific migration process you are using. There may be specific guidelines or prerequisites that need to be followed.
  
  
  
  Testing:
  
  After making the necessary adjustments, perform a test migration to ensure that the error is resolved.
  
  
  
  Related Information:
  
  SAP Notes: Check for any relevant SAP Notes that may provide additional insights or solutions for this specific error.
  SAP Community: Engage with the SAP Community forums to see if other users have encountered and resolved similar issues.
  Migration Cockpit Documentation: Review the official SAP documentation for the Migration Cockpit, as it may contain specific instructions for handling configuration discrepancies.
  
  By following these steps, you should be able to identify and resolve the cause of the CNV_20200_CHECK170 error in your SAP system.