How To Fix TPM_THX1652 - No deviant market data found for bus. trans. &1 &2 on &3

TPM_THX1652 - Overview

• Message type: E = Error

• Message class: TPM_THX1 - Treasury: Message Class for P-HA

• Message number: 652

• Message text: No deviant market data found for bus. trans. &1 &2 on &3

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_THX1652 - No deviant market data found for bus. trans. &1 &2 on &3 ?

  The SAP error message TPM_THX1652 indicates that there is no deviant market data found for a business transaction in the context of Treasury and Risk Management (TRM) or Financial Instruments Management (FIM). This error typically arises when the system is unable to find the necessary market data for a specific transaction, which is essential for processing or valuation.
  
  Cause:
  
  Missing Market Data: The most common cause is that the required market data (e.g., interest rates, foreign exchange rates, etc.) is not available in the system for the specified date or transaction.
  Incorrect Configuration: There may be issues with the configuration of market data sources or the way the market data is being retrieved.
  Data Validity: The market data might not be valid for the date of the transaction, or it may not have been updated in the system.
  Transaction Type: The specific business transaction type may not have corresponding market data defined in the system.
  
  
  Solution:
  
  Check