XI Error NO_RECEIVER_CASE_ASYNC.RCVR_DETERMINATION

My scenario is like this
client 010 NumberRangeRequest_Out --> XI --> NumberRangeRequest_IN client 020 and after this
client 020 NumberRangeConfirmation_Out --> XI --> NumberRangeConfirmation_Out client 010
when i execute NumberRangeRequest_Out from sproxy of client 010 , it goes to XI and client 020 but
it doesnt return from client 0320 because it gives errors "NO_RECEIVER_CASE_ASYNC.RCVR_DETERMINATION"
but when i try to send NumberRangeConfirmation_Out from client 020 to client 010 separatedly, it successfully arrives.
Why is the reason that i cannot get the message from client 020 after sending to it?
Thanks

Hi
As I mentioned in my previous post..
go thru each particular detail of the trace & steps in SXMB_MONI, for the msgs... double clicking it
not the overview alone..
however you said
"second message sender 10 and no receiver"
so
- is it the msg from client 20 (with wrong sender)
- or is it once again msg from client 10 ???
by comparing the above said info (details of msg in SXMB_MONI, trace, pipeline steps, etc), u will be able to fix the issue
Regards
Vishnu

Similar Messages

Error is "RCVR_DETERMINATION" NO_RECEIVER_CASE_ASYNC

Hi All,
I am facing error "RCVR_DETERMINATION">NO_RECEIVER_CASE_ASYNC when sending data from one system to another system.
pls let me know any one how to resolve this issue?
Thanks
Kumar.

Hi Kumar,
There might be configuration issue in the development of the interface.
Please test the Configuration objects in Integration Directory.
Steps to test the configuration.
1. In Integration Directory, Click on Tools.
2. Select Test Configuration.
3. Provide sender and receiver details and payload, then click on Test configuration on the screen.
4. Then click on Run.
This checks whether the configuration done is correct or lets us know if any issue in the configuration.
Thanks,

Message doesnot return back in sequantial asynchronous scenario

I have an scenario like this,all of messages are executing asynchronously by calling from sproxy,
Request
clientZET029 --> NumberRangeRequest_Out   XI NumberRangeRequest_In --> clientOER030
Response
clientOER030    --> NumberRangeConfirmation_Out XI   clientZET029 NumberRangeConfirmation_In--> clientA
when i try to carry out all scenario i get error "XI Error NO_RECEIVER_CASE_ASYNC.RCVR_DETERMINATION"
I executing NumberRangeRequest_Out service from sproxy of ZET029 and expecting a return message from OER030 but it arrives to OER030 but not come back it gives error, and like you see , sender of all messages are ZET029 it is the problem i think
here my sxmb_moni logs
Processed successfully               ZET029     NumberRangeRequest_Out               NumberRangeRequest_Out               SENDER     PROXY     IENGINE
Processed successfully               ZET029     NumberRangeRequest_Out          OER030     NumberRangeRequest_In               CENTRAL     IENGINE     IENGINE
Processed successfully               ZET029                         OER030     NumberRangeRequest_In               RECEIVERIENGINE     PROXY
System Error - Manual Restart Possible     ZET029     NumberRangeConfirmation_Out                                   CENTRAL     IENGINE
Processed successfully@               ZET029     NumberRangeConfirmation_Out          NumberRangeConfirmation_Out          SENDER     PROXY     IENGINE
Thanks

I can't understand in asynch how response will come back to sender?

EOIO Queues - Sysfail..

Hi,
I am getting messages from SRM to Int Server of XI directly using SAP Delivered BADI and in the BADI serialization is set so those Messages goes in to EOIO Queues.
Now all the Messages are stuck in different EOIO queues with Sysfail status of Queues Now so far there is two types of Sysfail errors:
1. XI Error NO_RECEIVER_CASE_ASYNC.RCVR_DETERMINATION
(Only one message in this status though I have tested the configuration In XI IR and works successfully)
2. An exception occurred that was not caught (All toghather 5 messages)
Any suggestion what can be the Case?
Thanks,

Hi,
I have recreated all the config objects again so it solved the first problem but the second problem is still there and the queues are still getting stuck saying
An exception occurred that was not caught.
and when I click the queue it opens the ABAP code for function module SXMS_ASYNC_EXEC
Detailed analysis in SXMB_MONI:
the message processing is stuck at "Message Branch According to Receiver List" step. Also in the trace of the same step I can see following:
- <Trace level="1" type="B" name="CL_XMS_MAIN-PERSIST_READ_MESSAGE">
<Trace level="3" type="T">Trace object available again now. OK.</Trace>
<Trace level="3" type="T">Message was read from persist layer. OK.</Trace>
<Trace level="3" type="T">Message properties in XMB object were setup. OK.</Trace>
<Trace level="3" type="ToDo">Make sure we catch exceptions in persist read</Trace>
<Trace level="3" type="ToDo">Tracing obj. not avail. before return of CL_XMS_MAIN-PERSIST_READ_MESSAGE</Trace>
</Trace>
<Trace level="1" type="T">Root-Exception from packaging: An exception with the type CX_SY_REF_IS_INITIAL occurred, but was neither handled locally, nor declared in a RAISING clause</Trace>
<Trace level="1" type="T">Continue single processing</Trace>
<Trace level="1" type="T">Note: the following trace entry is written delayed (after read from persist)</Trace>
<Trace level="1" type="B" name="SXMS_ASYNC_EXEC" />
Any help resolving this will be appreciated.
Thanks.
-Adrean.
Message was edited by:
Adrean Hart

Error in receiver determination - Client proxy to IDOC using PI-IS

Hi,
I am using client proxy to send the order acknowledgement from SCM to R/3 , I am getting below error
<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>
I am using the standard SAP message interface in the sproxy.
Also I am getting error in Proxy generation "Logical port template not determined" "LPT could not be created without DT".
Thanks,
Menaga

<SAP:Code area="RCVR_DETERMINATION">NO_RECEIVER_CASE_ASYNC</SAP:Code>
The above error occurs due to:
1) You have configured a wrong receiver service in the Receiver Determination
2) You have configured the correct receiver but the cache is not updated
So check if the receiver service exists and the cache is updated.
Also I am getting error in Proxy generation "Logical port template not determined" "LPT could not
be created without DT".
Check if you get any lead from this thread:
Failed to time to generate proxy - TRX SPROXY
Does it mean that you have no proxy generated and you are testing??....if yes then you will get the above error (NO_RECEIVER_CASE_ASYNC).
Regards,
Abhishek.

RCVR_DETERMINATION

Hi,
Iam getting the following error message when the XI interface is run. Can someone help in understanding the problem.
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <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>
Best Regards
Suresh

Hi,
This error occurs only when ever there is problem in Receiver Determination configuration.
The error NO_RECEIVER_CASE_ASYNC indicates that your scenario is not working due to unavailability of Receiver Determination.
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.
refer
Strange error
No receiver could be determined. (File to Idoc)
XI 3.0 No receiver could be determined
Thanks
Swarup

PI 7.1 - Multiple Operations - NO_RECEIVER_CASE_ASYNC

Hello All
I am using PI 7.1, Proxy to JDBC scenario. I a trying to use a single Service Interface with multiple operations (Customer, Vendor). When I test the scenario I am getting the error "NO_RECEIVER_CASE_ASYNC" at SXMB_MONI. Receiver Determination is configured as Operation Specific. However this error occurs.
Has anyone who could help me on this?
Thanks
John Jeyaraj

Hi John ,
following is one of my wiki where I have explained how to determine receiver system based on operation if you have multiple operations under single service interface..
http://wiki.sdn.sap.com/wiki/pages/viewpage.action?pageId=233472879
in your case make sure that you have done configuration as expected and object receiver determination is active and there is no problem in Cache..
if configuration is correct then this might be problem with cache..
check cache..
check your object status in tcode SXI_CACHE
try activating your receiver determination object and one more time..
Thanks,
Bhupesh

IDOC- XI- Mail Scenario

Hi All,
I am configuring IDOC-XI-Mail scenario using following web-log:
/people/michal.krawczyk2/blog/2005/03/07/mail-adapter-xi--how-to-implement-dynamic-mail-address
I follow following steps:-
1) In IR-create Name Space -"http://sap.com/xi/XI/Mail/30 "
2) In IR-Upload XSD file from SAP note: 748024
3) In IR-Do message mapping with Imported IDOC
4) In ID-Add Business System's for SAP & XI
5) In ID-Create mail receiver communication channel
(URL/User ID/Password/User Mail Package only)
When I test trigger IDOC from SAP, I get Error in SXMB_MONI
(Error category:RCVR_DETERMINATION, Error ID:NO_RECEIVER_CASE_ASYNC)
Is i need to do more configuration's in IR & ID that is not explained in Web-log?
Is there is any other configuration need to be done on server to send mails?
Please guide me in completing Idoc->Mail scenario.
Thanks & Regards

Hi Rohan,
"4) In ID-Add Business System's for SAP & XI"
You donot have to create a business system for XI.
First of all you can either create a business system which needs to be created in SLD such that it is pointing to your target system (which here is the mail server) or you can use a business service. Choose any one of them.
"When I test trigger IDOC from SAP, I get Error in SXMB_MONI
(Error category:RCVR_DETERMINATION, Error ID:NO_RECEIVER_CASE_ASYNC)"
Check if you have defined your message interfaces correctly. Since you are not expecting any response from the mail adapter, the inbound and outbound interfaces should be asynchronous.
Also check if you have defined your receiver determination correctly. Here you should give the source and target systems and interfaces correctly. The problem sems to lie here. Check these configurations once again.
Regards,
Sushumna

Idoc to Proxy Scnerio

Dear All ,
We are having one ECC--PI-SUS Scneriao . We triggering an Idoc from ECC named "Z_CREMAS_SUSMM.CREMAS03" and on receiver side having Inbound Proxy. Idoc is getting successfully trnasfered from ECC to Pi but in PI Sxmb_moni we are getting below error "<SAP:Code
area="RCVR_DETERMINATION">NO_RECEIVER_CASE_ASYNC</SAP:Code">.
When we test the payload in INtegratation Directory using test configuration it successfully passes all the steps mention.
Please help.

Hi,
Have you gone thru these links below?
error message : RCVR_DETERMINATION">NO_RECEIVER_CASE_ASYNC</SAP:Code>
RCVR_DETERMINATION.NO_RECEIVER_CASE_ASYNC
RCVR_DETERMINATION - NO_RECEIVER_CASE_ASYNC
NO_RECEIVER_CASE_ASYNC
NO_RECEIVER_CASE_ASYNC
RCVR_DETERMINATION
RCVR_DETERMINATION">NO_RECEIVER_CASE_ASYNC
Please also search SCN before asking this commonly asked question. If you did search. Copy the links that you used and which links did not resolve your issue.
Regards,
Jannus Botha

Message ID SXMS_MSG_GUID not getting displayed in alert inbox

Hi,
In ALRTCATDEF i have defined container element named SXMS_MSG_GUID which has ABAP Dict. Data Type SXMSMGUIDC. In the message title i have used that container element using &SXMS_MSG_GUID&. I am getting alert in my alert inbox in RWB but all the other texts are displayed except the message id. I even tried using dynamic text but no luck. Can anyone plz tell me how can i get the message id displayed in my alert inbox?
Please advice!!!
Regards,
Mateen.

Bhavesh,
The message is failing because of the error "NO_RECEIVER_CASE_ASYNC" says "No receiver could be determined". Its not related to an adapter error. I went through the note which you suggested but its not providing much help.
Regards,
Mateen.

SOAP Adapter doesn't find channel

Hi all,
I currently have XI 3.0 SP11 running and I'm trying to set up a simple <SOAP> -> <XI> -> <SOAP> scenario with it. Therefore I configured a Business Service called "WSClient" without associating it to a party. This service contains a Communication Channel called "SOAPClient" that is configured to use the SOAP Adapter and to act as a sender.
When i now try to send data to XI using a simple web service client i get the following error:
SystemError:
 <context>XIAdapter</context>
 <code>ModuleUnknownException</code>
 <text><![CDATA[
com.sap.aii.af.mp.module.ModuleException: either no channelID specified or no channel found for the specified party, service, and channel name, MessageServlet(Version $Id: //tc/aii/30_REL/src/_adapters/_soap/java/com/sap/aii/af/mp/soap/web/MessageServlet.java#7 $)
 at com.sap.aii.af.mp.soap.web.MessageServlet.doPost(MessageServlet.java:497)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
 at ...
</text>
Therefore I tried to use the HelperServlet to see if the channel is available. When invoking the HelperServlet with the parameters action=FindChannel&channel=:WSClient:SOAPClient
I get the following error:
<SOAP:Fault>
 <faultcode>SOAP:Server</faultcode>
 <faultstring>Server Error</faultstring>
 <detail>
 <s:SystemError>
 <context>XIAdapter</context>
 <code>ADAPTER.SOAP_EXCEPTION</code>
 <text>
java.lang.Exception: Channel not found for SOAPClient in http://sap.com/xi/XI/System^SOAP
 at com.sap.aii.af.mp.soap.web.HelperServlet.processFindChannel(HelperServlet.java:408)
 at
Somehow the Adapter Engine seems not to recognize the channel I have configured.
Any ideas how to solve this problem?
Thanks for your help.
Christian

Hi,
I have observed that when the SOAP sender channel is not activated, and a request is posted to XI, u will get "ModuleUnknownException".
When the Sender SOAP Adapter is created in BE mode and "no receiver determination" is created, you will encounter "DeliveryException" while testing using XMLSPY. U will find that the message has failed in XI with an error "NO_RECEIVER_CASE_BE"
When the Sender SOAP Adapter is created in EO/EOIO mode and "no receiver determination" is created, you will not encounter any error while testing using XMLSPY. But you will find that the message has failed in XI with an error "NO_RECEIVER_CASE_ASYNC"
Also make sure you defined the correct
"Default Interface NameSpace" and
"Default Interface Name"
in the Sender SOAP Channel. Else the message will fail b'cos it will not find the correct receiver Determination.
Cheers,
Siva Maranani

Question regarding XI/PI and Idoc processing.

Hi,
I'm learning XI/PI and I have a question regarding Idoc processing in PI.
We need to configure communication between our BW system and our PI system using Idocs.
The Idocs are sent from BW to our PI systems and are then sent back to the BW system, there are no third system involved. The idocs are only between PI and BW.
Our BW system is already connected with many other R3 systems by using WE20 / WE21 and RFC's and everything works perfectly.
While I configure this communication between BW and PI it seems that PI is passing the Idoc to the Idoc adapter, converts it to xml and tries to find a receiver for the particular Idoc. I see the error "NO_RECEIVER_CASE_ASYNC" in SXMB_MONI.
Is this a normal behaviour in PI ? Why is PI thinking that the Idoc needs to be sent to another system when it is infact for itself ??
Thanks and regards
Remi

Hi
for error "NO_RECEIVER_CASE_ASYNC" in SXMB_MONI.
This problem may occur due to one of following reasons, so check
1 service is active in message? transaction SICF and activate service sap/xi/engine (right click, activate)
2 Is the port 8001 defined in the services on the smicm under services?
3 Check the roles assign PIDIRUSER
http://help.sap.com/saphelp_nw04/helpdata/en/56/361041ebf0f06fe10000000a1550b0/content.htm
role: SAP_XI_ID_SERV_USER attached to it
Also Check Whether PIDIRUSER has following role
SAP_SLD_CONFIGURATOR
SAP_XI_RWB_SERV_USER
SAP_XI_RWB_SERV_USER_MAIN
Regards
Abhishek

RCVR_DETERMINATION" NO_RECEIVER_CASE_ASYNC error while monitering

hi every body....
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <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>
all my configuration steps are perfect in ID...
why ian gting this error while moniteriong..
JOhn

Hi,
This error occurs brcause of
1.Message will stay in XI for no receiver found
Solution
1. Check whether it has been configured correctly (Receiver Determination step also check if you are using XPATH in it, ie for conditional receiver determination and check it for correct info)
2. It has correct receiver agreement.
3. If its receiver determination includes the conditional receiver then make sure that it satisfies the condition.
4. Also make sure that its value for funloc is the same.
regards
Aashish Sinha
PS : rewrd points if helpful

Error: RCVR_DETERMINATION:NO_RECEIVER_CASE_ASYNC

Hi Experts,
I'd like to ask for help about that specific error:
RCVR_DETERMINATION:NO_RECEIVER_CASE_ASYNC
We are using Enhanced Receiver Determination for this one, testing the mapping using the test tab results in having a proper receiver identified. But when it comes to runtime, the error above is shown in sxi_monitor.
We are also using an HTTP-RFC destination (Response 200) in our Plain HTTP Adapter. I have also done a full sxi_cache refresh and the changes are already showing in the cache, but still I'm getting the RCVR DETERMINATION error. I also have consulted similar threads here, but that did not help.
Regards,

You are definately missing something
Either you have given a wrong condition or the characters in the condition and the one coming in the message is not right
Check these items:
1. Check the inbound XML if the values coming according to the desired one
2. Check if the condition in the Reciver determination is working fine...
The problem sure is very small you need to trace it.. it would be good if you can paste some of the trace from sxmb_moni with details of the message u hve tested
Rgds
Aditya

BPM Error --- RCVR_DETERMINATION NO_RECEIVER_CASE_ASYNC

Hi All,
For my simple BPM scenario -- I am getting RCVR_DETERMINATION NO_RECEIVER_CASE_ASYNC
Point to add -- My BPM has correct Receiver Determination.
1. Because When I activate my ID objects and checked in Environment -- Cache Status Overview
It displays --Integration Server ABAP Cache -- Not Yet Started
2. Also -- In SXI_CACHE in Integration process Node I am not able to see my BPM object
Can u pls let me know how to resolve this cache and BPM problem.
Regards

did you follow the steps mentioned as in this document:
http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/1a69ea11-0d01-0010-fa80-b47a79301290&overridelayout=true
You seem to have checked the destination in SM59....similarly did you check the services in SICF?
Regards,
Abhishek.

XI Error NO_RECEIVER_CASE_ASYNC.RCVR_DETERMINATION

Similar Messages

Maybe you are looking for