How To Fix CNV_20000254 - New accounting number &1 already exist in CoCod &2

SAP Error Message - Details

• Message type: E = Error

• Message class: CNV_20000 - Messages for fiscal year change

• Message number: 254

• Message text: New accounting number &1 already exist in CoCod &2

What causes this issue?

Given <ZH>prefix </> has been concatenated with the accounting document
(using external number ranges) which will result in an issue with
duplicate records during the conversion because:
The new accounting number &V1& is already present in company code &V2&
While doing mapping using the prefix, as soon as the system finds any
one document that already exists in the database it is logged as an
error. The remaining mapped accounting documents using that prefix are
not checked which helps to prevents runtime as short as possible.

How to fix this error?

Re-execute the activity and assign a unique prefix.

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_20000254 - New accounting number &1 already exist in CoCod &2 ?

  The SAP error message CNV_20000254 indicates that there is an attempt to create a new accounting number (or account) that already exists in the specified company code (CoCod). This error typically arises during data migration or conversion processes, particularly when using SAP's Migration Cockpit or during the execution of a conversion program.
  Cause:
  
  
  Duplicate Account Numbers: The primary cause of this error is that the accounting number you are trying to create already exists in the specified company code. This can happen if:
  
  The data being imported or converted contains duplicate entries.
  There was a previous migration or data load that created the account before the current attempt.
  
  
  
  Incorrect Mapping: If the mapping of accounts from the legacy system to the new system is not done correctly, it may lead to attempts to create accounts that already exist.
  
  
  Data Integrity Issues: There may be issues with the integrity of the data being migrated, such as missing or incorrect records.
  
  
  Solution:
  
  
  Check for Existing Accounts: Before attempting to create a new accounting number, check the existing accounts in the specified company code to confirm whether the account number already exists. You can do this by using transaction codes like FS00 (G/L Account Master Data) to view the accounts.
  
  
  Modify the Data: If the account number already exists and you need to create a new one, consider modifying the data being imported to use a different accounting number that does not conflict with existing ones.
  
  
  Data Cleansing: Ensure that the data being migrated is cleansed and validated to remove any duplicates or inconsistencies before the migration process.
  
  
  Review Mapping: If you are using a mapping file or tool, review the mapping to ensure that it correctly reflects the intended relationships between legacy and target accounts.
  
  
  Consult Documentation: Refer to SAP documentation or notes related to the specific migration or conversion process you are using, as there may be additional guidelines or best practices.
  
  
  Error Logs: Check the error logs for more detailed information about the error, which may provide insights into the specific records causing the issue.
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as FS00 for G/L account maintenance, OBY6 for company code settings, and SE38 for executing programs.
  SAP Notes: Search for SAP Notes related to the error message CNV_20000254 for any specific patches or updates that may address known issues.
  Migration Cockpit: If using the SAP Migration Cockpit, review the migration templates and guidelines provided by SAP to ensure compliance with the expected data formats and structures.
  
  By following these steps, you should be able to resolve the error and successfully complete your data migration or conversion process.