SAP Connector¶

Summary¶

The Jitterbit Harmony SAP Connector establishes access to either SAP ECC version 6 and above or SAP S/4HANA on-premises.

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 Connections 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.

Note

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.

Note

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.

Note

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:

Deployment of invalid SAP operations is allowed
- Summary: Operations that contain more than one SAP activity, or that contain an SAP activity and a NetSuite, Salesforce, Salesforce Service Cloud, ServiceMax, or SOAP activity, appear to be valid and are able to be deployed without error.
- Additional Information: The operation will fail at runtime.
- Workaround: Follow a valid operation pattern and don't use more than one SAP, NetSuite, Salesforce, Salesforce Service Cloud, ServiceMax, or SOAP activity in the same operation.

Troubleshooting¶

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

Ensure the SAP connection is successful by using the Test button in the configuration screen. If the connection is not successful, the error returned may provide an indication as to the problem.
Check the operation logs for any information written during execution of the operation.
Enable operation debug logging (for Cloud Agents or for Private Agents) to generate additional log files and data.
If using Private Agents, you can check the agent logs for more information.