SAP E-Mobility & SAP Concur integration deep dive
You have activated your SAP E-Mobility subscription successfully. Now it is time to setup the scenario for charge@home for your business. You are looking for a deep dive of the one time integration setup and want to understand technical possibilities.
Charge@home is defined as employees charging their EV cars at home. The electrical consumption resulting the home charge is being reimbursed by the company. While SAP E-Mobility is collecting the charging history, the reimbursement is done via SAP Concur integration automatically.
The documentation assumes the same user ID will be used for the initial integration setup. Within this blog post we will discuss the requirement of using 2 different user ID’s, as SAP E-Mobility and SAP Concur IDs cannot be combined.
- Initial integration set up of SAP E-Mobility and SAP Concur.
- The SAP Concur userID needs the “Web Services Administrator” role
- The E-Mobility userID should be assigned to the “EmspManager” and “SAP_EMSP_Manager” roles
- You are familiar with the SAP Help documentation and can access it.
.SAP Admin guide
… Connecting to SAP Concur. The following blog post gives more insights to this URL.
- Supported architecture of SAP E-Mobility and SAP Concur Integration
Scenario: 1 SAP Concur Tenant and 1 SAP E-Mobility Subaccount
Preparation: Trust Configuration
- SAP Business Technology Platform (BTP) is using the Default SAP Identity Provider within the SAP E-Mobility subaccount. The E-Mobility application for the user authorizations is set up with the Default SAP Identity Provider.How to check: Logon to the SAP Business Technology Platform (BTP) cockpit, locate the SAP E-Mobility subaccount and the Trust Configuration under the menu Security on the left. In the next screenshots there are two Trust Configurations active, the Default one and the Custom. If a custom Trust Configuration is being used, please ensure the roles will be updated accordingly.
- Within SAP Business Technology Platform (BTP) the collective role has been created for the integration setup. Single roles EmspManager and SAP_EMSP_Manager needs to be included. If you assign the collective role to your user, close and re-open your browser to clear the cache or use an incognito window. In case of custom Trust Configuration for the E-Mobility application, the collective role needs be pointing to it. The next screenshot contains the collective role within the SAP Business Technology Platform (BTP) cockpit, with the single roles EmspManager and SAP_EMSP_Manager and without custom Trust Configuration.
The initial integration setup will be started with the SAP Concur tenant login and from there the connection to SAP E-Mobility subaccount will be created.
1. URL prefixes
The link to the SAP Concur Marketplace is given in the SAP E-Mobility documentation, from where you can jump directly into the SAP Concur Marketplace. It can happen your browser includes a prefix such as ‘http://help.sap.com/disclaimer?site‘ in the link. Please make sure to cut off the prefix and use the correct URL.
The SAP Concur Marketplace should be ‘https://www.concursolutions.com/?hpo=20&cte=618d45e10c286300152952d6‘
2. Single Sign On (SSO)
https://www.concursolutions.com or a SAP Concur direct link like https://***.concursolutions.com
plus the suffix
*** custom defined.
In the following screenshot you can see the SAP Concur marketplace, the URL and the logon screen.
3. Concur App Center
After the SAP Concur login please navigate to the ‘App Centre’ in the menu bar. The SAP E-Mobility app might not be available.
Remember to use the trick w/ the URL to make the app visible: https://www.concursolutions.com/?hpo=20&cte=618d45e10c286300152952d6
another way getting the SAP E-Mobility app to appear in the SAP Concur Marketplace is simple – just parse your URL together:
SAP Concur direct link like https://***.concursolutions.com
add the suffix
into the final URL
…and SAP E-Mobility will show up.
Once the SAP E-Mobility App is showing up, push the ‘Connect’ button.
The screenshot contains the parsed link, the menu selection and the connect button.
Agree to access authorization in order to continue.
After pushing of the ‘Connect’ button and authorizing the access a new window, which will have a new URL will be generated. In the screenshot the URL is following a pattern.
Copy this URL and hand over to the SAP E-Mobility userID to complete the setup timely. The token will come with an expiration time of 24hrs. If SAP Concur and E-Mobility user are the same, just continue the setup.
The tenant subdomain is referring to SAP E-Mobility subaccount subdomain and can be found in the SAP BTP cockpit. In menu path Overview you need to select the E-Mobility subaccount. The subdomain will be available.
In the example the subdomain is e-mobility, which will be entered on the logon screen in field ‘Tenant Subdomain’.
Please note: The subdomains used for connection are case sensitive. Although the BTP subaccount is setup w/ capital letters, while connecting, please watch the URL’s resolution of the subdomain:
*** the subdomain
This was the last step in the setup and the integration was created successfully.
Concur Tenant changes for M&A scenarios
In case you need to connect your existing SAP E-Mobility solution to another SAP Concur tenant, follow the following steps:
Sequence is crucial
- Disconnect the existing SAP Concur connection to E-Mobility and connect the new SAP Concur tenant
- Immediately after, change all the impacted badges in the SAP E-Mobility solution for the charge @home scenario or add the (new) Concur loginID or GUID. Ideally, removed the GUIDS with the more readable LoginID’s
- Make other changes to the badges after step 2.
Recent Concur Integration updates 4/25/22 – Automatic expensepostings
As of the beginning of the week, automatic expense postings are possible in Concur.
The following KBA note contains the ‘How to setup’ of the SAP E-Mobility configuration in PDF form. It also provides the Postman collection to set the variables for the location, the expense receipt and the expense type.
http://KBA note: https://launchpad.support.sap.com/#/notes/3192053
Now you should be enabled and
- validate the architecture for the charge@home setup,
- validate if a custom Trust Configuration is being used and what impact there is on the setup,
- navigate around SSO and certificates,
to setup successfully the initial integration between SAP Concur and SAP E-Mobility. It is a supplement to the SAP Help documentation Connecting to SAP Concur.
Please stay in touch and provide feedback. What other topics do you want to discuss about SAP E-Mobility?
Please use this Q&A tag link on SAP Community:
SAP Help Portal for SAP E-Mobility
SAP E-Mobility User upload
SAP E-Mobility simple setup
Hi Mareike -
Thanks very much for providing a very detailed configuration steps on the integration with Concur and SAP E- Mobility.
Is the configuration set up same as we do in S4 HANA or ECC?
Can you please advise the same?
From an architecture perspective the connections are in the following direction for the charge@home scenario:
SAP E-Mobility (on SAP BTP) --> SAP Concur --> SAP S/4HANA or SAP ECC.
There is no direct link between SAP E-Mobility and SAP S/4HANA or SAP ECC.
Regarding setup on E-Mobility for the charge@home, yes there is a tiny setup step involved. You need to link the SAP E-Mobility Badges w/ the SAP Concur user ID. SAP Help Documentation or use the upload file of the badges for mass updates.