Integration & Exception Monitoring

Objectives

After completing this lesson, you will be able to:
  • Summarize basic concepts of Integration & Exception Monitoring
  • Use Integration & Exception Monitoring to monitor message flows and exceptions
  • Outline the setup of Integration & Exception Monitoring
  • Explain the role model and the permissions assigned to each role

Basic Concepts of Integration & Exception Monitoring

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:

Overview of Integration & Exception Monitoring in SAP Cloud ALM, highlighting end-to-end monitoring of data transfer between various systems and services..

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:

Screenshots from Integration & Exception Monitoring showing the end-to-end message flow and embedded alerting capabilities.

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.

The Use of Integration and Exception Monitoring to Monitor Message Flows and Exceptions

Once you have configured the Integration & Exception Monitoring in SAP Cloud ALM, you can explore how to use the app. Main entry point for the user is again the Home Page:

Home page of Integration & Exception Monitoring, displaying the status of Business Services, as well as selected services and systems as favorites in a card format.

On the Integration & Exception Monitoring Home page (1), you can monitor the status of selected services, systems, or business services as per your scope selection in a card format. Each card represents a service, system or a business service.

The card displays the status for the selected time frame. The color on the left frame of the card (2) is the overall status.

The messages on a card are displayed as per their status in respective color codes. For more information on the color code, select the information icon (3) on each card.

The exceptions on a card are displayed in numbers. By selecting Exceptions  (4), you can jump directly to the Exceptions page and view the details.

By selecting the Quality icon (5) on a card, you can view the status of data collection of the services at the category level. You can also view if there's a connectivity issue between a managed service and Integration & Exception Monitoring in SAP Cloud ALM. The overall data collection rating depends on the worst rating of any of the selected services within the scope.

By selecting the Alert number (6) of the card, you can jump to the Alerting  page and view the alert details.

You can navigate further to the Managed Component View, for example by choosing more (the 3 dots) followed by Go to Details option (7).

The following screenshot displays the Managed Component view:

Screenshot of Integration & Exception Monitoring showing the Managed Component View including details.

The Managed Component View displays the overview of the selected managed component. The Details include:

  1. The total number of Messages, Exceptions and Alerts collected for the managed component.
  2. The integration topology.
  3. The number of messages collected for a specific message or exception category, sorted by status.
  4. Further details can be seen in the Category View, which can be reached via the navigation icon.

This screenshot displays the Category view:

Screenshot of Integration & Exception Monitoring showing the Category View listing all exceptions or messages for a specific category with drill-down capabilities.

The Category View displays the list of all exceptions or messages collected for a specific category (1). Use the interactive charts or attribute filters (2) to refine items in the Messages or Exceptions table. In order to check individual issues, a drill down to a single message or exception details view (3) is provided.

The screenshots below show the Message Details view:

Screenshot of the Message Details View in Integration & Exception Monitoring, showing status details and application data for a message flow.

In the Message Details View on the tab Message Details, you find the status details (1) for the message flow, which contains the status information and processing timestamps for the message.

Also the Application Data (2), which contains collected context attributes for the message, for example object references and/or technical context like business system information or reported business context.

On the tab Related Messages & Exceptions, you also find each managed component (3) the selected message was processed in, and related messages (4), for example acknowledgements or retries.

Note

By selecting a component, you can access the instance of the message on this component. By selecting the message in the Related Messages table, you can see the status and application data for the selected message.

To learn how you can use the Integration & Exception Monitoring Application to analyze errors in messages, watch our demo video:

You can follow along with this demonstration either by using the SAP Cloud ALM Public Demo tenant or your own SAP Cloud ALM tenant, if this use case has already been set up. To do this, simply select the Operations group and then choose the Integration & Exception Monitoring tile.

Caution

Please be aware that the content may vary from what is shown in the video in both cases.

The following screenshots display the Exception page:

Screenshot of the Exceptions page in Integration & Exception Monitoring, displaying exceptions for business services in a card format with trend analysis.

On the Exceptions overview (1) page, you can view exceptions for the business services as per the scope selection in a card format (2). You get the number (count) of component-specific exceptions (3) implicitly impacting the integration or business of your cloud or hybrid scenarios for the selected time frame and scope. This allows you to see which area currently has the highest number of issues and their evolution (trend) (4).

For further analysis, drill down from a high-level perspective of all exceptions per category to the detailed descriptions of individual exceptions (5), along with relevant context information. You can do so by choosing the respective category on a card.

Note

Please note: Only exceptions that have occurred since the application configuration are displayed.

This screenshot displays the Tracking page:

Screenshot of the Tracking view in Integration & Exception Monitoring, allowing users to search and track messages based on business or application context attributes.

The Tracking (1) capability allows users to search and track single messages based on specific business or application context attributes like the order number, employee ID, object reference, component name, etc. As a prerequisite, context information must be exposed by the relevant component and sent together with the message's log fragments to SAP Cloud ALM. The search is executed cross-component and cross-category. Messages that match the search query are listed under Messages, and exceptions that match the search query are listed under Exceptions. Selecting an item from the list opens the message or exception details.

To enhance your search, make use of the following functions:

  • Limit your search to services, systems, or a specific business service by choosing the range (2).
  • Use wildcard characters to further refine your search.
  • Limit your search to a particular message category using the Related Categories option available in Advanced Search (3).
  • View attributes that match your search term in the Matching Attributes column (4).

Finally a screenshot from the Alerting page:

Screenshot of Integration & Exception Monitoring, showing the embedded Alert Inbox with alert details and available actions.

The embedded Alert Inbox (Alerting) (1) provides the starting point for further root cause analysis. Based on the collected data, alerts for certain error situations (2) can be defined, for example messages in status ERROR on a specific component or in a specific scenario. The alert contains each message that contributed to the alert creation. In the alert details (3), you can perform actions (4) like assign a processor, add comments, or confirm an alert, send a notification, or start an operation flow.

Setup of Integration & Exception Monitoring

As a prerequisite to the configuration of Integration & Exception Monitoring, it is necessary that you register the managed systems and the services that you want to monitor in SAP Cloud ALM. The way to register a supported service or system depends on the data collection strategy.

This overview slide explains where you configure monitoring in Integration & Exception Monitoring, and what you can control in each area:

A two-column table (

Note

A detailed description of the configuration options follows. You can either read it here, or jump to the configuration screenshots and read it there (except for Application Settings).

Managed Components → Services / Systems

Purpose: Configure monitoring for specific services or systems.

  • See what data categories are collected for each connected service or system (for example: IDoc, PI messages, web service messages, etc.).

  • Activate / deactivate Data Collection using the switch.

  • Optionally remove configuration for selected rows (stop monitoring that component).

Monitoring configuration Tab

  • Enable/Disable data collection by category (choose what you want to monitor).
  • Use filters (via Details) to narrow down what gets collected (e.g., only specific interfaces, senders/receivers, message types).
  • For some categories you can collect additional attributes (extra fields for search, reporting, and drilldown).

Events configuration tab

  • Define parameters and filters that determine when an event is created (e.g., failed status, delays, missing message, etc.).
  • Maintain Event Actions to trigger when an event occurs, such as:
    • Alert
    • E-mail
    • Operation Flow
    • Chart Notification
    • Ticket

Note

This is the technical monitoring setup—enable collection, restrict scope with filters, and define event triggers + reactions

Managed Components → Business Services

Purpose: Model monitoring from a business scenario perspective, grouping multiple systems/services together.

  • Add Business Services, which represent end-to-end business scenarios (e.g., Order-to-Cash integration, Invoice processing, Master data distribution).
  • Within Services/Systems:
    • Add Services/Systems that participate in the scenario.
    • Manage filters to define what messages/exceptions belong to this scenario.
    • Edit Event Details (parameters, grouping, actions) from to the technical setup.
  • Within Paths:
    • Define Paths: the connections between services and systems.
    • These are visualized as a topology map in the Managed Components view, helping you understand and monitor end-to-end flows.

      Note

      Business Services turn technical monitoring into business-readable monitoring by grouping components and showing the flow between them.

Application Settings

Purpose: Control global behavior of Housekeeping like data retention, aggregation, and data volume.

Key settings
  • Housekeeping: Set retention periods for:
    • single message status groups
    • exception status groups

      (i.e., how long detailed records stay available)

  • Aggregation: Configure how messages/exceptions are summarized and how long aggregated data is retained.
  • Data Volume: View memory consumption and volume information to manage sizing/performance.
  • Flow Discovery: Turn on automatic discovery of message flows between connected systems (helps identify actual integration paths; only available for integration with SAP LeanIX).

Note

These are governance and lifecycle controls—how long data stays, how it’s summarized, and how flows are discovered.

Key Takeaways

  • Services/Systems = configure what to collect and what triggers an event per managed component
  • Business Services = organize those components into end-to-end business scenarios and paths
  • Application Settings = manage retention, aggregation, and data volume globally

Configuration of Services and Systems

The next slide shows how to configure monitoring for a specific managed service/system in Integration & Exception Monitoring:

The screenshot
Services / Systems list (Top area)

This is the inventory of connected components that Integration & Exception Monitoring can monitor (e.g., S/4HANA Cloud system, SAP Integration Suite tenant).

Key columns:

  • Name / Type: Which system/service it is
  • Categories: What kind of monitoring is available (message types)
  • Data Collection (ON/OFF): Master switch for collecting monitoring data
  • Events (Active): Whether event monitoring is active for that component
  • Last Changed fields: Audit trail (who/when)

Note

This is the entry point. If Data Collection is OFF here, nothing below (categories/events) will produce monitoring results.

Monitoring configuration (buttom left panel)

This panel is about what data Integration & Exception Monitoring collects.

Monitoring Categories (upper-left)

Example categories shown for S/4HANA Cloud:

  • SAP S/4HANA Cloud Data Replication
  • SAP S/4HANA Cloud Asset Central Foundation

For each category you can:

  • Set Data Collection ON/OFF (category-level)
  • See endpoint/type (e.g., push) depending on the integration

Note

Use category switches to control scope and performance (collect only what you need).

Filters (middle-left)

Filters restrict collection to only relevant messages (reduces noise and data volume). You can:

  • Add a filter (for a selected category)
  • Delete a filter
  • See filter summary and audit data

Filter Parameters (bottom-left)

This is where you define the exact selection logic (examples visible on the slide):

  • Object (e.g., DRF_OUTBOUND)
  • Subject
  • Program / Transaction / User (optional, depending on category)

Each parameter has:

  • Operator (e.g., "Is")
  • Value

Hint

Start broad (few filters), validate that monitoring works, then tighten filters to reduce irrelevant events.

Events configuration (Right panel)

This panel is about creating events when something happens (exceptions, delays, missing messages, etc.) and what actions to trigger.

Events list (upper-right)

Shows existing event definitions:

  • Category (often EXCEPTION)
  • Active ON/OFF
  • Audit information

You can Add new event definitions here.

Event Settings (middle-right)

When you select an event, you maintain:

  • Event Name (template/technical event type)
  • Display Name (what users see)
  • Description (documentation for operators)

Actions / Variant (bottom-right)

This is the what should Integration & Exception Monitoring do when the event occurs (Event action):

  • Create Alert
  • Send Email
  • Start Operation Flow
  • Send Chat Notification
  • Create Ticket
  • Payload storage (e.g., "Store event payload for 24 hours")

There is also a Variant concept (save action settings as a reusable preset).

Note

Events define detection logic; actions define response/notification.

Best practice: enable category collection first, confirm data arrives, then add filters, then activate events and actions."

Configuration of Business Services

The next slide shows how to configure Business Services in Integration & Exception Monitoring for a managed component

Screenshot of Integration & Exception Monitoring showing
Business Services list (top-left table)

You see existing Business Services (e.g., Calm40 BS, ExternalWorkforce_BS_for_IEM), with:

  • Name / Description
  • Status (green check = active/ok)
  • Last changed metadata
Key action: Add
  • Click Add to create a new Business Service.
  • In the pop-up, maintain (right hand side):
    • Name* (mandatory)
    • Description (optional but recommended)
  • Press Save to create it.

Choose the name of the business service (in blue) or use the arrow at the end of a row to open the details of that Business Service (the lower sections of the slide).

Services / Systems section (middle-left)

The Service/Systems area defines which managed components are part of the Business Service.

Examples shown:

  • MyS4HANACloud_01 (SAP S/4HANA Cloud)
  • MyCPI_01 (SAP Integration Suite / CPI)
  • MyFieldGlass_01 (SAP Fieldglass)

Important controls

  • Add / Delete: include or remove systems from the Business Service.
  • Monitoring / Events toggles
    • Monitoring = ON means the system is considered in monitoring for this service.
    • Events = ON/OFF controls whether event collection/alerting is used for that system in this service context (depends on setup and use case).

Filters (lower-left: Filter For Data)

Filters define which messages/interfaces belong to this Business Service—so you don’t monitor everything, only what’s relevant.

  • Add: create a filter (e.g., for an interface, iFlow, AIF runtime, etc.)
  • Edit/Display/Copy/Delete: manage existing filters.
  • The Summary column shows the criteria (e.g., interface names or patterns).

Note

Good filters are the difference between a clean business-service dashboard and noisy monitoring.

Event details for a filter (bottom-left)

For the selected filter, you can manage which event types are active.

Examples shown:

  • Anomalies detected in the number of AIF messages
  • AIF Message(s) detected with high processing time
  • Erroneous Message (AIF) Detected (Single)

Key action: Edit

Turn individual event types ON/OFF depending on what you want to alert on.

Hint

Start with a small set of meaningful events (errors, stuck/failed messages, high processing time), then expand once stable.

Paths (right side)

Paths define the end-to-end flow direction between the systems in this Business Service.

You see a matrix with:

  • Rows = Source
  • Columns = Target
  • Checkboxes indicate allowed/expected paths, e.g.:
    • S/4HANA Cloud → CPI
    • CPI → Fieldglass

Note

Paths allow monitoring and drilldown to reflect the real integration chain, not just isolated systems. They will be visible in the monitoring view.

Configuration Examples

This screenshots illustrates the setup steps for the Services/Systems configuration:

Screenshot from Integration & Exception Monitoring showing the necessary steps for the expert setup.

With the Services/Systems configuration, you can activate and deactivate single monitoring categories. You can restrict the alerted artifacts using monitoring category-specific filters and you can also create events.

The steps for the expert setup are:

  1. Choose the pencil icon in the Configuration tray.
  2. On the Monitoring tab, activate or deactivate monitoring categories by choosing ON or OFF.
  3. Go to the Events tab. The Events page displays existing events.
  4. At the end of the line you want to change, use the pointed bracket icon to open the Event Details.

Events are used to trigger a reaction if Integration & Exception Monitoring detects a situation that requires attention. These reactions can be an alert, sending a notification and/or triggering an operation flow. The screenshots below demonstrate the steps for creating a Monitoring Event:

Screenshot from Integration & Exception Monitoring showing the steps for creating a monitoring event.
  1. Select/Change the event you want to set up from the Event Name drop-down box.
  2. Adjust the default Display Name to a descriptive name.
  3. Expand the Event Actions tray.

    Note

    Trigger the desired action by switching it ON or OFF using the slider button .

    The following Event Actions are available:

    • Create Alert: You can create an alert that will show up in the applications alert inbox.
    • Send EMail to: To send an email, select the recipients from the list of verified recipients by choosing the + button.
    • Start Operation Flow: To start an operation flow, select the relevant operation flow from the list of available flows using the + button.
  4. Scroll down to add filters to your event, to restrict the messages you react to.
  5. Expand the Filter Configuration tray:
    • Enter a filter name.
    • Select the filter category.
    • Maintain the available filter fields (Parameter Name, Operator, Value). Which filter fields are available, depends on the managed service and system and the selected category.
  6. Save your changes.

The screenshots provided below demonstrate the setup process and monitoring result for the Business Service Configuration:

Screenshot from Integration & Exception Monitoring showing the steps to configure a business service.

A business service in Integration & Exception Monitoring of SAP Cloud ALM allows you to group point-to-point interfaces that belong to a more complex interface scenario. All connections that are part of a business service can then be displayed together in a topology (As shown on the right hand side of the slide above). By adding filters to the connections you can define which messages and exceptions are in scope for a business service and isolate their status information in the monitoring application.

So you can start to configure a business service:

  1. Choose the Configuration button in the Integration & Exception Monitoring UI.
  2. Scroll down to the Business Services section.
  3. Choose the pen icon to open the Configuration for Business Services.

The following video shows how to configure Integration & Exception Monitoring for a Service or System. This is the same video that you can find on the SAP Help Portal. If you know the video already, please skip it:

Related Information for Integration & Exception Monitoring – Configuration

The role model and the permissions assigned to each role

As part of SAP's role harmonization initiative across SAP Cloud ALM for Operations, the original three integration monitoring roles — Integration Architect, Integration Owner, and Integration Owner Sensitive — have been deprecated and replaced with five new roles that reflect a more structured, security-aware permission model.

The new model introduces a deliberate separation of responsibilities:

  • Configuration is split between Administrator (data collection) and Configurator (events and business services)
  • Operational monitoring is handled by the Processor, who can access the alerting inbox and process alerts
  • Read-only access is covered by the Viewer for non-sensitive data
  • Sensitive data access is explicitly separated into the Sensitive Data Viewer role, enforcing the principle of least privilege

The next slide provides an overview of the deprecated and new roles in the SAP Cloud ALM Integration & Exception Monitoring application, showing the recommended migration path for each deprecated role and the permissions assigned to each role in both models:

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.
What [D] means

Roles marked [D] are deprecated. SAP keeps them active during a transition period, but they will be removed. Users must be migrated to the new roles before that happens. In this slide, [D] appears both in the column headers (deprecated roles) and in one row — "Configure monitoring and events [D]" — marking that specific action as deprecated too.

What the numbers (1), (2), (3) mean

The numbers indicate the direct migration path from a deprecated role to its recommended replacement:

  • (1): Architect [D] → Administrator [NEW]
  • (2): Owner [D] → Viewer [NEW]
  • (3): Owner Sensitive [D] → Sensitive Data Viewer [NEW]

Configurator [NEW] and Processor [NEW] carry no number — they are entirely new roles in the harmonized model that have no direct deprecated predecessor. They represent a finer split of responsibilities that did not exist before.

What "(new)" on an action means
Two rows are labelled (new): "Configure data collection" and "Configure events and business services". These capabilities did not exist when the deprecated roles were designed.
What n/a means in the matrix

n/a appears in two situations:

  • Deprecated roles in the two (new) action rows — the feature did not exist in the old model
  • New roles in the Configure monitoring and events [D] row — this action no longer exists in the new model and has no equivalent

A blank cell means the role exists but does not have that permission.

Additional Information