How To Fix FDT_CHANGE_INFO667 - Default currency was changed from &1 to &2

FDT_CHANGE_INFO667 - Overview

• Message type: E = Error

• Message class: FDT_CHANGE_INFO - FDT: Changes info in object for different versions

• Message number: 667

• Message text: Default currency was changed from &1 to &2

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 FDT_CHANGE_INFO667 - Default currency was changed from &1 to &2 ?

  The SAP error message FDT_CHANGE_INFO667 indicates that the default currency for a particular financial document or transaction has been changed from one currency (denoted as &1) to another (denoted as &2). This message typically arises in the context of financial transactions, where the currency settings are critical for accurate reporting and processing.
  
  Cause:
  
  Manual Change: A user may have manually changed the default currency in the configuration settings or during the transaction entry.
  System Configuration: Changes in the system configuration, such as updates to company code settings or currency settings in financial modules, can lead to this message.
  Data Migration: During data migration or system upgrades, the default currency may have been altered inadvertently.
  Integration Issues: If there are integrations with other systems (like third-party applications), discrepancies in currency settings can trigger this message.
  
  
  Solution:
  
  Review Changes: Check the transaction or configuration settings to understand why the currency was changed. Look for any recent changes made by