How To Fix C1220 - Currency key &1 is replaced by currency key &2 when saving

SAP Error Message - Details

• Message type: E = Error

• Message class: C1 - Characteristics maintenance messages

• Message number: 220

• Message text: Currency key &1 is replaced by currency key &2 when saving

Self-Explanatory Message

Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of messages in the SAP system have a message text, however this is frequently insufficient to comprehend or resolve the problem.

To make things easier, more detailed information is frequently added to describe the issue, how to fix it, and the necessary steps or configuration modifications.

Unfortunately, there isn't any extra information in this error notice.

What else can you do?

First, use our AnswerBot below to get a possible cause and solution (requires a premium subscription).

Also, review the in-depth Common Questions & Answers listed below; you could discover a solution there or be able to connect with others who have faced similar challenges.

You can also try searching the SAP support portal (support.sap.com) but you need a special user ID to access it. It is possible that an SAP support note exists that provides additional details about the mistake or even steps for fixing it.

Smart SAP Assistant

• What is the cause and solution for SAP error message C1220 - Currency key &1 is replaced by currency key &2 when saving ?

  The SAP error message C1220 indicates that there is a currency key conflict when saving a transaction or document. Specifically, it means that the currency key you are trying to use (denoted as &1) is being replaced by another currency key (denoted as &2) during the save process. This typically occurs in scenarios where the system has certain rules or configurations that dictate which currency keys are valid for a particular transaction or document.
  Causes:
  
  Currency Configuration: The currency key you are trying to use may not be valid for the specific transaction or document type. This can happen if the currency is not defined in the relevant configuration settings.
  Document Type Settings: The document type you are working with may have specific currency settings that override the currency you are trying to use.
  Master Data Issues: The master data (such as customer or vendor records) may have a different currency defined, leading to a conflict when trying to save a transaction.
  Cross-Company Code Transactions: If you are dealing with transactions that span multiple company codes, the currency settings for those company codes may differ, causing the system to replace the currency key.
  
  Solutions:
  
  Check Currency Configuration: Verify the currency settings in the relevant configuration areas (e.g., transaction OB22 for defining currencies for company codes).
  Review Document Type Settings: Check the settings for the document type you are using to ensure that the currency you are trying to use is allowed.
  Update Master Data: If the issue is related to master data, update the relevant records (e.g., customer or vendor) to ensure that the correct currency is defined.
  Use the Correct Currency: If the system is replacing the currency key, consider using the currency that the system is suggesting (i.e., &2) if it is appropriate for your transaction.
  Consult with SAP Support: If the issue persists and you cannot identify the cause, it may be beneficial to consult with SAP support or your internal SAP team for further investigation.
  
  Related Information:
  
  Transaction Codes: You may want to use transaction codes like OB22 (for currency settings) or OBA5 (for document type settings) to review and adjust configurations.
  SAP Notes: Check for any relevant SAP Notes that may address this specific error or provide additional guidance.
  Documentation: Review SAP documentation related to currency management and document types for a deeper understanding of how currencies are handled in your specific SAP environment.
  
  By following these steps, you should be able to identify the cause of the error and implement a solution to resolve it.