How To Fix CNV_20600_CHECK364 - Accounting code &1 in mapping, but not associated company code &2

SAP Error Message - Details

• Message type: E = Error

• Message class: CNV_20600_CHECK - Messages for Check classes

• Message number: 364

• Message text: Accounting code &1 in mapping, but not associated company code &2

What causes this issue?

Accounting code &V1& is in mapping, but no mapping for the associated
company code &V2&.

System Response

Error

How to fix this error?

The 1:1 relationships between accounting codes and company codes must be
preserved.
Adjust the mappings.

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_20600_CHECK364 - Accounting code &1 in mapping, but not associated company code &2 ?

  The SAP error message CNV_20600_CHECK364 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 mismatch between the accounting code (or account) being used in the mapping and the company code that is associated with it.
  Cause:
  The error arises due to one of the following reasons:
  
  Mapping Issues: The accounting code specified in the mapping does not belong to the company code that is being processed. This can happen if the mapping was incorrectly set up or if the accounting code is not valid for the specified company code.
  Configuration Errors: There may be configuration issues in the system where the accounting code is not properly assigned to the company code in the financial settings.
  Data Integrity Issues: The data being migrated may contain inconsistencies, such as references to accounting codes that are not valid for the target company code.
  
  Solution:
  To resolve this error, you can take the following steps:
  
  
  Check Mapping Configuration:
  
  Review the mapping configuration in the migration tool to ensure that the accounting code is correctly mapped to the appropriate company code.
  Ensure that the accounting code exists and is valid for the specified company code.
  
  
  
  Verify Company Code Settings:
  
  Go to the configuration settings in SAP and check the assignment of the accounting code to the company code.
  Use transaction codes like OBY6 (for company code settings) and FS00 (for G/L account master data) to verify the settings.
  
  
  
  Data Validation:
  
  Validate the data being migrated to ensure that all accounting codes referenced are valid for the respective company codes.
  If necessary, clean up the data to remove any invalid references.
  
  
  
  Consult Documentation:
  
  Refer to SAP documentation or notes related to the specific migration tool you are using for any additional guidance or known issues.
  
  
  
  Testing:
  
  After making the necessary adjustments, perform a test migration to ensure that the error does not occur again.
  
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as OBY6 (Company Code Global Settings), FS00 (G/L Account Master), and SE16N (Data Browser) to check the underlying data.
  SAP Notes: Check for any SAP Notes related to the migration tool you are using, as they may provide specific fixes or workarounds for known issues.
  Migration Cockpit: If you are using the SAP S/4HANA Migration Cockpit, ensure that you are following the best practices and guidelines provided by SAP for data migration.
  
  By following these steps, you should be able to identify and resolve the cause of the CNV_20600_CHECK364 error in your SAP system.