SAP Concur Setup Guide

Follow our setup guide to connect SAP Concur to Fivetran.

Prerequisites

To connect SAP Concur to Fivetran, you need:

• a SAP Concur account with the Web Services license
• a Web Services Administrator role assigned to your SAP Concur user
  The Web Services Administrator role is required to access the OAuth 2.0 Application Management tool and generate a Company Request Token. We need it only during initial setup and not for the ongoing connector operation. For admins working with Standard entities, a user with the Can Administer permission also has the Web Services Administrator role.

• a SAP Concur OAuth 2.0 application with the correct grants and scopes configured. See the Create an OAuth app section below.

Supported authentication modes

We support the following authentication modes for SAP Concur connections:

• Password Grant
• Company Level

The following table outlines the key differences and helps determine the authentication mode you prefer:

Setup instructions

Create OAuth app

You must create an OAuth 2.0 application in SAP Concur to generate the Application ID and Application Secret. SAP Concur displays them as Client ID and Client Secret.

1. In SAP Concur, go to Administration > Company > Authentication Admin.

2. Click OAuth 2.0 Application Management.

3. Click Create New App.

4. Enter the details in the following fields:

   • App Name
   • App Description
   • App Stage
   • Application Type

5. In the Allowed Grants section, select password and refresh_token.

6. In the Allowed Scopes section, select the scopes you want to assign to your API token. The following table lists the tables synced for each scope:

   Scope	Tables
   ATTEND (required)	ATTENDEE, ATTENDEE_TYPE
   CONFIG	PAYMENT_TYPE, POLICY, EXPENSE_TYPE
   EXPRPT	REPORT, DELEGATOR, LOCATION, EXPENSE_ENTRY, ENTRY_ATTENDEE_ASSOCIATION, ITEMIZATION, ALLOCATION
   ITINER	TRIP, BOOKING, PASSENGER, AIR, HOTEL, CAR, RAIL, RIDE, TRAVEL, DINING, EVENT, PARKING, CHARGE_RATE, CHARGE_RATE_WITH_ALLOWANCE, CHARGE_FIXED, CHARGE_PERCENT
   spend.list.read	LIST ¹
   spend.user.general.read	SPEND_USER, SPEND_USER_AUTHORIZED_APPROVER, SPEND_USER_EXPENSE_DELEGATE, SPEND_USER_CUSTOM_DATA, SPEND_USER_ROLE, REPORT_APPROVER
   travelrequest.write	TRAVEL_REQUEST, TRAVEL_REQUEST_COMMENT, TRAVEL_REQUEST_EXCEPTION, TRAVEL_AGENCY
   identity.user.ids.read, identity.user.core.read, identity.user.coresensitive.read, identity.user.enterprise.read, identity.user.sap.read	USER
   expense.report.read, expense.report.readwrite	EXPENSE_COMMENT ²
   INVPMT	PAYMENT_REQUEST_DIGEST, PAYMENT_REQUEST, LINE_ITEM, LINE_ITEM_ALLOCATION, LINE_ITEM_MATCHED_PURCHASE_ORDER_RECEIPT ³
   INVVEN	VENDOR, VENDOR_BANK, VENDOR_STATUS, VENDOR_GROUP, VENDOR_BANK_STATUS ³

   • ¹ LIST is available only for Professional Edition entities (Concur Expense, Invoice, or Request Professional Edition). Standard Edition entities cannot use the List v4 API. If LIST does not appear in your schema, verify if your entity is on Professional Edition.
   • ² EXPENSE_COMMENT is only available for Company Level authentication in the Fivetran connector. It also requires the expense.report.read expense.report.readwrite scopes in your OAuth app.
   • ³ Requires the corresponding SAP Concur optional module.
   • ATTEND is a mandatory scope. The connector calls the ATTENDEE_TYPE endpoint during Save & Test even if you exclude the ATTENDEE tables.
   • If you add scopes to your OAuth app after the initial connection is set up, you must re-authenticate in Fivetran to get a new token that includes the updated scopes. For Company Level authentication, generate a new company request token and save the connection. Existing tokens carry only the scopes that were granted when they were first issued.
   • travelrequest.write is the only scope SAP Concur provides for the Travel Request API. Despite the name, the connector uses this scope only to read Travel Request data no write operations are performed. There is no read-only alternative scope available from SAP Concur.
   • The openid scope may be pre-selected by the tool — it is safe to keep.

7. Click Submit.

8. Make a note of your Client ID and Client Secret. You will need them to configure Fivetran.

Create company request token

1. Go to Administration > Company > Company Admin > Authentication Admin > Company Request Token.
2. In the App ID field, enter the Client ID you generated.
3. Click Submit.
4. Make a note of the Company UUID and Company Request Token. You will need then to configure Fivetran.

Finish Fivetran configuration

1. In the connection setup form, enter the Destination schema name of your choice.

2. Choose your Authentication Mode: Password Grant or Company Level.

3. If you chose Password Grant as the authentication mode, do the following: i. Enter your SAP Concur Username and Login Password.

4. If you chose Company Level as the authentication mode, do the following: i. Enter the Company UUID and Company Request Token you created.

5. Enter the Application ID and Application Secret you generated.

6. Enter the Region your SAP Concur data center entity is hosted in:

   Data Center	Region
   US2 (North America)	us2
   EU2 (EMEA)	eu2
   APJ1 (Asia Pacific)	apj1
   CCPS (US Government)	usg
   GLZ (Global Landing Zone)	glz
   US Implementation (PSE)	us-impl
   EMEA Implementation (PSE)	emea-impl

   If you are not sure of your data center, check with your SAP Concur administrator. For more information, see the SAP Concur's Base URI documentation.

7. In the Historical Sync Limit (optional) field, select a date to restrict the amount of historical data we sync.

   The historical sync limit applies only to incremental tables. It doesn't apply to re-import tables.

8. Click Save & Test. Fivetran will take it from here and sync data from your SAP Concur account.

Related articles

Connector Overview

Schema Information

Release Notes

API Connector Configuration

Documentation Home