How To Fix TPM_TRDT117 - Original nominal amount is not supported for product type &1

SAP Error Message - Details

• Message type: E = Error

• Message class: TPM_TRDT - Legacy Data Transfer Messages

• Message number: 117

• Message text: Original nominal amount is not supported for product type &1

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_TRDT117 - Original nominal amount is not supported for product type &1 ?

  The SAP error message TPM_TRDT117, which states "Original nominal amount is not supported for product type &1," typically occurs in the context of Treasury and Risk Management (TRM) when dealing with financial instruments or products that have specific requirements regarding their nominal amounts.
  Cause:
  The error is usually triggered when:
  
  Product Type Restrictions: The product type specified does not support the original nominal amount being entered. Each product type in SAP has specific configurations and rules regarding nominal amounts.
  Configuration Issues: The configuration for the product type may not be set up correctly to handle the nominal amount you are trying to enter.
  Data Entry Errors: There may be a mistake in the data entry, such as entering a nominal amount that is not valid for the selected product type.
  
  Solution:
  To resolve this error, you can take the following steps:
  
  
  Check Product Type Configuration:
  
  Go to the configuration settings for the specific product type in SAP. Ensure that the product type is configured to accept the nominal amount you are trying to enter.
  You may need to consult with your SAP administrator or a functional consultant to verify the settings.
  
  
  
  Review the Nominal Amount:
  
  Ensure that the nominal amount you are entering is valid for the product type. Check if there are any specific rules or limits for the nominal amount associated with that product type.
  
  
  
  Consult Documentation:
  
  Review the SAP documentation or help files related to Treasury and Risk Management for any specific guidelines regarding nominal amounts for different product types.
  
  
  
  Test with Different Values:
  
  If possible, try entering different nominal amounts or using a different product type to see if the error persists. This can help identify if the issue is with the specific amount or the product type itself.
  
  
  
  Contact SAP Support:
  
  If the issue persists after checking the configuration and data entry, consider reaching out to SAP support for further assistance. They may provide insights or patches if it’s a known issue.
  
  
  
  Related Information:
  
  SAP Notes: Check for any relevant SAP Notes that might address this specific error or provide additional context.
  Transaction Codes: Familiarize yourself with relevant transaction codes in SAP for managing Treasury products, such as TPM1 for creating financial transactions.
  User Roles and Authorizations: Ensure that the user has the necessary roles and authorizations to perform actions related to the product type in question.
  
  By following these steps, you should be able to identify the cause of the error and implement a solution to resolve it.