How To Fix FTR_GUI713 - &1 Product type &2 is not permitted

SAP Error Message - Details

• Message type: E = Error

• Message class: FTR_GUI - TR Transaction Management

• Message number: 713

• Message text: &1 Product type &2 is not permitted

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 FTR_GUI713 - &1 Product type &2 is not permitted ?

  The SAP error message FTR_GUI713 indicates that a specific product type is not permitted in the context of the transaction or operation you are trying to perform. This error typically occurs in the context of financial transactions, particularly in the area of treasury and risk management, where different product types (like derivatives, loans, etc.) are managed.
  Cause:
  
  Configuration Issues: The product type you are trying to use may not be configured correctly in the system. This could be due to missing settings in the customizing (SPRO) for treasury management.
  Authorization Issues: The user may not have the necessary authorizations to use the specified product type.
  Product Type Restrictions: The product type may be restricted for certain transactions or may not be allowed in the current context (e.g., certain types of financial instruments may not be allowed for specific operations).
  Data Inconsistencies: There may be inconsistencies in the master data or transaction data related to the product type.
  
  Solution:
  
  
  Check Configuration: 
  
  Go to the customizing settings (SPRO) and verify the configuration for the product type in question. Ensure that it is set up correctly for the intended use.
  Check if the product type is active and allowed for the specific transaction you are trying to perform.
  
  
  
  Review Authorizations:
  
  Ensure that the user has the necessary authorizations to access and use the specified product type. This can be checked in the user roles and profiles.
  
  
  
  Consult Documentation:
  
  Review the SAP documentation or help files related to the specific product type and the transaction you are trying to execute. This may provide insights into any restrictions or requirements.
  
  
  
  Check Master Data:
  
  Verify the master data related to the product type. Ensure that all required fields are filled out correctly and that there are no inconsistencies.
  
  
  
  Contact Support:
  
  If the issue persists after checking the above points, consider reaching out to your SAP support team or consulting SAP Notes for any known issues related to this error message.
  
  
  
  Related Information:
  
  SAP Notes: Search for relevant SAP Notes in the SAP Support Portal that may address this specific error message or provide additional troubleshooting steps.
  Transaction Codes: Familiarize yourself with transaction codes related to treasury management (e.g., TRM transactions) to better understand the context in which the error occurs.
  User Forums: Check SAP community forums or user groups for discussions related to this error, as other users may have encountered and resolved similar issues.
  
  By following these steps, you should be able to identify the cause of the error and implement a solution.