How To Fix OT086 - RFC destination deleted

SAP Error Message - Details

• Message type: E = Error

• Message class: OT - SAP Online Correction Support (SOCS)

• Message number: 086

• Message text: RFC destination deleted

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 OT086 - RFC destination deleted ?

  The SAP error message OT086, which indicates that an RFC (Remote Function Call) destination has been deleted, typically arises when a program or transaction attempts to access an RFC destination that no longer exists in the system. This can happen for various reasons, such as manual deletion, system changes, or configuration issues.
  Cause:
  
  Manual Deletion: The RFC destination may have been manually deleted by an administrator or during system maintenance.
  Transport Issues: If the RFC destination was part of a transport request that was not properly imported, it may not exist in the target system.
  Configuration Changes: Changes in system configuration or updates may lead to the deletion or alteration of RFC destinations.
  System Migration: During system migrations or upgrades, certain configurations may not be carried over, leading to missing RFC destinations.
  
  Solution:
  
  
  Check RFC Destination: 
  
  Go to transaction code SM59 (RFC Destinations) and check if the destination exists. If it does not, you will need to recreate it.
  
  
  
  Recreate RFC Destination:
  
  If the destination is missing, you can create a new RFC destination by following these steps:
  
  In SM59, click on "Create" and enter the necessary details (e.g., destination name, connection type, target host, system number, etc.).
  Test the connection to ensure it is working correctly.
  
  
  
  
  
  Review Transport Requests:
  
  If the RFC destination was supposed to be transported from another system, check the transport requests to ensure they were imported correctly.
  
  
  
  Check System Logs:
  
  Review system logs (transaction SM21) for any related errors or warnings that might provide additional context about the deletion.
  
  
  
  Consult Documentation:
  
  If the RFC destination is part of a specific application or module, consult the relevant documentation or support resources for guidance on the required configuration.
  
  
  
  Contact SAP Support:
  
  If you are unable to resolve the issue, consider reaching out to SAP support for assistance, especially if this is impacting critical business processes.
  
  
  
  Related Information:
  
  RFC Destinations: These are configurations that allow SAP systems to communicate with each other or with external systems. They can be of different types, such as TCP/IP connections, HTTP connections, etc.
  Transaction Codes:
  
  SM59: Manage RFC destinations.
  SM21: View system logs.
  ST22: Check for dumps that might provide additional context.
  
  
  Documentation: SAP Help Portal and community forums can provide additional insights and troubleshooting steps.
  
  By following these steps, you should be able to identify the cause of the OT086 error and implement a solution to restore the necessary RFC destination.