cancel
Showing results for 
Search instead for 
Did you mean: 

Alert Rule - not working. Wild Card character issue

former_member187437
Contributor
0 Kudos

Hi All,

I have a requirement where I need to trigger alerts for mapping failures

of all the interfaces whose namespace is urn:abc.com:odna* or urn:abc.com.odna*. (in the first instance, there is dot before odna and int he second instance, a colon before odna )

So to suit both the cases, I gave urn:abc.comodna in the Alert Rule.

It worked before. But now its not working.

Then when i changed it to urn:abc.com:odna* it works again. i really dont understand how it worked before and why it fails now.

What is the reason for the unpredicatable behaviour of WildCard Character based Alert Rules?

Should Wild Card Characters be avoided completely?

Accepted Solutions (1)

Accepted Solutions (1)

former_member181962
Active Contributor
0 Kudos

Hi Aarthi,

Check if the List Box: Bound to Message is not selected as "Yes"

It should either be No ro Not Relevant for your case.

Regards,

Ravi Kanth Talagana

former_member187437
Contributor
0 Kudos

Hi Ravi,

Already its set to Not Relevant.

Answers (4)

Answers (4)

former_member187437
Contributor
0 Kudos

Thanks for all your responses.

According to Help.Sap, * should be given either at Start of String or End of String and not anywhere in between .

Former Member
0 Kudos

Hey

Just create two separate alert rules for the same alert category

one for urn:abc.com:odna* and another for urn:abc.com.odna*.

but before that please make sure that "Suppress multiple alerts of this rule" box is unchecked.

Also please check SAP Note 913858

Thanx

Aamir

Edited by: Aamir Suhail on May 20, 2009 9:16 AM

Former Member
0 Kudos

Hi Aarthi,

you should better check report [SXMSALERT_LOGREADER].

this report shows Alert logs.

regards

Yuki

former_member187437
Contributor
0 Kudos

Hi Yuki,

I tried the log reader report.

For urn:abc.comodna it shows 'no rule found' even if there is a Alert Rule for that Namespace.

madanmohan_agrawal
Contributor
0 Kudos

Hi Aarthi,

Just put the * in sender namespace and fill its corresponding Sender Service and Sender Interface with exact value. It will work.

Regards,

Madan Agrawal

former_member187437
Contributor
0 Kudos

For everything other than Receiver namespace i have given *.

madanmohan_agrawal
Contributor
0 Kudos

>>For everything other than Receiver namespace i have given *.

No, please change it.

Enter the other values (reeiever service and interface) those are unique

and enter * in receiver namespace.

regards,

Madan Agrawal

Former Member
0 Kudos

Hi!

Why not defining a rule for both namespaces?

That is urn:abc.com:odna* AND urn:abc.com.odna*

Regards,

Volker

former_member187437
Contributor
0 Kudos

Hi Volker,

That is what i did now. It works.

But still want to know why a ' *' creates problems even if the given value is correct.