Set up the SAP Concur spoke
- UpdatedAug 1, 2024
- 4 minutes to read
- Xanadu
- Now Platform Capabilities
Integrate the ServiceNow instance and SAP Concur by creating a custom OAuth application in SAP Concur to authenticate ServiceNow requests.
Before you begin
- Request an Integration Hub subscription.
- Activate the SAP Concur spoke.
- Role required: admin
Procedure
-
Register
SAP Concur as an OAuth provider.
- Navigate to System OAuth > Application Registry.
-
Click New.
The system displays the message What kind of OAuth application?
-
Select Connect to a third party OAuth Provider.
The system displays a blank Application Registries form.
-
On the form, fill these values.
Field Description Name Name to uniquely identify the application registry. For example, SAP Concur OAuth. Client ID Client ID of your SAP Concur client application. Contact SAP Concur Implementation team to obtain this value. Client Secret Client secret of your SAP Concur client application. Contact SAP Concur Implementation team to obtain this value. Default Grant type Grant type used to establish the token. Select Resource Owner Password Credentials. Token URL URL from which the ServiceNow instance obtains the access token. Format of the token URL is, https://<host-name>/oauth2/v0/token. Here, host name is the fully qualified domain name of the target host where SAP Concur is installed. Redirect URL OAuth callback endpoint in this format: https://<instance>.service-now.com/oauth_redirect.do. -
Right-click the form header, and click Save.
- The system validates the OAuth credentials and populates the Redirect URL.
- The system populates OAuth Entity Profile with Grant Type as Resource Owner Password Credentials. For example, OAuth Entity Profile is created with default Name, SAPConcur
-
Create a credential record for the
SAP Concur spoke.
- Navigate to Connections & Credentials > Credentials.
-
Click New.
The system displays the message What type of Credentials would you like to create?.
- Select OAuth 2.0 Credentials.
-
On the form, fill these values.
Field Value required Name Name to uniquely identify the record. For example, enter SAP Concur Cred. Active Option to actively use the credential record. OAuth Entity Profile OAuth profile you created when you registered the custom SAP Concur application as an OAuth provider. For example, select SAPConcur. Applies to Select the MID Servers that can use this credential. For example, select All MID Servers. Order Select the order to apply this credential. For example, enter 100. - Save the record.
-
Create a connection record for the
SAP Concur spoke.
- Navigate to Connections & Credentials > Connection & Credential Aliases.
- Open for the record, SAPConcur.
- From the Connections tab, click New.
-
On the form, fill these values.
Field Value required Name Name to uniquely identify the connection record. For example, enter SAP Concur Connection. Credential Credential record you created for SAP Concur. For example, select SAP Concur Cred. Connection URL Connection URL to connect to SAP Concur in this format: <Host>/api. Host Fully qualified domain name of the target host where SAP Concur is installed. For example, us.api.concursolutions.com or eu.api.concursolutions.com. Protocol https Base path /api - Click Submit.
-
Generate OAuth token by providing the
SAP Concur API user credentials.
- Navigate to Connections & Credentials > Credentials.
-
Open the credential record you had created.
Example: SAP Concur Cred
- Click the Get OAuth Token related link and provide the SAP Concur API user credentials to generate the OAuth token.
-
Configure the connection, SAP Concur Event Subscription
Service.
- Navigate to Process Automation > Flow Designer.
- Click the Connections tab.
- Locate the SAP Concur Event Subscription Service connection alias and click View Details.
- To configure the spoke for the first time, select Configure or click Edit.
-
On the Connection form, fill in the fields.
Field Description Name Name of the connection alias record. Connection URL Connection URL in this format: https://www-<Region>.api.concursolutions.com. Replace <Region> with the appropriate SAP Concur region.
Version Enter v4. Token URL Token URL in this format: https://<Region>.api.concursolutions.com/oauth2/v0/token. Replace <Region> with the appropriate SAP Concur region.
Client ID Client ID of your SAP Concur client application. Contact SAP Concur Implementation team to obtain this value. Client Secret Client secret of your SAP Concur client application. Contact SAP Concur Implementation team to obtain this value. - Click Create and Get OAuth Token.
A confirmation message is displayed that the OAuth token is generated successfully. -
Configure the connection, SAP Concur v4 APIs.
- Navigate to Process Automation > Flow Designer.
- Click the Connections tab.
- Locate the SAP Concur v4 APIs connection alias and click View Details.
- Click Edit or if you are configuring the spoke for the first time, click Configure.
-
On the Connection form, fill in the fields.
Field Description Name Name of the connection alias record. Connection URL Connection URL in this format: https://<Region>.api.concursolutions.com. Replace <Region> with the appropriate SAP Concur region.
Version Enter v4. Token URL Token URL in this format: https://<Region>.api.concursolutions.com/oauth2/v0/token. Replace <Region> with the appropriate SAP Concur region.
Client ID Client ID of your SAP Concur client application. Contact SAP Concur Implementation team to obtain this value. Client Secret Client secret of your SAP Concur client application. Contact SAP Concur Implementation team to obtain this value. -
Click Create and Get OAuth Token.
In a new window, you will be prompted to enter Username and Password.
-
For Username, provide the Company ID of the
SAP Concur instance and for Password, provide the value of Company Request Token.
Note: Contact SAP Concur Implementation team to obtain the values of Company ID and Company Request Token.
- Click Get OAuth Token.
-
Map
SAP Concur users to the ServiceNow user in the SAP Concur User Mappings module.
- Navigate to SAP Concur Spoke > SAP Concur User Mappings.
- Click New.
-
On the form, fill these values.
Field Description ServiceNow User Reference to the user record in the User [sys_user] table. SAP Concur User ID User ID of the required user in SAP Concur. -
Click Submit.
Note: If a user attempts to access data in the SAP Concur Expense Entries module without being mapped to the corresponding SAP Concur User ID in the SAP Concur User Mappings module, this error message is displayed.A user with username adminn does not exist.
Map the ServiceNow user to the correspnding User ID in SAP Concur too access data in the SAP Concur Expense Entries module.
- SAP Concur spoke is set up.
- Data is retrieved and displayed in the SAP Concur Expense Entries and SAP Concur Expense Reports modules.