SAP Concur

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 FRUN.

Integration Scenario

Please, select...

Unlike the classic point-to-point interfaces like e.g. IDocs, Web Services or RFCs, when talking about monitoring for cloud services, you always also have to consider the integration component of the scenario. For most cloud services, Advanced Integration Monitoring for the cloud service itself concentrates on monitoring exceptions happening in the cloud service. But to fully monitor a cloud service scenario it is also important to monitor the integration between the cloud service and the on-premise backend system. This integration consists of different point-to-point interfaces of different types.

The following section describes the different integration options for the cloud service. Please choose the integration option you are using and consider also setting up the monitoring for the relevant interface types that are part of the integration scenario for the cloud service.

On this page we describe the monitoring categories that are available for this specific cloud service type. For information on how to set up the monitoring categories for the other technical system and cloud service types, please refer to the setup documentation of the respective interface type.

After setting up the monitoring for the single components and interface types, you can use the scenario configuration to group all relevant messages and exceptions of the cloud integration scenario in one Advanced Integration Monitoring scenario. Information how to create scenarios can be found here


For SAP Concur the following integration scenarios are possible: 

The different scenarios contain the following exceptions and point-to-point connections:

  • Integrating ABAP backend with the Concur in a direct connectivity scenario: 1, 3
  • Integrating ABAP backend with the Concur mediated via SAP CPI: 1, 2

Scenario Component Monitored Content Monitoring Category
Systems: ABAP on-premise system Exceptions and successful replications in Concur Integration Add-on Concur Integration Add-on
Cloud Services: SAP Cloud Platform Integration Exceptions in SAP CPI SAP Cloud Platform Integration
Systems: ABAP on-premise system RFC destination to Concur Connection Monitoring (SM59)

To know which iFlows to monitor for Concur please refer to the documentation provided at:

The RFC destination to Concur is maintained during the Concur setup in transaction CTE_SETUP. You can use this transaction to find out which RFC destinations were created. 


Technical Prerequisites

The exceptions for SAP Concur are collected from the Concur integration add-ons installed in the ABAP backend system. So this monitoring category is only available for ABAP systems, which have one or more of the Concur integration add-ons installed.

For more information on the add-on installation please refer to SAP note 2298170 - Installation and upgrade of add-ons for PV - SAP ERP-CONCUR INTEGRATION 1.0.

To set up this monitoring category you have to add the ABAP backend system to Advanced Integration Monitoring. 


Configure Cloud Service

You do not need to connect the SAP Concur cloud service to monitor exceptions in SAP Concur. All exceptions are replicated to the SAP Concur integration add-in in the backend system.

Focused Run monitors all exceptions and also the data communication in the SAP backend system.

The monitoring for SAP Concur exceptions and communication is set up via the ABAP technical system. 


Set Up Integration & Cloud Monitoring

Please, select...

To be able to monitor interfaces of an on-premise system you first have to add it to Interface & Cloud Monitoring and select the monitoring categories you want to monitor for the system. 

  1. Open the Advanced Integration Monitoring Application by clicking on the 'Integration & Cloud Monitoring' tile in transaction FRUN
  2. Click on the pinwheel in the upper right corner of the 'Integration & Cloud Monitoring' application
  3. In the configuration panel expand the 'Technical Systems' tray and click on the pen icon in the upper right corner. This will open the 'Integration and Cloud Monitoring - Systems' view. 
  4. If your system is not on the list yet, click the 'Add' button to add it. If it is on the list, click on the system ID of the system. 

In the next step, you see all monitoring categories which are available for the system, depending on the system type and the installed software components. Some recommended standard monitoring categories are preselected.

Select the monitoring categories in scope.

Available Monitoring Categories

For SAP Concur the following monitoring category is available.

  • SAP Concur Integration Add-on: Collects exceptions that happen in the integration add-on on the backend system. This category is configured for the ABAP backend system 
  • Concur Communication Monitor: Collects messages to and from SAP Concur in the Integration add-on on ABAP backend system

Please, select...

After selecting your monitoring categories you have to maintain filters to define what exactly you want to monitor. Some monitoring categories come with standard filters that usually just select all items of this monitoring category. SAP Focused Run can handle this high amount of monitoring data, so you can stick to this standard filters. Or you can set up filters of your own. 

Please note that the filters you set in the 'Monitoring' step filter the data which is collected from the managed system or cloud service. You can also set up filters later in the 'Alerting' step, which will filter the data already in Focused Run.

You can create more than one filter for a monitoring category.

  1. Select the view 'Monitoring'
  2. To add a new filter click the '+' button on the upper right corner of the table
  3. Select the Category for the filter. The drop down list will contain all activated categories for the system
  4. Enter a filter name
  5. Select the target client for the ABAP system / the end-point for the cloud services
Which filter fields are available depends on the selected category.

Available Filter Options

Concur Integration Add-on

Concur Integration Add-on is based on the ABAP Application Log. Hence you have to select at least the Subobject. The Object is preselected in the coding to collect logs from the Concur Integration add-in.

  • Subject (mandatory): Choose one of the values from the drop-down box (e.g. EMPLOYEE)
  • External ID: External ID of the Application Log entry
  • Message ID: Message Class
  • Message Number: Message Number
  • Text: Message Text
  • Status: Error (E) or Warning (W)
  • Program: Program triggering the log entry
  • Transaction: Transaction code triggering the log entry
  • User: The user who triggered the log entry
Concur Communication Monitor
  • System Key: Identifies the SAP Concur target system

Please, select...

The setup of the filters for the monitoring categories only makes sure that the data is collected, however, alerts are not created automatically. To create alerts and notifications you have to create an alert individually. 

  1. Go the the view 'Alerting'
  2. Click on the '+' button in the upper right corner of the alerts table. A new panel will appear below the table for you to enter the alert information
  3. Select the monitoring category
  4. Select the metric name. The available metrics depend on the monitoring category.
  5. Enter a name for the alert

In the next sub-step, you have to maintain the filter. For most monitoring categories the available filter fields will be the same as for the 'Monitoring' configuration described above. 

For some metrics, you have additional filter fields or you have to maintain metric parameters. You can check the collected data in Focused Run to determine which filter values to use for alerting. Most of the fields can be found in the Collection Context of the collected data.

Please note that the filters on 'Alerting' level filter the data that is already available in Focused Run. They do not influence the data collection itself. You can only filter for data that is collected. Be aware of this if you created strict filters in the 'Monitoring' step.

  1. Enter a name for the filter
  2. Maintain the necessary filter fields

In the last sub-step you have to activate the alert:

  1. Check the check box next to 'Active'
  2. You can adjust the calculation frequency and the severity
  3. Available threshold types depend on the metric selected. If the threshold type allows it you can adjust the threshold value which triggers the alert.
  4. Select the notification variant and the outbound connector variant from the drop-down list.

For single exceptions, the threshold type is always 'Already Rated'. This means depending on the calculation frequency the number of exceptions is checked and an alert is created if this number is bigger than 0. If you want to reduce the number of alert for these metrics, you could increase the value for the calculation frequency to increase the time between checks.

Available Metrics

For Concur the following metrics are collected:

SAP Concur Integration Add-on

  • CONCUR TE Foundation exceptions: Indicates that new exceptions were collected during the last data collection interval
Concur Communication Monitor
  • Concur Communication Monitor failed objects: Indicates the new failed messages collected during the last data collection interval.