SAP Concur connector for Jitterbit Integration Studio
Summary
The SAP Concur connector establishes access to SAP Concur.
The SAP Concur connector provides an interface for creating an SAP Concur connection, the foundation used for generating instances of SAP Concur activities. These activities, once configured, interact with SAP Concur through the connection.
The SAP Concur 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 Concur 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 Concur connection and its activities are referred to as an SAP Concur endpoint:
-
Read: Retrieves all object data from SAP Concur and is intended to be used as a source in an operation.
-
Query: Queries specified object data from SAP Concur and is intended to be used as a source in an operation.
-
Create: Creates object data in SAP Concur and is intended to be used as a target in an operation.
-
Update: Updates object data in SAP Concur and is intended to be used as a target in an operation.
-
Delete: Deletes object data from SAP Concur and is intended to be used as a target in an operation.
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
The SAP Concur connector requires the use of an agent version 10.1 or later. These agent versions automatically download the latest version of the connector when required.
The SAP Concur connector uses the SAP Concur REST API versions v3.0, v3.1, v3.2, and v4.0. Refer to the API documentation for information on the schema nodes and fields.
Troubleshooting
If you experience issues with the SAP Concur connector, these troubleshooting steps are recommended:
-
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).
-
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.
-
For additional troubleshooting considerations, see Operation troubleshooting.