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

The following table describes the available integration tasks and stored data within SaaS Management.

Available Integration Tasks	Information Stored
Application Roster	Active Date Email First Name Last Name Middle Name User Name
Expense Discovery	Amount Transaction Date Expense Type Name Currency Merchant Name Owner Login ID Comments 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.

Required Expense (SAP) Scopes

Scope	Description	Integration Task Name
identity.user.core.read identity.user.coresensitive.read identity.user.ids.read To enable these scopes, you must reauthorize the integration using the OAuth 2.0 With Password and Refresh Token Grant types authentication method as described in the Expense (SAP) Authentication Method.	Enables you to read the list of users in your SAP Concur account. For more information, see SAP Concur's documentation topic, Scope Usage.	Application Roster
EXPRPT	Enables you to get, add, approve, or update expense reports in your SAP 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

warning

As of May 31, 2024, existing Expense (SAP) integrations will no longer work in SaaS Management. SAP Concur has provided new Expense (SAP) API Endpoints and an enhanced authentication method. You must reauthorize the integration by completing the steps in the following Task section. These steps implement the OAuth 2.0 With Password and Refresh Token Grant types authentication method. Data from existing integrations will be preserved.

The required authentication method is OAuth 2.0 With Password and Refresh Token Grant types.

For more information, see the following SAP Concur's documentation topics:

• Client app calls Oauth2 password grant to get an access token for the company

• Refreshing a token

• Password grant.

To reauthorize an existing Expense by SAP integration to implement the OAuth 2.0 With Password and Refresh Token Grant types authentication method:

1. Your organization's admin with the Web Services Administrator role must ensure the SAP Concur OAuth 2.0 Application Management tool is enabled. If not, contact the SAP Concur Client Web Services. This tool is required for generating the Client ID (App ID) and Client Secret and viewing the Client ID.
2. Refer to the SAP Concur document, Using the Tool to complete the following tasks:
   1. On the SAP Concur Application List page, select the Client ID that is already configured in SaaS Management.
   2. On the SAP Concur App Details page, update the required scopes for the Application Roster task by referring to the Required Expense (SAP) Scopes.
   3. On the SAP Concur App Details page, go to the Grants/Scopes section. In the Allowed Grants field, select refresh_token and password grant type.
   4. Click Submit.
3. Generate the Company UUID and Company Request Token using the Client ID (App ID), which is configured in SaaS Management as per the SAP Concur document, Generating a Company Request Token.
4. To reauthorize the Expense by SAP integration in SaaS Management, go to SaaS > Managed Applications > Expense > Integration.
5. Click Setup.
6. Enter all values in the Expense by SAP integration configuration slideout.
7. Click Next.
8. Click Authorize.
9. Enable the Application Roster and Discovery integration tasks.

Required Expense (SAP) Credentials

The following credentials are required:

• Client ID

• Client Secret

• Company Request Token

• Company UUID

• Geolocation

• Password

• Username.

Integrating Expense (SAP) With SaaS Management

Complete the following steps to integrate SAP Concur with SaaS Management. These steps require the OAuth 2.0 With Password and Refresh Token Grant types authentication method as described in the Expense (SAP) Authentication Method.

1. This integration uses SAP Concur's Oauth2 framework for authentication. Contact the SAP Concur Client Web Services to have the OAuth 2.0 Application Management tool enabled for your organization. This tool must be enabled, so that your organization's admin with the Web Services Administrator role can generate the Client ID (App ID) and Client Secret. Once the tool is enabled, complete the following tasks as per the SAP Concur document, Using the Tool.

   1. Generate the Client ID and Client Secret.
   2. On the SAP Concur Create New App page, go to the Grants/Scopes section. In the Allowed Grants field, select refresh_token and password grant type. Select the Allowed Scopes by referring to the Required Expense (SAP) Scopes.

2. Using the above generated Client ID, you need to generate the Company UUID and Company Request Token as per the SAP Concur document, Generating a Company Request Token.

   note

   The Company Request Token expires after 24 hours. If you cannot complete the authentication workflow within 24 hours of generating the Company Request Token, you must regenerate the token before completing the workflow. You can regenerate the Company Request Token by reentering the App ID/Client ID, clicking Company Request Token as per Generating a Company Request Token, and clicking Submit.

3. The following table lists the locations that SAP Concur currently supports with the corresponding geolocation. You will later enter the appropriate geolocation in SaaS Management as per the SAP Concur document Generating a Company Request Token.

   Location	Geolocation
   United States (North America)	us2
   Europe	eu2

4. Add the Expense by SAP application in SaaS Management. For more information, see Adding an Application.

5. In the Expense by SAP integration setup slideout, enter the following values:

   • Geolocation
   note

   You need to enter your geolocation to successfully enable the Expense Discovery integration task.

   • Username

   • Password

   • Client ID

   • Client Secret

   • Company UUID

   • Company Request Token.

6. Click Authorize.

Expense (SAP) API Endpoints

Application Roster

• https://<Geolocation>.api.concursolutions.com/oauth2/v0/token

• https://<Geolocation>.api.concursolutions.com/profile/identity/v4.1/Users

Expense Discovery

• https://<Geolocation>.api.concursolutions.com/oauth2/v0/token

• https://<Geolocation>.api.concursolutions.com/api/v3.0/expense/reports

• https://<Geolocation>.api.concursolutions.com/api/v3.0/expense/entries