How To Fix /SMB/CUSTOMIZING066 - RFC destination &1 not found

SAP Error Message - Details

• Message type: E = Error

• Message class: /SMB/CUSTOMIZING -

• Message number: 066

• Message text: RFC destination &1 not found

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 /SMB/CUSTOMIZING066 - RFC destination &1 not found ?

  The SAP error message /SMB/CUSTOMIZING066 RFC destination &1 not found indicates that the system is unable to find the specified RFC (Remote Function Call) destination. This can occur in various scenarios, such as when trying to access a remote system or when executing a function that requires communication with another SAP system or external application.
  Cause:
  
  Missing RFC Destination: The specified RFC destination does not exist in the system.
  Incorrect Configuration: The RFC destination may be incorrectly configured or may have been deleted.
  Authorization Issues: The user may not have the necessary authorizations to access the RFC destination.
  Network Issues: There may be network connectivity issues preventing access to the remote system.
  Typographical Errors: There may be a typo in the name of the RFC destination.
  
  Solution:
  
  
  Check RFC Destination:
  
  Go to transaction code SM59 in the SAP GUI.
  Look for the RFC destination specified in the error message.
  If it does not exist, you will need to create it.
  
  
  
  Create or Update RFC Destination:
  
  If the RFC destination is missing, create a new one by clicking on the "Create" button.
  Fill in the required fields, such as the target host, system number, and client.
  Test the connection to ensure it is working correctly.
  
  
  
  Verify Configuration:
  
  Ensure that the configuration settings (like user credentials, connection type, etc.) are correct.
  Check if the destination is set to the correct type (e.g., TCP/IP, HTTP, etc.).
  
  
  
  Check Authorizations:
  
  Ensure that the user has the necessary authorizations to access the RFC destination.
  You may need to consult with your security team to verify user roles and permissions.
  
  
  
  Network Connectivity:
  
  Check if there are any network issues that might be preventing access to the remote system.
  Use tools like ping or telnet to test connectivity to the target host.
  
  
  
  Review Logs:
  
  Check the system logs (transaction SM21) for any additional error messages that might provide more context.
  
  
  
  Related Information:
  
  RFC Destinations: RFC destinations are used in SAP to define how to connect to other systems. They can be local or remote and are essential for various integrations.
  Transaction Codes:
  
  SM59: Manage RFC destinations.
  SM21: View system logs.
  SU53: Check authorization issues.
  
  
  Documentation: Refer to SAP Help documentation for detailed information on configuring RFC destinations and troubleshooting connectivity issues.
  
  By following these steps, you should be able to resolve the error message /SMB/CUSTOMIZING066 RFC destination &1 not found. If the issue persists, consider reaching out to your SAP Basis team for further assistance.