Overview
The purpose of Integration & Exception Monitoring is to provide transparency for data exchange processes. The application can help to make the problem resolution process more efficient and enables the collaboration between the Line of Business (LoB) users and the IT department.
This is done by providing you with an end-to-end monitoring by correlating single messages to end-to-end message flows across services and systems as illustrated in the following graphic:

The functionality of Integration & Exception Monitoring provides support to monitor messages processed by platforms like SAP Integration Suite as well as support of peer-to-peer interface technologies as Application Interface Framework (AIF) messages as part of SAP S/4HANA Cloud. In addition, the monitoring of integration related exceptions is provided.
The application further comes with an integrated search and track functionality, which allows you to find a single message, based on technical attributes as well as exposed business context attributes like, for example, the order number across all the components this message might have touched during its execution.
The embedded alerting capabilities can be used to inform an integration owner in IT about critical issues during the data exchange process with the possibility to drill-down into alert details.
Please watch this video to learn more about how data collection functions in Integration & Exception Monitoring:
Caution
In the context of SAP Application Lifecycle Management products, the SAP Passport is not used as a digital ID on the Internet. Instead, it is used to store logging and tracing information for each processing step within a managed component to enable the later message correlation within the SAP Application Lifecycle Management product (like SAP Solution Manager, SAP Focused Run or SAP Cloud ALM).
The following screenshots showcase the key features:

The main features of Integration & Exception Monitoring can be summarized by the following capabilities:
- End-to-end monitoring by correlating single integration artifacts to end-to-end message flows across components and across technology.
- Embedded monitoring of integration-related exceptions.
- Support of message flows processed by platforms like SAP Integration Suite as well as support of peer-to-peer interface technologies as AIF messages as part of SAP S/4HANA Cloud.
- Search and track single messages based on exposed business context attributes like order number.
- Embedded alerting to inform integration owner in IT about critical issues including drill-down in alert details.
- Integration with operation automation to trigger operation flows context-sensitively.












![A permission matrix titled Integration & Exception Monitoring – Roles. The matrix has eight columns: three deprecated roles marked [D] with a single asterisk — Architect (1), Owner (2), and Owner Sensitive (3) — and five new roles marked [NEW] with a double asterisk — Administrator (1), Configurator, Processor, Viewer (2), and Sensitive Data Viewer (3). Numbers in parentheses show the recommended migration path; Configurator and Processor carry no number as they are entirely new roles. The rows list ten permissions: Access the app; View non-sensitive monitoring data; View sensitive monitoring data; View the Business Objects page; Configure data collection (new); Configure events and business services (new); Configure monitoring and events [D]; View monitoring and event configurations; View the alerting inbox; and Process alerts. Each cell contains X (permitted), blank (not permitted), or n/a (not applicable). Key observations: all roles can access the app, view non-sensitive monitoring data, view monitoring configurations, and view the alerting inbox; sensitive monitoring data and Business Objects access is restricted to Owner Sensitive [D], Administrator [NEW], and Sensitive Data Viewer [NEW]; the two (new) configuration actions show n/a for all deprecated roles and are available only to Administrator [NEW] and additionally Configurator [NEW] for events and business services; the deprecated configuration action Configure monitoring and events [D] is available only to Architect [D] and shows n/a for all new roles; alert processing is available to Architect [D], Administrator [NEW], and Processor [NEW] only. A legend states that [D] means Deprecated, a single asterisk indicates the deprecated Integration role set, and a double asterisk indicates the new Integration Monitoring role set. A footnote states that completeness cannot be guaranteed due to short-term software updates and that the information is subject to change. A permission matrix titled Integration & Exception Monitoring – Roles. The matrix has eight columns: three deprecated roles marked [D] with a single asterisk — Architect (1), Owner (2), and Owner Sensitive (3) — and five new roles marked [NEW] with a double asterisk — Administrator (1), Configurator, Processor, Viewer (2), and Sensitive Data Viewer (3). Numbers in parentheses show the recommended migration path; Configurator and Processor carry no number as they are entirely new roles. The rows list ten permissions: Access the app; View non-sensitive monitoring data; View sensitive monitoring data; View the Business Objects page; Configure data collection (new); Configure events and business services (new); Configure monitoring and events [D]; View monitoring and event configurations; View the alerting inbox; and Process alerts. Each cell contains X (permitted), blank (not permitted), or n/a (not applicable). Key observations: all roles can access the app, view non-sensitive monitoring data, view monitoring configurations, and view the alerting inbox; sensitive monitoring data and Business Objects access is restricted to Owner Sensitive [D], Administrator [NEW], and Sensitive Data Viewer [NEW]; the two (new) configuration actions show n/a for all deprecated roles and are available only to Administrator [NEW] and additionally Configurator [NEW] for events and business services; the deprecated configuration action Configure monitoring and events [D] is available only to Architect [D] and shows n/a for all new roles; alert processing is available to Architect [D], Administrator [NEW], and Processor [NEW] only. A legend states that [D] means Deprecated, a single asterisk indicates the deprecated Integration role set, and a double asterisk indicates the new Integration Monitoring role set. A footnote states that completeness cannot be guaranteed due to short-term software updates and that the information is subject to change.](https://learning.sap.com/service/media/topic/f6eeb07b-5e8c-459f-bc0e-e76f9a36e2d2/CALM40_03_en-US_media/CALM40_03_en-US_images/U2L2O4_IEM_ROLE_TABLE.png)