3440815 - Error "There is no SAP Cloud Connector (SCC) connected to your subaccount RFC_COMMUNICATION_FAILURE" In S/4HANA On-Premise Connection - SAP Datasphere

This KBA applies to SAP Datasphere connections to ABAP-based On-Premise systems (e.g., S/4HANA, ECC, or BW) via SAP Cloud Connector.

The following error occurs for feature data flow and replication flow when validating connection in SAP Datasphere.

• Connection "<connection_name>" couldn’t be established. 
  - Data flows can’t be used because of errors in the connection. 
  - Replication flows can’t be used because of errors in the connection.
  
  Data Flows: Cause: ABAP connector(Axino) ABAP connection check FAILED: request failed: rc=1, msg="Message: Opening connection to backend failed: There is no SAP Cloud Connector (SCC) connected to your subaccount matching the requested tunnel for subaccount \"<Subaccount>\" and SCC location ID \"<Location_ID>\". Check the configuration on SCC and cloud side.\nCode: RFC_COMMUNICATION_FAILURE"
  Please refer to SAP Note 2849542 for more information.
  
  Replication Flows: Cause: ABAP connector(Axino) ABAP connection check FAILED: request failed: rc=1, msg="Message: Opening connection to backend failed: There is no SAP Cloud Connector (SCC) connected to your subaccount matching the requested tunnel for subaccount \"<Subaccount>\" and SCC location ID \"<Location_ID>\". Check the configuration on SCC and cloud side.\nCode: RFC_COMMUNICATION_FAILURE"
  Please refer to SAP Note 2849542 for more information. 

Below message will occur if location ID is not set:

• Data Flows: Cause: ABAP connector(Axino) ABAP connection check FAILED: request failed: rc=1, msg="Message: Opening connection to backend failed: There is no SAP Cloud Connector (SCC) connected to your subaccount matching the requested tunnel for subaccount \"<Subaccount>\" and SCC location ID, with default value, that is empty string or simply not configured. Check the configuration on SCC and cloud side.\nCode: RFC_COMMUNICATION_FAILURE"
  Please refer to SAP Note 2849542 for more information.
  
  Replication Flows: Cause: ABAP connector(Axino) ABAP connection check FAILED: request failed: rc=1, msg="Message: Opening connection to backend failed: There is no SAP Cloud Connector (SCC) connected to your subaccount matching the requested tunnel for subaccount \"<Subaccount>\" and SCC location ID, with default value, that is empty string or simply not configured. Check the configuration on SCC and cloud side.\nCode: RFC_COMMUNICATION_FAILURE"

SAP Datasphere 

Validate the connection in SAP Datasphere.

The issue is caused by a misconfiguration in SAP Cloud Connector (SCC). Specifically, the SAP Datasphere subaccount is either missing in SCC or not correctly mapped to the intended Location ID.

Alternatively this issue can also appear if the SCC Certificate is expired, on this cause please renew certificate with appropriate subaccount user. 

To resolve the issue, ensure the SAP Cloud Connector is correctly configured to connect with SAP Datasphere:

1. Add the Correct Subaccount in SAP Cloud Connector, follow guidelines from SAP Datasphere Help: Configure Cloud Connector
   • Please make sure the Subaccount used in Cloud Connector is from Datasphere -> System -> Administration -> Data Source Configuration -> SAP BTP Core Account -> Subaccount.
     See Point 1 in KBA 3456850 Pre-analysis Cloud Connector related issues when creating connection in Datasphere.
     
     
   • Even for SAP Datasphere CPEA tenants, use the Datasphere's subaccount instead of BTP's subaccount. See KBA 3290588.
     !!! Please DO NOT use the subaccount in BTP Cockpit !!!
   • 
     
     
2. Verify Location ID Consistency
   • Please make sure the Location ID defined in Cloud Connector matches exactly with the Location ID specified in the Datasphere connection settings.
     See Point 2 in KBA 3456850 Pre-analysis Cloud Connector related issues when creating connection in Datasphere.
     
   • If you cannot find the Location ID in dropdown menu of Datasphere connection, please navigate to the following path: Datasphere -> System -> Administration -> Data Source Configuration -> On-Premise Data Sources -> Add a new location to add the Location ID.

• KBA 3290588 - SAP BTP subaccount and SAP Datasphere tenant subaccount are not matching
• KBA 3456850 - Pre-analysis Cloud Connector related issues when creating connection in Datasphere

RFC_COMMUNICATION_FAILURE, Subaccount mapping, Replication Flow, Data Flow, ABAP , KBA , DS-DI-CON , Connections , Bug Filed