Show TOC

Procedure documentationConfiguring Exception Management Locate this document in the navigation structure

 

You configure exception management within the application itself, in the Root Cause Analysis work center, under   Exception Management   Configuration  .

The Configuration view is divided into the following tab pages:

  • Overview

    Provides an overview of the current exception management configuration in your landscape.

    Via Setup, you can specify which exception data you want to extract from each technical system, by choosing exception categories and defining selection parameters.

  • Instrumentation Platform

    Specify which exception logging data collected via the Exception Management Instrumentation Platform you want to display in exception management.

  • Repository

    Specify which business process type belongs to which combination of business process category and business process subcategory. This assignment ensures that there is a detailed error source description for multiple-step exceptions.

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

    For more information about extractors, see Extractor Framework.

Procedure

Configuring Exception Management for Single-Step Exceptions
Select Exception Categories and Selection Parameters

  1. On the Overview tab page, select a technical system, and then choose Setup.

  2. Switch to edit mode, and then choose Add.

  3. For the implementation source, select the category of exceptions you want to collect for the technical system.

    Note Note

    You should only select Exception Management IP if you have implemented the code instrumentation for the processes and components to be monitored on the selected technical system. For more information, see Exception Management Instrumentation Platform and the instructions for configuring exception management for multiple-step exceptions, below.

    End of the note.

  4. For each category you select, you can specify selection parameters.

    Recommendation Recommendation

    The purpose of the parameters is to limit the data extraction to business-critical exceptions. It is especially important to use meaningful parameters for the ABAP Application Log category. Do not use wildcards (*) only, or you will end up with excessively high data volume.

    End of the recommendation.

  5. Save your settings.

    When you save the configuration, the relevant data extractors are scheduled for the selected scope.

Configuring Exception Management for Multi-Step Exceptions

If you have implemented code instrumentation using the SAP Exception Management Instrumentation Platform (SAP EM-IPA) you can monitor cross-component, multiple-step, process-flow-driven exceptions with exception management.

Set Up Collection of Local Exception Data (Stored via EM-IPA) into SAP Solution Manager

  1. On the Overview tab page, select a technical system, and then choose Setup.

  2. Switch to edit mode, and then choose Add.

  3. For the implementation source, select Exception Management IP.

  4. Save your settings.

Specify Data Collection Modes for EM-IPA

On the Instrumentation Platform tab page, under Specific Settings, you can specify the following data collection modes, per system, for EM-IPA at runtime:

  • Business Process Journaling Mode

    Data is written for every processing step to exception management logging, regardless of whether an exception occurred. Only step data is persisted; in other words, there is no error or payload information. This setting is not sensitive to the trace flags provided by SAP Extended Passport. This means that tracing occurs for all users in all sessions in which the appropriate processing step is executed.

  • Business Process Trace Mode

    Data is written for every processing step to exception management logging, regardless of whether an exception occurred. This setting is sensitive to the trace flags provided by SAP Extended Passport. This means that the trace information is written only if the appropriate the trace flags are set from outside, for example, by SAP Client Plug-In. The complete information, including the call stack and payload, is persisted.

  • Exception Management Mode

    Data is written for every processing step to exception management logging, but only when an exception has occurred. In this case, the complete information, including the call stack and payload, is persisted.

  • Integration Test Mode

    Data is written for every processing step to exception management logging, regardless of whether an exception occurred. The complete information, including the call stack and payload, is persisted.

    Note Note

    In exception mode and test mode, you can selectively switch off the collection of payload and/or call stack information.

    End of the note.
Map Business Process Type IDs to Category/Subcategory

  • On the Repository tab page, under General Settings, configure the following:

    During instrumentation, it is necessary to specify a business process type ID to distinguish the different process types. If different business process type IDs were specified, these have to be maintained accordingly within the exception management repository. The process ID is mapped to a category/subcategory, which can either be imported from the Solution Directory or manually maintained here.