Describe User Interface

In this lesson, we'll walk through the standard building blocks you'll find in every SAP Cloud ALM for Operations app. Regardless of the specific use case, the Overview page follows the same structure and controls. We will cover:

• Home page: the standard landing area with Overview and Favorites, plus forward navigation to detail pages.

• Select a Scope: the universal control used to choose which services, systems,  or Business Services (not available in all use cases)

• Configuration (short overview): the common entry point to app-level settings; the options vary by use case, but this is where you tailor behavior and presentation.

• Monitoring cards: the consistent card layout that summarizes key KPIs and alert counts, provides quick actions, supports forward navigation to details, and lets you pin items as Favorites.

By the end of this lesson, you'll recognize these shared elements across different operations use cases and know how to use them efficiently in your daily monitoring.

Here's a concise tour of the Overview page elements that are common across SAP Cloud ALM for Operations use cases:

Home and tabs

• Home icon brings you to the app's landing page.
• Two tabs are always available: Overview , and Favorites. Favorites shows items you've pinned from the Overview.

Global header controls

• Last Refresh timestamp shows when data was last updated.
• Time Frame filter lets you set the analysis window (e.g., last hour, last day).
• Scope Selection defines which systems/services/tenants are included in the view.
• Configuration opens app-level settings (options vary by use case, but it's the place to adjust app behavior).
• In-App Help opens a help panel with contextual topics plus quick links to the Expert Portal and SAP Help Portal.

Left-side navigation

• Consistent icons take you to additional pages such as Monitoring/Analysis, Exceptions, and Alerting.
• A Links icon opens a resource panel with standard references: recorded demos, how-to videos, Expert Portal, Learning Journeys, SAP Help Portal, Support FAQs, SAP Community, and Contact Us.

Overview content area (card layout)

• Each managed object (system, service) or business service (if applicable) appears as a card with key KPIs/status bars and an Open Alerts indicator.
• Forward navigation: clicking the card title or KPI takes you to the relevant detail page for deeper analysis.
• Quick actions on each card include an Open Alerts shortcut and a star icon. Use the star on any card to add/remove it from the Favorites tab for quick access.

What's consistent across use cases: the two-tab Home structure, global filters (Time Frame and Scope), a configuration entry point, the in-app help panel, left-side navigation to detail pages, a card-based overview with KPIs and alert shortcuts, and the ability to pin items as favorites.

Below is a quick training guide for the Select a Scope dialog in SAP Cloud ALM as shown in the following slide:

Using the Select a Scope Icon at the top will open the Dialog.

Top-right actions

• Adapt Filters: Let's you choose which filter fields are shown in the filter bar (for example, you can add "Customer Number" if it's relevant to you).

• Toggle Filter Bar: Shows or hides the full set of filter fields above the table. By default, only the table and the Search field are visible.
• Go: Executes the search with the current filter criteria in the filter bar. After changing filter values, click Go to refresh the result list.

Filter Bar Fields

• Managed Components (Business Services | Services | Systems): Multi-select that defines what you want to scope. This is the master selector; the other filters adapt to the chosen type(s)
  • Business Services: Logical, user-defined business services (often group services/systems for monitoring).
  • Services: Cloud or BTP services/tenants (e.g., SAP Cloud Integration, Event Mesh, Ariba, SuccessFactors).
  • Systems: Technical systems such as SAP S/4HANA, ABAP, Java, HANA, etc.Use this first to narrow the universe you are searching.
• Name: Filters by the component's name. Useful when you know the exact or partial name of a service/system/business service.
• Description: Free-text filter on the description maintained for the component.
• Service Status: Filters by lifecycle/configuration state (e.g., Configured/Active, Not Configured, In Preparation). Use this to focus on components already set up for monitoring.
• Source: Filters by where the component originated from (for example, synchronized from an SAP source versus created in Cloud ALM). Helpful to differentiate manually created items from synchronized ones.
• Service Type: Narrows to a particular SaaS/BTP service category (e.g., SAP Cloud Application Event Hub, SAP Cloud Integration, SAP Ariba, etc.).
• System Number: Filters by the installation/system number (useful for ABAP/on-prem systems).
• Main URL: Filters by the primary URL/tenant endpoint of a service.
• Role: Filters by the role maintained for the component (commonly Dev/QA/Prod or similar operational role; exact roles depend on your landscape setup).
• System Type: Filters by technology type of a system (e.g., ABAP, Java, HANA, or generic "Cloud Service").
• System ID: Filters by the technical ID/SID of a system.

• Customer Number: Filters by the SAP customer number linked to the component. Useful for partners or central teams working across multiple customers. (If not needed, hide it via Adapt Filters.)

Table and selection

• Search (Full Table Search): Client-side, instant full-text search over the visible table columns. Use it for quick narrowing when you don't need field-specific filters. It doesn't require Go
• Row checkbox (Select/Unselect Component): Selects individual components from the result list to include in your scope.
• Apply (n): Confirms your selection and closes the dialog. The number indicates the number of components you're about to include. Cancel abandons the selection.

1. Choose Managed Components to set the context (Systems, Services, and/or Business Services).
2. Toggle Filter Bar and use Adapt Filters to show the fields you need.
3. Enter filter values and press Go to refresh the list.
4. Optionally, use the table Search for quick narrowing.
5. Tick the checkboxes for the components you need and click Apply to confirm the scope.

Next find configuration options for the Integration & Exception Monitoring as an example:

Service / System (##)

You can enable/disable the data collection for a service or system as required.

You can do the following customizations to the data collection for services and systems:

• Activate or Deactivate Data Collection for Individual Message Categories
• Use Filters to Collect Specific Messages
• Collect Additional Attributes
• Create Events
• Remove (Monitoring) Configuration

Business Services (##)

Create a Business ServiceConfigure data collection and events for Business Services:

• Event Settings
• Filters
• Parameters
• Grouping
• Event Actions

Application Settings - Section Housekeeping

In this section, you can configure the retention period for single messages and exceptions.

Application Settings - Section Aggregation

In this section, you can configure the aggregation settings for messages and exceptions, and their retention periods. When aggregation is enabled, the collected messages and exceptions are aggregated, and stored in the aggregated data store.

Application Settings - Section Data Volume

In this section, you can view the memory consumption details of the app. The total memory used to store messages and exceptions are displayed separately.

For more Information, consult: SAP Help Portal: Integration & Exception Monitoring or the SAP Learning CALM10.

What a card represents

A card is the compact summary for one managed component (for example, an S/4HANA Cloud tenant, an integration tenant, a job host, or a monitored application) over the currently selected time frame.

It aggregates status, key counts/KPIs, and offers drill-downs and quick actions. The same pattern is reused across Operations use cases (Health Monitoring, Integration & Exception Monitoring, Job Monitoring, Business Process Monitoring, etc.), so once you know the elements, you can read any card.

 Here is a general, use-case-independent explanation of the card pattern in SAP Cloud ALM for Operations:

Overall Status

• The vertical color stripe at the left edge is the component's overall health for the chosen time frame.
• It is derived from the most critical condition visible on the card (worst severity wins).
• Typical semantics: green = OK, amber = warning/degraded, red = error/critical, gray = no data/not connected. This lets you triage quickly without opening details.

Navigation to Detail Pages

• The header area (component name, type) and many KPI elements are deep links.
• Clicking the header opens the component's overview page in the current use case; clicking a KPI (for example a count or a bar segment) opens the corresponding detail page already filtered to this component and time frame.
• The "more" menu (three dots) provides context actions without leaving the dashboard.
• Typical entries: open details, go to configuration/scope, open the alert inbox pre-filtered to this component, manage thresholds/rules, open documentation, or launch related tools. The exact set varies by use case.

Content Area (depending on Use Case)

• The central panel shows the KPIs relevant to that use case.
• In your example:
  • Messages: a segmented bar with counts by severity (red errors, amber warnings, green successful). Each segment is clickable.
  • Exceptions: a count of detected exceptions (technical or business), also clickable.
• In other use cases this area might show job runs by status, monitored metrics and their current values, business process incidents, interface throughput, etc. The layout changes, but drill-down behavior is consistent.

(i) Explanation Panel

• The info icon opens a small explanation panel describing what the card shows, how colors are determined, and any thresholds or rules used.
• In the example, it clarifies that the left frame's color indicates overall component status for the selected time frame (e.g., red means at least one error message or exception has been detected).

Favorite Toggle

• The star pins/unpins the card as a personal favorite.
• Favorited cards are prioritized (e.g., shown at the top or in a "Favorites" view) and are retained per user to support personal dashboards.

Events

• Opens the Operations Event Calendar for the component.
• Use it to view or record planned or unplanned events (maintenance windows, deployments, outages). Events help correlate spikes or failures with changes and can be used to suppress or adjust alerting during approved windows.

Open Alerts (including Navigation link)

• Shows how many alerts are currently open for this component in the selected time frame.
• Clicking navigates to the Alert Inbox with filters applied (component, use case, time window), so you can act immediately (acknowledge, assign, close, or investigate).

Data Quality Indicator

• The "Quality" indicator reflects the state of data collection for this component.
• It warns when telemetry is delayed, incomplete, disconnected, or otherwise unreliable. Treat KPIs cautiously if quality shows a warning/error. Clicking typically opens a view explaining the data source condition.

• Time frame awareness: All counts and statuses reflect the currently selected time window in the page header. Changing the time frame recalculates the overall status and the KPIs.
• Scope/filter consistency: Cards inherit the page scope (system, environment, site, landscape). Drill-downs keep those filters in place, allowing you to move seamlessly from summary to detail.
• Worst-case roll-up: If any KPI in the content area is critical, the overall stripe will be critical. This makes the card reliable for at-a-glance triage.
• Clickable KPIs: Bars, numbers, and badges are not just visuals-they are navigation anchors to the relevant analysis pages.

Using this mental model, you can interpret and operate any card across SAP Cloud ALM for Operations, regardless of the specific use case.