Overview

This appendix explains how an RFC destination is used to get data either directly or indirectly. The following figure (also in Chapter 1) shows how data from SAP servers 2 and 3 is extracted directly into SAS.

Solution Architecture

Data from SAP Server 1 is extracted indirectly using SAP Server 2.

Note: A hub can retrieve data from other SAP servers only if they are of the same SAP threaded kernel release.

SAP Server 2 is used as a hub to get data from SAP Server 1 using an SAP destination.

The advantage of direct access is that there is no load on the hub.
The advantage of indirect access is that you do not have to install any ABAP functions or maintain a remote machine.
The disadvantage of using a hub is that if the hub is down, then extractions from other machines are not made.

Note: If there are no restrictions on installing ABAP functions on each machine, then you should use direct access.

The following example shows an SAP ECC 6.0 (release 6.10) being used as an adapter gateway server. The RFC destination for this adapter gateway server is the predefined NONE internal connection.

Type SM59 on the command line to display the RFC destination. The Display and maintain RFC destinations window appears. To display the internal connection properties for NONE, double-click NONE.

The RFC Destination NONE window appears. The properties for the RFC Destination NONE are displayed. The following figure shows the Technical Settings tab.

The following figure shows the Logon & Security tab.

The following figure shows the Special Options tab.