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.
Connect SAP Concur
Perform the step described on the page below to connect SAP Concur to SAP Focused Run:
Set Up Integration & Cloud Monitoring
Please, provide a valid admin page (see the wiki for details)
Enter the preview mode to see the content - a reminder that the admin page should be activated separately.
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.
- 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, provide a valid admin page (see the wiki for details)
Enter the preview mode to see the content - a reminder that the admin page should be activated separately.
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.
- Subobject (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
- System Key: Identifies the SAP Concur target system
Please, provide a valid admin page (see the wiki for details)
Enter the preview mode to see the content - a reminder that the admin page should be activated separately.
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 failed objects: Indicates the new failed messages collected during the last data collection interval.
Integration Scenario
Please, provide a valid admin page (see the wiki for details)
Enter the preview mode to see the content - a reminder that the admin page should be activated separately.
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.
- Integrating ABAP backend with the Concur in a direct connectivity scenario: 1, 3, 4
- Integrating ABAP backend with the Concur mediated via SAP Integration Suite (Cloud Integration): 1, 2
| 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.