Contact Us
×
How you can contact us:

  • Technical Assistance

    Request product support from SAP

  • Non-Technical Assistance

    Request non-product support or provide feedback on SAP Support Portal site

  1. SAP Support Portal Home
  2. Application Lifecycle Management
  3. SAP Focused Run
  4. SAP Focused Run Expert Portal
  5. Integration & Exception Monitoring For Cloud Services

SAP Concur

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 SAP Focused Run.

Connect SAP Concur

Perform the step described on the page below to connect SAP Concur to SAP Focused Run:

Integration Monitoring Setup

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 (To be deprecated): Collects messages to and from SAP Concur in the Integration add-on on ABAP backend system
  • Concur Objects: Collects messages to and from SAP Concur in the Integration add-on on ABAP backend system
 

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
Concur Communication Monitor (To be deprecated)
  • System Key: Identifies the SAP Concur target system

Concur Objects

  • Status: The status of the messages
  • Status Group: The status group of the messages

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
  • Data filter fields:
    • Client: The client in the SAP backend system
    • 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
Concur Communication Monitor (To be deprecated)
  • Concur Communication Monitor failed objects: Indicates the new failed messages collected during the last data collection interval.

Concur Objects

  • Erroneous Messages detected: Failed messages have been found in the Concur integration add-in
  • Concur Objects issues for longer than N minutes: Messages have been in an error state for longer than N minutes.
  • Data filter fields:
    • Category Type
    • Direction
    • Name
    • Status
    • Status Group
    • Status Text
  • Metric parameters:
    • OLDER_THAN_MINUTES = Only consider messages older than [minutes]