How To Fix CNV_20200_CHECK136 - FI-SL ledger &1: diff. settings and not present in all particip. CoCodes

SAP Error Message - Details

• Message type: E = Error

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

• Message number: 136

• Message text: FI-SL ledger &1: diff. settings and not present in all particip. CoCodes

What causes this issue?

FI-SL ledger &V1& has different settings in the participating company
codes and does not exist in all participating company codes.

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_CHECK136 - FI-SL ledger &1: diff. settings and not present in all particip. CoCodes ?

  The SAP error message CNV_20200_CHECK136 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 settings of the Financial Statement Version (FI-SL ledger) across different company codes (CoCodes) involved in the migration.
  Cause:
  The error message suggests that:
  
  Inconsistent Settings: The settings for the FI-SL ledger are not consistent across all participating company codes. This could mean that some company codes have different configurations or that the ledger is not activated for all company codes.
  Missing Configuration: The ledger might be configured in some company codes but not in others, leading to inconsistencies that prevent the migration process from proceeding smoothly.
  
  Solution:
  To resolve this error, you can follow these steps:
  
  
  Check Ledger Configuration:
  
  Go to the SAP GUI and navigate to the configuration settings for the FI-SL ledger.
  Ensure that the ledger is configured consistently across all participating company codes.
  
  
  
  Activate Ledger for All Company Codes:
  
  If the ledger is not activated for some company codes, you need to activate it. This can typically be done in the configuration settings under Financial Accounting (FI) > General Ledger Accounting > Master Data > Ledger > Define Ledgers.
  
  
  
  Review Financial Statement Versions:
  
  Ensure that the financial statement versions are the same across all company codes. If there are differences, you may need to standardize them.
  
  
  
  Run Consistency Checks:
  
  Use transaction codes like OB22 (for ledger settings) and OB58 (for financial statement versions) to review and adjust settings as necessary.
  You can also run consistency checks or reports to identify discrepancies.
  
  
  
  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 has been resolved.
  
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as OB22, OB58, and SCC4 (for client settings).
  SAP Notes: Check for any SAP Notes related to the error message or the migration process you are using. SAP frequently updates its knowledge base with solutions to common issues.
  Migration Cockpit: If you are using the SAP S/4HANA Migration Cockpit, ensure that you are following the recommended steps and prerequisites outlined in the migration guide.
  
  By addressing the configuration inconsistencies and ensuring that all participating company codes have the same settings, you should be able to resolve the CNV_20200_CHECK136 error and proceed with your migration successfully.