How To Fix CNV_20100075 - In CoCd &3, &1 can only be posted to automatically, while &2 cannot

SAP Error Message - Details

• Message type: E = Error

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

• Message number: 075

• Message text: In CoCd &3, &1 can only be posted to automatically, while &2 cannot

What causes this issue?

Either account &V1& or account &V2& can only be posted to automatically
in company code &V3&.
This is determined by the indicator <zk>Is account only posted
to automatically?</> (field SKB1-XINTB).
These accounts are to be converted into account &V4&. However problems
may occur due to the different settings.

System Response

The conversion can take place anyway.

How to fix this error?

You may have to change the mapping table.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message CNV_20100075 - In CoCd &3, &1 can only be posted to automatically, while &2 cannot ?

  The SAP error message CNV_20100075 typically occurs during the data migration process, particularly when using the SAP S/4HANA Migration Cockpit or other data migration tools. This error indicates that there is a conflict in the posting rules for the specified company code (CoCd) and the accounts involved in the transaction.
  Cause:
  The error message CNV_20100075 arises when:
  
  You are trying to post a transaction to a specific account that is not allowed for automatic postings in the specified company code.
  The account specified in the error message (&2) is not configured to allow automatic postings, while the other account (&1) is.
  
  Solution:
  To resolve this error, you can take the following steps:
  
  
  Check Account Configuration:
  
  Go to the account settings for the account that is causing the issue (the one indicated by &2).
  Ensure that the account is set up to allow automatic postings. This can be done in the account master data settings.
  
  
  
  Adjust Posting Rules:
  
  Review the posting rules for the company code in question. Make sure that the accounts involved in the transaction are compatible with the posting type you are trying to execute.
  
  
  
  Review Migration Data:
  
  Check the data being migrated to ensure that it adheres to the posting rules defined in the system. If necessary, adjust the data to comply with the requirements.
  
  
  
  Consult Documentation:
  
  Refer to SAP documentation or notes related to the specific migration process you are using. There may be additional guidelines or prerequisites that need to be followed.
  
  
  
  Testing:
  
  After making the necessary adjustments, perform a test migration to see if the error persists. If it does, further investigation into the specific accounts and their configurations may be required.
  
  
  
  Related Information:
  
  Transaction Codes: You may need to use transaction codes like FS00 (to maintain G/L account master data) or OBY6 (to check company code settings) to review and modify account settings.
  SAP Notes: Check for any relevant SAP Notes that might address this specific error or provide additional troubleshooting steps.
  Migration Cockpit: If you are using the SAP S/4HANA Migration Cockpit, ensure that you are following the correct procedures for data mapping and transformation.
  
  By following these steps, you should be able to identify the root cause of the error and implement a solution to allow for successful postings in the specified company code.