How To Fix CNV_20100396 - After conversion, account / cost element is new in account group &1

SAP Error Message - Details

• Message type: E = Error

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

• Message number: 396

• Message text: After conversion, account / cost element is new in account group &1

What causes this issue?

After the conversion, the G/L account or cost element &V3& will newly
lie in the account group.
Old/New account group: &V1&
Old/New Interval: &V2&
Old G/L account or cost element: &V3&
New G/L account or cost element: &V4&

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

System Response

Warning

How to fix this error?

If necessary, change the mapping for interval limits for the relevant
account group accordingly.
Alternatively you should manually check your account groups for
consistency after the conversion.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message CNV_20100396 - After conversion, account / cost element is new in account group &1 ?

  The SAP error message CNV_20100396 indicates that after a data conversion process, an account or cost element has been identified as new in the specified account group. This typically occurs during data migration or conversion activities, such as when using the SAP S/4HANA Migration Cockpit or other data migration tools.
  Cause:
  The error arises when the system detects that the account or cost element being processed does not match any existing entries in the target system's account group. This can happen due to several reasons:
  
  Data Mapping Issues: The mapping of accounts or cost elements from the source system to the target system may not have been correctly defined.
  Missing Master Data: The required master data (e.g., account groups, cost elements) may not exist in the target system.
  Configuration Differences: Differences in configuration between the source and target systems can lead to discrepancies in account groups and cost elements.
  Data Quality Issues: The data being migrated may contain errors or inconsistencies that prevent proper mapping.
  
  Solution:
  To resolve this error, you can take the following steps:
  
  
  Check Mapping Configuration:
  
  Review the mapping configuration used during the conversion process to ensure that all accounts and cost elements are correctly mapped to the corresponding account groups in the target system.
  
  
  
  Verify Master Data:
  
  Ensure that all necessary master data (account groups, cost elements) exists in the target system. If any are missing, create them as needed.
  
  
  
  Data Validation:
  
  Validate the data being migrated for any inconsistencies or errors. Clean up the data in the source system if necessary before re-running the migration.
  
  
  
  Consult Documentation:
  
  Refer to SAP documentation or notes related to the specific migration tool you are using. There may be specific guidelines or known issues that can help you troubleshoot the problem.
  
  
  
  Use Transaction Codes:
  
  Use transaction codes like OBD2 (for account groups) or KA01 (for cost elements) to check the configuration in the target system.
  
  
  
  Run Migration Again:
  
  After making the necessary adjustments, re-run the migration process to see if the error persists.
  
  
  
  Related Information:
  
  SAP Notes: Check for any relevant SAP Notes that may address this specific error or provide additional guidance on data migration.
  SAP Community: Engage with the SAP Community forums to see if other users have encountered similar issues and what solutions they found effective.
  Testing: Always perform thorough testing in a development or quality assurance environment before executing migrations in production.
  
  By following these steps, you should be able to identify the root cause of the error and implement a solution to successfully complete the data conversion process.