Show TOC

Background documentationException Management Instrumentation Platform Locate this document in the navigation structure

 

Many SAP customers operate in complex, heterogeneous system landscapes in which business processes are distributed across systems and over multiple application components. To enable sufficient exception management, that is, logging of technical and business exceptions during runtime, you use SAP Exception Management Instrumentation Platform (SAP EM-IPA) to mark critical locations in the source code.

EM-IPA allows you instrument critical process steps that are not fully covered by the standard instrumentation, on a customer-specific basis. This may include, for example, remote and/or local interface calls between different application components, or between SAP and customer coding. When problems arise, the instrumentation enables you to track and correct the execution of individual process steps, by using the extracted payload.

Process

Instrumentation

Instrumentation can be done via implicit and explicit enhancement points when enhancing the SAP coding, or it can be done directly in customer coding.

For ABAP code, you use SAP EM-IPA, which is based on static code instrumentation.

Note Note

The ABAP instrumentation platform is part of the Solution Tools Plug-In (ST_PI) and can be deployed independently.

End of the note.

With instrumentation, the actual business process flow is broken down into single processing steps. Within one process step, multiple modularization unit calls (local/remote API calls) can be executed. During runtime, SAP EM-IPA logging information is optionally written to a local EM store in the managed system, and then transferred to the central exception store in SAP Solution Manager.

SAP Business Process Passport

SAP Business Passport (SAP BPP) collects all the logging and tracing information belonging to a single process instance. SAP BPP is a token that uniquely identifies a process instance, that is, a single execution of a certain process type. Once a business process instance ID and a business process type ID are generated and injected in the SAP BPP, the BPP is transferred cross-system and cross-technology from one processing step to the successor processing step via the SAP Passport, and is persisted together with the logging and tracing information for each processing step. In addition to the unique identifier, the SAP BPP contains the predecessor/successor relationships of the instrumented processing steps and the business process type information.

Result

Via SAP Exception Management Instrumentation Platform, all relevant information for every critical processing step is logged in a dedicated logging format. The logged information contains the following:

  • Technical information derived from the SAP Extended Passport

  • Process information derived from SAP Business Process Passport

  • Processing step information, including involved modularization unit calls, exceptions messages, payload, and execution time