Accessing and Using R/3 Data

Accessing Data Using Secure Network Communications

The SAP System and the RFC protocol support secure network communications (SNC). SNC can be configured to enable single sign-on (SSO). SNC can also be used without single sign-on; in this case, user name and password credentials are still required. This section shows two examples of how to specify the SNC logon information with the SAP LIBNAME engine. The SAP System and the user accounts must be configured for SNC. For information about how to configure the SAP System and SNC, see the SAP document Secure Network Communications User's Guide.

Using the saprfc.ini File

This method requires creating an entry in the saprfc.ini file similar to the following example:

DEST=SI9
TYPE=A
ASHOST=sapr3srv.sup.com
SYSNR=03
SNC_MODE=1
SNC_PARTNERNAME=p:SAPServiceSI9@sup.com
SNC_LIB=C:\Public\win32sso\gssntlm.dll

Then, use the LIBNAME statement to use the connection:

libname a r3 dest=SI9;

Using the RFC_STRING option

Another alternative is to use the RFC_STRING option to apply additional settings:

 libname a r3 ashost=sapr3srv.sup.com sysnr=03 
    rfc_string="SNC_MODE=1 SNC_PARTNERNAME=p:SAPServiceSI9
    SNC_LIB=C:\Public\win32sso\gssntlm.dll";

Note: The SNC_LIB string must not contain blanks. [cautionend]

This document shows two examples of how to use SNC for single sign-on in a LIBNAME statement. For more information about SNC and SNC configuration, see SAP documentation and other third-party documentation.

Top of Page