<i>***How can I trigger an alert when the interface fails in the SAP system ?</i>
If the interface not successful, then it will throw error in XI itself. If it is a application error, you can trigger the alert. From SP14 onwards , you can trigger alert for Adapter Framework also.
If you want to get trigger alert based on the success of your message( for e.g update of master table,etc), then if you want to trigger alert for that, then get the response from the R/3 and based on that trigger an alert.
you can trigger an alert in the backend using the appropriate function modules of the alert framework. The only requirement is that you connect your R/3 system to the central alert server in this case most likely your XI system.
If you say you have a SAP interface i assume you have created a Proxy? in this case you can call the alert framework from within your proxy processing based on the outcome of your updates. If you use other methods, such as IDocs, you should have a look at the IDoc processing Workflows which would be the standard method to handle IDoc processing errors. However even there you could modify the IDoc inbound processing to use the Alert Framework.
As i told if your requirement is in the target application side, then you can trigger alert from R/3 side itself. Even there is a function module for this. As mentioned in the earlier reply.
And if you want to trigger an alert without BPM, then you also , you can trigger an alert for these cases-
-Integration Engine level
-Adapter Engine Level ( if SP14 and above)
And it is based on your requirement , where you need to trigger an alert.
In TCODE ALRTCATDEF, go to Settings->Configuration, here the default option is INTERNAL PROCESSING, choose SMTP FORWARDING AS XML and give the email id so as to enable you to send an email alert whenever an error occurs in XI.
If you are on SP14 and above, activation of end to end monitoring is not needed for Alerting, refer note 870232 for the same.Other note being 913858.
It will help you in doing your entire Alert Configuration.
Next,from SP14 onwards, activation of end to end monitoring is not needed for Alerting. Refer to this note 870232 for this info.
Next, to test if your Alerts have been defined correctly, go to SE38. In the program , type RSALERTTEST and then click on EXECUTE button ( F8 ). In the next window, it will ask you for your ALERTCATEGORY. Just give the name of your ALERT CATEGORY and click EXECUTE.
If you have configured your alerts correctly, you will receive a message that tells ALERT IS GENERATED and will give the ALERT ID.
Now, go to your Run TIme workbench and then select ALERT INBOX and see if you have got the ALERT message in your ALERT INBOX.
If this is working fine, then the last step, implement the note 913858.
The blog speaks about using system variables such as message id in the alert message. Can we use out own variables or the fields in the message in the alert message?
ex: I want to send the material number for which a process failed in the mapping.
Like moorthy told, when trying to trigger alerts without a BPM , the only data that can be passed dynamically are those that are available in this link,
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.