How To Fix CNV_20100058 - G/L account &1 is merged with secondary cost element &2

SAP Error Message - Details

• Message type: E = Error

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

• Message number: 058

• Message text: G/L account &1 is merged with secondary cost element &2

What causes this issue?

According to the mapping table, the G/L account &V1& is
to be merged with a secondary cost element into target
account &V3&.

System Response

Secondary cost elements cannot be merged with G/L accounts.
Conversion cannot take place.

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_20100058 - G/L account &1 is merged with secondary cost element &2 ?

  The SAP error message CNV_20100058 indicates that a General Ledger (G/L) account has been merged with a secondary cost element. This typically occurs during data migration or conversion processes, particularly when using the SAP S/4HANA Migration Cockpit or similar tools.
  Cause:
  The error arises when there is a conflict between the G/L account and the secondary cost element during the migration process. This can happen if:
  
  The G/L account is being used in a way that conflicts with the secondary cost element.
  The mapping of accounts during the migration is incorrect, leading to the merging of accounts that should remain separate.
  There are inconsistencies in the configuration of the accounts in the source system.
  
  Solution:
  To resolve this error, you can take the following steps:
  
  
  Review the Mapping: Check the mapping of G/L accounts and secondary cost elements in your migration settings. Ensure that they are correctly defined and that there are no unintended merges.
  
  
  Check Configuration: Verify the configuration of the G/L accounts and secondary cost elements in the SAP system. Make sure that they are set up correctly and that there are no conflicts.
  
  
  Adjust Migration Data: If the error is due to incorrect data in the migration files, you may need to adjust the data before re-running the migration. Ensure that the G/L accounts and secondary cost elements are properly separated.
  
  
  Consult Documentation: Refer to SAP documentation or notes related to the specific migration process you are using. There may be specific guidelines or known issues that can help you resolve the error.
  
  
  Testing: After making adjustments, perform a test migration to ensure that the error does not occur again.
  
  
  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 and migration scenario.
  
  
  Related Information:
  
  SAP Notes: Check for any relevant SAP Notes that may address this specific error or provide additional guidance on handling G/L account and cost element migrations.
  Migration Cockpit: Familiarize yourself with the SAP S/4HANA Migration Cockpit and its functionalities, as it provides tools and templates for migrating data effectively.
  Data Validation: Implement data validation checks before migration to catch potential issues early in the process.
  
  By following these steps, you should be able to identify the root cause of the error and implement a solution to resolve it.