Skip to Content
Technical Articles

Configure Cloud Connector for RFC connection from cloud to on-premise

Hi All,

I am writing this blog to describe steps to build RFC connection from cloud to on-premise using SAP Cloud Connector.


Local PC

  • OS: Windows10 64-bit
  • CF cli: 6.51.0+2acd15650.2020-04-07

Cloud Foundry

  • CF (Europe – Frankfurt)

Netweaver ABAP

  • NetWeaver ABAP 7.53 SP0

Cloud Connector

  • SAP Cloud Connector 2.11.2


1. Setup Cloud Connector

Access SAP Cloud Connector and setup connection from SAP Cloud Platform to ABAP Server.

1.1. Add Subaccount

Click on “Add subaccount” button via menu “Connector”.

Enter Subaccount information.

If you use a trial account, do not use “Europe(Rot) – trial”.  It is for Neo Environment.

“Subaccount” is displayed on SAP Cloud Platform Cockpit menu “Overview”.

1.2. Add ABAP Server to Subaccount setting.

Select “Cloud To On-Premise” menu and click on “+” icon.

Select “ABAP System” as Back-end Type.

Select “RFC” as Protocol.

My ABAP server does not have any Load balancers.

Enter “Application Server” and “Instance Number”.

Enter “Virtual Application Server” and “Virtual Instance Number”.  This is dummy name and number, so just name them for easily recognizable.

No description at this point.

“Check Internal Host” is on and click on “Finish” button.


Click on check availability icon and check the availability.

1.3. Add Accessible Function modules

Click on “+” icon.

Enter Function information and the result is like this.  I used Prefix Naming Policy, which does not need “*” as wildcard.

“BAPI_” is ncessary, since SAP Cloud SDK automatically call “BAPI_TRANSACTION_COMMIT”.  I have not check the exact condition to call the BAPI.

Now Cloud Connector setting is completed.  As a result, we can see the ABAP system from SAP Cloud Platform Cockpit.

Go to Subaccount and select menu Connectivity -> Cloud Connecotrs.

2. Define ABAP Server Destination

Create Destination service by CF cli command “cf create-service”.  “lite” is service plan name.

cf create-service destination lite <destination name>

In my case, I have already created my destination service.

Now define destination for invocation.  Go to SAP Cloud Cockpit destination instance and define ABAP service destination like this.  Though I defined the destination under destination service,  you can also define the one under subaccount -> Connectivity.


You can test the connection!



You must be Logged on to comment or reply to a post.
  • Hi good post!

    I followed the steps, however I don’t see the “Cloud Connectors”  in the section “Connectivity” only “Destinations”. Any idea?



    • Hi

      Are you using Trial account?
      At this point, menu “Cloud Connectors” may not be displayed on Trial Account.

      I’m not sure when it comes again.


        • Hi Michat-san,

          I haven’t tried to use Cloud Connector with Trial Account recently.

          But my colleague said she could use the one for http connection, though she didin’t use RFC connection.



          • cloud%20trial%20accountHi Yohei,

            cloud trial account

            I try to setup http with trial account bout could not found cloud connector under “Connectivity”.

            Could you please suggest?

            ps. my scenario is to connect on-premise to SCP for business application studio to develop UI5 from Odata service.




          • Hi Boonsom-san,

            Though the menu is not displayed, you can connect between SAP CP and Cloud Connector.
            Please try to configure destinations and test the one.



  • Hello, good post!

    With cloud connector is it possible to connect to an on-premise system that uses SAProuter string?

    I need to deploy my application from sap webide but I am not connecting to the client system, maybe because it uses SAProuter

    Any idea?

    Thanks for your return

    • Hi,

      I’m not sure about SAProuter.

      It seems to be used for SAP remote connection.

      I think SAP Cloud platform connects to on-premise systems via cloud connector or reverse proxy.