3342716 - Error "Could not invoke function RFC_FUNCTION_SEARCH" 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="An Error occurred: Could not invoke function \"RFC_FUNCTION_SEARCH\" | rfcSDKError[Number:000, RFC_ABAP_EXCEPTION, NO_FUNCTION_FOUND, , , 000, , , , ]. An Error occurred: Could not invoke function \"RFC_FUNCTION_SEARCH\" | rfcSDKError[Number:000, RFC_ABAP_EXCEPTION, NO_FUNCTION_FOUND, , , 000, , , , ]. "
Please refer to SAP Note 2849542 for more information. Code:1103002

Replication Flows: Cause: ABAP connector(Axino) ABAP connection check FAILED: request failed: rc=1, msg="An Error occurred: Could not invoke function \"RFC_FUNCTION_SEARCH\" | rfcSDKError[Number:000, RFC_ABAP_EXCEPTION, NO_FUNCTION_FOUND, , , 000, , , , ]. An Error occurred: Could not invoke function \"RFC_FUNCTION_SEARCH\" | rfcSDKError[Number:000, RFC_ABAP_EXCEPTION, NO_FUNCTION_FOUND, , , 000, , , , ]. "
Please refer to SAP Note 2849542 for more information. Code:1103002

Or

Data Flows: Cause: ABAP connector(Axino) ABAP connection check FAILED: rfc connection broken: rc=1, msg="An Error occurred: Could not invoke function \"RFC_FUNCTION_SEARCH\" : rfcSDKError[Partner signaled an error: Access denied for RFC_FUNCTION_SEARCH on ds.sin.sap.alembic.co.in:sapgw00. Expose the function module in your Cloud Connector in case it was a valid request., RFC_COMMUNICATION_FAILURE, RFC_COMMUNICATION_FAILURE, , , , , , , ]. An Error occurred: Could not get function description for \"RFC_FUNCTION_SEARCH\" : rfcSDKError[An invalid handle 'RFC_CONNECTION_HANDLE' was passed to the API call, RFC_INVALID_HANDLE, RFC_INVALID_HANDLE, , , , , , , ]. "
Please refer to SAP Note 2849542 for more information.

Replication Flows: Cause: ABAP connector(Axino) ABAP connection check FAILED: rfc connection broken: rc=1, msg="An Error occurred: Could not invoke function \"RFC_FUNCTION_SEARCH\" : rfcSDKError[Partner signaled an error: Access denied for RFC_FUNCTION_SEARCH on ds.sin.sap.alembic.co.in:sapgw00. Expose the function module in your Cloud Connector in case it was a valid request., RFC_COMMUNICATION_FAILURE, RFC_COMMUNICATION_FAILURE, , , , , , , ]. An Error occurred: Could not get function description for \"RFC_FUNCTION_SEARCH\" : rfcSDKError[An invalid handle 'RFC_CONNECTION_HANDLE' was passed to the API call, RFC_INVALID_HANDLE, RFC_INVALID_HANDLE, , , , , , , ]. "
Please refer to SAP Note 2849542 for more information. 

Or

Cause: ABAP connector (Axino) ABAP connection check FAILED
Details: RFC connection broken: rc=1
Message: "An invalid handle 'RFC_CONNECTION_HANDLE' was passed to the API call"
Code: RFC_INVALID_HANDLE

Or

When creating data flow or replication flow, while browsing the source connection, error appears:

HTTP Status: 500 Internal Server Error
Error Code: connectionbrowse
Technical Message: Failed to fetch the data. Error in getDisConnectionChildren. Failed to get container children for /.

SAP Datasphere

ABAP Source system is missing prerequisites for Data Flows and Replication Flows features.

1. Verify System Compatibility (Critical)
   To use Data Flows or Replication Flows, your source system MUST meet one of the following criteria. If not met, troubleshooting SCC resources is futile:
   • If using S/4HANA On-Premise:
     Must be 1909 or higher (S4CORE 104+).
     Note for 1709/1809: You cannot install a standalone DMIS add-on to bypass this, as DMIS is embedded in S4CORE. The only path is a system upgrade.
   • If using ECC / BW / NetWeaver / ABAP:
     Must have DMIS Add-on installed (e.g., DMIS 2018 SP08 / DMIS 2020 SP04).
2. SCC Source Configuration
   Make sure to add the required resources in the Cloud Connector as per Datasphere Help page Configure Cloud Connector #3 Section d.
   Ensure there are no typos when maintaining the resources.
3. Upgrade SAP Cloud Connector (SCC) to the latest version, according to KBA 2539713 - Upgrade to a new version of the Cloud Connector.

• SAP Note 2675613 - SLT (DMIS 2010 / DMIS 2011 / DMIS 2018 / DMIS 2020 / S/4HANA) Installation, Corrections and Release Information
• SAP Note 3016862 - DMIS Note Analyzers with separated scenarios for ABAP-based Migration and Replication Technology (DMIS2011/DMIS2018/DMIS2020/SAP S/4HANA)
• SAP Note 3016862 - DMIS Note Analyzers with separated scenarios for ABAP-based Migration and Replication Technology (DMIS2011/DMIS2018/DMIS2020/SAP S/4HANA)

datasphere, dwc, data warehouse cloud, Opening connection to backend failed: LOCATION CPIC (TCP/IP) on local, getDisConnectionChildren , KBA , DS-DI-CON , Connections , Known Error