Alert Configuration

[Former Member]

I could make Alerts work. But I am not able to make the "Where did the error occur?" with restriction like

Integration Engine -

Error Category - XIServer

Error Code - RCVR_DETERMINATION.NO_RECEIVER_CASE_ASYNC

It works fine if I have * in Error Category and Error Code.

I am using SP 15.

Any help appreciated.

[moorthy]

HI Micheal,

<i>

Error Code - RCVR_DETERMINATION.NO_RECEIVER_CASE_ASYNC</i>

• this error you may get if your Business System used in the Reciever System is not in sync with SLD. Or if you have file to Idoc scenario, if your Adapter Specific properties for the Reciever Business system is not pointing correctly you get this error.

Similar Error-

Thanks,

Moorthy

[Former Member]

In my case I have a condition on the Receiver Determination and if the condition is not satisfied I get the error No Receiver Found. In SXMB_MONI I get the error No Receiver Found.

<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>

- <!-- Receiver Identification

-->

- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">

<SAP:Category>XIServer</SAP:Category>

<SAP:Code area="RCVR_DETERMINATION">NO_RECEIVER_CASE_ASYNC</SAP:Code>

<SAP:P1 />

<SAP:P2 />

<SAP:P3 />

<SAP:P4 />

<SAP:AdditionalText />

<SAP:ApplicationFaultMessage namespace="" />

<SAP:Stack>No receiver could be determined</SAP:Stack>

<SAP:Retry>M</SAP:Retry>

</SAP:Error>

But I am not able to trap this via Aler Configuration

[Former Member]

The error is a good Error. I have condition on Receiver Determination which stops certain messages going to the receivers.

I would like to notify users when this happens.

[bhavesh_kantilal]

Hi Michael,

There is <b>no provision</b> for entering Specific Receievr Determination Errors in the <b>ALERT RULE--> WHERE DID THE ERROR OCCUR.</b>

One option would be to give the <b>RECEIVER INTERFACE</b> for the <b>CONDITION and then use NO RESTRICTION.</b>

This way, errors occuring in your RECEIVER DETERMINATION can be trapped.

Regards,

Bhavesh

[Former Member]

I do have a condition on Reciever Determination. When I use No Restriction it works fine. But on the alert rule if you do not use restriction then you cannot for sure say it is the problem with Receiver Determination.

[Former Member]

Hi Michael,

Even with 'No restriction' option, you can find different Error type for diffrent errors.

Anand More.

[Former Member]

But if you select No Restriction Error Category and Error Code are greyed out.

What I am looking is to give appopriate message depending on the error Code.

Even if i can do some kind of if then else in the Shot Text / Long Text in ALRTCAT def I am fine.

[bhavesh_kantilal]

Michael,

<i>Even if i can do some kind of if then else in the Shot Text / Long Text in ALRTCAT def I am fine.</i>

Unfortunately, this is is not possible.

Wouldnt using RECEIVER INTERFACE and then INTEGRATION ENGINE errors solve your problem?

Regards,

Bhavesh

[Former Member]

Hi Michael,

you should be able to do what you want. You can define

rule which has condition and the restriction where the

error occured e.g. in Integration Engine or Adapter

Engine. It works for us!

If you get error please use the report SXMSALERT_LOGREADER

to analyse the error. There you can see what would going

wrong. Also use transaction slg1 to see the application

log of the alert framework.

Regards,

Ly-Na Phu

[Former Member]

What SP level of XI are you on?

[Former Member]

Hi Michael,

we are on SPS15. We just define two part of rule and set

condition to error which occur in the adapter engine and

the other which occur in the integration server. We don't

set condition on Interface level or business system coz.

we don't need it for our requirements.

regards,

Ly-Na Phu

[Former Member]

You distinguish between Integration Engine error or Adapter Engine error.

Let us take the Integration Engine Case. Do you select Error Category and Error Code? For me it works if I leave these *. If I select any specific one it does not work.