3460828 - Error "Expose the system in your Cloud Connector in case it was a valid request 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: Opening connection to <host:port> denied. Expose the system in your Cloud Connector in case it was a valid request.\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: Opening connection to <host:port> denied. Expose the system in your Cloud Connector in case it was a valid request.\nCode: RFC_COMMUNICATION_FAILURE"
Please refer to SAP Note 2849542 for more information.

• SAP Datasphere
• SAP Cloud Connector

Validation the connection.

The Virtual Host and Port in the connection settings do not match the configuration in SAP Cloud Connector. 

Please have a look at Point 5 in KBA 3456850 - Pre-analysis Cloud Connector related issues when creating connection in Datasphere.

• If using application server, the virtual port is like sapgw<nn>
• If using message server, the virtual port is numeric format (without leading zero)

----------------------------------------------------------------------

Note: If Cloud Connector is used for Remote Table Data Provisioning, in this case:

1. There will be 2 mappings in SCC. One is with RFC protocol; another is with HTTPS protocol. They should have the same virtual host. The virtual port for RFC protocol mapping should be system number, which is sapgw<instance number>. For example, if the instance number is 00, the virtual port would be 00, and finally be sapgw00.
2. In Datasphere connection SCC part, the virtual host and port of HTTPS protocol should be maintained there.

For detail, please see SAP S/4HANA On-Premise Connections | SAP Help Portal.

• SAP Help Portal Documentation: SAP Datasphere
• SAP Community: SAP Datasphere
• SAP Community: SAP Datasphere - Best Practices and Troubleshooting
• open.SAP course : Introduction to SAP Datasphere
  
• SAP Tutorial for Developers: SAP Datasphere
• KBA 3456649 - FAQ: Datasphere simple questions
• SAP Help Portal Documentation: SAP S/4HANA On-Premise Connections
• KBA 3369433 - How to troubleshoot Cloud Connector related issues when creating connection in Datasphere (search for 'it was a valid request')
• SAP Note 2835207 - ABAP connection type for SAP Data Intelligence / SAP Datasphere (search for 'for SAP Datasphere')

Data, Sphere, S4, S4Hana, Hana, Cloud, Connector, On, Premise, Virtual, Host, Connection, Fail, Failed, Error, help, Port, IP , KBA , DS-DI-CON , Connections , Problem