How To Fix FTOE_CORE164 - Risk currency &1 is not permitted for company code &2

SAP Error Message - Details

• Message type: E = Error

• Message class: FTOE_CORE -

• Message number: 164

• Message text: Risk currency &1 is not permitted for company code &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 FTOE_CORE164 - Risk currency &1 is not permitted for company code &2 ?

  The SAP error message FTOE_CORE164 indicates that there is an issue with the risk currency being used in a transaction for a specific company code. The message states that the risk currency (denoted as &1) is not permitted for the specified company code (denoted as &2). This typically occurs in the context of financial transactions, particularly in Treasury and Risk Management modules.
  Cause:
  
  Configuration Issue: The risk currency may not be configured correctly in the system for the specified company code. This can happen if the currency is not included in the allowed currencies for that company code in the relevant configuration settings.
  Master Data Settings: The master data for the company code may not include the risk currency, or the currency settings may not be aligned with the transaction being processed.
  Transaction Type Restrictions: Certain transaction types may have restrictions on which currencies can be used, and the risk currency in question may not be allowed for the specific transaction type.
  
  Solution:
  
  
  Check Configuration:
  
  Go to the configuration settings for Treasury and Risk Management in SAP.
  Verify the settings for allowed currencies for the company code in question. Ensure that the risk currency is included in the list of permitted currencies.
  You can check this in the following path: 
  
  SPRO > Financial Supply Chain Management > Treasury and Risk Management > Risk Management > Define Risk Currencies.
  
  
  
  
  
  Review Master Data:
  
  Check the master data for the company code to ensure that the risk currency is properly defined and allowed.
  Ensure that the currency settings in the relevant master data records (like business partners, financial instruments, etc.) are correct.
  
  
  
  Transaction Type Settings:
  
  Review the transaction type settings to ensure that the risk currency is permitted for the specific transaction you are trying to execute.
  You can find this in the configuration for the specific transaction type under Treasury and Risk Management.
  
  
  
  Consult Documentation:
  
  Refer to SAP documentation or help notes related to Treasury and Risk Management for any specific guidelines or additional configuration steps that may be required.
  
  
  
  Contact Support:
  
  If the issue persists after checking the above configurations, consider reaching out to SAP support for further assistance. They may provide insights based on the specific version of SAP you are using.
  
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes in SAP that pertain to Treasury and Risk Management, such as FTR_CREATE, FTR_EDIT, etc.
  SAP Notes: Search for SAP Notes related to error FTOE_CORE164 for any patches or updates that may address this issue.
  User Roles and Authorizations: Ensure that the user executing the transaction has the necessary authorizations to work with the specified currencies and company codes.
  
  By following these steps, you should be able to identify the cause of the error and implement the necessary solutions to resolve it.