How To Fix TPM_THXE1804 - For this process, only the MDS category 2 is supported

SAP Error Message - Details

• Message type: E = Error

• Message class: TPM_THXE1 - message class for effectiveness test

• Message number: 804

• Message text: For this process, only the MDS category 2 is supported

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 TPM_THXE1804 - For this process, only the MDS category 2 is supported ?

  The SAP error message TPM_THXE1804, which states "For this process, only the MDS category 2 is supported," typically occurs in the context of Treasury and Risk Management, particularly when dealing with financial instruments and their valuation.
  Cause:
  This error usually arises when there is an attempt to process a financial transaction or instrument that is not compatible with the expected MDS (Market Data Source) category. In this case, the system is indicating that only MDS category 2 is supported for the specific process you are trying to execute. This could happen due to:
  
  Incorrect Configuration: The system may be configured to expect a specific MDS category that is not being provided.
  Data Issues: The market data being used may not be categorized correctly or may be missing.
  Process Limitations: The specific transaction or process you are trying to execute may have limitations regarding the types of market data it can utilize.
  
  Solution:
  To resolve this error, you can take the following steps:
  
  
  Check MDS Configuration:
  
  Go to the configuration settings for the Treasury module and verify the settings related to MDS categories. Ensure that MDS category 2 is properly configured and that the system is set up to use it for the relevant processes.
  
  
  
  Review Market Data:
  
  Ensure that the market data being used is categorized correctly. You may need to check the data source and confirm that it is providing the necessary MDS category 2 data.
  
  
  
  Transaction Review:
  
  Review the specific transaction or process you are trying to execute. Ensure that it is compatible with MDS category 2 and that you are not attempting to use a different category.
  
  
  
  Consult Documentation:
  
  Refer to SAP documentation or help resources related to Treasury and Risk Management for more details on MDS categories and their usage.
  
  
  
  Contact SAP Support:
  
  If the issue persists after checking the configuration and data, consider reaching out to SAP support for further assistance. They may provide insights specific to your system configuration and version.
  
  
  
  Related Information:
  
  MDS Categories: Understanding the different MDS categories and their purposes can help in troubleshooting. MDS category 2 typically relates to specific types of market data that are used for valuation and risk management.
  SAP Notes: Check for any relevant SAP Notes that may address this error or provide additional guidance on MDS configuration and usage.
  User Forums: Engaging with SAP community forums can also provide insights from other users who may have encountered similar issues.
  
  By following these steps, you should be able to identify the root cause of the TPM_THXE1804 error and implement a suitable solution.