How To Fix CNV_20200_CHECK101 - Participating company codes use FI-SL with different settings

SAP Error Message - Details

• Message type: E = Error

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

• Message number: 101

• Message text: Participating company codes use FI-SL with different settings

What causes this issue?

The participating company codes use FI-SL with different settings.
The system identifies the following issues:
The company codes do not use the same FI-SL ledgers
The company codes use the same FI-SL ledgers but with different settings
The company codes use the same FI-SL ledgers but with different
activities or the activities have a different posting indicator

System Response

Error

How to fix this error?

A company code merge will lead to 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_CHECK101 - Participating company codes use FI-SL with different settings ?

  The SAP error message CNV_20200_CHECK101 indicates that there is a discrepancy in the settings of Financial Accounting (FI) and Special Ledger (FI-SL) for participating company codes during a data migration or conversion process. This error typically arises in the context of using the SAP S/4HANA Migration Cockpit or during a system conversion where multiple company codes are involved.
  Cause:
  The error occurs when:
  
  Different company codes that are part of the same migration or conversion process have inconsistent settings in their FI-SL configurations.
  This inconsistency can be due to differences in the configuration of ledgers, such as the use of different accounting principles, fiscal year variants, or other FI-SL settings.
  
  Solution:
  To resolve this error, you can follow these steps:
  
  
  Check Company Code Settings:
  
  Go to the transaction code OB22 (for FI-SL settings) and review the settings for each participating company code.
  Ensure that the settings for the Special Ledger (FI-SL) are consistent across all company codes involved in the migration.
  
  
  
  Standardize Settings:
  
  If discrepancies are found, standardize the settings across the company codes. This may involve aligning the ledger types, fiscal year variants, and other relevant configurations.
  
  
  
  Review Migration Cockpit Settings:
  
  If you are using the SAP S/4HANA Migration Cockpit, ensure that the settings in the cockpit are correctly configured to reflect the intended structure and settings of the company codes.
  
  
  
  Consult Documentation:
  
  Refer to SAP documentation or notes related to the specific version of SAP you are using. There may be specific guidelines or recommendations for handling FI-SL settings during migration.
  
  
  
  Testing:
  
  After making the necessary adjustments, perform a test migration to ensure that the error does not reoccur.
  
  
  
  Seek Support:
  
  If the issue persists, consider reaching out to SAP support or consulting with an SAP expert who can provide more tailored assistance based on your specific system configuration.
  
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as OB22 (for FI-SL settings) and SPRO (for configuration settings).
  SAP Notes: Check for any SAP Notes related to the error message CNV_20200_CHECK101 for additional insights or patches that may address the issue.
  Migration Cockpit: Understand the role of the Migration Cockpit in the context of your migration project, as it may have specific requirements for data consistency across company codes.
  
  By following these steps, you should be able to identify and resolve the underlying issues causing the CNV_20200_CHECK101 error.