How To Fix CNV_20100069 - &1 has its balances only in local currency in CoCd &3, whereas &2 has not

SAP Error Message - Details

• Message type: E = Error

• Message class: CNV_20100 - Messageclass for chart of account conversion

• Message number: 069

• Message text: &1 has its balances only in local currency in CoCd &3, whereas &2 has not

What causes this issue?

In company code &V3&, account &V1& has its balances only in local
currency, while account &V2& has not.
This is determined by the indicator <zk>Only Manage Balances in
Local Currency</> (field SKB1-XSALH).
These accounts are to be converted into account &V4&.

System Response

Error.
From a technical point of view, this error message can be ignored.
However, this only makes sense if one of the following prerequisites is
met:
There are no postings for either of these accounts
These accounts/cost elements are not used any longer and are to be
converted into a dummy account

How to fix this error?

Change the mapping table accordingly.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message CNV_20100069 - &1 has its balances only in local currency in CoCd &3, whereas &2 has not ?

  The SAP error message CNV_20100069 typically occurs during data migration or conversion processes, particularly when using the SAP S/4HANA Migration Cockpit or similar tools. This error indicates that there is a discrepancy in the currency balances between two company codes during the migration process.
  Cause:
  The error message states that:
  
  &1 (the account) has balances only in the local currency of CoCd &3 (the first company code).
  &2 (the second company code) does not have corresponding balances.
  
  This situation can arise due to several reasons:
  
  Data Inconsistency: The financial data for the two company codes may not be aligned, leading to discrepancies in the balances.
  Currency Settings: The company codes may have different currency settings, which can cause issues when trying to consolidate or migrate data.
  Missing Data: There may be missing entries or transactions in the second company code that should correspond to the first company code.
  
  Solution:
  To resolve this error, you can take the following steps:
  
  
  Check Data Consistency:
  
  Verify that the balances for the accounts in both company codes are consistent. You may need to run reports or queries to check the balances in both company codes.
  
  
  
  Review Currency Settings:
  
  Ensure that both company codes are set up with the correct currency settings. Check the local currency and any other currencies that may be relevant.
  
  
  
  Data Mapping:
  
  If you are migrating data, ensure that the mapping between the two company codes is correct. You may need to adjust the mapping to ensure that the balances are correctly aligned.
  
  
  
  Adjust Balances:
  
  If necessary, you may need to make adjustments to the balances in either company code to ensure that they match. This could involve posting adjustments or corrections.
  
  
  
  Consult Documentation:
  
  Review the SAP documentation related to the migration process you are using. There may be specific guidelines or steps to follow to resolve this type of error.
  
  
  
  Engage with SAP Support:
  
  If the issue persists, consider reaching out to SAP support for assistance. They may have additional insights or tools to help resolve the error.
  
  
  
  Related Information:
  
  Transaction Codes: You may want to use transaction codes like FS00 (to check account details) or FBL3N (to view line items) to investigate the balances in the respective company codes.
  Migration Cockpit: Familiarize yourself with the SAP S/4HANA Migration Cockpit and its functionalities, as it provides tools for data migration and can help identify issues during the process.
  SAP Notes: Check for any relevant SAP Notes that may address this specific error or provide additional troubleshooting steps.
  
  By following these steps, you should be able to identify the root cause of the error and implement a solution to resolve it.