SAP Concur Connector¶
The SAP Concur connector for Jitterbit Harmony Cloud Studio provides an interface for entering user-provided input such as credentials to create an authenticated SAP Concur connection. That connection provides the foundation to configure associated SAP Concur connector activities that interact with the connection. Together, a specific SAP Concur connection and its activities are referred to as an SAP Concur endpoint.
Supported API Versions and Prerequisites¶
The SAP Concur connector uses the SAP Concur REST API v3. Refer to the API documentation for information on the schema fields.
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.
This connector is used to first configure an SAP Concur connection, establishing access to SAP Concur, and then used to configure one or more SAP Concur activities associated with that connection as a source or target within an operation:
Read: Reads all of an object's data at an SAP Concur endpoint and is intended to be used as a source in an operation.
Query: Retrieves an object's data using query parameters at an SAP Concur endpoint and is intended to be used as a source in an operation.
Create: Creates an object at an SAP Concur endpoint and is intended to be used as a target in an operation.
Update: Updates an existing object at an SAP Concur endpoint and is intended to be used as a target in an operation.
Delete: Deletes an object from an SAP Concur endpoint and is intended to be used as a target in an operation.
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.
Accessing the Connector¶
The SAP Concur connector is accessed from the design component palette's Connections tab (see Design Component Palette).
If you experience issues with the SAP Concur connector, these troubleshooting steps are recommended:
Ensure the SAP Concur 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.
If using Private Agents, you can check the agent logs for more information.