Show TOC

 RFC: Internal DestinationsLocate this document in the navigation structure

At start-up, the AS ABAP automatically generates the RFC internal destinations to application servers within the same system(type = I). The system also automatically makes their respective entries in the table SNCSYSACL. You cannot manually maintain these entries.

Note

For performance reasons, we do not recommend using SNC for internal destinations! (See Recommendations.)

If you do want to secure RFCs to internal destinations with SNC, then set the parameters snc/r3int_rfc_secure and snc/r3int_rfc_qop in the initiating AS ABAP's profile (see Profile Parameter Settings on AS ABAP). Make sure that these parameters are identically set for the various application servers that are to use RFCs to internal destinations.

If internal RFCsare not to be protected with SNC (snc/r3int_rfc_secure= 0), then leave the profile parameter snc/accept_insecure_r3int_rfc to  its default value "1". Otherwise, you cannot use internal RFCs and your system will not function correctly.

Note

For incoming RFCs to internal destinations, the system does verify the entry in the SNCSYSACL table. This entry is automatically created as an internal destination (type = I) at start-up, based on the information located in the above mentioned profile parameters.