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 | ||
| Data blocking | ||
| Column hashing | ||
| Re-sync | ||
| Row filtering | ||
| API configurable | API configuration | |
| Priority-first sync | ||
| Fivetran data models | ||
| Private networking | ||
| Authorization via API |
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 connections.
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:
PAYMENT_REQUEST_DIGESTREPORTTRAVEL_REQUESTTRIP
Re-import
We re-import the following tables and their associated child tables in full to update them:
ATTENDEE_TYPEATTENDEE_TYPE_V4ATTENDEE_V4DELEGATORLISTLOCATIONSPEND_USERUSERVENDOR
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 |
Capturing deletes
Fivetran captures deletes only when you trigger a table re-sync.
When you trigger a table-level re-sync, Fivetran uses the _fivetran_deleted column to captures deletes as follows:
- Initially, we mark the existing parent and child records in the destination with
_fivetran_deleted = true. - As the re-sync progresses, we set the value of the
_fivetran_deletedcolumn tofalsefor every record that the SAP Concur API returns. - Records that the API does not return remains marked as
_fivetran_deleted = true, allowing you identify stale records in your destination.
A table re-sync retrieves a complete set of records for the specific tables from SAP Concur. We don't have a look-up window for each table. For incremental tables, during the re-sync we retrieve records from the connector's Historical Sync Limit which is configured from 1993-01-01 during initial setup. For non-incremental tables, the SAP API returns the complete set of records without a specific window on every sync.
During regular syncs, we do not capture deletes for parent tables. For first-level child tables, we continue to hard delete records that we detect using weak primary keys.
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,LOCATION,PAYMENT_REQUEST_DIGEST, andREPORTtables and their child tables. - Version 3.1 to sync the
VENDORtable and its child tables. - Version 4.0 to sync the
ATTENDEE_TYPE_V4,ATTENDEE_V4,EXPENSE_COMMENT,LIST, andTRAVEL_REQUESTtables and their child tables. - Version 4.1 to sync the
SPEND_USERandUSERtables.