How To Fix CNV_20200_CHECK096 - All involved company codes have identical settings for local currencies

SAP Error Message - Details

• Message type: E = Error

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

• Message number: 096

• Message text: All involved company codes have identical settings for local currencies

Self-Explanatory Message

Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of messages in the SAP system have a message text, however this is frequently insufficient to comprehend or resolve the problem.

To make things easier, more detailed information is frequently added to describe the issue, how to fix it, and the necessary steps or configuration modifications.

Unfortunately, there isn't any extra information in this error notice.

What else can you do?

First, use our AnswerBot below to get a possible cause and solution (requires a premium subscription).

Also, review the in-depth Common Questions & Answers listed below; you could discover a solution there or be able to connect with others who have faced similar challenges.

You can also try searching the SAP support portal (support.sap.com) but you need a special user ID to access it. It is possible that an SAP support note exists that provides additional details about the mistake or even steps for fixing it.

Smart SAP Assistant

• What is the cause and solution for SAP error message CNV_20200_CHECK096 - All involved company codes have identical settings for local currencies ?

  The SAP error message CNV_20200_CHECK096 indicates that all involved company codes have identical settings for local currencies. This error typically arises during data migration or conversion processes, particularly when using SAP's Conversion Tools or during the implementation of SAP S/4HANA.
  Cause:
  The error occurs because the system expects different local currency settings for the company codes involved in the migration or conversion process. If all company codes share the same local currency settings, the conversion process may not be able to proceed as expected, leading to this error.
  Solution:
  To resolve this error, you can consider the following steps:
  
  
  Check Company Code Settings:
  
  Go to the transaction code OBY6 (or use the path: SPRO > Financial Accounting > General Settings > Define Company Code).
  Verify the local currency settings for each company code involved in the process. Ensure that at least one company code has a different local currency setting.
  
  
  
  Adjust Local Currency Settings:
  
  If all company codes are indeed set to the same local currency and this is not intended, you may need to adjust the settings. This could involve changing the local currency for one or more company codes to ensure they are not identical.
  
  
  
  Review Migration/Conversion Configuration:
  
  If you are using a migration tool or a specific conversion program, review the configuration settings to ensure that they are set up correctly. Make sure that the tool is configured to handle the local currency settings appropriately.
  
  
  
  Consult Documentation:
  
  Refer to the SAP documentation related to the specific migration or conversion process you are undertaking. There may be specific guidelines or prerequisites that need to be followed.
  
  
  
  Seek Support:
  
  If you are unable to resolve the issue on your own, consider reaching out to SAP support or consulting with an SAP expert who can provide guidance based on your specific system configuration and requirements.
  
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as OBY6 (Define Company Code) and OB22 (Define Currencies).
  SAP Notes: Check for any SAP Notes related to the error message CNV_20200_CHECK096 for additional insights or patches that may address the issue.
  Migration Tools: If you are using SAP S/4HANA Migration Cockpit or other migration tools, ensure you are following the best practices outlined in the respective documentation.
  
  By following these steps, you should be able to identify the cause of the error and implement a solution to proceed with your migration or conversion process.