Testing the Alert Category Configuration in PI

[Former Member]

Hi Experts,

I have a PI scenario of IDOC to XML. To get the Alert mails, I have set the Alert Category Configuration using the Transaction ALRTCATDEF, also the RWB settings are done and the sender namespace given is that of IDOC in RWB.

The issues faced are,

1. If some IDOC (ORDRS05) fails then it gives all the proper mails with all the Container element information, but if IDOC (DEBMAS06) fails then it doesnt trigger mails.

2. If it triggers then container elements are also not displayed in the mails

Can any one please provide a solution for the above issues, or even a test plan that tells how to test the IDOC failure notifications.

Rregards,

Rohit.

[Former Member]

Unlike the proxy scenario, failed IDOC can not trigger the alert if the IDOC has not reach PI.

If this is customized IDOC, then in your program, then in your ABAP program, you send IDOC by calling function MASTER_IDOC_DISTRIBUTE, you can check the exception return value,then call function SALERT to send proper alert.

Now it is standard IDOC, then you have to find the similar place that sending IDOC out of your sender system, implement enhancement on your function that sending IDOC by calling SALERT triggering alert.

Regards

Liang

[Former Member]

Hi Rohit,

> 1. If some IDOC (ORDRS05) fails then it gives all the proper mails with all the Container element information, but if IDOC (DEBMAS06) fails then it doesnt trigger mails.

When you are creating the alert rules in RWB have you mentioned any sender interface, sender party and namespace details? if yes check those things are same for the DEBMAS06 also, if it is not same then you have to create one more rule. otherwise if you want to trigger this alerts to all the interfaces then put * in all the fields.

> Can any one please provide a solution for the above issues, or even a test plan that tells how to test the IDOC failure notifications.

By executing one report program we can test the Alerts.

execute the report RSALERTTEST in SE38

Regards,

Ramesh

[Former Member]

Hi Ramesh,

Even after giving ' * ' in all the filter fields of RWB, it doesnt give proper details of the alert. It works for other interfaces where the sender is not an IDOC, but doesnt give proper information when IDOC is sender

Regards,

Rohit

[former_member200962]

where is the IDOC failing?

You would get an alert in the Integration Engine (pipeline) steps like mapping error....or error while sending to receiver adapter

Regards,

Abhishek.

Edited by: abhishek salvi on Aug 10, 2010 4:44 PM

[Former Member]

Hi Rohit,

> Even after giving ' * ' in all the filter fields of RWB, it doesnt give proper details of the alert. It works for other interfaces where the sender is not an IDOC, but doesnt give proper information when IDOC is sender

Which type of error you selected?

No restriction or Adapter engine error or Integration engine error in the RWB?

Regards

Ramesh

[Former Member]

No Restriction in the RWB

[Former Member]

Hi Rohit,

Check by creating the separate rule for this idoc(DEBMAS06) and give the all details about this scenario like interface name, namespace,..

Regards

Ramesh

[Former Member]

Hi,

Tested with seperate configuration for DEBMAS06 but didnt get any alerts,

The scenario's where we are testing the alert are,

1. The Output from the target structure of PI is given as an input to a program that inserts data into SQL database, if this program is down then we get a '500 Internal Server error' in SXMB_MONI

2. The IDOC is extended but not reimported in PI, It gives 'No receiver determined' error in SXMB_MONI

How to get Alert mails for such errors??

Regards,

Rohit

[Former Member]

Hi,

Check the suppress multiple alerts has been selected in the alert rule if it has been selected then you need to complete the alert generated earlier...

also execute the report SXMSALERT_LOGREADER for the logs of the alerts..

HTH

Rajesh