SAP Concur
SAP Concur provides an integrated online business travel and expense management software solution that automates your travel expenses.
Features
| Feature Name | Supported | Notes |
|---|---|---|
| Capture deletes | ||
| History mode | ||
| Custom data | check | |
| Data blocking | check | |
| Column hashing | check | |
| Re-sync | check | |
| API configurable | check | API configuration |
| Priority-first sync | ||
| Fivetran data models | ||
| Private networking | ||
| Authorization via API | check |
Supported deployment models
We support the SaaS Deployment model for the connector.
Setup guide
Follow our step-by-step SAP Concur setup guide to connect SAP Concur with your destination using Fivetran connectors.
Schema information
This schema applies to all SAP Concur connectors.
To zoom, open the ERD in a new window.Updating data
Fivetran will use one of the following strategies to update the tables that you included in your sync:
Incremental
We update the following tables and their associated child tables incrementally:
REPORTTRAVEL_REQUESTTRIP
Reimport
We reimport the following tables and their associated child tables in full to update them:
ATTENDEE_TYPEDELEGATORLISTLOCATIONUSER
The frequency with which we update these reimport tables is based on how fast we can ingest them from SAP Concur.
| Table Import Duration | Import Frequency |
|---|---|
| 10 minutes or less | Every sync |
| Between 10 minutes and 60 minutes | Once a day |
| More than 60 minutes | Once a week |
Concur API version
Fivetran uses different versions of the SAP Concur REST API to sync different tables:
- Version 1.1 to sync the
TRIPandDELEGATORtables. - Version 3.0 to sync the
ATTENDEE_TYPE,REPORT,USER,LIST, andLOCATIONtables. - Version 4.0 to sync the
TRAVEL_REQUESTandLISTtables and their associated child tables.