Configuring SNC: Using RFC from AS ABAP 

To use SNC with RFC calls from AS ABAP, you must configure the SNC options for each RFC destination individually. You can either use transaction SM59 or SM30 (table RFCDESSECU). In this chapter, we describe the procedures using transaction SM59.

Transaction SM59 distinguishes the following types of RFC destinations:

●     R/2 connections (SNC is not supported for these connections.)

●     R/3 connections

●     Internal connections (created automatically and cannot be maintained)

●     Logical destinations

●     Connections to external programs (TCP/IP connections)

It is also possible to maintain HTTP destinations with transaction SM59. To protect these connections, use the Secure Sockets Layer (SSL) protocol and not SNC.

The maintenance of the SNC options for the initiating side of the communication (AS ABAP) is similar for all of these categories and is described in Maintaining RFC Destinations and their SNC Options Using Transaction SM59.

The specifics, along with the options to set for the accepting side, are described in the following topics:

●     RFC: AS ABAP → AS ABAP

●     RFC: Internal Destinations

●     RFC: Logical Destinations

●     RFC: TCP/IP Connection – Start an External Program on an Application Server

●     RFC: TCP/IP Connection – Start an External Program on an Explicit Host

●     RFC: TCP/IP Connection – Start an External Program over SAP GUI

●     RFC: TCP/IP Connection – Registered Program

●     Remote Logon Using Transaction SM51

●     Special Destinations and RFC Groups