Concur is an SAP SaaS solution that provides travel and expense management services to our customers. Concur integrates seamlessly with SAP on premise solutions via an ABAP add-on installed in the on premise SAP ERP system. Exceptions in this add-on can be monitored using SAP Solution Manager.
For SAP Concur the following integration scenarios are possible:
The different scenarios contain the following exceptions and point-to-point connections:
|Scenario Component||Monitored Content||Interface Channel Type||Since SP|
|1||Systems: ABAP on-premise system||Exceptions in Concur Integration Add-on||Cloud: Cloud (Concur)||7.2 SP08|
|2||Cloud Services: SAP Integration Suite - Cloud Integration||Exceptions in integration flows (IFlow) in SAP Integration Suite - Cloud Integration||Cloud: Cloud (SAP Cloud Integration)||7.1 SP12*|
|3||Systems: ABAP on-premise system||HTTP RFC destination availability and performance||HTTP: HTTP Client (from ABAP)||7.1 SP14|
*) Monitoring content was extended with later support packages (see monitoring template page for details)
To know which iFlows to monitor for Concur please refer to the documentation provided at:
The HTTP RFC destination to Concur, used for the direct connect scenario, is maintained during the Concur setup in transaction CTE_SETUP. You can use this transaction to find out which RFC destinations were created, or you can check in transaction SM59 under type G.
The following technical prerequisites have to be met in order to monitor this scenario:
The following Concur exceptions are currently covered in public cloud operations with SAP Solution Manager:
All exceptions that happen in the Concur cloud service itself and are relevant to the customer are also recorded in the Concur Integration Add-in. That's why it is not planned currently to monitor exceptions directly in the Concur cloud service.
The exceptions for SAP Concur are collected using Exception Management in SAP Solution Manager. After they are collected in Exception Management they can be reused for monitoring in Interface and Connection Monitoring.
|Metric Name||Description||MAI Category||Since SP|
|Single exceptions in Concur Add-On||Single exceptions detected for the Concur Integration add-on||Exceptions||7.2 SP08|
Number of Exceptions in Concur Add-On
|Number of exceptions detected in the SAP Concur Integration Add-on since the last data collection||Exceptions||7.2 SP13|
Number of Exceptions in Concur Add-On (Last 24h)
|Number of exceptions detected in the SAP Concur Integration Add-on in the last 24 hours||Exceptions||7.2 SP13|
For SAP Concur you don't have to connect the actual cloud service to SAP Solution Manager, as all exceptions are collected from the Concur integration add-on. The log store for the exception collection is set up on the ABAP backend system.
The Concur Integration add-on writes single exceptions into error messages in the ABAP Application Log. These application log entries can be collected with the log store for the Concur Network Integration. The exceptions collected via Exception Management and stored in the central exception store are the basis for the Integration Monitoring data collection.
Configuration for Exceptions from SAP Concur
The log store is set up on the SAP ABAP on premise system on which the add-on is installed.
To access the Exception Management setup please go to transaction SOLMAN_SETUP → Application Operations → Exception Management
The last step is the configuration of Interface and Connection Monitoring.
To access the Integration Monitoring setup please go to SAP Solution Manager Configuration (SOLMAN_SETUP) → Application Operations → Integration Monitoring → Interface and Connections.
Monitoring Template: Cloud (Concur)
Navigate to the step 'Define Scope'. You can create a new scenario for the SAP Concur monitoring or use an existing one. Make sure the on premise system for the SAP Concur scenario is part of the Interface and Connection Monitoring scenario.
Create the Interface Channel:
Maintain the Interface:
Since the data collection is based on the content of the global exceptions store, you can always check the collected exceptions in Exception Management. All filter parameters are part of the collection context of the exceptions. The filters applied in Interface and Connection Monitoring allow you to filter the exceptions collected by the Exception Management further. However if the filters in Exception Management do not collect an exception, it is not available in the central exception store and you will not be able to find it in Interface and Connection Monitoring!
Thresholds and the collection schedule are maintained in the next step of the guided procedure. Once you have maintained all your channels, click 'Next' in the main guided procedure to move to the step 'Activation'.
Maintain Thresholds and Schedule:
If not active you can also activate the reporting for the channels by checking the box in the column 'Reporting'. This way you can see a history of the number of exceptions that happened and also place the metric on the OCC Dashboard in Focused Insights.