Symptom
When developing a cloud application on BTP to call a function module in an on-premise ABAP system via RFC, the call fails with the following error messages:
- Errors:Initialization of repository destination xxxx failed: Opening connection to backend failed: There is no SAP Cloud Connector (SCC) connected to your subaccount matching the requested tunnel for subaccount "JCoSingleTenantKyma" and SCC location ID "xxxx". Check the configuration on SCC and cloud side.
- com.sap.conn.jco.JCoException: (102) JCO_ERROR_COMMUNICATION: Opening connection to backend failed: There is no SAP Cloud Connector (SCC) connected to your subaccount matching the requested tunnel for subaccount \"JCoSingleTenantKyma\" and SCC location ID \"xxxx\". Check the configuration on SCC and cloud side.
An incorrect subaccount JCoSingleTenantKyma is shown in the message above.
Read more...
Environment
BTP Cloud Foundry
Cloud Connector
Product
SAP Business Technology Platform all versions
Keywords
JCO_ERROR_COMMUNICATION, JCoSingleTenantKyma, xsuaa, Authorization and Trust Management Service , KBA , BC-MID-CON-JCO , Java-Connector , BC-MID-SCC , SAP Cloud Connector On-Demand/On-Premise Connectivity , Problem
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.