Exception 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 cross-component, process-flow driven, multiple-step exceptions in a central exceptions store. To log multiple-step exceptions, you must mark the critical points in the ABAP source code using the SAP Exception Management Instrumentation Platform (SAP EM-IPA).
In the Exception Management Cockpit, you can correlate, analyze and process exceptions, and use predefined guided procedures to handle errors quickly.
The exceptions store also provides exception data to the central Alert Inbox and other SAP Solution Manager monitoring applications based on the End-to-End Monitoring and Alerting infrastructure (MAI).
The figure below illustrates the integration of exception management in the system landscape:
Integration of Exception Management in System Landscape
Prerequisites
Administration has set up your system landscape in the
SAP Solution Manager Configuration
work center.Exception collection has been configured:
Features
Monitoring Single Exceptions
Single exceptions occur in one location and only affect that location. You can 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.
Exception management can collect single exceptions from any defined log store for any system type managed by SAP Solution Manager.
Note
You can monitor exceptions that occur in supported cloud services in the context of an SAP-based hybrid monitoring scenario. The cloud application is represented in SAP Solution Manager as a technical system of type UNSPAPP
(unspecific standalone application system). For more information, see Integrating Cloud Services for Exception Monitoring.
Technical System Type | Abbreviation |
|---|---|
Application Server ABAP | ABAP |
Apache Tomcat Server | ATC |
Application Server Java | JAVA |
SAP BusinessObjects Cluster | BOBJ |
SAP HANA database | HANADB |
SAP liveCache | LIVE_CACHE |
SAP NetWeaver Master Data Management Server | MDM |
Microsoft Internet Information Services | MSIISINST |
Microsoft .NET System | MS_.NET |
SAP Mobile Platform (formerly Sybase Unwired Platform) | SUP |
IBM WebSphere Application Server | WEBSPHERE |
SAP Web Dispatcher | WEBDISP |
TREX System | TREX |
Unspecific 3 tier system | UNSP3TIER |
Unspecific standalone application system | UNSPAPP |
Unspecific cluster system | UNSPECIFIC |
Monitoring Multiple-Step Exceptions
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.
You can 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
You can handle exceptions as follows:
Assign processors to exceptions
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)
Use guided procedures to resolve exceptions. Exception Management is integrated with the Guided Procedure Authoring (GPA) infrastructure, allowing you to search for predefined error handling procedures or create procedures for future use.