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, currently available only for Jitterbit Harmony Design Studio. See Design Studio SAP Connector, SAP Configuration for Communication with Jitterbit, and SAP Event Listener Configuration.
The Jitterbit Harmony SAP Connector is accessed from the Connectivity tab of the design component palette:
This connector is used to first configure an SAP connection, establishing access to either SAP ECC version 6 and above or SAP S/4HANA on-premises, and then used to configure one or more SAP activities associated with that connection as a target within an operation:
BAPI: An SAP BAPI (Business Application Programming Interface) activity 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: An SAP RFC (Remote Function Call) activity 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.
IDoc: An SAP IDoc (Intermediate Document) activity 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.
Refer to the SAP Help Portal and engage with your SAP administrator or SAP consultant for information on BAPI, RFC, and IDoc schema fields.
The SAP connector requires the use of a cloud or private agent version 10.1 or later.
Together, a specific SAP connection and its activities are referred to as an SAP endpoint. Once a connection is configured, activities associated with the endpoint are available from the Endpoints filter:
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, ServiceMax, or SOAP activity, appear to be valid and are able to be deployed without error.
- Additional Info: The operation will fail at runtime.
- Workaround: Follow a valid operation pattern and don't use more than one SAP, NetSuite, Salesforce, ServiceMax, or SOAP activity in the same operation.
Last updated: Nov 08, 2019
- No labels