SAP NetWeaver Application Server for ABAP (higher than 7.40)

Category	Type	Description
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
PI Messages	Messages	Messages to and from the SAP PI system
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)
ABAP Web Service Provider	Exceptions	Web service errors for incoming web service calls (available with ST-PI 7.40 SP16)

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 NetWeaver Application Server for ABAP.

Please note:

If an 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.

Implement SAP Note 3259248 to activate the Collection of SAP Passport in SAP Cloud ALM for IDoc Messages.

Available Events

Erroneous Message(IDOC) Detected(Single): The event is created for each failed IDoc.
Erroneous Messages(IDOC) Detected(Grouped): The event is created if one or more IDocs failed since the last data collection.
Messages(IDOC) 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
Message Type Status Status Group	Basic Type Direction Message Function Message Type Message Variant Receiver Address Receiver Partner Function Receiver Partner Number Receiver Partner Type Receiver Port Sender Address Sender Partner Function Sender Partner Number Sender Partner Type Sender Port Status Status Group Status Text

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".

To find the segment field name:
1. Log on to the managed ABAP backend system
2. Go to transaction WE05
3. Enter the search parameters to find one IDoc message for the IDocs you are interested in
4. Double-click on the IDoc to open it
5. Expand 'Data Records'
6. Select the segment that you are interested in
7. You find the segment fields on the screen "Content of Selected Segment"
To set up the data collection of payload attributes click on the > button at the end of the line for the category IDoc
In the area "Collect Additional Attributes"
1. Click the "Add" button to add the payload attribute
2. Enter the filter value:
  1. Message Type
  2. Segment Name
  3. Field Name
3. Click "OK"
Click the "Save" button

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

The Minimum System Requirements to monitor SXMB_MONI for Web Services is SAP BASIS 7.02 SP08

Available Events

Erroneous Message(WS) Detected(Single): The event is created for each failed web service message.
Erroneous Messages(WS) Detected(Grouped): The event is created if one or more web service messages failed since the last data collection.
Messages(WS) 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	Adapter Type Direction Message State Processing Status Group Processing Status Group Text Receiver Interface Name Receiver Interface Namespace Receiver Interface Operation Receiver Party Sender Interface Name Sender Interface Namespace Sender Interface Operation Sender Party Status Status Group Status Text

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".

Find the payload attribute name:
1. Log on to the managed ABAP backend system
2. Go to transaction SRT_MONI
3. Enter the search parameters to find one web service message for the web service you are interested in
4. Double-click on the web service message to open it
5. Select 'Message Body'
6. Click the button 'Original XML' to open the formatted XML message
7. Find the attribute you are interested in
8. Note down the XML tag name
To set up the data collection of payload attributes click on the > button at the end of the line for the category "Web Service Messages"
In the area "Collect Additional Attributes"
1. Click the "Add" button to add the payload attribute
2. Enter the filter value:
  1. Attribute: The XML tag name on the attribute
3. Click "OK"
Click the "Save" button

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

The Minimum System Requirement to monitor PI Messages is ST-PI 7.40 SP20

Available Events

Erroneous PI Messages Detected (Single): The event is created for each failed PI message.
Erroneous PI Messages Detected (Grouped): The event is created if one or more PI messages failed since the last data collection.
PI 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	Adapter Type Direction Message State Processing Status Group Processing Status Group Text Receiver Interface Name Receiver Interface Namespace Receiver Interface Operation Receiver Party Sender Interface Name Sender Interface Namespace Sender Interface Operation Sender Party Status Status Group Status Text

Setup Collection for Additional Payload Attributes

You can collect payload data from PI Messages. To collect data you need to define User Defined Search (UDS) attributes in SAP Process Integration. This data will be available in the message details on the tab "Message Data".

To set up the data collection of payload attributes click on the > button at the end of the line for the category "PI Messages"
In the area "Collect Additional Attributes"
1. Click the "Add" button to add the payload attribute
2. Enter the filter value:
  1. Attribute: The name of the UDS attribute
3. Click "OK"
Click the "Save" button

The setup of the User-Defined Message Search is performed in the SAP PI system. You can define UDS attributes in the Advanced Adapter Engine, as well as in the Integration Engine.

For more information please refer to the SAP Help Portal:

https://help.sap.com/viewer/product/SAP_NETWEAVER_PI/ALL/en-US → <Your release>: Process Integration (Function-Oriented View) → Advanced Adapter Engine → Monitoring the Advanced Adapter Engine → Monitoring Messages → Configuring User-Defined Message Search
https://help.sap.com/viewer/product/SAP_NETWEAVER_PI/ALL/en-US → <Your release>: Process Integration (Function-Oriented View) → Integration Engine → Monitoring the Integration Engine* → Monitoring XML Messages → Configuring User-Defined Message Search

Setup Collection of Passport Information for PI Messages

With a prerequisite of at least ST-PI SP22 we have enabled the collection of passport information for PI message for ABAP systems in Integration Monitoring. This requires some additional steps to be done in the ABAP system:

Install the collective SAP Note 2645656 - XI runtime: Passport property enhancement of XI log
Follow the manual steps described in the solution section of the note.
1. You have to activate the forwarding of the SAP Passport in every system and client that you use in your scenario.
2. Transaction SXMB_ADMIN → "Configuration">"Integration Engine Configuration" → "Specific Configuration"
3. Category "RUNTIME"
  Parameter "PASSPORT"
  Subparameter ""
  Value "0" / "1" (default "0", SAP Passport is not saved or transferred)

Available Events

Erroneous ABAP Aborted Job: The event is created for aborted ABAP jobs.

Available Filters

Filters for Data Collection	Filters for Events (planned)
Job Name User	Coming soon.

Available Events

Erroneous ABAP Gateway Errors: The event is created for ABAP gateway exceptions.

Available Filters

Filters for Data Collection	Filters for Events (planned)
Service Name User Host Message Location Message Id	Coming soon.

Available Events

Erroneous ABAP Runtime: The event is created for ABAP runtime errors.

Available Filters

Filters for Data Collection	Filters for Events (planned)
Runtime Error~Exception Program User Message	Coming soon.

Available Events

Erroneous ABAP System Log: The event is created for exceptions in the ABAP System Log.

Available Filters

Filters for Data Collection	Filters for Events (planned)
Message Id Program User Status	Coming soon.

Available Events

Erroneous ABAP Update: The event is created for ABAP Update errors.

Available Filters

Filters for Data Collection	Filters for Events (planned)
User Transaction	Coming soon.

Available Events

Erroneous ABAP Web Service Consumer: The event is created for errors in the web service log for ABAP Web Service Consumers.

Available Filters

Filters for Data Collection	Filters for Events (planned)
Message Proxy Name User	Coming soon.

Available Events

Erroneous ABAP Web Service Provider: The event is created for errors in the web service log for ABAP Web Service Providers.

Available Filters

Filters for Data Collection	Filters for Events (planned)
Message WS Name (Proxy) User	Coming soon.