Show TOC

Procedure documentationConfiguring Collection of Single Exceptions


You can collect single exceptions for ABAP and non-ABAP systems. In this activity, you specify which log stores to collect in the central exceptions store per technical system. For each log store, you can define filters to limit the collection to business-critical exceptions and avoid excess data volume. You can save log stores, categories, and filters as a template to simplify the configuration of additional systems.

For example, exception management supports collection of the following types of technical, single exceptions for ABAP systems:

  • Application log errors

  • Runtime errors (dumps)

  • Job errors

  • System log errors

  • Update errors

  • Web service exceptions

The exceptions store can provide data to the central Alert Inbox and other MAI-based technical monitoring applications. For ABAP systems, you can activate MAI-based monitoring directly in the exception management configuration.

Note Note

If required, you can add generic 3rd party log stores to exception management. If there is no existing log store that corresponds to the format of the 3rd party log store, you may need to contact SAP support for assistance with setting up the required metamodel.

End of the note.


  1. In the Root Cause Analysis work center, choose Exception Management.

  2. Choose Configuration.

    The Overview tab page provides an overview of the current configuration.

  3. Select the Show all Technical Systems check box to also show systems that have not yet been configured.

  4. Select a technical system, and then choose Setup.

  5. Choose Add Log Store.

  6. Select the log stores to collect, and confirm your selection.

    The selected log stores are displayed in the list of exception sources for the technical system.

    Note Note

    The standard ABAP log stores are automatically assigned to a category. For other types of log stores, you can maintain your own category names by typing directly in the category field. When monitoring exceptions, you can query and sort by category.

    End of the note.
  7. For each log store you add, you can specify selection filters to limit data extraction to business-critical exceptions.

    Recommendation Recommendation

    It is especially important to use meaningful parameters for application logs. You are required to set up at least one filter for this category. Do not use wildcards (*) only, or you will end up with excessively high data volume.

    End of the recommendation.
    1. Select the log store and then choose Add Filter.

    2. Under Filter Definition, choose Add Fields.

    3. Select the fields to filter by.

    4. For each field, enter parameter values and select the appropriate operators.

      Note Note

      If you want to use wildcards (*), choose the Covers Pattern or Not Covers Pattern operators.

      End of the note.
  8. Save your entries.

    Note Note

    You can save the current log stores, categories, and filters as a template to simplify the configuration of additional systems. To do this, type a name in the Template field and then choose Save as template. You can later select and load this template when configuring a similar system. The loaded template will overwrite the currently selected log stores and filters.

    End of the note.
  9. For ABAP systems, you can automatically activate data providers that transfer single exception data to the MAI-based technical monitoring and alerting applications.

    Note Note

    To activate MAI-based monitoring for ABAP systems, you must configure system monitoring in SAP Solution Manager Configuration (solman_setup), Technical Monitoring scenario.

    End of the note.
    1. To automatically activate monitoring, choose Next.

      A dialog box appears.

    2. Choose Yes to activate monitoring.

      A list of metrics and alerts that can be activated is displayed.

    3. Select which metrics you want to enable for monitoring.

    4. Save your entries.


The relevant data extractors are scheduled for the selected scope.

Other Settings
  • Housekeeping

    Specify how long the system retains the exception data in the exception management store.

  • Self Monitoring

    Administer the exception management extractors. You can activate and deactivate extractors, and display the extractor log and detailed information about each extractor. The log shows when the extractors last sent exceptions from the managed systems, the quantity of data, and whether there were any problems.

More Information

Extractor Framework.