SAP® connections
If an SAP® connection cannot be established or if IDocs and RFC calls are not being sent, check the following points. If the flow does not reach the transfer stage at all, first follow the steps in “: Transfer Is Not Running” at.
Check the connection
The SAP® connection includes its own test: In the plug-in configuration, go to “Check connection” to check whether the connection is established, and then apply the settings—see Setting Up the SAP® Connection.
If IDoc redundancy is enabled, test the connection to the Redis cache separately using the dedicated button on the “” tab under “Advanced”.
Access is denied
The OPC Router requires its own authorizations in the SAP® system. If these are missing, the connection will not fail, but access to function modules and tables will be denied. The required authorization objects are listed at Required SAP® Authorizations .
To use the preferred settings of the SAP® user, the OPC Router also requires read access to the SAP® table USR01.
The port is incorrect
By default, the OPC Router uses port 33<System-Nummer>. If the SAP® system uses a different port and the SAP® GUI is not installed, the port must be adjusted in the operating system’s services file. The steps are described at Adjusting the Port Used .
For IDocs that the SAP® system sends to the OPC Router, the incoming port of the IDoc trigger must also be enabled—see Network Ports.
The secure connection (SNC) cannot be established
If the connection is secured via Secure Network Communications, the SAP® Crypto files are also required: All users need access to the PSE file, and the environment variable SECUDIR must point to the path containing the SAP® Crypto files. The complete prerequisites are available at Secure Network Communications (SNC).
These files are not required for connections using Basic Authentication.
IDocs Are Not Being Received
Check the route from the SAP® side: Use transaction WE19 to send an IDoc to the OPC Router; errors can be viewed in WE07. For information on which function to call in the SAP® system, see IDoc-Trigger.
In redundant operation, there is an additional cause: If both instances have the same program ID, the SAP® system cannot reliably distinguish which instance should be addressed—see SAP® in Redundant Operation .
An RFC call returns an error
The RFC trigger returns the result of the transfer via TRANSFER_OK to the SAP® system. The value 3 = Error indicates that an error occurred during execution: The request must be resent later and must not be marked as completed by the connected system. The full meaning of the return values can be found at RFC-Trigger .
The service pauses in the event of a trigger error
In the "" tab, under "Advanced" > "," there is a specific option for this: If it is enabled, the OPC Router will not stop in the event of an error in the SAP® trigger—RFC or IDoc—and will continue to run.