SAP Knowledge Base Article - Preview

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

Symptom

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"

Image/data in this KBA is from SAP internal systems, sample data, or demo systems. Any resemblance to real data is purely coincidental. 


Read more...

Environment

SAP Datasphere 

Product

SAP Datasphere all versions

Keywords

RFC_COMMUNICATION_FAILURE, Subaccount mapping, Replication Flow, Data Flow, ABAP, There is no SAP Cloud Connector (SCC), location ID , KBA , DS-DI-CON , Connections , Bug Filed

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.