SNC Authentication for DeltaQ and OHS
This article shows how to enable Secure Network Connection (SNC) authentication for DeltaQ or OHS extractions types. When using SNC, the application server, RFC destination (SM59), and SAP user must enable SNC via partner name. Communication between the application server and Board Connector then occurs via an RFC destination for DeltaQ or OHS extractions types.
User Configuration in SAP
To enable SNC for the SAP user in Board Connector:
- Open SAP and run the SAP transaction SU01.
- Enter the name of the SAP user that is used in the XTRACT Connection Manager and click [Change].
- Open the SNC tab and provide the SNC name of the SAP user
. In the depicted example, MALAPATI is the user and THEOBALD.LOCAL is the domain.

- Click [Save].
The SAP user can now be used for the SAP connection in Board Connector.
SAP Connection Settings in Board Connector
To set up SNC for your SAP connection in Board Connector, follow the instructions in the Documentation: Configure SNC in the SAP Source.
RFC Destination Configuration in SAP
Enable SNC for the RFC destination using the Service Principal Name (SPN) of the SAP user account:
- Open SAP and run the SAP transaction SM59.
- Double-click on an existing TCP/IP RFC destination, see Create an RFC Destination.
- Navigate to Edit > SNC Options. The window "Change View "SNC Extension": Details" opens.

- Enter the SAP user account SPN in Partners , e.g., p:RfcServer/Malapati@THEOBALD.LOCAL.
- Set Quality of Protection to 8 - Default .
- Activate the SNC Active checkbox .
- Open the Unicode tab and activate Unicode.

- Click [Save] to save your changes.
Board Connector now uses SNC to communicate with the SAP RFC destination.
Related Topics
- Documentation: Create an RFC Destination
- Documentation: Connect to SAP
- Documentation: SAP Connection with SNC
- SAP Help: Maintaining RFC destinations and their SNC options