How To Fix RSDS_ACCESS035 - No RFC destination defined for source system &1

SAP Error Message - Details

• Message type: E = Error

• Message class: RSDS_ACCESS - Access Messages

• Message number: 035

• Message text: No RFC destination defined for source system &1

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 RSDS_ACCESS035 - No RFC destination defined for source system &1 ?

  The SAP error message RSDS_ACCESS035 indicates that there is no RFC (Remote Function Call) destination defined for the specified source system in the context of SAP Data Services or SAP BW (Business Warehouse). This error typically occurs when trying to access data from a source system that has not been properly configured in the SAP system.
  Cause:
  
  Missing RFC Destination: The most common cause is that the RFC destination for the source system has not been created or is not correctly configured in the SAP system.
  Incorrect Source System Configuration: The source system may not be properly defined in the SAP BW system or the Data Services environment.
  Authorization Issues: The user may not have the necessary authorizations to access the RFC destination or the source system.
  Network Issues: There may be network connectivity issues preventing access to the source system.
  
  Solution:
  
  
  Create or Check RFC Destination:
  
  Go to transaction SM59 in the SAP GUI.
  Check if the RFC destination for the source system exists. If it does not, create a new RFC destination.
  Ensure that the destination type is set correctly (usually "3" for a TCP/IP connection).
  Test the connection to ensure it is working properly.
  
  
  
  Configure Source System:
  
  In the SAP BW system, go to transaction RSA1 (Data Warehousing Workbench).
  Navigate to the "Source Systems" section and ensure that the source system is defined correctly.
  If necessary, reconfigure the source system settings.
  
  
  
  Check Authorizations:
  
  Ensure that the user has the necessary authorizations to access the RFC destination and the source system.
  Check roles and profiles assigned to the user.
  
  
  
  Network Connectivity:
  
  Verify that there are no network issues preventing access to the source system.
  Check firewall settings and network configurations.
  
  
  
  Review Logs:
  
  Check the system logs (transaction SM21) and the application logs (transaction SLG1) for any additional error messages that may provide more context.
  
  
  
  Related Information:
  
  RFC Destinations: RFC destinations are used in SAP to define how to connect to other SAP systems or external systems. They contain connection parameters such as the target system's hostname, system number, and client.
  SAP BW Source Systems: In SAP BW, source systems are external systems from which data is extracted. Proper configuration is essential for data extraction processes.
  SAP Notes: Check SAP Notes for any known issues or patches related to the error message RSDS_ACCESS035.
  
  By following these steps, you should be able to resolve the error and ensure that the RFC destination for the source system is correctly defined and accessible.