Call a Remote Function Module From SAP Cloud Platform, ABAP Environment

First, you need to connect your ABAP on-premise system to a Neo subaccount by means of SAP Cloud Connector.

1. Log on to SAP Cloud Connector:

   • Address = e.g. https://localhost:<port> (Default = 8443)
   • User = Administrator
   • Initial password = Manage (You will change this when you first log in)

2. Choose Add Subaccount:

• Region = Your region. You can find this in SAP Cloud Cockpit (see screenshot below). Note that your SAP Cloud Platform Neo and SAP Cloud Foundry accounts need to run in the same region (e.g. here, Europe Rot)
• Subaccount = “Neo Technical Name”. You can find this by choosing your Neo subaccount in SAP Cloud Cockpit and choosing the information (i) icon. (see screenshot below)
• Display Name = (Neo Subaccount) Display Name. You can find this in by choosing your Neo subaccount in SAP Cloud Cockpit (see screenshot below)
• Subaccount User = for the Neo Subaccount
• Password
• Location ID = Optional here. However, it is mandatory if you want to connect several Cloud Connectors to your subaccount. This can be any text, e.g. your initials

Your configuration should now look like this:

1. In your sub-account, Display Name, choose Cloud to On-Premise > Access Control.

1. In the Mapping Virtual… pane, choose Add (+).

1. Enter the following values, and choose Save.

   • Backend Type = ABAP
   • Protocol = RFC
   • Without load balancing…
   • Internal Host and port (see below)
   • Virtual Host = e.g. es5host. Here, es5host represents an external hostname, so that you can hide the internal hostname from the outside world. You will need this external hostname and port later.
   • Virtual Port = usually, enter the internal Port
   • Principal Type = None
   • Check Internal Host = Ticked
   

2. To find the port, in your on-premise system, choose the transaction SMICM > Goto > Services, then choose an active HTTP port.

The mapping should now look something like this. Check that the status = Reachable. If not, check that you chose the correct port, or whether an internal firewall is preventing communication:

Now, still in the Cloud to On-Premise > Access Control tab, enter the resource you need, RFC_SYSTEM_INFO.

1. Add the resource RFC_SYSTEM_INFO by choosing the Protocol = RFC, then choosing +.

   

2. Enter the name of the RFC, e.g. RFC_SYSTEM_INFO. Alternatively, add RFC as a Prefix. Then choose Save

   

3. Add BAPIs to the list of resources by choosing + again. (You will need this BAPI in a later tutorial.)

4. Enter the name BAPI_EPM as a Prefix, then choose Save.

5. The list of resources should now look roughly like this:

   

You will now create two destinations in the ABAP Environment. These must be created at Space level, e.g. Dev, not subaccount level.

1. In SAP Cloud Cockpit, open your ABAP Environment > your space, such as Dev, then choose Service Instances.

   

2. Open the destination service you created in Create a Communication Arrangement for Outbound Communication

   

3. Create a new destination for the destination service instance

   

1. Again, choose New Destination and enter the following values:

   • Name, e.g. : ES5
   • Type: RFC
   • Description, e.g. ES5 RFC
   • Location ID: same as in step 1, e.g. your initials
   • User: Your user for the on-premise system
   • Password: Your password

2. Add the following additional properties and values, by choosing New Property:

   • jco.client.ashost = <myHost> - again, the external hostname of your on-premise ABAP System in lower-case
   • jco.client.client = <Your ABAP System client, e.g. 002
   • jco.client.sysnr = <Your ABAP System number>, e.g. 11

When you created the communication system for outbound communication, you created the arrangement first, then the system. This time, it is easiest to create the system first, then the arrangement.

1. Go back to your space Dev and choose Service Instances, then choose your abap service instance, e.g. T02.

   

2. Open the Dashboard.

   

3. In the Dashboard, choose Communication Systems > New.

4. In the Destination Service panel, deactivate the destination service function by moving the slider to Off.

   

5. Enter the credentials for the SAP Cloud Connector administration user for your SAP Cloud Platform Neo account.

   • Hostname = URL for your Neo subaccount, without protocol or account, e.g. if your Neo URL = https://account.hana.ondemand.com, then you need hana.ondemand.com

   • User and Password = the same user as in step 1 above

     

     .
     

1. Go back to the Dashboard Home, choose Communication Arrangements again, then choose New.

   

2. Enter the following values and choose Create.

   • Scenario: SAP_COM_0200 (SAP Cloud Connector Integration)
   • Name: SAP_COM_0200_XXX

3. Enter the Communication System you have just created.

4. In the details screen, enter the Account Name: <NEO Technical Name>

   

1. Create a new ABAP class: Choose File > New > Other… > ABAP Class.

2. Enter a name and description. The name should be in the form ZCL_...RFC_XXX. Replace XXX with your group number or initials.

3. Create or assign a transport request.

1. Implement the interface by adding this statement to the public section:

   interfaces if_oo_adt_classrun.

   This allows you to test your class by displaying the output in the ABAP Console.

2. In the implementation section, add the METHOD and ENDMETHOD statements:

   METHOD IF_OO_ADT_CLASSRUN~MAIN.
ENDMETHOD.

1. Create the data types that specify your remote connection information.

IMPORTANT: Always specify the authentication mode using the interface if_a4c_cp_service. Never hard-code your password in the class.

```ABAP
DATA(lo_destination) = cl_rfc_destination_provider=>CREATE_BY_CLOUD_DESTINATION(
                        i_name                  = 'ES5_RFC_XXX'
                        i_service_instance_name = 'OutboundComm_for_RFCDemo_XXX'
                        i_authn_mode            = if_a4c_cp_service=>service_specific
                       ).

DATA(lv_destination) = lo_destination->get_destination_name( ).

DATA lv_result type c length 200.
```

1. Replace the i_service_instance_name with your service instance name, specified in the Communication Arrangement (which you created in Create a Communication Arrangement for Outbound Communication).

2. Replace the i_name with your the name of the specific RFC destination (which you created in SAP Cloud Cockpit in the tutorial Create a Communication Arrangement for Outbound Communication).

   

1. Save and activate the class, using Ctrl+S, Ctrl+F3.

2. Run the class by choosing F9. Some system information, such as the hostname, the System ID ( <SID> ), and the IP address should be displayed.