How To Fix TQ371 - Test RFC was successful

SAP Error Message - Details

• Message type: E = Error

• Message class: TQ - SAPup Messages

• Message number: 371

• Message text: Test RFC was successful

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 TQ371 - Test RFC was successful ?

  The SAP error message TQ371, which states "Test RFC was successful," is not actually an error message in the traditional sense. Instead, it indicates that a Remote Function Call (RFC) test was executed successfully. This message typically appears when you are testing the connectivity between SAP systems or between an SAP system and an external system.
  Cause:
  
  The message is generated when you perform a test of the RFC connection using transaction codes like SM59 (RFC Destinations) and the test is successful. It confirms that the connection settings are correct and that the systems can communicate with each other.
  
  Solution:
  Since TQ371 indicates a successful test, there is no action required to resolve an error. However, if you are expecting an error or if you are troubleshooting connectivity issues, consider the following steps:
  
  
  Verify Configuration: Ensure that the RFC destination is configured correctly in transaction SM59. Check parameters such as the target host, system number, client, user credentials, and any necessary logon information.
  
  
  Check Network Connectivity: If you are experiencing issues with other RFC calls, ensure that there are no network issues preventing communication between the systems.
  
  
  Review Authorizations: Make sure that the user credentials used for the RFC connection have the necessary authorizations to perform the required actions.
  
  
  Monitor Logs: Check the system logs (transaction SM21) and the application logs (transaction SLG1) for any related messages that might provide more context if you are facing issues elsewhere.
  
  
  Test Other RFC Calls: If you are troubleshooting a specific function module or program, test other RFC calls to ensure that the issue is not isolated to a particular function.
  
  
  Related Information:
  
  
  Transaction Codes:
  
  SM59: Manage RFC destinations.
  SM21: View system logs.
  SLG1: View application logs.
  
  
  
  RFC Types: Understand the different types of RFC connections (e.g., synchronous, asynchronous, transactional) and their use cases.
  
  
  SAP Notes: Check SAP Notes for any known issues or updates related to RFC connectivity.
  
  
  Documentation: Refer to SAP Help documentation for detailed information on configuring and troubleshooting RFC connections.
  
  
  In summary, TQ371 is a confirmation of a successful RFC test, and no action is needed unless you are facing other issues related to RFC communication.