How To Fix CNV_20335_CHECK028 - Differences regarding currency keys detected; merge not possible

SAP Error Message - Details

• Message type: E = Error

• Message class: CNV_20335_CHECK - Message Class for 20335 Checks

• Message number: 028

• Message text: Differences regarding currency keys detected; merge not possible

What causes this issue?

The participating business processes use different currencies. If you
want to merge the business processes, a currency conversion must be done
before the conversion. If not, the mapping needs to be changed.
You cannot run the transformation solution Controlling Area Merge
because certain prerequisites have not been met. Please change your
mapping accordingly or contact SAP for support by creating a ticket
using component CA-LT-CNV.

System Response

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

How to fix this error?

Procedure for System Administrators

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message CNV_20335_CHECK028 - Differences regarding currency keys detected; merge not possible ?

  The SAP error message CNV_20335_CHECK028 indicates that there are differences in currency keys between the source and target systems during a data migration or conversion process. This error typically arises in the context of SAP's data migration tools, such as the SAP S/4HANA Migration Cockpit or other conversion tools.
  Cause:
  The error occurs when the system detects that the currency keys (which represent different currencies) in the source data do not match those in the target system. This can happen due to several reasons:
  
  Different Currency Configuration: The source and target systems may have different currency configurations, such as different currency types or missing currencies in the target system.
  Data Inconsistencies: There may be inconsistencies in the data being migrated, such as records that reference currencies not defined in the target system.
  Customizations: Custom developments or configurations in the source system that are not replicated in the target system can lead to mismatches.
  
  Solution:
  To resolve this error, you can follow these steps:
  
  
  Check Currency Configuration:
  
  Verify the currency settings in both the source and target systems. Ensure that all currencies used in the source system are also defined in the target system.
  Use transaction codes like OB08 (for maintaining exchange rates) and OBY6 (for defining currencies) to check the configuration.
  
  
  
  Update Target System:
  
  If there are currencies in the source system that are not present in the target system, you may need to add these currencies to the target system.
  Ensure that the currency types (e.g., local currency, document currency) are consistent between the two systems.
  
  
  
  Data Mapping:
  
  If certain currencies in the source system should be mapped to different currencies in the target system, you may need to create a mapping strategy to handle these conversions.
  
  
  
  Data Cleansing:
  
  Review the data in the source system for any inconsistencies or errors related to currency keys. Cleanse the data if necessary before migration.
  
  
  
  Consult Documentation:
  
  Refer to the SAP documentation for the specific migration tool you are using. There may be additional guidelines or best practices for handling currency-related issues.
  
  
  
  Testing:
  
  After making the necessary adjustments, perform a test migration to ensure that the error is resolved and that the data is correctly migrated.
  
  
  
  Related Information:
  
  SAP Notes: Check for any relevant SAP Notes that may provide additional insights or solutions for this specific error message.
  Migration Cockpit: Familiarize yourself with the SAP S/4HANA Migration Cockpit and its functionalities, as it provides tools and guidelines for data migration.
  Community Forums: Engage with the SAP Community or forums where other users may have encountered similar issues and can share their solutions.
  
  By following these steps, you should be able to identify the cause of the error and implement a solution to successfully complete your data migration.