cancel
Showing results for 
Search instead for 
Did you mean: 

NO_RECEIVER_CASE_ASYNC

Former Member
0 Kudos

Hi,

this is proxy-->soap Async scenario and i have 'Integrated Configuration' in Directory and this is on 7.3 dual stack. i know there are lots of threads on this error. but nothing helped me. can somebody help in resolving this?

i have this error:

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

- <!--

Receiver Determination

-->

- <SAP:Error SOAP:mustUnderstand="1" xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
<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:Stack>No receiver could be determined</SAP:Stack>

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

</SAP:Error>

I I see this thread: http://scn.sap.com/thread/3181937  is there any SAP note regarding this? Just wanted to make sure this change doesn't affect other things major.

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hey Prema, the problem might be that your message is being sent to the Integration Engine, not towards the Advanced Adapter Engine. You need to create the configuration in SXMSIF and SXMB_ADM.

You can find the whole description in this document:

http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/70066f78-7794-2c10-2e8c-cb967cef4...

Check section "4.1 Configurations in the Sender ABAP System."

Former Member
0 Kudos

thanks Aerv, the config is in place.

Answers (7)

Answers (7)

Former Member
0 Kudos

I tried with "receiver determination" instead of "integrated configuration"; it works like charm.. any settings i should take care when doing with integrated configuration? thank u all for your help.

former_member190624
Active Contributor
0 Kudos

Hi Prema,

You can not use Integrated configuration ,Since the Integration Server does not participate in the processing of messages, any functions provided only on the Integration Server are not available for local message processing.

The following functions are not available when using local processing in the AAE:

Adapters: IDoc, HTTP

Mapping: ABAP

ccBPM

Proxy

Regards

Hari.

Former Member
0 Kudos

Using proxies in Integrated Configurations is perfectly possible. You just have to use the SOAP XI adapter instead of the XI adapter...

Former Member
0 Kudos

If your message is still arriving in the integration server, your setup (sxmb_adm and sxmsif) is not correct. You need to follow every step in the document and make sure all steps are done correctly.

Former Member
0 Kudos

you are so right Aerv. thanks so much for your coerce on the settings..

Sender/Reciver ID of that proxy in sxmb_admin was pointing to wrong system(prod); now is changed to point to correct system(sanbox) in ECC system.

whenever ECC integration do not find right Sender/Receiver ID then it just send the message to IE of PI from ECC system.

the document you shared is very useful one. thanks. in that document it says to make it as "*" but we changed to point to perticular system.

this resolved our issue.

former_member190624
Active Contributor
0 Kudos

Hi Prema,

I faced same error "NO_RECEIVER_CASE_ASYNC" . In my case i used wrong communication component. Please check you are using correct sender business system .

Regards

Hari.

Former Member
0 Kudos

thanks Hari; i have the correct BS.

former_member190624
Active Contributor
0 Kudos

So  your problem solved now? If yes,please close this thread

Former Member
0 Kudos

no not yet.

Former Member
0 Kudos

Can you add this to your SoapSenderAdapter:

I am not 100% sure though.

For the sap.com/com.sap.aii.af.soapadapter/XISOAPAdapterBean add these parameters:

generateSysAck = true

ignoreDuplicate = true.

Former Member
0 Kudos

the parameters are already there Aerv, thanks.

Former Member
0 Kudos

Prema: Could you check if the error is on the Original message or on the response? Also, can you check if the target system is raising an exception?

Former Member
0 Kudos

Feroz, it is stuck at the 2nd step "Receiver Determination". it comes in PI 1st step "Inbound Message" i see the payload;

  as this is Async message; there is no response. its proxy to file. its not reaching partner system yet.

and i don't understand why this error is showed in sxmb_moni (IE) not in AAE? as this is proxy and is soap.

baskar_gopalakrishnan2
Active Contributor
0 Kudos

Please check the following.  Do you specify the receiver business component, target service interface and namespace accordingly without any error in the integrated configuration object? Do you have multiple operation in the service interface?

Former Member
0 Kudos

Baskar, Yes i checked the details many times. it has receiver business component, target service interface and namespace. thanks.

rajasekhar_reddy14
Active Contributor
0 Kudos

The problem looks with receiver determiantion like the condition written in RD not satisfied . i am not sure how PI 7.3 Configurtaion works(like no need to create RD/ID??).

Former Member
0 Kudos

Raja; no I don't have any condition. also i don't have receiver determination; I have integrated configuration.

iaki_vila
Active Contributor
0 Kudos

Hi Prema,

At first you should say to the community what you have tried and the people could avoid to repeat a possible solution that you already have tried.

I have a question, are you sharing the communication channel in several scenarios?

Regards.

Former Member
0 Kudos

No Inaki; the CC is not shared. This is the only place it is used. thanks.