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

Similar Messages

WebService Call: RCVR_DETERMINATION: NO_RECEIVER_CASE_BE

Hello,
I want to call an external Web Service from my ABAP Code, but I get an error in transaction sxmb_moni:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <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_BE</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 have no idea, where this error message comes from... Have you any solution proposals?
Thank you

Hi Yu
for the error RCVR_DETERMINATION.NO_RECEIVER_CASE_BE error
look at these thrad discussed the same
Consume a Web Service: No receiver could be determined
Error in my HTTP > XI > RFC (BAPI) senario
Http to IDOC Error
Regards
Abhishek

Error:RCVR_DETERMINATION" NO_RECEIVER_CASE_BE

hi all,
In my soap-xi-rfc scenario this is the error i am getting in MONI when using .wsdl file from EP
<i><SAP:Category>XIServer</SAP:Category>
<SAP:Code area="RCVR_DETERMINATION">NO_RECEIVER_CASE_BE</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>N</SAP:Retry>
</SAP:Error></i>
but when i am testing the same data from HTTP client it is working fine.
I have deleted the receiver determination and interface determination and created again,but the error continues.
Also in MONI in the message list i can see the sender interface but i am not able to see the receiver system and interface
Can anyone help me out with this??
thanks and regards,
Nisheeta

Hi,
Check the trace in SXMB_MONI, and refresh cache.
Check you configred the determinations correctly or not,
check the receiver interfaces also in IR.
Please compare the entries in IB directory (receiver determination) with entries in Monitoring (SXMB_MONI): Service, Interface, Namespace
also see the below links
RCVR_DETERMINATION">NO_RECEIVER_CASE_BE
Consume a Web Service: No receiver could be determined
Regards
Chilla
<i>reward points if it is helpful..</i>

RCVR_DETERMINATION.NO_RECEIVER_CASE_BE

Hi,
I am trying to consume a web service (which published by a third party, out side of my network) through PI 7.11 . I have created the external definition via the web service WSDL then defined the Service Interfaces, Message Mappings and Operation Mapping in IR. Later i configured the scenario in ID and tested in Test Configuration in ID. It found correct receivers with the payload.
I also generated ABAP Proxy in ECC system and run test in SPROXY. It gave me "RCVR_DETERMINATION.NO_RECEIVER_CASE_BE No receiver could be determined" error message. I have run "http://<saphost>:<port>/CPACache/refresh?mode=full" many times but didnt help. I copied below TRACE message from SXMB_MONI.
I also noticed that there are two lines per test. One is sender and one is receiver but both Interfaces are same and outbound one.
What could be the problem?
KR,
Altug

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

<SAP:Trace xmlns:SAP="http://sap.com/xi/XI/Message/30">
<Trace level="1" type="T">CL_XMS_MAIN->DETERMINE_EXT_PID: CENTRAL</Trace>
<Trace level="1" type="T">Party normalization: sender</Trace>
<Trace level="1" type="T">Determining the sender agreement</Trace>
<Trace level="1" type="B" name="CL_XMS_HTTP_HANDLER-HANDLE_REQUEST" />

<Trace level="1" type="T">XMB was called with URL /sap/xi/engine?type=entry</Trace>
<Trace level="1" type="T">User = XXXXXX</Trace>
<Trace level="1" type="T">Message ID = 4C0A5693C69C010DE10080000AA6001A</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-ENTER_XMS">
<Trace level="1" type="T">CL_XMS_MAIN->DETERMINE_EXT_PID: CENTRAL</Trace>
<Trace level="1" type="T">CL_XMS_MAIN->DETERMINE_INT_PID: SAP_CENTRAL</Trace>
<Trace level="1" type="B" name="CL_XMS_TROUBLESHOOT-ENTER_PLSRV" />
<Trace level="1" type="T">system-ID = BPD</Trace>
<Trace level="1" type="T">client = 100</Trace>
<Trace level="1" type="T">language = E</Trace>
<Trace level="1" type="T">user = XXXXXX</Trace>
<Trace level="1" type="Timestamp">2010-06-09T06:04:21Z CET</Trace>
<Trace level="1" type="T">ACL Check is performed</Trace>
<Trace level="1" type="T">XML validation is executed</Trace>
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_UC_EXECUTE">
<Trace level="1" type="T">PLNAME = CENTRAL</Trace>
<Trace level="1" type="T">QOS = BE</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_SYNC" />

<Trace level="1" type="T">>>>PID delete old pid determination coding</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
<Trace level="1" type="B" name="PLSRV_XML_VALIDATION_RQ_INB">
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
<Trace level="1" type="B" name="CL_XMS_PLSRV_VALIDATION-ENTER_PLSRV">
<Trace level="1" type="T">Reading sender agreement</Trace>
<Trace level="1" type="T">Message does not contain a sender agreement</Trace>
<Trace level="1" type="T">Inbound validation by Integration Engine does not take place</Trace>
</Trace>
</Trace>
</Trace>
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
<Trace level="1" type="B" name="PLSRV_RECEIVER_DETERMINATION" />

<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL" />

<Trace level="1" type="B" name="CL_RD_PLSRV-ENTER_PLSRV">
<Trace level="1" type="T">R E C E I V E R - D E T E R M I N A T I O N</Trace>
<Trace level="1" type="T">Cache Content is up to date</Trace>
<Trace level="1" type="T">No Relation found - accept given Receivers.</Trace>
</Trace>
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
</Trace>
<Trace level="1" type="T">An Exception has occured</Trace>
<Trace level="1" type="T">Error Text: No receiver could be determined</Trace>
<Trace level="1" type="T">SystemError message generated. Guid: 4C0C7AEFF2EC0079E10080000AA60016</Trace>
<Trace level="1" type="T">Error during execution of message : 4C0A5693C69C010DE10080000AA6001A</Trace>
<Trace level="1" type="T">ApplicationMessage was (=RefToMsgId): 4C0A5693C69C010DE10080000AA6001A</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />

</SAP:Trace>

"RCVR_DETERMINATION" NO_RECEIVER_CASE_ASYNC

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

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

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.

Error RCVR_DETERMINATION

Hi,
all iam doing IDOC TO JDBC scenarion.
IDOC is passing from R/3 to XI in SXMB_MONI giving following error. In error ID having the follwoing error message.
<?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>
regards
kumar

Hi,
This error occurs if your Business System used in the reciever is not the same in SLD. See your Adapter Specific properties for the Reciever Business system is correct.
Check this thread this will help you
No Receiver Determination
Errors about 'No receiver could be determined'
Thanks,
Prakash

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

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

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

RCVR_DETERMINATION.NO_RECEIVER_CASE_BE - encoded URL in WSDL

Hi
I have a SOAP to RFC scenario and generated the wsdl using PI 7.11 Integration Builder. The generated URL in the wsdl contains HTML encoded characters because the URL contains a URL e.g..
https://myhost/sap/xi/engine?type=entry&version=3.0&Sender.Service=BC_MY_SENDER&Interface=http%3A%2F%2Four_host%2Fsap%2Fabcd%5ESI_MY_PROCESS_OUTBOUND.
I have tried to use this URL in soapUI but it does not work and returns a message like the one in this thread's subject.
If you urldecode the url it works in soapUI. One of our clients who will use this web service to call us has to have the url encoded (with %) in it because of the url in a url. Problem is as soon as it hits PI, PI does not perform a urldecode and it fails.
Has anybody else encounter this problem?
Regards
Naas

Hi
If I use the suggested method I get this message:
Servlet com.sap.aii.adapter.soap.web.MessageServlet (Version $Id: //tc/xpi.adapters/NW711_05_REL/src/_soap_application_web_module/webm/api/com/sap/aii/adapter/soap/web/MessageServlet.java#6 $) bound to /MessageServlet
Classname ModuleProcessor: null
Lookupname for localModuleProcessorLookupName: localejbs/ModuleProcessorBean
Lookupname for remoteModuleProcessorLookupName: null
ModuleProcessorClass not instantiated
ModuleProcessorLocal is Instance of $Proxy95
ModuleProcessorRemote not instantiated
I tried the following: (No party) where SI = Service Interface, BC = Buss. Comp and CC = Comm. Channel - all for the Sender.
http://myhost/XISOAPAdapter/MessageServlet?channel=:SI:BC
http://myhost/XISOAPAdapter/MessageServlet?channel=:BC:CC
http://myhost/XISOAPAdapter/MessageServlet?channel=:SI:CC
http://myhost/XISOAPAdapter/MessageServlet?channel=:CC:BC
Then I tried the suggestion in point 1 of the note.
https://dpi.buw.bu.edu/XISOAPAdapter/MessageServlet?senderParty=&senderService=BC_TEST_SENDER&interface=SI_TEST_OUTBOUND&receiverParty=&receiverService=BC_TEST_RECEIVER&interfaceNamespace=http://myhost/sap/kcrm
What am I missing?
Naas

RCVR_DETERMINATION MESSAGE_INCOMPLETE

Hi Gurus,
i am facing a problem with PI 7.0.
I try to call an Endpoint in the PI, which i got by "Web Service Definition" Wizard at the Configuration Runtime. The WSDL gives me the following endpoint
http://xitest:8000/sap/xi/engine?type=entry&version=3.0&Sender.Service=SOAP_EIP&Interface=http://test.de/ami^SmartMeterMeterReadingDocumentERPCreateConfirmation
The problem is that the PI does not interprets the Sendernamespace and Senderinterface (which is separated by the char ^ ).
In the SXI_MONITOR i see
Sender-Service = SOAP_EIP (korrekt)
Sender-Namespace = http://test.de/ami^SmartMeterMeterReadingDocumentERPCreateConfirmation
Sender-Interface = (initial)
Can you tell me why it can not separate the namespace from the interface?
This is not a error because of the &
Thank you in advance!

HI,
Try using Target URL as http://<hostname>:<port>/ XISOAPAdapter/MessageServlet? channel=
<party>:<service>:<channel> wihtout interface name and namespace. Its not mandatory you need to have both in the target URL.
regards,
Vineetha.

Error while testing the Webservice

HI,
When I Tried the Same It is showing an Error"Error in Sending the Soap Data"
When i teted the configuration it is showing an error in message interface,but is there and running fine when tested
Hi,
When I am Testing the same in the Altova,I am Getting an error as Below
"<SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
<SOAP:Body>
<SOAP:Fault>
<faultcode>SOAP:Server</faultcode>
<faultstring>System Error</faultstring>
<detail>
<s:SystemError xmlns:s="http://sap.com/xi/WebService/xi2.0">
<context/>
<code>RCVR_DETERMINATION.MESSAGE_INCOMPLETE</code>
<text>Message is incomplete. No Sender found</text>
</s:SystemError>
</detail>
</SOAP:Fault>
</SOAP:Body>
</SOAP:Envelope>
I Configured all the Required in Id and Tested the Design in the IR.
Thanks,
Srinivasa

Hi Srinivas,
Check these threads..
RCVR_DETERMINATION: MESSAGE_INCOMPLETE
BPM Message is incomplete. No Sender found
cheers,
Prashanth
P.S Please mark helpful answers

Getting error when testing Proxy to File interface

Hi Guru's,
While I am testing a Proxy to File Interface, using SPROXY transaction i am sending a message from R/3 to PI.
the message showing successful in R/3 Moni,but in PI moni I am getting the following Error..
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error SOAP:mustUnderstand="" 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>
In this inreface, I am suppose to send the mesasage to only one Target system(ftp server) . i have checked in ID part also,
every thing is clear in ID. Can any body please tell where the mistake might exists...
Thanks in advance..
Regards
Raj

Hi,
No receiver could be found means Check your Receiver Determination. Activate and update cache. Asysnchronous messages can be manually restarted.
have you seen this threads,
NO_RECEIVER_CASE_ASYNC
No receiver could be determined
regards,
ganesh.

RCVR_DETERMINATION

Similar Messages

Maybe you are looking for