Expense (SAP)
SAP Concur is a cloud-based expense and travel management software solution that enables executives to manage travel expenses. It enables finance executives to monitor expenses and cash flows related to travel expenditures.
The following sections explain prerequisites, resources, and instructions for integrating with SaaS Management.
| • | Stored Expense (SAP) Information |
| • | Required Minimum Permissions for Expense (SAP) |
| • | Expense (SAP) Authentication Method |
| • | Required Expense (SAP) Credentials |
| • | Integrating Expense (SAP) With SaaS Management |
| • | Expense (SAP) API Endpoints |
Stored Expense (SAP) Information
The following table describes the available integration tasks and stored data within [ProductName].
|
Available Integration Tasks |
Information Stored |
|||||||||||||||||||||
|
Application Roster |
|
|||||||||||||||||||||
|
Expense Discovery |
Note:Expense data is sourced for the past 90 days on the initial run. |
Note:The information stored is subject to change as enhancements are made to the SaaS application.
Required Minimum Permissions for Expense (SAP)
The minimum API required permissions are based on the Required Expense (SAP) Scopes and the Required Expense (SAP) User Role.
|
Scope |
Description |
Integration Task Name |
|
user.read |
Enables you to read the list of users in Concur account. For more information, see SAP Concur’s documentation topic, Learn More About Scopes. |
Application Roster |
|
expense.report.read |
Enables you to read the list of expense reports in Concur account. For more information, see SAP Concur’s documentation topic, Learn More About Scopes. |
Expense Discovery |
Required Expense (SAP) User Role
Note:The following SaaS application user role is not applicable to Flexera One roles.
The access token owner (OAuth Consumer) must have the Web Services Admin role to use this parameter. For more information, see SAP Concur’s documentation topic, Reports v3.
Expense (SAP) Authentication Method
The required authentication method is OAuth 2.0 With Password Grant Type. For more information, see SAP Concur’s documentation topic, Company Level Authentication.
Required Expense (SAP) Credentials
The following credentials are required:
| • | Geolocation |
| • | Username |
| • | Password |
| • | Client ID |
| • | Client Secret. |
Integrating Expense (SAP) With SaaS Management
Complete the following steps to integrate SAP Concur with SaaS Management.
To integrate SAP Concur with SaaS Management:
| 1. | This integration uses SAP Concur’s new Oauth2 framework for authentication. In this version, the client ID, client secret, and geolocation cannot be obtained via the Concur UI and must be requested via a Concur support ticket. For more information, see SAP Concur’s documentation topic, Obtain Your Application clientID and clientSecret. |
| 2. | The following table lists the location that SAP Concur currently supports with the corresponding geolocation code for integrating with an implementation account and production account. |
|
Location |
Production Account |
Implementation Account |
|
United States |
us |
us-impl |
| 3. | Add the SAP Concur application in SaaS Management. For more information, see Adding an Application. |
The following API endpoints are used for production and implementation accounts.
Application Roster
| • | https://www.concursolutions.com/api/v3.0/common/users |
| • | https://implementation.concursolutions.com/api/v3.0/common/users |
Expense Discovery
| • | https://www.concursolutions.com/api/v3.0/expense/entries |
| • | https://implementation.concursolutions.com/api/v3.0/expense/entries |
| • | https://www.concursolutions.com/api/v3.0/expense/reports |
| • | https://implementation.concursolutions.com/api/v3.0/expense/reports |