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.
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||Monitoring Category|
|1||Systems: ABAP on-premise system||Exceptions and successful replications in Concur Integration Add-on||SAP Concur Integration Add-on, Concur Communication Monitor|
|2||Cloud Services: SAP Integration Suite - Cloud Integration||Exceptions in SAP Integration Suite - Cloud Integration IFlows||SAP Integration Suite|
|3||Systems: ABAP on-premise system||RFC destination to Concur||Connection Monitoring (SM59)|
|4||Systems: ABAP on-premise system||HTTP communication to Concur||HTTP(S) Performance|
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.
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.
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.
Available Monitoring Categories
For SAP Concur the following monitoring category is available.
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.
For Concur the following metrics are collected:
SAP Concur Integration Add-on