On this Page
|Table of Contents|
This account is used by the Snaps in the SAP Account Snap Pack.
You can create an account from with the Designer or Manager. In Designer, when working on pipelines, every Snap that needs an account prompts you to create a new account or use an existing account. The accounts can be created in or used from:
- Your private project folder: This folder contains the pipelines that will use the account.
- Your Project Space’s shared folder: This folder is accessible to all the users that belong to the Project Space.
- The global shared folder: This folder is accessible to all the users within an organization in the SnapLogic instance.
Required Permissions in SAP Account
|Authorization Object||Parameter||Expected Value|
Depending on what BAPI method or which IDoc type is used in the Pipeline, you may need to extend the permissions in your SAP account.
In Manager, you can navigate to the required folder and create an account in it (see Accounts). To create an account for SAP:
- Click Create, then select SAP, then any SAP JCo Account.
- Supply an account label.
- Supply the necessary information for the appropriate account type:
- SAP JCo Account
- SAP Load Balanced JCo Account
- (Optional) Supply additional information on this account in the Notes field of the Info tab.
- Click Apply
SAP JCo Account
SAP Load Balanced JCo Account
The SAP Load Balanced JCo Account is used to connect to a message server.
Installing JCO Library
Install the SAP Java Connection (JCO) library for this Snap Pack to work.
- In all nodes of the Snaplex, install
sapjco3.dllin %SL_ROOT%\ldlib (usually, c:\opt\Snaplogic\ldlib).
- Upload the
sapjco3.jarfile into the project that you want to use for SAP integration.
- Set the Windows PATH variable to point to c:\opt\Snaplogic\ldlib. Restart the Snaplex (JCC).
If an MSHOST is configured, add
sapms<SystemID><MSHOSTPort>/tcp, for example:to %WINDIR%\System32\drivers\etc\services.
- In all nodes of the Snaplex, install
libsapjco3.soin $SL_ROOT/ldlib (usually /opt/Snaplogic/ldlib).
libsapjco3.jnilibin $SL_ROOT/ldlib (usually /opt/Snaplogic/ldlib).
- Upload the
sapjco3.jarfile into the project that you want to use for SAP integration. Restart the Snaplex (JCC).
- If an MSHOST is configured, add
, for example:to /etc/services. For example,
Please update the following native library files under $SL_ROOT/ldlib/:
a) libsapjco3.so for Linux-based JCC nodes.
and let the SAP server informthe user
you regarding the failure. However, in the latest driver, if the function module is not remote-enabled, the JCo would detect it in advance, and let the Snap failfast.
If you want to revert to the previous behavior, the JCo properties could be set through the jvm_options:
BAPI and IDoc Integration
BAPI (Business Application Programming Interface) and IDoc (Intermediate Document) are different interfaces that SAP ERP provides to enable business-data exchange across SAP and non-SAP platforms.
BAPI is a library of functions stored on the SAP platform that can be called by SAP or non-SAP platforms to perform specific operations. All related data is exchanged immediately and not stored anywhere during transit. SnapLogic uses the RFC (Remote Function Call) protocol provided by the SAP Java Component to call BAPI remotely.
IDocs, on the other hand, are formatted data containers that can be transferred between SAP platforms or non-SAP platforms. IDocs are stored in database tables on the SAP side, and can be sent to a receiver system using their ALE technology.
Configuring SAP for BAPI Integration
There is no additional configuration required for standard BAPI integration other than ensuring that the configured SAP user has sufficient roles/privileges to access and invoke the desired BAPIs. If the standard functions do not meet your integration requirements, you must design and implement a custom function according to your needs.
Configuring SAP for IDoc Integration
The following configurations are required in SAP to send or receive IDocs.
- Add a logical system using transaction code SALE.
- Create/Change the distribution model using transaction code SALE or BD64.
- You may either create a new model view or edit an existing one. Then add sender/receiver (Logical System) and message types.
- Generate partner profiles. Use the transaction code we20.
Additional SAP Configuration for Outbound IDoc Integration
The following configurations are required in SAP to send outbound IDocs to the SnapLogic SAP account.
- Register the external program in the SAP gateway by editing the reginfo file. For additional information, see Gateway Security Files secinfo and reginfo.
- Import reginfo in Gateway using the transaction code SMGW.
- Create RFC Destination of Type = 'T' (TCP/IP). For additional information, see SAP JCo Server Programming.
- Check the gateway monitor to ensure that the connection is registered correctly.
- Create a port using transaction code WE21.
Local TID Database Configuration (Outbound IDoc Only)
When listening for outbound IDocs sent from SAP, the SAP Snaps require a local database to track the TIDs for the IDocs received and processed successfully. The SnapLogic SAP account must be able to access that database. If the database is not supported by default, you must obtain the appropriate JDBC driver and add it to the SnapLogic SAP Account.