File to RFC to File error "No receiver could be determined"

Hi everybody.
I have a errors in BPM ...
<?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_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 where i enter in transaction SXMB_MONI_BPE -> Continue Processes Folowing Errors, entered in my item and choose "Send Message Synchronously" appear window "Display work item" in this "Work item information" line Status=Error press button "i Message" appear following message:
No exception defined for fault message
INTERNAL_ERROR INTERNAL_ERROR
Help me what do now?
Anvar.

Hi,
I've browse through your error document and everything seems to be ok. In the menu is this full cache refresh. Remember also to activate all objects in integration directory
Regards,
Wojciech

Similar Messages

System Error: No receiver could be determined

Hi,
When i logged into the portal and click on Time management link which takes you to the time entry application (HRESS_C_CATS),and the below mentioned message is displayed. "System Error: No receiver could be determined ".
Could you pls let me know why this error shown.? This error appeared when a functional guy changed the employee profile.
Any idea how to solve this error?
Thanks,
Lakshmi.
Edited by: Lakshmi Atukury on Feb 13, 2012 7:30 AM

Check siddarth reply in below thread
http://forums.sdn.sap.com/thread.jspa?threadID=2135503
Regards
Srinivas

Error:No receiver could be determined

Hi Experts,
While monitoring XML messages, I am getting one error "No receiver could be determined" for sender interface catalogupdatenotification_out. Please let me know how i can maintain receiver for this interface. I am SRM consultant and know very little about PI and we are not having any PI consultant this month.
Thanks for your help.
Regards,
Raj Saini

Hi Raju
As you are new go through the below link to understand a simple XI Scenario
http://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/1345
specific to your error , you need to check why there are no receivers for the inteface , either there are filter conditions in Receiver determination which are not satisfied or your configuration scenario is cofigured in appropiratly ,refer above blogs and try to configure correctly,
Also for your reference , you can find a lot of information in the bleow link (may be its lot of information for you at this stage)
http://wiki.sdn.sap.com/wiki/display/XI/PI7.0and7.1Mapping-Blogs%2CArticles%2CWiki%2CCodeSamplesandVideos+Collections
Regards
$rinvias

Acknowledgment error : "No receiver could be determined" !?

HI,
This is my flow :
SAP R/3 sends idoc to a third party through XI. This idoc must be changed in flat file type CSV. This flow works fine but there is a problem in the acknowledgement : "No receiver could be determined".
What is the problem ?
Error :
<SAP:ReliableMessaging xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SystemAckRequested="false" SystemErrorAckRequested="true" ApplicationAckRequested="true" ApplicationErrorAckRequested="true" SOAP:mustUnderstand="1">
 <SAP:QualityOfService>ExactlyOnce</SAP:QualityOfService>
</SAP:ReliableMessaging>
<SAP:Diagnostic xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
 <SAP:TraceLevel>Information</SAP:TraceLevel>
 <SAP:Logging>Off</SAP:Logging>
</SAP:Diagnostic>
<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:Error>
Thanks.
Best regards

Sorry but this error desapear. With have a new error : ATTRIBUTE_INV_SND_SERV
We use mapping conversion and CSV file channel.
Thanks

Error No receiver could be determined in PI71

hello Expert,
i am testing a sample scenario with proxy->xi->file
application BC6, xi server PI71
configuration test is okey.
i used the BC(BS_File) is as the sender and receiver
but after run, the sender name in the record in sxmb_moni is changed BS_EC6.
i never used the bs_ec6 as sender.
so a error with 'no receiver could be determined ' happened
who could tell me why
the sender must be a Businees System?
Best Regards,
Kevin
Edited by: Kevin Gao on Dec 19, 2008 10:00 PM

Sender system must be business system for proxy scenario

Error while process the CPPR-Rfx "No receiver could be determined"

Hi Experts,
We are working on SRM 7.0 Extended Classic Scenario, While testing the CPPR-Rfx process we are getting the error msg in Portal
"No receiver could be determined".
We implemented Badi ME_REQ_SOURCING_CUST & BBP_EBPXML_OUT_BADI
We are getting this ERROR " No receiver could be determined" While clicking the "CREATE RFX" with reference to Purchase Requisition through Hormonized roles.
Pl suggest what could be the problem.
Regards,
Mohan

Check if below settinjgs are in place:
Parameter CV_EXT_RFX_IND is set to true in ME_REQ_SOURCING_CUST to create RFX.
Business functions are activated in backend ECC system.
In backend system Event type linkage is activated for receiver WS53800009, event RFXREQUESTED and BO BUS2105
In Backend system Activate outbound messages for events RFCREQUESTED for object type BUS2105.
RFC user used in PI system is assigned to Purch org in SRM org structure.
Maintain the service call RFQRequestSUITERequest_In in XI/PI.
Maintain transac type for RFx in SRM.
Do you see any entries in XI monitor and queues?
Thanks,
Jagadish

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>

BPM sync to jdbc produces No receiver could be determined

Hi,
I am sending a sync select statement from BPM to JDBC adapter but I get the following error: No receiver could be determined.
I checked in MONI and I can see the select statement, even the response but I get this error. I looked at the graphical workflow log and every step "executes successfuly" but in the XML messages list I have 3 messages, 2 with the successful flag and one with a red flag, the red flag displays this error.
Since both interfaces, the BPM abtract interface and the inbound interface for the JDBC adapter are BOTH SYNC, shouldn the response message arrive back at the BPM automatically ? or must I define another reciever determination ?
Cheers.

Hi,
How have you used the send step? In this case it should be used with sync mode.
Selcet the mode property of "send" step as synchronous. Then you will have to give two message types one for request and the other for response.
After this send step you can have a normal send step and you can use this to send response wherever you need.
Regards,
P.Venkat

BPM "No receiver could be determined"

Hi everybody...
What i do for
<?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_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>
Message was edited by:
 Anvar Palvanov

Hi everybody...
I am open transaction SXMB_MONI_BPE -> Diagnosis Processes with Errors
ID Type Work item text CreateDate CreateTime
Misc
19 F Doc_RFC_BPM http://sap.com/xi/XI/Demo/F 01.12.2006 17:47:09
 in errors
No receiver could be determined
Work item 000000000021: Object CL_SWF_XI_MSG_BROKER method SEND_SYNCHRON cannot be executed
No exception defined for fault message INTERNAL_ERROR INTERNAL_ERROR
Error handling for work item 000000000021
No exception defined for fault message INTERNAL_ERROR INTERNAL_ERROR
Anvar.

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.

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 To RFC To File

Hi All,
I am trying to do File To RFC To File using BPM.
I am following the given link.
http://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/1926. [original link is broken] [original link is broken]
I did exactly same .But it is showing error as "RED" in the workflow as I checked it in sxmb_moni.
I am very new to BPM.
Can anyone please help me solve this.
Thanks
Rabi

Hi All,
Thanks to you.
My problem is solved now.
I checked by using tcode SXMB_MONI_BPE which is showing error as "Object CL_SWF_XI_MSG_BROKER method SEND_SYNCHRON cannot be executed".
"No handler defined for this system exception".
So I checked all channels in RWB.
Problem was in my receiver RFC channel configuration.
I corrected it and it is solved.
Thanks
Rabi

File to Rfc to File in pi7.1

Hiii,,
Iam trying file to rfc to file scenario...when iam montoring sender commuication channel it shows below mentioned error...wat may the issue..help me out
"Delivering the message to the application using connection RFC_http://sap.com/xi/XI/System failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException: com.sap.aii.af.service.administration.api.cpa.CPAChannelStoppedException: Channel stopped by administrative task.. Setting message to status failed"
With Regards..
Dinesh

Hi,
I checked the namespace its rite...whether i have to check the same namespace in sap system...if yes, where to find it..
I guess your File CC configuration is not correct. Namespace will be your source interface namespace in PI. This is a very basic question and should be searched on SDN / SAP Help before posting here.
Go through this SAP Help ...
http://help.sap.com/saphelp_nw04/Helpdata/EN/e3/94007075cae04f930cc4c034e411e1/content.htm
Regards,
Neetesh

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

SAP PI7.1 File to RFC to File

Hiiii,,,
i have doubt in mapping related to file to rfc to file scenario...
i have a source message type i have two field name ( 1.field_name 2.table_name)...i have to map this two fields to RFC_READ_TABLE function module to the field query_table and field_name...how to map this...
With Regards.....
Dinesh

Hi Dinesh,
i have one data type in source with two fields (1.table_name 2.field_name).
.i mapped this to target RFC_READ_TABLE to the parameter query_table and fielname in that function module
Please let us know if you have any mapping rules for creating the mapping, i mean
what are you trying to fetch from the RFC, what are the values you are sending and
what you want in response.
Its based on your requirement and you need to decide which field is to be mapped
to RFC structure.If you are getting error while testing , please let us know.
Also ensure that your RFC Function module is working when tested in sap system.
Go to Se37 and enter your Fn module name and test with the valid inputs.
check if its outputting the desired values.
Regards,
Srinivas

File to RFC to File error "No receiver could be determined"

Similar Messages

Maybe you are looking for