SAP Complaint Handling

Category	Type	Description
SAP Complaint Handling Master Data Messages	Messages	Master Data Messages sent to and from SAP Complaint Handling
SAP Complaint Handling Configuration Messages	Messages	Configuration Messages sent to and from SAP Complaint Handling
SAP Complaint Handling Transactional Messages	Messages	Transactional Messages sent to and from SAP Complaint Handling

Setup Integration & Exception Monitoring

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 Business Network.

Please note:

If input help is available for the filter parameters, this input help is filled based on the messages and exceptions collected in SAP Cloud ALM so far.
If no filter is set up for the data collection, all messages or exceptions will be collected for the category.

Available Events

Anomalies Detected in SAP Complaint Handling Master Data Messages: The event is created, when the number of processed messages in your managed service or system is too low or too high.
Erroneous SAP Complaint Handling Master Data Messages Detected (Single): The event is created for each failed message in the managed service.
Erroneous SAP Complaint Handling Master Data Messages Detected (Grouped): The event is created if one or more messages in the managed service failed since the last data collection.
Issues detected for SAP Complaint Handling Master Data Message(s): The event is by default relevant for messages in error and warning state.
SAP Complaint Handling Master Data Message(s) detected with high processing time: The event is created, when the processing time of messages in a managed component exceed a defined period.

Available Filters

Filters for Data Collection	Filters for Events
Status Status Group	Client Direction Follow Up Document Type Method

Available Events

Anomalies Detected in SAP Complaint Handling Configuration Messages: The event is created, when the number of processed messages in your managed service or system is too low or too high.
Erroneous SAP Complaint Handling Configuration Messages Detected (Single): The event is created for each failed message in the managed service.
Erroneous SAP Complaint Handling Configuration Messages Detected (Grouped): The event is created if one or more messages in the managed service failed since the last data collection.
Issues detected for SAP Complaint Handling Configuration Message(s): The event is by default relevant for messages in error and warning state.
SAP Complaint Handling Configuration Message(s) detected with high processing time: The event is created, when the processing time of messages in a managed component exceed a defined period.

Available Filters

Available Events

Anomalies Detected in SAP Complaint Handling Transactional Messages: The event is created, when the number of processed messages in your managed service or system is too low or too high.
Erroneous SAP Complaint Handling Transactional Messages Detected (Single): The event is created for each failed message in the managed service.
Erroneous SAP Complaint Handling Transactional Messages Detected (Grouped): The event is created if one or more messages in the managed service failed since the last data collection.
Issues detected for SAP Complaint Handling Transactional Message(s): The event is by default relevant for messages in error and warning state.
SAP Complaint Handling Transactional Message(s) detected with high processing time: The event is created, when the processing time of messages in a managed component exceed a defined period.

Available Filters

Filters for Data Collection	Filters for Events
Direction Status Status Group	Direction Method Name Status Status Group Status Text Target System