How To Fix FQ004 - Currency key & does not exist

SAP Error Message - Details

• Message type: E = Error

• Message class: FQ - Payment Requests and Payment Program

• Message number: 004

• Message text: Currency key & does not exist

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 FQ004 - Currency key & does not exist ?

  The SAP error message FQ004, which states "Currency key & does not exist," typically occurs when the system is unable to recognize or find the specified currency key in the relevant currency tables. This can happen in various contexts, such as during the posting of financial transactions, when generating reports, or while processing invoices.
  Causes:
  
  Missing Currency Configuration: The currency key may not be defined in the system. This can happen if the currency has not been set up in the currency configuration tables.
  Incorrect Currency Key: The currency key being used in the transaction may be misspelled or incorrectly entered.
  Inactive Currency: The currency might be inactive or not allowed for the specific transaction type or company code.
  Data Migration Issues: If data has been migrated from another system, there may be inconsistencies or missing entries in the currency tables.
  Custom Development: If there are custom programs or enhancements, they may not be handling currency keys correctly.
  
  Solutions:
  
  
  Check Currency Configuration:
  
  Go to the transaction code OB08 (Maintain Exchange Rates) and verify if the currency key exists.
  If it does not exist, you may need to create it or ensure it is properly configured.
  
  
  
  Verify Currency Key:
  
  Double-check the currency key being used in the transaction. Ensure that it is spelled correctly and matches the expected format.
  
  
  
  Activate Currency:
  
  If the currency is inactive, you may need to activate it. This can typically be done in the configuration settings for currencies.
  
  
  
  Review Company Code Settings:
  
  Ensure that the currency is allowed for the specific company code in the configuration settings.
  
  
  
  Data Migration Review:
  
  If the issue arose after a data migration, review the migration process to ensure that all necessary currency data was transferred correctly.
  
  
  
  Consult Documentation:
  
  Review SAP documentation or help resources for any specific notes related to the currency key in question.
  
  
  
  Contact SAP Support:
  
  If the issue persists, consider reaching out to SAP support for further assistance, especially if it involves custom developments or complex configurations.
  
  
  
  Related Information:
  
  Transaction Codes: 
  
  OB08: Maintain Exchange Rates
  OB22: Define Currencies
  OB37: Define Currency Types
  
  
  Currency Tables: 
  
  Check tables like TCURC (Currency Codes) and TCURR (Exchange Rates) for relevant entries.
  
  
  SAP Notes: Search for relevant SAP Notes in the SAP Support Portal that may address specific issues related to currency keys.
  
  By following these steps, you should be able to identify the cause of the FQ004 error and implement a solution to resolve it.