Special Destinations and RFC Groups 

The following information applies to SNC protection for special cases in RFC.

Destination BACK

When a function module establishes an RFC call using the destination BACK, the return connection is automatically protected with SNC if the original connection was SNC-protected. The system does not set up a new connection for the BACK destination; it uses the original connection for the return connection.

Destination NONE

The destination NONE is a special internal destination and is handled in the same way as other internal destinations. If you apply SNC protection to internal connections, then connections that use the destination NONE will also use SNC protection. (See the profile parameter snc/r3int_rfc_secure.)

Destinations without RFCDES Entry

Destinations without an RFCDES entry cannot use SNC protection.

RFC Groups

RFC groups combine the application servers of a single SAP system into a group. When you use RFC calls to groups (CALL FUNCTION ... DESTINATION IN GROUP ...), the application server is selected at the time of the call. Currently, you cannot apply SNC protection for calls to RFC groups.

RFC groups are internal destinations, and therefore you do not need to protect them with SNC. You can provide protection for internal destinations by isolating your local network and protecting it with a firewall. See Recommendations.