Show TOC

Function documentationException Management


You use exception management to centrally monitor and handle business-critical exceptions in your system landscape. Exception management collects technical, single exceptions as well as process-flow driven, multiple-step exceptions in a central exceptions store. From the exception management Monitoring view, you can analyze errors, correlate and process exceptions, and document the error resolution in guided procedures.

Single exceptions occur in one location and only affect that location. Exception management can collect single exceptions from any defined log store for the following types of technical systems:

  • .NET System

  • Apache Tomcat Server

  • Application Server ABAP

  • Application Server Java

  • SAP BusinessObjects Cluster

  • IBM WebSphere Application Server

  • SAP liveCache

  • SAP NetWeaver Master Data Management Server

  • Microsoft Internet Information Services

  • SAP Web Dispatcher

  • SAP HANA database

  • TREX System

  • Unspecific Standalone Application System (UNSPAPP): Technical systems that represent SAP cloud-based services

    For information on how to enable exception management for cloud-based services, see Setting up Exception Management for Cloud Services.

Multiple-step exceptions can occur in interfaces and processes distributed among multiple components in a heterogeneous system landscape, which can include SAP components, customer-developed components, and legacy systems. To enable logging of technical and business exceptions during runtime, you use SAP Exception Management Instrumentation Platform (SAP EM-IPA) to mark critical locations in ABAP source code.

The exceptions store can also provide data to MAI-based technical monitoring applications in SAP Solution Manager, including the central Technical Monitoring Alert Inbox.

The figure below illustrates the integration of exception management in the system landscape:


  • You have set up your system landscape in the SAP Solution Manager Configuration work center.

  • To log multiple-step exceptions that occur in business processes distributed across components and technologies, you must mark the critical points in the ABAP source code using the SAP Exception Management Instrumentation Platform (SAP EM-IP).

  • You have configured the collection of exceptions to the central exceptions store.


Exception Monitoring and Analysis
  • Monitor technical, single exceptions, grouped by category, and display error details such as the error message, context, calling stack, and payload of the processing unit

  • Monitor process-flow-driven, multiple-step exceptions, and display process step information, including predecessor/successor relationship, duration, context information, and executed unit calls

Exception Handling
  • Create and use guided procedures to resolve exceptions. You can search for existing error handling procedures or document your own procedures for future use. For more information, see Guided Procedure Authoring (GPA).

  • Assign processors to exceptions for further processing

  • Create incident messages or e-mail or SMS notifications about exceptions

  • Navigate to your Alert Inbox to view notifications and incidents for a selected exception instance (if technical monitoring has been activated)