Prerequisites for Creating a Connection
You must satisfy the following prerequisites to create a connection with the SAP Concur Adapter.
Identify the SAP Concur Application Edition
There are two types of SAP Concur application editions: Professional Edition and Standard Edition. Perform the following steps to identify the edition of the SAP Concur application you are using before creating an SAP Concur connection.
- Sign in to the SAP Concur application.
- In the left navigation pane, click the Administration (gear) icon.
- Under Administration, select the
Expense option.
The Expense Administration module appears.
If... Then... You see Expense Administration. Your organization is using the Professional Edition. The Expense Administration option does not appear. You are likely using the Standard Edition or a different edition. - If this menu is not clear, you can also:
- Check with your SAP Concur administrator or SAP Support for confirmation.
- Review your licensing information or contract details in the Company Admin section.
Obtain the Client ID and Client Secret
The SAP Concur administrator must perform the following tasks to obtain the client ID and client secret.
-
Sign in to the SAP Concur application.
-
In the left navigation pane, click the gear icon labeled Administration.
-
Select Company from the expanded menu.
-
Select Authentication Admin under the Company submenu.
-
Click OAuth 2.0 Application Management.
This opens the application list where you can manage and create OAuth 2.0 apps.
-
Click Create New App in the Application list page.
- Fill in the details on the Create New App page:
Element Description App Name Update the app name:
Company_Name - description_text today’s_date
- Manually replace Company_Name and today’s_date with your own values.
- Update description_text with a description appropriate for your environment.
App Type Leave blank. App Description Update the app name:
Company_Name - Client_Web_Services_PROD today’s_date
- Manually replace Company_Name and today’s_date with your own values.
- Update description_text with a description appropriate for your environment.
Allowed Grants Select refresh_token, password, and client_credentials. Allowed Scopes Add all or restrict, as needed. Principals Leave unchecked. - Click Submit to create the app.
Enable the APIs
The SAP Concur administrator must perform the following steps to enable APIs for a registered OAuth 2.0 application.
- Sign in to the SAP Concur application.
- In the left navigation pane, click the Administration (gear) icon.
- Select Company from the expanded menu.
- Click Authentication Admin.
- Click OAuth 2.0 Application Management.
- Click the registered application or click Create New App.
- In the Grants/Scopes section, select the
following:
Element Description Allowed Grants Select refresh_token, password, and client_credentials. Allowed Scopes Select all scopes required for API operations (such as extract or payment batch). - Click Submit to save the changes.
The APIs are enabled for this application by the scopes you selected.
Enable the Permissions for the Extract API and Payment Batch API for the Registered Application
The SAP Concur administrator must perform the following steps to enable the permissions specifically for the Extract API and Payment Batch API for a registered OAuth 2.0 application.
- Sign in to the SAP Concur application.
- In the left navigation pane, click the Administration (gear) icon.
- Select Company from the expanded menu.
- Click Authentication Admin.
- Click OAuth 2.0 Application Management.
- Click the registered application to view the details.
- Click Edit.
- Under Grants/Scopes, ensure the following scopes are selected
in the Allowed Scopes section.
- Scope for the Extract API (such as extract.read)
- Scope for the Payment Batch API (such as paymentbatch.write)
- Click Submit to apply permissions.
The registered application now has access to the Extract API and Payment Batch API as per the selected scopes.
Note:
In the new SAP Concur user interface, enabling API permissions is managed by selecting the appropriate scopes during OAuth 2.0 application creation or editing in the OAuth 2.0 Application Management section. There is no longer a separate Modify dialog or checkboxes to enable APIs for registered applications. Scopes directly determine which APIs and operations are permitted for the integration.