Overview

The SAP connector is based on SAP’s NetWeaver RFC SDK. It allows you to natively connect to an SAP system using an RFC connection and call remote-enabled functions, also known as BAPIs. There are over 3,500 BAPIs that have been released by SAP for public use, all of which are pre-delivered in ClearProcess as an API. You can view them in the ClearProcess builder. In addition to BAPIs, there are the following integration options:

  • iDoc – any SAP iDoc can be triggered from ClearProcess using the API IDOC_INBOUND_SYNCHRONOUS. See CreatePricingCondition in ClearProcess for an example.
  • BDC – If you have exhausted all of your options and cannot integrate with SAP via a BAPI or iDoc, there is an option to record a batch input session (transaction SHDB) and invoke the session from ClearProcess. This should always be a last resort and will only be supported after receiving written approval from Clear. See PayCustomerItems in ClearProcess for an example.

Setting Up the SAP Connection

Setting up a connection to your SAP system can be a little tricky because the documentation is scarce. Below are the most common types of connections. The entire list of SAP connection parameters can be found here:

Application Server

Use this type of connection if there is only one SAP application server and your users log in with a user name and password.

Load Balancer

Use this type of connection if you have a load balancer and your users log in with a user name and password.

Load Balancer + SSO

Use this type of connection if you have a load balancer and your users log in through a Single Sign On service.