cancel
Showing results for 
Search instead for 
Did you mean: 

"RCVR_DETERMINATION">NO_RECEIVER_CASE_ASYNC

Former Member
0 Kudos

Hi all,

I am doing an interface Siebel to SAP, the inbound adapter is RFC and i am getting an error in the MONI as :

<?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>

and when i checked adapter monitoring: it is showing as below with a green signal:

"Receiver channel 'RFC_OCC_120' for party '', service 'BS_R3D_120' (internal name 'RfcClient[RFC_OCC_120]')

Client data: {jco.client.lang=en, jco.client.snc_mode=0, jco.client.client=120, jco.client.passwd=******, jco.webas.ignore_jdsr_error=1, jco.client.user=sapdev05, jco.client.sysnr=00, jco.client.ashost=sapdev2}

Repository data: {jco.client.lang=en, jco.client.snc_mode=0, jco.client.client=120, jco.client.passwd=******, jco.webas.ignore_jdsr_error=1, jco.client.user=sapdev05, jco.client.sysnr=00, jco.client.ashost=sapdev2}

Current pool size: 0, max pool size : 10"

and

Is a user defined for component AF? is showing red signal and the details are as follows:

Details for 'Is a user defined for component AF?'

com.sap.aii.adapterframework.serviceuser.name = null

com.sap.aii.adapterframework.serviceuser.pwd = null

com.sap.aii.adapterframework.serviceuser.language = null

Any inputs plz!!!!

thanks & regards

viji

Accepted Solutions (1)

Accepted Solutions (1)

former_member189558
Contributor
0 Kudos

Vijaya,

Your receiver determination is failing...

Check the Receiver determination again if the conditions(if any) is satisfied or not...

The Sender Service and Sender Interface in RD should be same as what your inbound message is having.....

Cheers,

Himadri

Former Member
0 Kudos

Hi

i hv checked that... no issues with receiver determination...

regards

former_member189558
Contributor
0 Kudos

Hope ur ID objects are active...

Former Member
0 Kudos

yep

regards

bhavesh_kantilal
Active Contributor
0 Kudos

Hi,

In MONI, check the sender interface, sender Namespace and the sender business service to your message .Is this what you have configured the Receievr Determination for?

Also, how is Siebel sending data to XI?

Regards

Bhavesh

Former Member
0 Kudos

hi Bhavesh,

Siebel is sending thru HTTP.

thanks & regards

Former Member
0 Kudos

hi bhavesh,

any inputs plzl!!!

Thanks & Regards

bhavesh_kantilal
Active Contributor
0 Kudos

Hi,

Like mentioned this has to do with some problem with the receievr determiantion.

The run time is not able to find the receiver.

Like I mentioned please look into the sender service, sender interface, sender namespace of your message in MONI and check if this is what for which you have configred the Receiver Determination.

Test this with a HTTP Client and check if it works.

Check if the QOS is correct!

Regards

Bhavesh

Former Member
0 Kudos

hi bhavesh,

i jst forwarded the screen shots of my scenario to your yahoo id, can u plz, look into that....

regards

viji

bhavesh_kantilal
Active Contributor
0 Kudos

Hi,

can you send it across to my other mail id.

Regards

Bhavesh

Former Member
0 Kudos

Hi Viji,

Can you check what Bhavesh has already ponted out...

In SXMB_MONI, check your msg..

1. Sender service

2. Sender Interface

3. Sender Interface name space

Make sure, these detail match with your receiver determination object in ID.

During runtime, XI finds the receiver only based on these information. If any of these are entered inocrrectly in Receiver determination, Xi can not find a suitable receiver for the msg(which is what is happening in your case)

Regards,

Jai Shankar

Former Member
0 Kudos

Hi,

plz check ur official id.

Thanks & Regards

Former Member
0 Kudos

TQ Jay,

i cldnt find any error in that...

regards

former_member189558
Contributor
0 Kudos

Vijaya,

If you have already tried many things -- i suggest you try one more thing....as sometimes we overlook minor changes for very similar message types ....

1) You copy the Sender Interface from Receiver determination...

paste that in a notepad...

then you copy the sender interface from SXMB_Moni and paste just below it .. and see if they are exactly identical and no change of spelling or anything....

2) Try this for Sender Service and namespace as well .....

Check if you can notice any difference ... we once faced this issue and the difference was 0 and O in the interface name....

Thanks,

Himadri

Former Member
0 Kudos

tq himadri,

wl try to do that.

regards

Former Member
0 Kudos

Hi All,

thanks for ur help, i cld able to find out the error i.e while sending data from siebel itself..

Regards

viji

Answers (2)

Answers (2)

Former Member
0 Kudos

Hi,

Check your Receiver Determination and QOS(BE only In case of mode synchronous). If all are correct then try CPA cache refresh mode = full.

Regards

Sridhar Raju

Former Member
0 Kudos

HI,

Can you please check your receiver determination in integration directory.

Thanks,

TUhin