How To Fix SRT_ADMIN013 - Service RFC destination & does not exist (SM59)

SAP Error Message - Details

• Message type: E = Error

• Message class: SRT_ADMIN - Administration Messages for SOAP Runtime

• Message number: 013

• Message text: Service RFC destination & does not exist (SM59)

The given RFC destination is not in the list of RFC destinations of type
3.

What causes this issue?

The RFC destination required for SOAP Runtime to run properly does not
exist.

System Response

A correctly defined RFC destination is a prerequisite for SOAP Runtime
to run properly.

How to fix this error?

Inform your system administrator.

Procedure for System Administrators

Use transaction SM59 to define an RFC destination with the type 3.
Remember to enter the required system user and password under "Logon <(>
&<)> Security". The value of the current client must also be entered in
the "Client" field. Assign profile values to the system user, for
example as specified in the standard profile
WS_RT_LOC_SRV_USR_BGRFC_OUTB.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message SRT_ADMIN013 - Service RFC destination & does not exist (SM59) ?

  The SAP error message SRT_ADMIN013 indicates that a specified RFC (Remote Function Call) destination does not exist in the system. This error typically occurs when trying to configure or use a service that relies on an RFC destination that has not been defined in the SAP system.
  Cause:
  
  Missing RFC Destination: The specified RFC destination is not created in transaction SM59.
  Incorrect Configuration: The RFC destination may exist but is incorrectly configured or inactive.
  Typographical Error: There may be a typo in the name of the RFC destination being referenced.
  Authorization Issues: The user may not have the necessary authorizations to access the RFC destination.
  
  Solution:
  
  
  Create the RFC Destination:
  
  Go to transaction SM59.
  Check if the RFC destination exists. If it does not, create a new one:
  
  Click on the "Create" button.
  Enter the name of the RFC destination and configure the necessary parameters (e.g., target host, system number, client, user, password).
  Save the configuration.
  
  
  
  
  
  Check Existing RFC Destination:
  
  If the RFC destination exists, double-click on it to check its configuration.
  Ensure that all parameters are correctly set, including the connection type (e.g., T, 3, etc.), target host, and logon credentials.
  Test the connection using the "Connection Test" button to ensure it is working properly.
  
  
  
  Check for Typos:
  
  Verify that the name of the RFC destination being referenced in your configuration or code is spelled correctly.
  
  
  
  Authorization Check:
  
  Ensure that the user has the necessary authorizations to access the RFC destination. This may involve checking roles and authorizations in transaction PFCG.
  
  
  
  Check for System Issues:
  
  If the RFC destination is supposed to exist but is not found, check for any system issues or inconsistencies that may have caused the destination to be deleted or become inactive.
  
  
  
  Related Information:
  
  
  Transaction Codes:
  
  SM59: Manage RFC destinations.
  PFCG: Role maintenance for authorization checks.
  
  
  
  Documentation: Refer to SAP Help documentation for detailed information on configuring RFC destinations and troubleshooting connectivity issues.
  
  
  Logs: Check system logs (transaction SM21) for any related error messages that might provide additional context.
  
  
  By following these steps, you should be able to resolve the SRT_ADMIN013 error and ensure that the required RFC destination is properly configured and accessible.