The SAP NW Alert Management allows you to trigger alerts due to technical or business-critical situations. These alerts will be delivered over predefined channels to the responsible operators / persons in charge in order to inform them.
Aim of this Blog is to give you a quick overview about how to create and raise alerts.
Scenario 1: We want to inform the operator about a technical problem.
Step 1: Create an Alert category.
Go to transaction ‘ALRTCATDEF’ and create a new category ‘FILE_ADAPTER_ERROR’.
In the properties tab enter the required description and the Alias name. If you want to use the escalation functionality, make the ‘Escalation Active’ check box as checked and choose someone who should receive the alert after the ‘Tolerance Time’ has expired.
Provide the following text into the ‘Long and Short text’:
‘An Error has occurred within the file Adapter! Please take care of this. Thanks!’
Click on the button ‘Fixed Recipients’ in order to specify the users who should receive the alert. Choose your operator.
In the optional subseq.activities tab provide the url to you runtime workbench (your operator may want to start her or his investigations from here). Save your settings.
Step 2: Configure a rule to raise the alert.
Go to SAP Netweaver Runtime Workbench…
…click on the link Alert Configuration and choose your new alert category ‘FILE_ADAPTER_ERROR’.
Configure a new rule, so that your alert gets triggered when an error appears within the file adapter.
Step 3: Schedule Report RSALERTPROC (only necessary if you have marked the check box ‘Escalation Active’ in Step 1).
Schedule the report in order to have escalation working.
And basically that’s it. Now an alert should be triggered if an error occurs within the file adapter.
As result of your work your operator should receive an email like this one.
The same message/alert will be delivered to her/his inbox (transaction ‘ALRTINBOX’). If your operator does not respond to this message (and you picked ‘escalation active’), it should be forwarded to the user you provided in ‘escalation receiver’.
Having problems to follow this quick example for scenario 1? Please read Ajay Wandre more detailed article (includes configuration of SapConnect): http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/00e97ba2-85ce-2b10-20bc-bc05cd172154
Scenario 2: We want to use the ALM capabilities to support our own BAM (Business Activity Monitoring) and/or want to inform (for instance) our Key Account Manager about a business critical situation.
The trigger for our alert in scenario 1 was a rule. Now, in Scenario 2, an application or business process will act as trigger.
In case of an application you can simply use the function module SALRT_CREATE_API to raise an alert. I think there is no need to show that in more detail.
Within an integration process (SAP PI ccBPM) you can use the ‘control step’ to raise an alert.
Let’s see how to do this:
Step 1: Create an alert category with the Enterprise Service Builder.
Define Alert Category and fill a short and long text. In this example I am using a container variable ‘requestid’ which is use within the text. Every time the four-eye principle is needed, this alert comes in to play.
Step 2: Using the new alert category within an integration process.
Use a control step to trigger the alert on a certain condition.
Use ‘Enterprise Service Builder’ as source and choose your alert category.
Fill the parameter ‘requesteid’ from a container variable via the expression editor.