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 SAP Solution Manager.

Technical Prerequisites

The following technical prerequisites have to be met in order to monitor this scenario:

  • To collect single exceptions in the Concur Integration add-in you need at least SAP Solution Manager 7.2 SP03
  • To create alerts via HTTP Monitoring for HTTP RFC destinations you need at least SAP Solution Manager 7.1 SP12

Available Monitoring Content

The following Concur exceptions are currently covered in public cloud operations with SAP Solution Manager:

  • Business critical errors reported by the ABAP backend integration add-on

For Concur we collect exceptions that occur in the Concur Integration add-in. If you use SAP Cloud Platform Integration to integrate the ABAP backend with Concur, we can also monitor exceptions happening in SAP Cloud Platform Integration for the Concur integration.

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.

Concur integrates with on premise systems via different technologies. Depending on which one you use for your scenario you have to also monitor the integration solution to ensure the best possible monitoring coverage for the cloud scenario.

The following integration scenarios are possible (and which monitoring objects they have):

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

For the Concur the following monitoring content is relevant:

# Scenario Component Monitoring Object Description Monitoring Template Since SP
On-premise Exceptions in Concur Integration Add-on Errors written in the SAP Application Log can be collected to the central exceptions store and are available for detail analysis. CONCUR TE Foundation (ExMan) 7.2 SP03
On-premise Number of Exceptions in Concur Integration Add-on The number of exceptions written into the Application Log is monitored and alerted on in Interface and Connection Monitoring. This is a temporary workaround solution until Application Log errors are added to the HTTP template. RFC (see details below) 7.1 SP05* 
Integration Exceptions in SAP CPI  Exceptions in iFlows in SAP Cloud Platform Integration  Cloud (SAP HCI) 7.1 SP12* 
Integration HTTP client availability Availability and response time for HTTP connection from SAP ERP to Concur HTTP (see details below) 7.1 SP14

*) Monitoring content was extended with later support packages (see monitoring template page for details)

Configuration

Step 1: Configure Exception Management

For Concur you can set up the collection of single exceptions in Exception Management and use these collected exceptions for a detailed analysis later on.

Note: Exceptions in Concur Integration Add-On 

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

  1. In the step 'Define Scope' select the tab 'Technical Systems' and your SAP ABAP system. If you didn't configure the system before make sure to select 'All Systems' in the view drop-down. Click on 'Configure' or click 'Next' two times. You will enter the step 'Exception Configuration'.
  2. Click 'Add / Configure Log Store' → Standard. Select 'Concur Travel & Expense'.
  3. Select the fields for filtering for your log store. The field SUBOBJECT is always selected by default. While there are many filter fields available, as this log store is based on the Application Log log store, it doesn't necessarily make sense to use them all. Usually you would be good to go with just the SUBOBJECT. If you want to filter on the rest, please check the actual log record you are looking to catch in SLG1 and maintain the filter fields accordingly. The following filter fields are available:
    • SUBOBJECT: Choose one of the values from the drop-down box (e.g. EMPLOYEE)
    • EXTNUMBER: External ID of the Application Log entry
    • MSGID: Message Class (e.g. E (Error))
    • MSGNO: Message Number
    • MSGTXT: Message Text
    • PROGRAM: Program triggering the log entry
    • TCODE: Transaction code triggering the log entry
    • USER: The user who triggered the log entry
  4. Maintain the filter values for the fields in the Filter Definition panel under the log stores table. You can also add, remove or change filter fields and values later on in the area. You can use different operators for your filter value. You can add more than one filter field combination per log store. To add an additional filter field combination click on the button 'Add Filter' in the 'Configured Log Stores' panel.
  5. Once you are done with the Log Store setup click 'Next' to go to the alert configuration. The alert configuration is done in the 'Interface and Connection Monitoring' described in the next section.

Please note: You should not set up the monitoring for the Exceptions in the Exception Management. If you activate the monitoring here, you will receive an alert (and if set up this way an email) for every single exception in the application log.

Instead we will set up the actual monitoring and alerting for the application log entries in the Web Service monitoring in Interface and Connection Monitoring. This will collect the number of occurred errors and create one alert accordingly. You can then use the Exception Management to drill down into the single exceptions.

Step 2: Configure Interface and Connection Monitoring

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.

If you didn't perform the infrastructure configuration yet, please follow the Interface and Connection Monitoring Setup.

Configuration for Monitoring Template: HTTP Client (from ABAP)

The HTTP channel type is used to monitor the availability and performance of HTTP RFC destinations (type G and H) communication between the Concur Integration add-on in SAP ABAP and the Concur cloud solution.

For detailed setup information how to set up this channel type please refer to the configuration of HTTP channels. 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, or you can check in transaction SM59 under type G.

Use the template HTTP Client (from ABAP) for the monitoring. For the metric parameter 'Destination' use the name of the RFC destination. 

Configuration for Monitoring Template: RFC

The RFC monitoring template is used as a workaround  until we have added the metric for 'Number of AppLog Errors ' to the HTTP template. We use this template to collect the number of exceptions that are written to the SAP Application Log by the Concur Integration add-on.

For detailed setup information how to set up this channel type please refer to the Interface and Connection Monitoring wiki for configuration of RFC channels.

When you set up this channel set the Target system = the Source system. This will create a channel pointing to itself and make sure the measuring point is correct. You don't have to add an interface to the channel.

Select the metric 'Number of AppLog Errors (RFC)' and maintain the following metric parameters:

  • Technical system: your ABAP system
  • Object name: CONCUR_INTEGRATION
  • Sub-object name: you can select one of the following sub-objects or use '*'
    • COST_CENTER
    • EMPLOYEE
    • GDPR_DESTRUCTION
    • GDPR_DISCLOSURE
    • GDPR_READ_ACCESS
    • INTERNAL_ORDER
    • NETWORK
    • NETWORK_ACT
    • PAYROLL
    • POSTING
    • PROJECT
    • PURCHASE_ORDER
    • SALES_ORDER
    • SYSTEM_SETUP
    • VENDOR

The metrics for the Application Log Monitoring will create alerts based on the number of errors in the SAP Application Log. If you set up the Exception Management as well, you can analyze the single exceptions in Exception Management to find out more details about the errors that occurred.