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
<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>
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
reward points if it is helpful..

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

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>

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

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

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.

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

Consume a Web Service: No receiver could be determined

Hello,
I have a successful running Web Service on a JAVA stack. Now I want to consume this web service within the ABAP Stack. For this purpose I generated the appropriate proxy object from the WSDL.
However, while running my ABAP test program I am receiving an error: RCVR_DETERMINATION.NO_RECEIVER_CASE_BE No receiver could be determined
Does anybody know, what to do? Do I need to register the generated proxy somewhere? Or what went wrong?
Best Regards!

you dont need to do any settings in LPCONFIG
just create client proxy and activate the proxy class
then in LPCONFIG
enter the client proxy name and port name (port name can be any text) and check the checkbox "default" and click create and activate the same.
now you are ready to consume the webservice.
Regards
Raja
assigning points to helpful answers by choosing the appropriate radiobuttons in the answers in the SDN way of saying thanks.

Client Proxy to JDBC synchronous Scenario

I'm using Proxy--PI---JDBC synchronous shcenario, when i execute the proxy from R/3 it is giving me error "RCVR_DETERMINATION.NO_RECEIVER_CASE_BE" in configuration i have used one inbound receiver determination for request, my question is do i need to have one more reciever determination for response.
Thanks for help.

No, you do not have to add additional receiver determination
Usually in sync scenario, make sure you have one receiver determination, no arbitration.
If you have condition for receiver detemination, make sure the condition only return one true.
Liang

HTTP Sender - Sync

Hi all,
I have configured the following scenario:
Form a jsp Web page I create a Purchase Order in a R3 SAP system calling a BAPI.
I've created Asynchronously and it works. Next step I've tried is convert the scenario in a synchronous scenario, in order to see the BAPI result in the jsp page.
I've configured all steps and I find the followin error
"RCVR_DETERMINATION">NO_RECEIVER_CASE_BE
I've tried to refresh all cache as said in
RCVR_DETERMINATION">NO_RECEIVER_CASE_BE
but nothing...
I'ver also tried deleting and re-activating all objects in Directory...
Any idea?
Regards.
Urtzi.
Message was edited by: Urtzi Barandiaran Aguirre

Hi,
When you made the change from the Asynch to a Synch Scenario, did you change the outbound message interface to a Synch message Interface?
Did you create 2 mappings, one for reequest and one for response and used that in the interface mapping between the synch message interfaces?
Also, did you set the QOS to BEST EFFORT when making the call from the JSP page and finally, are all the parameters in the call from the JSP page like message interface , namespace etc correct?
Regards,
Bhavesh

SAP GRC ERROR - NO_RECEIVER_CASE_BE

Hi All, I'm try implemented GRC and get this error (SXMB_MONI):
<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>
My receiver determination with the following values:
Service - GRC_NFE_CORE_70 (name of my BSystem)
Interface - SRVSC_nfeStatusServicoNF_SYNC_OB
Namespace - http://sap.com/xi/NFE/005a
Configured receivers
Service - SEFAZ_GO_HOMOLOG (name of my BService created)
Condition - (/ p1: nfeStatusServicoNF/p1: CUF = GO)
This error changes when configured to remove the condition receivers, this condition: Condition = (/ p1: nfeStatusServicoNF/p1: CUF = GO)
New Error:
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>XIAdapterFramework</SAP:Category>
<SAP:Code area="MESSAGE">GENERAL</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText>com.sap.aii.af.ra.ms.api.DeliveryException: unable to create a socket</SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack />
<SAP:Retry>M</SAP:Retry>
Anybody help-me??
Thanks.
HMattos.

Venkat,
I make cache refresh full using the user PIDIRUSER, see result bellow:
CPA cache refresh (mode=full) successfully executed in 7077 milliseconds.
But the error persist..
Other sugestion?
Regards,
HMattos.

NO_RECEIVER_CASE_BE - No receiver could be determined error

Hi Experts,
Scenario: SOAP to JDBC BPM Scenario
Error: When I tried to execute the scenario, I am getting the below error. The interface mentioned in Integration Directory and SXMB_MONI are different. Where to do the correction?
Note :Refreshed the cache in SXI_CACHE and Administrator screen. I couldn't see the Integration Process in SXI_CACHE
<?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="1">
<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>
Regards
Sara

What was the resolution?

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 in Ws to File Scenario

Hi,
The Below error is displayed when executiong the proxy.
<?xml version="1.0" encoding="utf-8" ?>
- <asx:abap xmlns:asx="http://www.sap.com/abapxml" version="1.0">
- <asx:values>
<SYSTEMFAULT href="#o239" />
</asx:values>
- <asx:heap xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:abap="http://www.sap.com/abapxml/types/built-in" xmlns:cls="http://www.sap.com/abapxml/classes/global" xmlns:dic="http://www.sap.com/abapxml/types/dictionary">
- <cls:CX_AI_SYSTEM_FAULT id="o239">
- <CX_ROOT>
<TEXTID>F63AFF63DBE4BB4786A7F52CC4167145</TEXTID>
<PREVIOUS />
<KERNEL_ERRID />
- <INTERNAL_SOURCE_POS>
<PROGID>97</PROGID>
<CONTID>3413</CONTID>
</INTERNAL_SOURCE_POS>
</CX_ROOT>
<CX_STATIC_CHECK />
- <CX_AI_SYSTEM_FAULT>
<CODECONTEXT />
<CODE>RCVR_DETERMINATION.NO_RECEIVER_CASE_BE</CODE>
<ERRORTEXT>No receiver could be determined</ERRORTEXT>
<LANGUAGE />
</CX_AI_SYSTEM_FAULT>
</cls:CX_AI_SYSTEM_FAULT>
</asx:heap>
</asx:abap>
I am using the Webservice URL:http://www.webservicex.net/CurrencyConvertor.asmx?wsdl.
Senderinterfacename:CurrencyConvertorSoap_out
SenderinterfacenameSpace:http://www.webserviceX.NET/
I am calling the above url (CurrencyConvertorSoap->http://www.webserviceX.NET/) by creating Proxy.
Up on executing the same ,I am Getting the above error as pasted.
Pl look in to it and let me know the solution.
Thanks,
Srinivasa

Hi Srini,
 Can you explain detail?
 How you used ws to file with proxy..
 I thing your creating outbound proxy.In that your calling the URL and passed some value and get the
 response back. You passed that response to XI.If that may right then there is no need for sender
 communication chennal and Sender Agreement.Create a Receiver Determination with your Business
 system Select your message interface.
Regards,
Prakasu

XI 3.0 SP14 Synchronous SOAP- XI- ABAP Proxy - fails with "System Error"

Hi All,
The synchronous response message fails at the stage "Receiver Identification".
It seems that the synchronous response XML has no "sender" attribute, so obviously the receiver determination fails.
In the message monitor I can see the correct payload coming from the ABAP proxy, so that part looks OK.
I have the same scenario working perfectly on another system landscape, so there might be a configuration side to it.
Thanks is advance,
Ofer
Message was edited by: Ofer Even-Tsur

Hi,
for the error information SAP:Code area="RCVR_DETERMINATION">NO_RECEIVER_CASE_BE</SAP:Code>
looks like xi is not able to find a reciever of best case. Open up the scenario in COnfiguration, open up the modify(add spaces) and activate reciever determination / reciever communication channel.
cheers,
naveen

Error:RCVR_DETERMINATION" NO_RECEIVER_CASE_BE

Similar Messages

Maybe you are looking for