How To Fix CNV_20600_CHECK368 - Company codes are merged, but not their associated accounting codes

SAP Error Message - Details

• Message type: E = Error

• Message class: CNV_20600_CHECK - Messages for Check classes

• Message number: 368

• Message text: Company codes are merged, but not their associated accounting codes

What causes this issue?

Company codes are merged, but not their associated accounting codes.
There is normally a 1:1 relationship between accounting codes and
company codes.

System Response

Error

How to fix this error?

Verify the mapping.

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_CHECK368 - Company codes are merged, but not their associated accounting codes ?

  The SAP error message CNV_20600_CHECK368 typically occurs during a data migration or conversion process, particularly when merging company codes. This error indicates that while the company codes have been merged, their associated accounting codes (such as GL accounts, cost centers, etc.) have not been properly aligned or merged. This can lead to inconsistencies in financial reporting and data integrity.
  Cause:
  
  Incomplete Data Migration: The accounting codes related to the company codes were not included in the migration process.
  Configuration Issues: There may be configuration settings that prevent the proper merging of accounting codes.
  Data Integrity Issues: There could be existing inconsistencies or conflicts in the data that prevent the merging of accounting codes.
  Custom Code or Enhancements: If there are custom developments or enhancements in the system, they may interfere with the standard merging process.
  
  Solution:
  
  Review Migration Process: Ensure that the migration process includes all necessary accounting codes associated with the company codes. Check the mapping and transformation rules used during the migration.
  Data Validation: Perform a thorough validation of the data before and after the merge. Identify any discrepancies in the accounting codes and resolve them.
  Adjust Configuration: Check the configuration settings in the SAP system related to company code and accounting code merging. Make necessary adjustments to ensure they align.
  Run Consistency Checks: Use SAP tools to run consistency checks on the data to identify any issues that need to be addressed.
  Manual Intervention: If automated processes fail, consider manually merging the accounting codes or creating new mappings as needed.
  Consult Documentation: Refer to SAP documentation or notes related to the specific migration or conversion process you are using. There may be specific guidelines or patches available.
  Engage SAP Support: If the issue persists, consider reaching out to SAP support for assistance. They may provide insights or solutions based on similar cases.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as OBY6 (for company code settings) and OBD2 (for account assignment).
  SAP Notes: Search for SAP Notes related to the error message or the migration process you are using. These notes often contain fixes or workarounds.
  Data Migration Tools: If you are using SAP's data migration tools (like SAP S/4HANA Migration Cockpit), ensure you are following best practices and guidelines provided by SAP.
  Testing: Always perform testing in a development or sandbox environment before executing changes in the production environment to avoid data loss or corruption.
  
  By addressing the underlying causes and following the suggested solutions, you should be able to resolve the CNV_20600_CHECK368 error effectively.