How To Fix FTR_GENERAL536 - Product type &1 does not belong to the product category &2

SAP Error Message - Details

• Message type: E = Error

• Message class: FTR_GENERAL - Common messages for Correspondence object

• Message number: 536

• Message text: Product type &1 does not belong to the product category &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 FTR_GENERAL536 - Product type &1 does not belong to the product category &2 ?

  The SAP error message FTR_GENERAL536 indicates that there is a mismatch between the product type and the product category in the system. This error typically occurs in the context of financial transactions, particularly in the area of treasury and risk management, where products are categorized for various financial operations.
  Cause:
  The error arises when:
  
  The product type you are trying to use is not assigned to the specified product category in the system.
  There may be a configuration issue where the product type is not correctly linked to the product category in the customizing settings.
  The product type may have been changed or deleted, or the product category may have been modified.
  
  Solution:
  To resolve this error, you can take the following steps:
  
  
  Check Product Type and Category Configuration:
  
  Go to the customizing settings in SAP (Transaction code SPRO).
  Navigate to the relevant section for Treasury and Risk Management.
  Check the configuration for product types and product categories to ensure that the product type you are using is correctly assigned to the product category in question.
  
  
  
  Verify Product Type Assignment:
  
  Use transaction code FTR_CREATE or FTR_EDIT to check the specific product type and its assignment.
  Ensure that the product type is indeed linked to the correct product category.
  
  
  
  Review Master Data:
  
  Check the master data for the product you are trying to process. Ensure that all necessary fields are filled out correctly and that the product type is valid for the intended operations.
  
  
  
  Consult Documentation:
  
  Review SAP documentation or help files related to product types and categories to understand the relationships and dependencies.
  
  
  
  Contact SAP Support:
  
  If the issue persists after checking the configuration and master data, consider reaching out to SAP support for further assistance. They may provide insights specific to your system configuration.
  
  
  
  Related Information:
  
  
  Transaction Codes:
  
  SPRO: Customizing settings.
  FTR_CREATE: Create financial transaction.
  FTR_EDIT: Edit financial transaction.
  
  
  
  SAP Notes and Documentation:
  
  Check for any relevant SAP Notes that may address this specific error or provide additional guidance on product type and category configurations.
  
  
  
  User Roles and Authorizations:
  
  Ensure that the user has the necessary authorizations to access and modify product types and categories.
  
  
  
  By following these steps, you should be able to identify the cause of the error and implement a solution to resolve it.