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.
Perform the step described on the page below to connect SAP Concur to SAP Focused Run:
Available Monitoring Categories
For SAP Concur all exceptions are collected from the connected SAP ABAP backend system. Select the SAP ABAP backend system which has the Concur integration add-on installed, to select the relevant monitoring categories.
The following monitoring categories are 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
For SAP Concur the following integration options are available. Depending on the chosen integration different interface types and data collection points are relevant for monitoring.
|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.