Skip to Content

SAP connector


The SAP connector establishes access to either SAP ECC version 6 and above or SAP S/4HANA single-tenant.

Jitterbit's SAP connector relies on the SAP Java Connector (SAP JCo) library and network connectivity to communicate with ECC or S/4HANA. Customers must enable network connectivity between Harmony agents and the necessary SAP components, such as the SAP Application Server and the SAP Gateway. This may require changes to the network configuration of the on-premises or cloud hosting service (such as SAP RISE).

The SAP connector provides an interface for creating an SAP connection, the foundation used for generating instances of SAP activities. These activities, once configured, interact with SAP through the connection.

The SAP connector is accessed from the design component palette's Project endpoints and connectors tab (see Design component palette).

Connector overview

This connector is used to first configure an SAP connection. Activity types associated with that connection are then used to create instances of activities that are intended to be used as sources (to provide data in an operation) or targets (to consume data in an operation).

Together, a specific SAP connection and its activities are referred to as an SAP endpoint:

SAP activity types

  • BAPI activity: An SAP BAPI (Business Application Programming Interface) is a standard interface to business object models (function modules). A BAPI activity executes a function in SAP and is used as a target in an operation.

  • RFC activity: An SAP RFC (Remote Function Call) is a special type of function module used to communicate with remote servers. The RFC activity executes a function in SAP and is used as a target in an operation.


    SAP RFCs that declare tables using CHANGING parameters are not supported. Tables must be declared using TABLES parameters.

  • IDoc activity: An SAP IDoc (Intermediate Document) is configured to use a specific IDoc as a target in an operation. It can be used by an operation to send inbound IDocs (inbound to SAP, outbound from Jitterbit) to an SAP system.


    Outbound IDocs (outbound from SAP, inbound to Jitterbit) are not supported with the Cloud Studio SAP Connector. Outbound IDoc activities require the Jitterbit SAP event listener available for Design Studio.


This connector is a Connector SDK-based connector, which may be referred to by Jitterbit when communicating changes made to connectors built with the Connector SDK.

Prerequisites and supported API versions

For prerequisites, see SAP connector prerequisites.

For information on BAPI, RFC, and IDoc schema fields, refer to the SAP Help Portal or engage with your SAP administrator or SAP consultant.

Known issues

When configuring any SAP activity, you should be aware of this current known issue:


If you experience issues with the SAP connector, these troubleshooting steps are recommended:

  1. Click the Test button in the connection configuration to ensure the connection is successful and to ensure the latest version of the connector is downloaded to the agent (unless using the Disable Auto Connector Update organization policy).

  2. Check the operation logs for any information written during execution of the operation.

  3. Enable operation debug logging (for cloud agents or for private agents) to generate additional log files and data.

  4. If using private agents, you can check the agent logs for more information.

If you receive the error JCoException occurred No RFC authorization for function module BAPI_TRANSACTION_COMMIT when executing a custom Rfc activity, follow these steps:

  1. Ensure the RFC function module BAPI_TRANSACTION_COMMIT is remote-enabled.
  2. In a request transformation preceding the activity, set the field BAPI_COMMIT to true.
  3. Check that the SAP user used in the SAP connection has the S_RFC authorization permission for all related function groups.