Web Service to IDoc scenario: No receiver could be determined error

[nicole_bruneau2]

Hi. I am working on a web service to IDoc scenario. I am receiving this error:

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

I've taken the XML message being sent to me and tested the mapping and I've completed the test configuration in the IB. Both work fine. Any ideas? I've been looking into this for a couple of days, so I've been through all the previous posts I could find.

Thank you.

Nicole

[Former Member · Accepted solution]

hi,

This is not related to receiverdetermination ,whether you creaeted or not.

It is somthing related to receiver systemwhich was configured in Receier determination.

check the target BS is correct or not or the inbound interface.

Did you configured the proper receiver technical system..

OR

Check the Receiver Determination is configured correctly. i.e R/3

Verify all the configurations like SM59, Partner Profile/Logical systems. etc. Also check in SM58 of R/3 system.Make sure that All the objects are activated in the Directory.Refresh the cache.Verify is the business system is pointing to correct R/3 system . Go to Business system/Service->Menu->Adapter specific identifiers in the directory

You can test your configuration with sample

payload.

In ID goto to TOOLS -

---

> Test Configuration for testing.

Hope in this way you can still find at which point the interface goes wrong.

[nicole_bruneau2]

Hello. Thank you so much for all your suggestions.

We've gone through and checked all the above, and it all seems to be configured properly. As this is our first IDoc interface, is there something more or different from the regular RFC scenarios that needs to be done?

Thank you.

Nicole

[nicole_bruneau2]

We did a complete restart yesterday, refreshed all the caches. No change, however.

Thank you.

[dharamveer_gaur2]

check your business system,sender and reciever both.also check type of business system.

recieve business system should be Web as ABAP in your case.

also check software component is assigned to business system that u r using.

Edited by: Dharamveer Gaur on Sep 19, 2008 6:33 AM

[nicole_bruneau2]

The QOS is set to EO.

I just checked the J2EE logs, and I've got this error message in there:

"Error during parsing the SOAP part --- Unexpected content in SOAP:Envelope"

Is it possible it's the message coming in that's causing the problem? If so, how do I debug this?

Thank you.

Nicole

[Former Member]

you may like to give a try:

Restart the J2EE engine and also refresh all the Cahches.

Thanks

Kiran

[nicole_bruneau2]

We've been working on this problem for a while now, so everything has been checked and double-checked. Our basis guys are pretty sure everything is set up properly, I've recreated the entire scenario a couple of times already, as I read that sometimes fixed the problem. I'm not really sure where to look next...Any ideas?

Thanks for all your help.

[Former Member]

Did you also check the QOS in file adapter.

May be you are using BE instead of EOIO or EO.

Some times it can be authorization issues.

you may also like to check the SLD settings. and ensure that SAP is live.

Thanks

Kiran

Edited by: kiran dasari on Sep 19, 2008 1:25 AM

[nicole_bruneau2]

Hello. Yes, these all match the receiver determination's. Anything else?

Thank you.

Nicole

[Former Member]

Can you also re-check your port, rfc dest and other ale configurations.

also check the namespaces are pointing to the right one you are using in the scenario pointing the message interface.

Thanks

Kiran

Edited by: kiran dasari on Sep 19, 2008 1:15 AM

[nicole_bruneau2]

No, the scenario is completely async.

[Former Member]

Hi

Goto SXMB_MONI and check the Sender service, interface and namespace of the errored out message.

Check out whether you have used the same Sender service, interface and namespace in the receiver determination.

-Dava

[nicole_bruneau2]

My receiver determination is fine - the service, interface mapping and receiver agreement all show up and are configured properly. I've used the test configuration tool and it does not have any problems when it run. Anything else?

Thank you.

Nicole

[VijayKonam]

are you doing a complete Asyn scneario? Your sender and receiver interfaces must be async. This error might come if you have accidentally mixed these..

VJ

[VijayKonam]

It is clearly telling the error.. no receiver found.. check your receiver determination..!!

VJ