---
sourceDocument: Yokohama IT Operations Management
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/yokohama/it-operations-management

 Release :

    - yokohama

ft:locale :

    - en-US

ft:publication_title :

    - Yokohama IT Operations Management

ft:clusterId :

    - itom

bundleId :

    - itom

workflow :

    - Technology


---

# View alerts in the SAP Solution Manager inbox

# View alerts in the SAP Solution Manager inbox {#ariaid-title1}

* Release version: Yokohama
* 
* Updated January 30, 2025
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read

You can view alerts generated in SAP Solution Manager to see any pressing issues. All
alerts also forward to Event Management
automatically.

## Before you begin

Role required: evt_mgt_admin

## Procedure

1. On the SAP UI, open Solution Manager and select the System Alerts tab.  

   <br />

   The system alerts are listed on the page.
2. Navigate to (Event ManagementAll Alerts) to view the alerts in Event Management.  

   <br />

   The following table describes the field mapping between SAP Solution Manager and Event Management for alerts.  
   {#sap-view-alerts__table_tzr_frk_rhb__entry__3}

   | SAP Field | Event Management Field | Description |
   |-|-|-|
   | severity | severity | SAP uses a number from 1 (less critical) to 9 (more critical) |
   | message_key | message_key | SAP message group ID, messageGUID |
   | description | description | Event description |
   | source | source | SAP system ID |
   | managed_object_type | type | The type of the object, such as Host or Instance |
   | node | node | Object name |
   | managed_object_name | resource | Solution manager node name |
   | N/A (there is no value provided by SAP. Event Management generates the indicated field.) | source instance | The event class must match the connector pull instance name, with the structure \<Source\>_\<Client\>. |
   | source | additional_info.sid | SAP system ID |
   | rating | additional_info.rating | Event color in SAP |
   | resource | additional_info.mandant | SAP mandant |
   | metric_name | metric_name | Metric name for the SAP event |
   | time_of_event | time_of_event | Time of event in SAP |
   [Table 1. Field mapping for SAP Solution Manager and Event Management]

   {#sap-view-alerts__table_tzr_frk_rhb}

## High CPU Usage on SAP Host {#sap-view-alerts__example_xd1_v4l_g2c}

Scenario: An alert is generated in SAP Solution Manager when the CPU usage on a critical host exceeds 90% for more than 10 minutes.{#sap-view-alerts__table_ndw_x4l_g2c__entry__2}

| Field | Value |
|-|-|
| Severity | 8 (Critical) |
| Message Key | CPU_Overload_12345 |
| Description | High CPU usage on SAPHost01 |
| Source | SAP_Prod |
| Type | Host |
| Node | SAPNode_01 |
| Time | 2024-07-31T14:23:00Z |
[Table 2. SAP Solution Manager Alert]

{#sap-view-alerts__table_ndw_x4l_g2c}Here's how the alert is mapped in Event Management:{#sap-view-alerts__table_hyq_rpl_g2c__entry__2}

| Field | Value |
|-|-|
| Severity | 8 |
| Message Key | CPU_Overload_12345 |
| Source | SAP_Prod |
| Type | Host |
| Node/Resource | SAPNode_01 |
| Source Instance | SAP_Prod_100 |
| SID | SAP_Prod |
| Rating | Red |
| Mandant | 100 |
[Table 3. Mapped Event Management alert]

{#sap-view-alerts__table_hyq_rpl_g2c}

*[\>]: and then