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.

Similar Messages

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

Error when testing a web service created in XI

Hi experts,
I created a web service in XI to execute a RFC and return its result, but when the WSDL file is tested in XMLSpy, the below error is returned:
<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></context>
 <code>RCVR_DETERMINATION.MESSAGE_INCOMPLETE</code>
 <text>Message is incomplete. No Sender found</text>
 </s:SystemError>
 </detail>
 </SOAP:Fault>
 </SOAP:Body>
</SOAP:Envelope>
It's the first time I use XI, so I've no idea of which extra details I should provide to give a better description of my problem.
Thanks in advance,
André Ramos Souza

Souza,
If you see the message
<code>RCVR_DETERMINATION.MESSAGE_INCOMPLETE</code>
<text>Message is incomplete. No Sender found</text>
It is complaining baout recceiver determination incomplete or no sender agreement. So please check all your ID objects once again.
---Satish

Pl find the error in ws to file scenario

all the information in IR and Id is given .
<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>

>>Anything else I should look into
Look into the Reciever Determination object.
Check these details in SXMB_MONI
1. SenderService
2. Sender Interface
3. Sender Name space
There should be a mismatch between these details in SXMB_MONI and your Reciver Determination in ID.
Regards,
Jai Shankar

Configuring Sender SOAP Adapter

Hi, I am trying a simple scenario that worked well in XI 2.0 and I am trying to migrate the same scenario to XI 3.0 where I am having problems.
1. Created two data types: material_in that takes a material; material out that have three simple elements (description, type, and group).
2. Created two message types one for the inbound and other for the outbound
3. Created a message interface linking the outbound and inbound messages type outbound and synchronous.
4. Created all the mappings necessary that maps the material to a RFC-enabled Function module and the output of the function module is mapped to out message.
5. Then created the configuration part (Integration builder - configuration ) using configuration wizard.
6. The communication channel for the sender Business systems is SOAP where the default interface parameters have been provided
7. The communication channel for the receiving business systems is RFC.
The configuration wizard has created all the necessary steps including receiver determination, interface determination, sender and receiver agreement.
I activated all the components. Then using 'Define Web Service', created a WSDL file. I have imported this WSDL file into XMLSPY to test it out.
This is where I am hitting the wall.
When I tried using http://host:javaport/XISOAPAdapter/MessageServlet?channel=
URL, I am getting a http post error (500).
Then, I tried posting to http://host:port/sap/xi/engine?type=entry. This creates an XML message in the XI but comes back with an error 'RCVR_DETERMINATION.MESSAGE_INCOMPLETE'.
Any thoughts from your side is greatly appreciated.
Thanks, Ram Rayavarapu

Hi Ram,
sounds all ok, any more information on the 500?
The http://host:javaport/XISOAPAdapter/MessageServlet?channel=party:service:channel
is the right URL for XI 3.0 not the XI 2.0 one.
I guess you provides a valid user id and password to XMLSPY
when it asked for it and that user has enough rights to do XI work.
Did you try to enter the URL into a web browser? It should ask you for you user and password too and brings up a response of Message Servlet ok. If that does not show up then do you have a proxy on your network which might prevent you from hitting the XI server?
Cheers
Stefan

Synch. RFC call error - No Sender Found

Hi,
once execute the synchronous RFC call from BPM, rfc response message returns as following;
<SAP:Code area="RCVR_DETERMINATION">MESSAGE_INCOMPLETE</SAP:Code>
<SAP:Stack>Message is incomplete. No Sender found</SAP:Stack>
i've tried adding header mappings at receiver aggreement for bpm's name as sender service and target sap system name as receiver service. Same error.
Any help is greatly appreciated. Thanks

Hi,
>>>>i've tried adding header mappings at receiver aggreement for bpm's name as sender service and target sap system name as receiver service. Same error.
no need for any header mapping in that case
just configure the routing correctly - via directory wizard
and everything will work
Regards,
michal
<a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions">XI / PI FAQ - Frequently Asked Questions</a>

Message is incomplete. No Sender found

Hi everyone,
I made an Idoc outbound from SAP to JMS xml file delivery but now this error is appearing:
<?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">MESSAGE_INCOMPLETE</SAP:Code>
<SAP:P1>Sender</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:Stack>Message is incomplete. No Sender found</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
I'm receiving my Idoc into a BPM and transform it into an external definition file type and deliver it to the JMS receiver.
Any thoughts of what may be the cause?
Thanks

Hi,
Could you resolve this problem. I am facing the same problem. We are running SP19 on XI
I have a BPM. These are the steps.
1) BPM Receives the INVOIC idocs and collects them for 1 Minute
2) BPM transforms the idocs into file and RFC msg
3) BPM sends the file
4) BPM sends the RFC msg
in SXMB_MONI, The BPM is completed, but the 2 send steps from the BPM are in Error Status. The error message is as follows:
<SAP:Code area="RCVR_DETERMINATION">MESSAGE_INCOMPLETE</SAP:Code>
<SAP:P1>Sender</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Message is incomplete. No Sender found</SAP:Stack>
Any help to resolve this issue is appreciated.
Thanks
Vidya

BPM Message is incomplete. No Sender found

Hi,
i am not strong in using BPM, i have searched related to this error on sdn, but still not find.
bpm step
receive1, receive2 in fork in block, out of block transformation and then send step.
receiver determination
BSFILE01 -> BPM (no map)
BSFILE02 -> BPM (no map)
BPM -> BSFILE03 (map2)
i made two mapping in IR,
map1 : N -> 1.
BSFILE01 and BSFILE02 TO ABS(1)
map2 : ABS(1) TO BSFILE03
configuration time does not use map1,
bpm was received two receive in fork as well and then
my XI 3.0 sp info is SP15
error message on moni , but no error on PE, everything green.
<?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">MESSAGE_INCOMPLETE</SAP:Code>
<SAP:P1>Sender</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Message is incomplete. No Sender found</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
thanks
venjamin
Message was edited by: venjamin
Message was edited by: venjamin
Message was edited by: venjamin

Hi,
Are you trying to collect 2 different files into a single file or multiple same files into a single file?
If you are trying the former, which I think you are doing as you are using a fork with coreelation to collect the 2 files, you need to have a mapping step which will combine these 2 files into a single file ( N:1 ) mapping and , there is no need for a multiline container element as, both the files are of different message types.
Is this what you are tyring?
Regards,
Bhavesh

Bypass Adapter URI Endpoint with Escape Character for Web Service

Dear All,
I would like to apply by pass adapter URI Endpoint for XI webservice, the default format is
http://<host>:<port>/sap/xi/engine?type=entry&version=3.0&Sender.Service=<BusinessService>&Interface=<namespace>^<Outbound Interface name>
If I am using format using with carat () character then there has no problem to the service, but consumer doesn't support carat () character. I instead the carat (^) with URL Escape Character (%5E)
http://<host>:<port>/sap/xi/engine?type=entry&version=3.0&Sender.Service=<BusinessService>&Interface=<namespace>%5E<Outbound Interface name>
Then error occurred
<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>
How to resolve this error...
Thank you.
Regards,
Weng

Hi ,
as per my knowledge.....................
When you create a WSDL with the help of a wizard. In the Integration Directory, choose Tools -> Define Web Service to enter the wizard.
On Propose URL button, as this genertated URL default Point to Entegration Engine.. SO already proformance wise Good.
If You want to Point your URL to adapter engine , use below given URL this will point ur incoming soap message to SOAPadapter sender channel
http://<host>:<j2ee-port>/XISOAPAdapter/MessageServlet?channel=:<service>:<channel>.
Regards
Prabhat Sharma.

Testing Webservices in XI with XML Spy

Hi ,
 I am trying to define a Webservice in XI from the ID by going to Tools -> Define Webservice( the usual way ) and I got the WSDL.I am trying to use the same from XML Spy to send SOAP messages to XI.But there is something wrong in the link generated.Does somebody has a prior exp or idea about what needs to be done exactly to get it running.
Regards,
Sudip.

Hi Bhavesh,
 I was trying the second option to send it to the integration server directly. But the error which I get it as follows
<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>
But this is a working scenario.
link which is generated is as follows
http://bsw6220:51000/sap/xi/engine?type=entry&version=3.0&Sender.Party=http%3A%2F%2Fsap.com%2Fxi%2FXI%3AXIParty%3AAttachmentAdapter&Sender.Service=LockBoxFileCreationAtProvider&Interface=http%3A%2F%2Fsap.com%2Fxi%2FAP%2FGlobalization%5EUS_BAI2_IN_INTERFACE
Any idea what went wrong?
Regards,
Sudip.

SOAP sender endpoint problem

Hi all,
I'm now fighting for quite a time with a SOAP sender channel.
I generated a WSDL in the configuration. I used this wsdl in XMLSPY in order to send a request to XI.
And I must confess that I'm totally confused with the URLs. Which one do I need to take (we're using XI 3.0):
http://server:3400/sap/xi/engine?type=entry&version=3.0&Sender.Service=service&Sender.Interface=urnInterface
or
http://server:50000/XISOAPAdapter/MessageServlet?channel=party:service:channel
What is the difference between those URLs?
And for the Java URL (port 50000): Which channel do I have to announce? The Name of the SOAP sender communication channel?
Since XI proposes the url with 3400 port I think this one is appropriate. But whenever I use it I receive a RCVR_DETERMINATION.MESSAGE_INCOMPLETE error and the message is indicated in the monitoring as coming from "AnonymousClient". What do I do wrong? I also tried to force the SOAP adapter to use the parameters by checking the option "Use Query String" in the channel config.
Please help!
Thanks in advance.

Hi Frank,
thank you for your answer.
I added the default XI parameters.
Concerning the userID and Password: I am asked to enter login/pwd if I call the service. Is this what you mean?
Unfortunately this does not affect anything...
The response I get is the following:
<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/>
</s:SystemError>
</detail>
</SOAP:Fault>
</SOAP:Body>
</SOAP:Envelope>
What amases me is that the ns is http://sap.com/xi/WebService/xi2.0. I used the url including the part &version=3.0
Does this url work for you (I mean including the version)
Could the error also be related with other configuration errors (wrong receiver agreement) - I do'nt thnik so but sth goes definetively wrong.
Greets,
Joachim

Error while using Webservice.

Hi All,
we have one scenario SOAP to RFC ,where 3rd party using WEbservice to send the data using SOAP adapter to PI .
But now when 3rd party trying to send the data through websevice they are getting error message ' javax.xml.ws.soap.SOAPFaultException: Server Error' and message not reached to PI .
When I tried from my end from Altova XML SPY i m getting following error .
<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>
Any idea where will be error present.
any little help towards solving the issue will be very helpful.

Hi,
the SOAP sender channel can be addressed with:
http://host:port/XISOAPAdapter/MessageServlet?channel=party:service:channel
See as well [Configuring the Sender SOAP Adapter|http://help.sap.com/saphelp_nw2004s/helpdata/en/fc/5ad93f130f9215e10000000a155106/frameset.htm]
Obviously the "sender" is missing. Please check your wsdl for that and recreate it.
Regards,
Udo

Error Checking WSDL

Hi every one.
I´ve publicated an WSDL so a Third Party can cosume it.
I tried to check if the WSDL file is correct by using ALTOVA XMLSPY
( based on this link: https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/7ccd3e4e-0501-0010-95ae-afa58cb46b75 )
In XMLSPY I see that my file is valid, then I created a New SOAP Request, but when I try to Send it to the Server it returns the following message:
code>RCVR_DETERMINATION.MESSAGE_INCOMPLETE
Can someone give me some light about this??
Thanks in advanced.

Hi karla
refre this Links for your Error RCVR_DETERMINATION.MESSAGE_INCOMPLETE
Re: SOAP sender endpoint problem
SOAP sender endpoint problem
Configuring Sender SOAP Adapter
Regards
Abhishek

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

RCVR_DETERMINATION MESSAGE_INCOMPLETE

Similar Messages

Maybe you are looking for