Skip to main content
Version: 5.4

SAP®

warning

Warning: Docker exclusively supports the SAP NetWeaver protocol

SAP® plug-in connects OPC Router to all reachable SAP® systems (4.0b or higher) via IDoc, BAPI or RFC. Supported are all current SAP® systems (e. g. NetWeaver, ECC 6, R/3 ab 4.0b ...). Prerequisite are either the SAP® log-on pad or library librfc32.dll installed on the computer hosting OPC Router. The library has to be stored at \Windows\System32. If the program is to run in 32-bit mode on 64 bit OS, the 32-version of the DLL has to be in. \Windows\SYSWOW64 .

To use Netweaver, the SAP® NetWeaver RFC SDK must be installed. SAP® files have not be delivered by inray Industriesoftware GmbH. Therefore you need a current SAP® account (status 2018). The following link will help you: https://helpcenter.theobald-software.com/erpconnect/documentation/introduction/saplibraries/

When the librfc32 file is used, Microsoft Visual C++ 2005 Service Pack 1 must be installed on some systems:
https://www.microsoft.com/en-us/download/details.aspx?id=26347

The following SAP® authorizations are required by the OPC Router:

The following objects are needed at least to establish a connection:

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

Look up tables and table meta data:

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& ;

Look up table for IDocs: EDBAS or use the following separate authority check for each table to 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. To find out, which authority group belongs to which table look at table TDDAT (e.g. with SE16). If the table is not listed there the authority group is &NC&. For authorizing specific tables please use authorization object S_TABU_NAM instead of S_TABU_DIS.

If Custom functions like 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 here the name of the function group where the custom function module are located.

SAP Query: Look up and executing a query:

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

Defining access data:

  1. Open plug-in by clicking “SAP access data” in the project configuration’s plug-in list.
  2. Click the plus button or double click on the existing entry.
  3. Specify access data. (chapter Plug-in).
  4. Click on button “Check connection” to verify the OPC Router is getting access to the server and if access data are correct. This is to exclude one typical source of errors.
  5. Confirm with “OK”.

The SAP® server can now be used to define a connection.

note

Note: In any case, use the switchboard “Test” to check the connection and prevent runtime errors. Note that changes are accepted only after confirmation with “OK”.

note

Note: When using the NetWeaver protocol, access to the PSE file must be guaranteed for all users. In addition, the environment variable SECUDIR must be defined. The path to the SAP crypto files must be specified as the path. E.g. ‘C:\sapcrypto\nt-x86_64\sec’.