This is one stop global knowledge base where you can learn about all the products, solutions and support features.
Some of the managed SAP Cloud services use a PUSH mechanism to send alerts and exceptions to SAP Cloud ALM. To successfully set up this PUSH mechanism you need the SAP Cloud ALM Service Key to enter the SAP Cloud ALM credentials during the PUSH setup in the managed SAP Cloud service.
Prerequisites
The following video demonstrates the necessary steps to retrieve the SAP Cloud ALM service key from SAP BTP cockpit. A textual step by step description is provided in the section below the video.
To retrieve the SAP Cloud ALM Service Key please follow these steps:
Service Key Retrieval
At first you have to add the components to the scenario.
You can also maintain paths between the components to visualize a message flow.
Category | Type | Description |
---|---|---|
SAP Fieldglass Messages | Messages | Messages send from and to SAP Fieldglass which are recorded in the Subscription Audit Trail, the Integration Audit Trail and the Event Driven Audit Trail |
To perform the necessary setup steps in the SAP Fieldglass, please refer to:
To learn how to configure the monitoring, follow the documentation on the page Integration & Exception Monitoring - Setup & Configuration.
Below you find category-specific information for the monitoring categories available for SAP Fieldglass.
Please note:
Available Filters
Filters for Data Collection | Filters for Events |
---|---|
|
|
The following monitoring content is available for SAP S/4HANA and SAP Business Suite
Category | Type | Description |
---|---|---|
AIF Messages | Messages | Messages send via the Application Interface Framework |
IDoc | Messages | IDocs sent or received by the SAP S/4HANA system |
Web Service Messages | Messages | Messages sent or received via Web Services and Web Service Proxies |
Concur Objects | Messages | Monitors messages sent for the integration with Concur |
ABAP Web Service Provider | Exceptions | Web service errors for incoming web service calls (available with ST-PI 7.40 SP16) |
ABAP Runtime | Exceptions | ABAP runtime errors (available with ST-PI 7.40 SP16) |
ABAP Update | Exceptions | ABAP update errors (available with ST-PI 7.40 SP16) |
ABAP Gateway Errors | Exceptions | Exceptions in the ABAP Gateway (available with ST-PI 7.40 SP16) |
ABAP Aborted Job | Exceptions | ABAP aborted jobs (available with ST-PI 7.40 SP16) |
ABAP System Log | Exceptions | ABAP system log errors (available with ST-PI 7.40 SP16) |
ABAP Web Service Consumer | Exceptions | Web service errors for outgoing web service calls (available with ST-PI 7.40 SP16) |
SAP S/4HANA Asset Central Foundation Integration | Exceptions | Collects exceptions happening in SAP Intelligent Asset Management |
To perform the necessary setup steps in the SAP S/4HANA or SAP Business Suite system, please refer to:
To learn how to configure the monitoring, follow the documentation on the page Integration & Exception Monitoring - Setup & Configuration.
Below you find category-specific information for the monitoring categories available for SAP S/4HANA and SAP Business Suite.
Please note:
Available Filters
AIF Sub-category | Filters for Data Collection | Filters for Events |
---|---|---|
All sub-categories |
|
|
bgRFC(queue) |
|
|
bgRFC(trans) |
|
|
IDOC |
|
|
Odata Client Proxy | no additional filters | |
XI-runtime |
|
|
qRFC |
|
|
tRFC |
|
|
WS-runtime |
|
|
XML | no additional filters | |
Sync Log | no additional filters |
Available Filters
Filters for Data Collection | Filters for Events |
---|---|
|
|
Available Filters
Filters for Data Collection | Filters for Events |
---|---|
|
|
Setup Collection for Additional Payload Attributes
You can collect payload data from IDocs. This data will be available in the message details on the tab "Message Data".
You can search for the messages that contain the collected data in the Tracking application. Please enclose the value with '*' to successfully find the messages (e.g. *00123456*).
Prerequisites
Available Filters
Filters for Data Collection | Filters for Events |
---|---|
|
|
Setup Collection for Additional Payload Attributes
You can collect payload data from Web Service messages. This data will be available in the message details on the tab "Message Data".
You can search for the messages that contain the collected data in the Tracking application. Please enclose the value with '*' to successfully find the messages (e.g. *00123456*).
Available Filters
Filters for Data Collection | Filters for Events (planned) |
---|---|
Coming soon. |
|
Available Filters
Filters for Data Collection | Filters for Events (planned) |
---|---|
Coming soon. |
|
Available Filters
Filters for Data Collection | Filters for Events (planned) |
---|---|
Coming soon. |
|
Available Filters
Filters for Data Collection | Filters for Events (planned) |
---|---|
Coming soon. |
|
Available Filters
Filters for Data Collection | Filters for Events (planned) |
---|---|
Coming soon. |
|
Available Filters
Filters for Data Collection | Filters for Events (planned) |
---|---|
Coming soon. |
|
Available Filters
Filters for Data Collection | Filters for Events (planned) |
---|---|
Coming soon. |
|
Available Filters
Filters for Data Collection | Filters for Events (planned) |
---|---|
Predefined (not changeable)
|
|
Monitoring is supported for the following SAP Intelligent Asset Management solutions:
The following monitoring content is available for SAP Intelligent Asset Management:
Category | Type | Description |
---|---|---|
SAP Asset Central Foundation Messages | Messages | Collects messages send from and to SAP Asset Central Foundation |
SAP Event Distributor Messages | Messages | Collects event distributor messages sent from and to SAP Asset Intelligence Network and SAP Asset Strategy and Performance Management. |
To perform the necessary setup steps in SAP Intelligent Asset Management, please refer to:
To learn how to configure the monitoring, follow the documentation on the page Integration & Exception Monitoring - Setup & Configuration.
Below you find category-specific information for the monitoring categories available for SAP Intelligent Asset Management.
Please note:
Available Filters
Filters for Data Collection | Filters for Events |
---|---|
|
|
Available Filters
Filters for Data Collection | Filters for Events |
---|---|
|
|
Before you can set up Integration & Exception Monitoring in SAP Cloud ALM, you have to connect your subscribed SAP cloud services to your SAP Cloud ALM instance.
This is done by setting up the Landscape Management Service. Please follow the Setting Up Landscape Management guide in SAP Help on how to perform the setup.
To set up Integration & Exception Monitoring please follow the monitoring setup guide provided in the section "Monitoring Configuration" below.
On the product-specific pages you find additional information for each supported product like setup prerequisites, available monitoring categories, and available filter parameters.
The following video describes:
Attention: The setup of alerts and notification has recently changed. Please follow the written documentation below this video to learn about the new process.
Prerequisites for the video:
The data collection for
all
monitoring categories available for a managed system or service can be activated directly in the configuration tray in Integration & Exception Monitoring.
It is possible to customize the data collection for the managed services and systems by:
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.
If necessary it is possible to delete the monitoring configuration for a service or system. The deletion goes further than just a deactivation, as it removes all configuration from the service or system and sets its status back to "Not Configured" for Integration & Exception Monitoring.
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. 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.
The following video explains the configuration of business services. You can find a step-by-step textual description of the business service setup below.
Prerequisites for the video:
At first, you have to add the components to the business service.
You can also maintain paths between the components to visualize a message flow.