# SAP Concur

Information noteThis connector is deprecated, and cannot be used to create new tasks. Although deprecated, the connector remains fully supported, and tasks which are already using this connector will continue to work as usual.

SAP Concur is an expense management, travel and invoice software. You can use SAP Concur as a data source when landing or replicating data.

* For more information about connecting to SaaS applications, see [Connecting to SaaS applications](https://help.qlik.com/en-US/cloud-services/Subsystems/Hub/Content/Sense_Hub/DataIntegration/Landing/connecting-web-applications.htm).

* For more information about Lite connectors, see [SaaS application Lite connectors](https://help.qlik.com/en-US/cloud-services/Subsystems/Hub/Content/Sense_Hub/DataIntegration/Landing/connecting-web-applications.htm#SaaS2)

* Depending on your use case, you might need to install Data Movement gateway to move data from SaaS applications. For more information, see [When is Data Movement gateway required?](https://help.qlik.com/en-US/cloud-services/Subsystems/Hub/Content/Sense_Hub/Gateways/replication-gateway.htm#top).

## Preparing for authentication

To access your data, you need to authenticate the connection with your account credentials.

Information noteMake sure that the account you use has read access to the tables you want to fetch.

You need to register an application with SAP Concur to get Client ID and .Client Secret Contact your Partner Enablement Manager or Partner Account Manager.

## Creating the connection

For more information, see [Connecting to SaaS applications](https://help.qlik.com/en-US/cloud-services/Subsystems/Hub/Content/Sense_Hub/DataIntegration/Landing/connecting-web-applications.htm).

1. Click Authenticate when you have filled in the required connection settings.

   You may be asked to log in to the source application.

   A window is displayed with an authentication code.

2. Copy the code to the clipboard and return to the connection dialog.

3. Paste the code in Complete authentication with the code provided by the source and click Verify.

   Tip noteYou may need to scroll down to see this field.

   When status is Verified, the authentication is verified.

4. Provide a name for the connection in Connection name.

5. Select Open connection metadata to define metadata for the connection when it has been created.

Connection settings

| Setting | Description |
| --- | --- |
| Data gateway | Select a Data Movement gateway if required by your use case.<br><br>Information note<br><br>This field is not available with the Qlik Talend Cloud Starter subscription, as it does not support Data Movement gateway. If you have another subscription tier and do not want to use Data Movement gateway, select None.<br><br>For information on the benefits of Data Movement gateway and use cases that require it, see [Qlik Data Gateway - Data Movement](https://help.qlik.com/en-US/cloud-services/Subsystems/Hub/Content/Sense_Hub/Gateways/replication-gateway.htm). |
| Client ID | Client ID for SAP Concur OAuth authentication. |
| Client Secret | Client secret for SAP Concur OAuth authentication. |
| Base URL | Base URL.<br><br>When you create a Concur application you are provided with a geo location. Select the relevant https: URL for the location from this list: [Base URIs](https://developer.concur.com/platform/base-uris.html) |
| Scopes | A list of the scopes that you require, separated by +.<br><br>You can find the available scopes here: [Learn More About Scopes](https://developer.concur.com/api-reference/authentication/app-center-learn-more.html) |