Alert Configuration
Creating Alert Category
Setting Mail Server Connection
Testing of Alert Category
Alert Configuration in Runtime workbench
Alert Inbox
Creating Alert Category
Use transaction code ‘ALRTCATDEF’ to create a new alert category .click on
Display/Changecreate Alert
Provide an Alert Category name and description. In the Properties tab provide the Alias name
To maintain meaningful error messages use Container [Link] the Container tab create
new container elements using the Create button as shown in the screenshot below.
Similarly add other container variables using the Available Container variables table given
below
Available Container Variables table
Container Variable ABAP Dictionary Data Type Meaning
SXMS_MSG_GUID SXMSMGUIDC Message ID
SXMS_RULE_NAME SXMSDESCR Description of the alert rule
SXMS_ERROR_CAT SXMSERRCAT Error category
SXMS_ERROR_CODE CHAR70 Error code
SXMS_FROM_PARTY SXI_FROM_PARTY Sender party
SXMS_FROM_SERVICE SXI_FROM_SERVICE Sender service
SXMS_FROM_NAMESPACE SXI_FROM_ACTION_NS Sender namespace
SXMS_FROM_INTERFACE SXI_FROM_ACTION Sender interface
SXMS_TO_PARTY SXI_TO_PARTY Receiver party
SXMS_TO_SERVICE SXI_TO_SERVICE Receiver service
SXMS_TO_NAMESPACE SXI_TO_ACTION_NS Receiver namespace
SXMS_TO_INTERFACE SXI_TO_ACTION Receiver interface
The created container can then be referenced in the short and long text by enclosing
The container elements name in &…&, e.g. &SXMS_MSG_GUID&. To do so you can either enter
these variables manually or use the “Insert Expression” button.
Specify a short text and long text expression which indicates a possible reason and criticality
of the message failure to the receiving person. An example is shown below
To define dedicated recipients or roles that should receive an alert of this [Link] on
Fixed Recipients button
Specify the user that should get the alerts as shown below.
Save the alert configuration.
Every user that should receive mails must have a mail address maintained in its user profile
using transaction SU01 .An example is shown below
Setting Mail Server Connection
In transaction SCOT you have to maintain the SMTP Server information used for sending Mails.
Go to t-code SCOT. Double-click SMTP and specify the mail-host and mail-port for the
respective mail server.
Make the ‘Node in use’ check box as checked.
An example configuration is displayed in the screenshot below.
Clicking on the Set button next to the Internet item under ‘Supported address types’ ,you also
have the possibility to define routing rules. These rules specify the pattern of addresses
messages can be sent to. Possible values could be * or *.[Link] as used below.
Go to Menu->Settings->Default Domain and specify the domain id of the company. An
example is shown below.
Save the settings done in SCOT.
Testing of Alert Category
To test alert configurations run the report ‘RSALERTTEST’.
Specify the alert category that we have created in ALRTCATDEF. Execute (F8).
If the alert configuration is correct, an email will be sent to the specified recipient of the alert
mails (as shown below).
Creating Rules for Receiving Alert Mails
In Runtime Workbench->Alert Configuration choose the alert category that was created in
ALRTCATDEF.
Specify the condition in the Alert Rules to determine when a message based alert is triggered
using sender and receiver parameters for the created alert category.
Uncheck “Suppress Multiple Alerts in this rule” so that alerts are not just updated but new
alerts are generated later on in the “Alert Inbox”.
Click on Add Rule.
When an end-to-end scenario contains any errors, an email is automatically generated and
sent to the required recipient of the alert mails. You can check in Alert Inbox of Runtime
Workbench
Alert Inbox
The alert inbox is user-specific and displays all the alerts for each alert server that has been
generated based on the alert configuration as shown below.