No receiver could be determined - ERROR

[Former Member]

Folks - I am getting this error - "No receiver could be determined" when testing using an SAP provided HTTP client for us. I have input the following parameters in the URL:

http://srvhousapdemo:8013/sap/xi/adapter_plain?namespace=http%3A//www.wellogix.com/PIDX_12/R3_46&int...

ServerHost - srvhousapdemo

ServerPort - 8013

Client - 200

SenderService - XIS_eFT

QOS - BE

SenderInterface - Z_PO_Create

SenderNamespace - http://www.wellogix.com/PIDX_12/R3_46

ServiceUser - xiappluser

Password - xxxxxxxx

Any pointers will be appreciated!

Thanks.

-Cal

[STALANKI]

Is there any content based routing in that?

[Former Member]

No - we are simply using an SAP developed HTTP client for our company to send in an XML PO document to XI.

No routing etc..at this time.

[Former Member]

Just to confirm...

You have the following entries in the configuration :-

<b>1.Receiver Determination</b>

Sender service - XIS_eFT

Sender Interface - Z_PO_Create

Sender Namespace - http://www.wellogix.com/PIDX_12/R3_46

Configured Receivers - <Receiving_Service>

<b>2. Interface determination</b>

Sender service - XIS_eFT

Sender Interface - Z_PO_Create

Sender Namespace - http://www.wellogix.com/PIDX_12/R3_46

Receiver Service - <Receiving Service>

Configured Inbound Interfaces - <Inbound_interface> / <Interface_Mapping>(may or maynot be there)...

<b>3. Receiver Agreement</b>

Sender service - XIS_eFT

Receiver Service - <Receiving Service>

Receiver Interface - <Inbound_interface>

Receiver Namespace - <Inbound_interface_Namespace>

Receiver Communication Channel - <reciever_comm_channel>

[Former Member]

Yes confirmed. The only difference - my sender namespace has no 'www' in www.wellogix.com

[Former Member]

That may be the reason...the entries in your query string and the entries in the receiver determination has to match exactly....

Thanks,

Renjith

BTW ..welcome to SDN !

Message was edited by: Renjith Andrews

[Former Member]

If I have the exact information on both (which would make sense) - I do not get any response. But our system person checked the logs and it has - Couldn't find delivery channel for message -error

[Former Member]

Hi,

I have the same error

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

but in my case the interface has been succesfully executed before. We made no changes. Do you think that in this case could be something related with Cache?

Thanks.

Patricio.

[Former Member]

Hi patricio,

This error occurs only when ever there is problem in Receiver Determination configuration.

Please re check it again.

Regards

Hope it is helpful

[Former Member]

hey

do one think,change ur receiver to edit mode,make some changes and then delete those changes,u can jst enter a space and then delete it (do dis jst to make the "save" icon alive,nothin specific),then save ur obj and activate it.

also make sure ur ID steps are in place

thanx

ahmad

[former_member335553]

HI

1. If all the receiver determination and interface determination are correct, just make some dummy changes on your receiver determination and reactivate it.

2. There may be a mismatch in sender, sender interface, sender interface namespace (and optionally any conditions for content-based routing) values between your configured receiver determination and in the actual message header.

Check your acutal message header at runtime - SXMB_MONI, then Inbound Message->SOAP Header->Main. Check values within <SAP:Sender> for Service, Interface and namespace. These have to match those configured in your receiver determination.

[MichalKrawczyk]

hi,

>>>"No receiver could be determined

what about your receiver determination inside directory?

is it ok?

Regards,

michal

[Former Member]

Yes..I have defined the receiver determination settings in the Integration builder.