SAP Snap Pack
In this article
Overview
This Snap Pack lets you interact with SAP.
Use Snaps in this Snap Pack to:
- Execute the configured SAP business API (BAPI) given input data
- Read, write, or receive SAP IDoc requests.
- Listen to incoming RFC calls infinitely, and either generate output documents from the import parameters, or trigger a child Pipeline.
Supported Version
This SAP Snap Pack has been tested against SAP ECC 6.0 EPH8.
The JCo driver (3.1.x
) supports R/3 3.1I and higher releases and RFC communication (classic CPIC or via WebSocket). Learn more about JCo driver.
The SAP snap pack depends on a native library. The available versions of this library are:
Linux:
libsapjco3.so md5sum:
8c37756820516807e2edff3ff332fdc1)
- Mac:
libsapjco3.dylib
md5sum
:e3c360818d9f640d875d2f18725131fd)
Windows:
sapjco3.dll md5sum:
188977c0315ec2d76c0ed74159c81f35)
Optional. You can verify the integrity of the file using md5sum.
Breaking change for Pipelines using the SAP Snaps with Java Native Library
If you have any existing Pipelines that contain Snaps from the SAP Snap Pack, you must manually upgrade your SAP Java Connector (JCo) Native Library to 3.1.10 version. Learn more: SAP Configuration.
Known Issue
When you upgrade the SAP Snap Pack from 4.37 GA main24152
to 4.38 GA main27765
(in SnapLogic Manager), with the old SAP native library still installed, the following fatal initialization error displays:
Workaround:
Follow the steps below to resolve the issue:
Copy the updated native library:
For Linux, copy the updated native library
libsapjco3.so
file to the/opt/snaplogic/ldlib
folder on every node in the Snaplex.For Windows, copy the updated native library
sapjco3.dll
file to theC:\opt\Snaplogic\ldlib
folder on every node in the Snaplex.
Note: For Snaplexes with multiple nodes, make sure to install the library on every node.
Restart all the nodes in the Snaplex.
You can download the library here.
Learn more: Implementing the Library Upgrade for SAP Snap Pack