Skip to main content
Version: 5.5

SAP®

warning

Attention: Docker only supports the SAP NetWeaver protocol.

The SAP® plug-in connects the OPC Router to any number of SAP® systems (4.0b or higher) via IDocs, BAPIs, or RFC. This supports all current SAP® systems (e.g., NetWeaver, ECC 6, R/3 from 4.0b ...). The prerequisite is the Log-on Pad or librfc32.dll on the computer with OPC Router. The DLL file must be located in the \Windows\System32 directory. If the program is to run on 64-bit systems in 32-bit mode, the 32-bit version of the DLL must be located in \Windows\SYSWOW64.

To use NetWeaver, SAP® NetWeaver RFC SDK must be installed. SAP® files may not be delivered by inray Industriesoftware GmbH. Therefore, you need a current SAP® account (as of 2018). The following link provides support: https://helpcenter.theobald-software.com/erpconnect/documentation/introduction/saplibraries/

For Librfc32, Microsoft Visual C++ 2005 Service Pack 1 must be installed on some systems: https://www.microsoft.com/de-DE/download/details.aspx?id=26347

The following SAP® authorizations are required by OPC Router:

The following objects are required at a minimum to establish a connection:

S_RFC RFC_TYPE=FUGR ;RFC_NAME=SYST ;ACTVT=16 ; 
S_RFC RFC_TYPE=FUGR ;RFC_NAME=RFC1 ;ACTVT=16 ;

Lookup of tables and table metadata:

S_RFC            RFC_TYPE=FUGR ;RFC_NAME=SDTX ;ACTVT=16 ;  
S_RFC            RFC_TYPE=FUGR ;RFC_NAME=SDIFRUNTIME ;ACTVT=16 ;           
S_TABU_DIS       ACTVT=03 ;DICBERCLS=&NC;& ;

Lookup table for IDocs: EDBAS or use the following separate authorization check for each table to be read:

S_RFC            RFC_TYPE=FUGR ;RFC_NAME=SDTX ;ACTVT=16 ; 
S_RFC            RFC_TYPE=FUGR ;RFC_NAME=SDIFRUNTIME ;ACTVT=16; 
S_TABU_DIS       ACTVT=03 ;DICBERCLS=XXXX ;
S_TABU_NAM       ACTVT = 03; TABLE = DD02V

XXXX is the authority group for the table. You can find out which authorization group belongs to which table in table TDDAT (e.g., with SE16). If the table is not listed there, the authorization group is &NC;&. To authorize specific tables, please use the authorization object S_TABU_NAM instead of S_TABU_DIS.

If user-defined functions such as Z_XTRACT_IS_TABLE_COMPRESSION, Z_XTRACT_IS_TABLE, or Z_XTRACT_IS_TABLE_JOIN are used:

S_RFC            RFC_TYPE=FUGR ;RFC_NAME=XXXX ;ACTVT=16 ;

XXXX is the name of the function group in which the user-defined function module is located.

SAP Query: Looking up and executing a query:

S_RFC            RFC_TYPE=FUGR ;RFC_NAME=AQRC ;ACTVT=16 ;

The standard procedure is as follows:

  1. Open the plug-in by clicking on "SAP" in the "Plug-ins" menu.
  2. Click the plus button or double-click an existing entry.
  3. Make the necessary settings (see section "Properties of SAP® Connections".
  4. Use "Test Connection" to determine whether the connection is established.
  5. Confirm with "OK."

The SAP system is now available for projecting a connection.

note

Note: Be sure to use the "Test" button to check the connection and prevent runtime errors. Please note that changes are only applied after confirming with "OK."

note

Note: When using the NetWeaver protocol, all users must have access to the PSE file. In addition, the SECUDIR environment variable must be defined. The path to the SAP crypto files must be specified as the path. For example, "C:\sapcrypto\nt-x86_64\sec".