Web Service to IDoc scenario: No receiver could be determined error

Hi. I am working on a web service to IDoc scenario. I am receiving this error:
<?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>
I've taken the XML message being sent to me and tested the mapping and I've completed the test configuration in the IB. Both work fine. Any ideas? I've been looking into this for a couple of days, so I've been through all the previous posts I could find.
Thank you.
Nicole

hi,
This is not related to receiverdetermination ,whether you creaeted or not.
It is somthing related to receiver systemwhich was configured in Receier determination.
check the target BS is correct or not or the inbound interface.
Did you configured the proper receiver technical system..
OR
Check the Receiver Determination is configured correctly. i.e R/3
Verify all the configurations like SM59, Partner Profile/Logical systems. etc. Also check in SM58 of R/3 system.Make sure that All the objects are activated in the Directory.Refresh the cache.Verify is the business system is pointing to correct R/3 system . Go to Business system/Service->Menu->Adapter specific identifiers in the directory
You can test your configuration with sample
payload.
In ID goto to TOOLS -
> Test Configuration for testing.
Hope in this way you can still find at which point the interface goes wrong.

Similar Messages

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?

No receiver could be determined - ERROR

Folks - I am getting this error - "No receiver could be determined" when testing using an SAP provided HTTP client for us. I have input the following parameters in the URL:
http://srvhousapdemo:8013/sap/xi/adapter_plain?namespace=http%3A//www.wellogix.com/PIDX_12/R3_46&interface=Z_PO_Create&service=XIS_eFT&QOS=BE&sap-user=bmills&sap-password=xxxxxxxx&sap-client=200&sap-language=EN
ServerHost - srvhousapdemo
ServerPort - 8013
Client - 200
SenderService - XIS_eFT
QOS - BE
SenderInterface - Z_PO_Create
SenderNamespace - http://www.wellogix.com/PIDX_12/R3_46
ServiceUser - xiappluser
Password - xxxxxxxx
Any pointers will be appreciated!
Thanks.
-Cal

Just to confirm...
You have the following entries in the configuration :-
1.Receiver Determination
Sender service - XIS_eFT
Sender Interface - Z_PO_Create
Sender Namespace - http://www.wellogix.com/PIDX_12/R3_46
Configured Receivers - <Receiving_Service>
2. Interface determination
Sender service - XIS_eFT
Sender Interface - Z_PO_Create
Sender Namespace - http://www.wellogix.com/PIDX_12/R3_46
Receiver Service - <Receiving Service>
Configured Inbound Interfaces - <Inbound_interface> / <Interface_Mapping>(may or maynot be there)...
3. Receiver Agreement
Sender service - XIS_eFT
Receiver Service - <Receiving Service>
Receiver Interface - <Inbound_interface>
Receiver Namespace - <Inbound_interface_Namespace>
Receiver Communication Channel - <reciever_comm_channel>

No receiver could be determined Error - PurchaseOrderChangeRequest_Out

Hi,
I am working on SRM to SUS communication. When a PO change request has been sent from SRM to SUS via PI, I am receiving 'No Receiver could be determined' eror. I checked Integration Builder and we are missing the mapping.
When I tried to do the mapping, I did not find the PurchaseOrderChangeRequest_Out interface in ESR. I tried to download ESR content from swdc. But not sure which content to download. Is there a way to find that out?
Thanks,
SG

Hi,
You can downloaded from marketplace.
Please check the below threads which guides you ...
Re: SRM to PI/XI Integration
SRM And XI Integration
Also, refer to below document.
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/601d4fee-719f-2910-4f86-fa030ab07358?QuickLink=index&overridelayout=true
Thanks and Regards,
Naveen.

Web service to IDOC scenario

Hi,
I'm defining Web service (through the configuration builder) and the message interface that i'm using to publish is based on idoc.
when i'm trying to check the WSDL which was generated, in the wsnavigator i'm getting the following error:
"cannot download WSDL from http://<server.....filename.wsdl: cannot load java.class: typename = /wsdl:definition/wsdl:types/xsd:schema/xsd:elemen/xsd:complexType, elementName=TEST_BASIC_TYPE
please advise,
Pavel Sheynkman.

I think you have used the proposed url which was mentioned in defining the webservice in configuration. better to use this link:
http://hostname:port/XISOAPAdapter/MessageServlet?channel=:<service>:<sender channel name>.in that url. you have to mention the hostname of the server and the port number.

No receiver could be determined error in AAE - File Adapter

Dear Friends,
We have PI 7.1, EHP1.
We are doing migration of our existing configuration scenarios into AAE.
While do testing the interfaces after migration, we face one issue.
In a File to SOAP scenario (Async), once the file is polled from the source directory and failed with the error 'No Receiver Determination' in the sender channel, the source file will not be moved to the archive directory. (Processing Mode : Archive).
Due to this problem, the source file is keep on polling with the intervals specified in the channel and failed. We see this error in Sender Communication Channel.
But, If the receiver is determined, this problem will not come. File is picked up, moved to the archive directory and processed successfully.
Friends, can you clarify how to solve this issue? (We tried with Processing Mode as 'Delete' , in that case also file is not deleted when error 'No Receiver determination')
Thanking you,
Kind Regards,
Jegathees P.

Hello Friends,
Thanks for your reply. For the testing purpose, I removed the condition to determine receiver, to force the message fail. Purpose is to test how AAE behaves for different errors.
My doubt is, in the classical method, for the same error, the file will be moved to the archive directory and further polling will not happen, we know that. In this new method, why the system did not move the file to archive directory though the error comes.
Kind Regards,
Jegathees P.

Detail steps in dealing with Web Service to IDoc

Dear All,
Iam dealing with Web Service to IDoc Scenario . I want detail steps like how to proceed from start to end of this scenario. Please do the needful.
Thanks & Regards,
Sarat

Hi Sarat
Just try these
/people/riyaz.sayyad/blog/2006/05/07/consuming-xi-web-services-using-web-dynpro-150-part-i
/people/riyaz.sayyad/blog/2006/05/08/consuming-xi-web-services-using-web-dynpro-150-part-ii
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/a068cf2f-0401-0010-2aa9-f5ae4b2096f9
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/f272165e-0401-0010-b4a1-e7eb8903501d
/people/shabarish.vijayakumar/blog/2006/03/23/rfc--xi--webservice--a-complete-walkthrough-part-1
/people/shabarish.vijayakumar/blog/2006/03/28/rfc--xi--webservice--a-complete-walkthrough-part-2
/people/siva.maranani/blog/2005/09/03/invoke-webservices-using-sapxi - Invoke Webservices using SAPXI
/people/siva.maranani/blog/2005/03/01/testing-xi-exposed-web-services
/people/michal.krawczyk2/blog/2005/03/29/configuring-the-sender-rfc-adapter--step-by-step
https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/2131 [original link is broken] [original link is broken] [original link is broken]
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/336365d3-0401-0010-9884-a651295aeaa9
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/336365d3-0401-0010-9884-a651295aeaa9
Reward points if useful

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.

IDoc (Sender ) to File (Receiver): No receiver could be determined

Hi, Dear Friends,
Im implementing scenario Idoc-to-File by means XI.
I try to follow this scenario:
Satish Jaiswal. A Step-by-Step Guide on IDoc-to-File Using Business Service in the XI Integration Directory
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/e07dcaa0-a92b-2a10-3a96-b3d942bd1539
But I have an error.
In sender system I send IDoc by transaction WE19. After that in transaction WE05 I see IDoc with status 03 (successful).
After that in XI system:
1) in transaction WE05 I don't see any IDoc (IDoc is not received by the Receiver (XI Integration Server))
2) in transaction SXMB_MONI I see my message with error.
Status - System error.
In detail view at stage "Receiver Identification" in item "Error" I see: "No receiver could be determined"
Unfortunately I'm not expert in IDoc.
Can you recommend me what I need to verify?
Or advice me link on another full good example with IDoc.
What I need to read for quick start in IDoc understanding.
Thank you in advance.
Natalia Maslova.

Try these steps:
ALE Settings
SAP XI
1) RFC Destination (SM59)
a) Choose create.
b) Specify the name of the RFC destination
c) Select connection type as 3 and save
d) In the technical settings tab enter the details SAP SID/URL and system number#.
e) Enter the Gateway host as same details above SID/URL.
f) Gateway service is 3300+system number#.
g) In the Logon /Security tab, enter the client user & Password details of Destination system.
h) Test the connection and remote logon.
2) Create Port (IDX1)
a) Select create new button
b) Enter the port name as SAP+SID (The starting char should be SAP)
c) Enter the destination client.
d) Enter the RFC Destination created in SAP XI towards other system.
e) Save
3) Load Meta Data for IDOC (IDX2)
a) Create new
b) IDOC Message Type
c) Enter port created in IDX1.
SAP R/3
1) RFC Destination (SM59)
a) Choose create.
b) Specify the name of the RFC destination
c) Select connection type as 3 and save
d) In the technical settings tab enter the details SAP SID/URL and system number#.
e) Enter the Gateway host as same details above SID/URL.
f) Gateway service is 3300+system number#.
g) In the Logon /Security tab, enter the client user & Password details of Destination system.
h) Test the connection and remote logon.
2) Create Port (We21)
a) First Select Transactional RFC and then click create button
b) Enter the destination port name as SAP+SID (The starting char should be SAP)
c) Enter the destination client.
d) Enter the RFC Destination created in SAP R/3 towards other system.
e) Save
3) Create Partner Profile (WE20)
a) Create New
b) Create the Partner no. name as same the logical system name of the destination system.
c) Select Partner type LS
d) Enter details for Type: US/USER, Agent, and Lang.
e) Click on the + button to select the message type.
f) Select Partner no. and LS which ever create above.
g) Select Message type
h) Select Process code related to the Message type.
I) save.
In SLD System Landscape Directory
TS for R/3 (Logical system):-Assign the client name created in R/3 as Logical system Name.
Ts for Third Party (Logical system):-
BS for SAP R/3 (Logical system):- Assign the client name created in R/3 as Logical system Name.
BS for Third Party (Logical system):-Enter the XI logical system name.
In Transaction SALE
Define and Assign the logical system name.
Message was edited by:
Raghavesh Reddy
null

File Service to IDOC Scenario

HI ,
I am trying file service to IDOC scenario and iam getting following error "Unable to convert sender service FilesService_FILE2IDOC to an ALE logical system".
Here file has to be read and IDOC has to be posted in SAP system. Sender is not an SAP system / 3rd Party system ...itz an FILE sender service.
Settings i have done:
In Message Mapping in target IDOC structure i have disabled Control record
In integration directory IDOC Receiver Communication channel i have not selected "Apply Control Record values from Payload".
In receiver determination in header mapping i have put sender sevice "FilesService_FILE2IDOC ".
But still i receive the same error.
I do not want to send control record parameters in Message Mapping .
Pls throw some light on this ....
Regards
Sri

Hi Sridhar,
Regarding your error, below is the answer...
When you create the business system (in the SLD) you assign a "logical system name" or "ALE name". That is used as the ALE name for transporting IDOCs, and the sender system.
You have to also maintain this name in the R/3 System (tx. SALE, WE20), because IDOC will be noted as arriving from that system.
You also told that you dont want to pass the control records value....Do this, just deactivate the control records segments in your message mapping... let me not explain it further.... just check these blogs below for the same,
/people/sravya.talanki2/blog/2005/12/02/manipulating-idoc-control-records-from-payload
/people/michal.krawczyk2/blog/2005/09/01/xi-idoc-adapter--edidc40--demystified
And also go thru the following links to get a better idea about partner profile:
http://help.sap.com/saphelp_nw04/helpdata/en/dc/6b833243d711d1893e0000e8323c4f/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/dc/6b7cd343d711d1893e0000e8323c4f/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/32/692037b1f10709e10000009b38f839/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/5e/b8f8bf356dc84096e4fedc2cd71426/frameset.htm
I hope this helps you solve your problem.
Regards,
Abhy

Web Service to FTP scenario - MAPPING.NO_MAPPINGPROGRAM_FOUND error

Hi,
I am developing a Web Service to FTP scenario in XI, I am testing the interface by writing a client program using AXIS. when I invoke the service from the client, it is able to hit the service and writing the file to FTP with the data However the client is program receiving a fault with the below error.
"SystemError:<context/><code>MAPPING.NO_MAPPINGPROGRAM_FOUND</code><text>Unable to determine name of mapping program</text>"
I set quality of service to 'Exactly Once' on the SOAP sender adapter.
Would appreciate any help on this.

Hi,
What is the URL to which you are posting the SOAP message?
Is it?
http://<host>:<j2ee-port>/XISOAPAdapter/MessageServlet? channel=<party>:<service>:<channel>
If yes, then like mentioned the QOS is picked from the Sender SOAP adapter.
But, if the URL is ,
http://<server>:<ABAP-port>/sap/xi/engine?type=entry&version=3.0&Sender.Service=<YourService>&Interface=<YourNamespace>%5E<YourInterface>
Then you need to give the QOS as ,&QualityOfService=ExactlyOnce appended to the above URL.
More, /people/stefan.grube/blog/2006/09/21/using-the-soap-inbound-channel-of-the-integration-engine
Regards
Bhavesh

IDOC 2 XI: No receiver could be determined

Hello,
I am glad to send a IDoc to XI!
In IDX5 I got the error:
No receiver could be determined
Many questions:
I wonder there is a "Sender Agengy": bss_lp_idoc an
a "Sender service" bss_lp_idoc
1) Are the names for "Sender Agengy" and "Sender service" generated by the system?
2) What do I have to do to determine a receiver?
additional information:
IDOC has MESTYP = SYIDOC
IDOC has IDOCTYP = SYIDOC01.
IDOC-RCVPRT = LS
Thanks a lot!
Regards Mario

Hi Vishnu,
thank you much.
I know this document. But unfortunately that does not help me.
I got also several documents about sending IDOC to the XI.
But in all documents there are relevant things missing. So I try now to to this step by step by myself.
The first thing I have to know is:
How does the IE try to determine the receiver? Which fields in the origin IDoc are read? What does the XI do next after reading the relevant fields in the IDOC?
Thanks

No receiver could be determined in Proxy----File Scenario

Hi All,
Iam doing Proxy---File scenario
Every thing i got success in SAP R/3 side MONI
I got this Error in XI side MONI as No receiver could be determined
I check the Sender Service in MONI--- SOAP Header ---Main( Both R/3 side & XI side also)
Here it is showing like sapdev as my sender service, but actually my sender Business system is Sub_Dev_ssd.
How to get it rectify
Regards
Vamsi

Hi Chirag & Santosh,
As i said the problem is when i check in XI side MONI
The sender service is showing sapdev BUT it shld be Sub_Dev_SSD which i have selected in the Receiver Determination Step also.
The same is showing in the SAP R/3 side MONI also
According to my understanding , The Correct Business system which is there in the SLD & which i want to use is not Picking in the SAP R/3 side and so thats why iam getting the Service as sapdev & the same sapdev Service is passing to XI also
I think the Business system from the SLD is Not comming into picture.
What to do for this??
Regards
Vamsi

Web Service u0096 IDOC with acknowledgement interface

hi experts,
for this scenario do i need to use ccBPM??
Web Service IDOC with acknowledgement interface.
because we need response from idoc and idoc supports asynchronous processing.

hi,
yes you need to use a BPM if you want to use
acknowledgment to a web service from IDOC interface
more on IDOC can be found in my book:
<a href="/people/michal.krawczyk2/blog/2006/10/11/xi-new-book-mastering-idoc-business-scenarios-with-sap-xi">Mastering IDoc Business Scenarios with SAP XI</a>
Regards,
michal
<a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions">XI / PI FAQ - Frequently Asked Questions</a>

No receiver could be determined. (File to Idoc)

Hi,
I am getting below error for my file to idoc scenario.
Receiver determintation: NO_RECEIVER_CASE_ASYNC
Any inputs appreciated.
Thanks
Balaji

Hi,
Now my error message is changed to following:
<?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>XIAdapter</SAP:Category>
<SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_BE_NOT_SUPP</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Only asynchronous processing supported for IDoc adapter outbound processg</SAP:Stack>
<SAP:Retry>N</SAP:Retry>
</SAP:Error>
I have mentioned it as asynchronous in message interface. howcome i am getting this error message?
Thanks
Balaji

Web Service to IDoc scenario: No receiver could be determined error

Similar Messages

Maybe you are looking for