How To Fix RSDS220 - Could not check destination &1 of external system &2

RSDS220 - Overview

• Message type: E = Error

• Message class: RSDS - New DataSource

• Message number: 220

• Message text: Could not check destination &1 of external system &2

What causes this issue?

While checking destination&v1& of type <ZK>external system</> , an error
occurred.

System Response

It is not known whether the external system supports the object type
<ZK>DataSource</> (R3TR RSDS).

How to fix this error?

Only continue with the modeling if you are certain that DataSources are
supported by the external system.

Procedure for System Administrators

The system determines whether the source system can support DataSources
(R3TR RSDS) using BAPI_DSOURCE_IS_SUPPORTED.

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message RSDS220 - Could not check destination &1 of external system &2 ?

  The SAP error message RSDS220, which states "Could not check destination &1 of external system &2," typically occurs in the context of SAP Data Services or when trying to connect to an external system (like a database or another SAP system) using a defined RFC (Remote Function Call) destination.
  
  Cause:
  The error can be caused by several factors, including:
  
  
  Incorrect RFC Destination Configuration: The RFC destination may not be configured correctly in the SAP system. This includes incorrect connection parameters, such as the hostname, service number, or user credentials.
  
  
  Network Issues: There may be network connectivity issues preventing the SAP system from reaching the external system.
  
  
  Authorization Issues: The user credentials used in the RFC destination may not have the necessary authorizations to access the external system.
  
  
  External System Down: The external system may be down or not reachable due to maintenance or other issues.
  
  
  Firewall Restrictions: Firewalls or security settings may be blocking the connection to