How To Fix /SAPAPO/SCHED814 - RFC destination &1 is missing in table &2

SAP Error Message - Details

• Message type: E = Error

• Message class: /SAPAPO/SCHED -

• Message number: 814

• Message text: RFC destination &1 is missing in table &2

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 /SAPAPO/SCHED814 - RFC destination &1 is missing in table &2 ?

  The SAP error message /SAPAPO/SCHED814 RFC destination &1 is missing in table &2 typically indicates that there is a missing RFC (Remote Function Call) destination in the specified table, which is necessary for the system to communicate with other SAP systems or external applications.
  Cause:
  
  Missing RFC Destination: The specified RFC destination (denoted by &1) is not defined in the specified table (denoted by &2).
  Configuration Issues: The system may not be properly configured to connect to the required external system or service.
  Transport Issues: If the RFC destination was recently transported from another system, it may not have been included or properly configured in the target system.
  Authorization Issues: The user may not have the necessary authorizations to access the RFC destination.
  
  Solution:
  
  
  Check RFC Destination:
  
  Go to transaction code SM59 in the SAP GUI.
  Look for the RFC destination &1 in the list. If it is missing, you will need to create it.
  If it exists, check its configuration to ensure it is set up correctly (e.g., connection type, target host, system number, etc.).
  
  
  
  Create or Update RFC Destination:
  
  If the RFC destination is missing, create a new one by clicking on "Create" and filling in the necessary details.
  If it exists but is not functioning, you may need to update its settings or test the connection to ensure it is working properly.
  
  
  
  Check Table Configuration:
  
  Identify the table &2 mentioned in the error message. This could be a specific configuration table related to the application.
  Ensure that the RFC destination is correctly referenced in this table.
  
  
  
  Authorization Check:
  
  Ensure that the user has the necessary authorizations to access the RFC destination. This may involve checking user roles and profiles.
  
  
  
  Consult Documentation:
  
  Refer to SAP documentation or notes related to the specific application or module you are working with for any additional configuration steps or requirements.
  
  
  
  System Logs:
  
  Check system logs (transaction SLG1) for any additional error messages or warnings that may provide more context about the issue.
  
  
  
  Related Information:
  
  
  Transaction Codes:
  
  SM59: Manage RFC destinations.
  SLG1: Display application logs.
  SE11: Data dictionary to check table definitions.
  
  
  
  SAP Notes: Search for relevant SAP Notes in the SAP Support Portal that may address this specific error or provide additional troubleshooting steps.
  
  
  SAP Community: Consider checking the SAP Community forums for similar issues and solutions shared by other users.
  
  
  By following these steps, you should be able to resolve the error message and ensure that the necessary RFC destination is properly configured in your SAP system.