Skip to end of metadata
Go to start of metadata

RFC Destination is one of the way to connect from an ABAP system to an external system. This weblog talks about the basic HTTP connection to external server (type G).

Business usecase from my area of expertise is connecting any R/3 system to a CE ESR (mainly for Proxy generation of Services Modeled in ESR).

Step 1:

Go to transaction SM59.

UI looks like as follows:


Step 2:

As shown in the picture above, select the HTPP connection to external server and click on the Create icon (marked in red).

RFC Connection UI will come up. Fill in the necessary details as shown below:


 
Note that RFC Name should be unique, connection type should be Type-G.

Other information you need to enter is the host (or IP), Port and the Context root. The following URL should match the service deployed on AS.

A good example to use the RFC destination will be to write a small ABAP code to establish connection to a servlet deployed on AS. User can use HTTP protocol to invoke it from ABAP.

Step 3:

Click on the save icon  and you will recieve an info message stating "HTTP connection may not be secure" which is true.


 
Press  to continue.

Step 4:

Now most of the application which the RFC destination points to will require some basic authentication. And if it is not provided part of the RFC destination, quite possible when the program uses the RFC Destination, it prompts for username-password! So lets enter the logon & security details as shown below:

Step 5: 

Click on the save icon  and now press on the connection test button to see whether the server is available or not. Incase the entries point to the correct system, output should be somewhat similar as shown below:

 

More info:

- Incase wrong entries are provided error message comes at the status bar:

- Connection test DO NOT check the credentials. Even if wrong credentials are passed this information is not validated.

Next steps... write small abap code to invoke a servlet...!!! Sounds simple & interesting.