How To Fix TPM_THX1473 - Only automatically created documentation allowed for FX scenarios

SAP Error Message - Details

• Message type: E = Error

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

• Message number: 473

• Message text: Only automatically created documentation allowed for FX scenarios

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_THX1473 - Only automatically created documentation allowed for FX scenarios ?

  The SAP error message TPM_THX1473, which states "Only automatically created documentation allowed for FX scenarios," typically occurs in the context of Treasury and Risk Management (TRM) when dealing with foreign exchange (FX) transactions. This error indicates that the system is configured to only allow documentation that is automatically generated for FX scenarios, and manual documentation attempts are being blocked.
  Cause:
  
  Configuration Settings: The system is set up to restrict manual documentation for FX transactions. This is often a result of specific configuration settings in the Treasury module.
  Transaction Type: The transaction type being used may not allow for manual documentation, as it is designed to only support automatically generated documentation.
  Document Type Restrictions: Certain document types may have restrictions that prevent manual entries, especially in the context of FX transactions.
  
  Solution:
  
  Check Configuration: Review the configuration settings in the Treasury module to ensure that the settings for FX transactions allow for the type of documentation you are trying to create. This may involve checking the settings for transaction types and document types.
  Use Automatic Documentation: If the system is configured to only allow automatic documentation, ensure that you are following the correct process to generate the necessary documentation automatically. This may involve executing specific transactions or processes that create the documentation as part of the workflow.
  Consult Documentation: Refer to SAP documentation or help resources for guidance on how to handle FX transactions and the associated documentation requirements.
  Contact SAP Support: If you are unable to resolve the issue through configuration changes or process adjustments, consider reaching out to SAP support for assistance. They can provide insights specific to your system configuration and help troubleshoot the issue.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes in the Treasury module that pertain to FX transactions and documentation.
  SAP Notes: Check for any SAP Notes related to this error message, as they may provide additional context or solutions.
  User Roles and Authorizations: Ensure that the user attempting to create documentation has the necessary authorizations to perform the action, as restrictions may also be tied to user roles.
  
  By following these steps, you should be able to address the TPM_THX1473 error and ensure that your FX documentation processes are functioning as intended.