No reciever could be determined in BPM scenario

Dear Friends,
I am working on BPM scenario i.e sending the delivery idoc from one ECC to another ECC using XI,In XI side after one hour it has to be updated, for this scenario I am uisng Recieve-wait-send step types are using.
I have done all the steps but in SXMB_MONI iam getting this error
i.e No reciever could be determined and Error in Back routing and Error in Communication channel.
Please tell me the what are steps required extra.
Regards,
Shalini Shah.

Hi Shanlini,
Kindly find the below threads solved many times with same issue:
Re: No receiver could be determined
Re: No Receiver Could be determined
Re: No receiver could be determined
Reciever idoc adapter Determination error
Regards
Venkata Rao .G

Similar Messages

Reciever Determination: No reciever could be determined in SXMB_MONI

Reciever Determination: No reciever could be determined
Hello people,
When I tried transfering PO to supplier this error happened in XPP system.
Don't know how to solve this.
Is this a problem with the supplier.
Please give a solution.

Hello Deepak,
You getting error in XI system right while executing SXMB_MONI? If that is the case it looks like issue with XML mapping and determining supplier information from the xml message.
Please check your xml schema mapping you should able to identify issue.
Thank you
Ritesh

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

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

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 Determined" in BPM Sync RFC Call

My scenario is xml file -> XI BPM -> RFC1 -> RFC2 (will call RFC2 if RFC1 is successful).
I am still just trying to get the RFC1 call working properly. I have been using blogs 1822, 1403 and 1926. I have also used some related BPM threads. It seems to be making the RFC call properly, but failing on the response.
<SAP:Code area="RCVR_DETERMINATION">NO_RECEIVER_CASE_BE
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>No receiver could be determined</SAP:Stack>
These docs show my IB Repository and Directory setups. Can anyone look at them and tell me what is missing? Thanks in advance!
http://webpages.charter.net/kpwendel2/bsmDir.jpg
http://webpages.charter.net/kpwendel2/bsmRep.jpg

Keith,
the problem is quite clear.
In your BPM, you have a synchronous interface in your sync send step.
However, in configuration, you have configured two asynchronous interfaces.
To be able to use sync send step in BPM, your RFC needs to be able to send a response back. Then you need to have two message mappings (one for bpm->rfc messages, and other for rfc_response -> bpm_response messages) and a interface mapping between the 2 sync interfaces (bpm_sync_int -> rfc_sync_int) using these 2 message mappings.
Also, some hints:
1. Don't do these mappings in BPM transformation step. You can execute them outside of BPM. Doing this, you will get better performance and also won't need to create abstract interfaces for RFC messages.
2. Use configuration wizard in Integration Directory (first, remove and reimport your BPM in Integration Directory). This way, you avoid different interfaces errors.
Regards,
Henrique.

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?

Reciever idoc adapter Determination error

Hi,
I have scenario File-XI-R/3.I am using Idoc adapter to send data to R/3.
I am getting Reciever determination error.I have done all the steps according to the below weblog.
/people/ravikumar.allampallam/blog/2005/02/23/configuration-steps-required-for-posting-idocsxi
When I test my steps in configuration with test tool it is succesfull but give me error at runtime.
Below is error description.
<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>
Plz help me out if any one has some idea abt it.
Thanx
Rekha

Hi Rekha,
The End Point Type for your scenario should be an IDoc Adapter with parameters from your RFC destination in SM59.
The most common reason for this error is:
1. An error in configuration of sender adapter/proxy: wrong sender business system or namespace or interface name. Look, all this information you must put manually so be carefull on typos (one wrong or ommited letter and you can spend hours looking what is wrong). Copy (from Repository) and paste procedure is strongly recommended.
2. An error in Directory (Endpoint Configuration). Be careful to specified the correct host and port!!!
Hope this helps.
Regards
Suraj

File to File BPM scenario

Hi Experts,
I am getting the below error for File to File BPM scenario.
<SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="BPE_ADAPTER">MESSAGE_NOT_USED</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Message is not used by any processes</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Could you please tell me, why I am getting this error.
Regards
Sara

IR IP
FileTOFile_BPM
1. Receive Step (Used MI_Abs_Async)
2. Send Step (Used MI_Abs_Async)
Please find the below configurations which I hv done in ID
IP in ID
BPM_FileToFile
Business Service & CC
1. SENDER_SERVICE
CC: File_Sender_BPM
2. RECEIVER_SERVICE
CC:File_Receiver_BPM
3. Receiver Determination:
a) Sender Service : SENDER_SERVICE
Sender Interface : MI_Outbound_Async
Receiver Service : BPM_FileToFile
Receiver Interface : MI_Abs_Async
Mapping : IM_File
b) Sender Service : BPM_FileToFile
Sender Interface : MI_Abs_Async
Receiver Service : RECEIVER_SERVICE
Receiver Interface : MI_Inbound_Async
Receiver Agreement : File_receiver_BPM

Error in ALE service 29 Could not determine recipients for message type MAT

Hi Experts,
While transferring the material using ALE am getting error 29 ie 'Error in ALE service' and message is 'Could not determine recipients for message type MATFET'.
Also i ve recieved the materials with the proper status al the end am getting the above error.
Kindly help me out.
Thanks in advance.

Hi ,
Status 29 means " partner profile not found " . Please check if the recieving partner is configured properly in WE20 in sender system.
Also make sure that the Port and RFC definations are also completed. If the IDoc is manually triggered then please make sure that control record parameters of the idoc are properly filled - if we miss the details ( like wrong port given , wrong basic type for message type - or extended message type ) then also the idoc will fail in status 29 even though the partner profile is properly configured .
Since your idoc is getting generated i think no issues with BD64 since already interested recipeints were populated in control record of idoc.
Regards
Vikas Chaudhary

BPM Scenario

Hi,
    I am trying out an BPM scenario for an N:1 mapping,in which i'll be sending N number of 2 different structure of messages.The source file got picked from the Source.The SXMB_MONI describes that the "Message being sent",but i couldn't get at the target.I doubt that my BPM design could have strucked up in the looping and hence the message couldn't be delivered.Can anyone provide some pointer to get it resolved.The BPM design is as mentioned below :
Block
          Deadline
          Exception Handler
                                    Loop1     Recv1     Container1    Loop1
         Fork                                                                                Fork     Transformation(2:1)   Send Stop
                                  Loop2     Recv2      Container2      Loop2
Note : The loop will come out when the deadline time reaches 2 min.

Yes.The Correlation desfined as below
File1 of Abstract type Message Interface
FileList1 of of Abstract type Message Interface(Multiline checked)
File2 of Abstract type Message Interface
FileList2 of of Abstract type Message Interface(Multiline checked)
TargetFile of Abstract type Message Interface

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 with BPM Scenario

Hi all,
 I am trying to implement a Sender File ( async ) to RFC (sync ) to Receiver File with a BPM. I using the blog https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/1926. [original link is broken] But it doesnt work. First message FileRequestOut is correct in SXMB-MONI, but the second is showing a error. I checked in SXMB-MONI-BPE and I say in workitem is follow message:
Message Error Workflow
Error handling for work item 000000001714
Work item 000000001714: Object CL_SWF_XI_MSG_BROKER method SEND_SYNCHRON cannot be executed
No reference message specified when sending a response
No reference message specified when sending a response
I configured my BPM scenario in this way:
( Sender File Adapter )
First Step
Receiver Step ( Asynchronous )
Mode: Asynchronous
Receive Message: File Request
( Receiver RFC Adapter )
Second Step
Send Step ( Synchronous )
Mode: Synchronous
Request Message: File Request
Response Message: File Response
Receiver From: Send Context
( Receiver File Adapter )
Third Step
Send Step (Asynchronous )
Mode: Asynchronous
Receive Message: File Response
Receiver From: Send Context
 I have changed it, many times and I can get solve it. About my configuration objects, I think it is ok, because a tested my Interfaces in Configuration Test Tools it was ok. ( Receiver Det. Interface Mapping, etc)
 I have seen in SDN, this error maybe Sencond Step must be Synchronous e Third Step must be Synchronous too. Is it true? In other hand, I have seen, it is possible to use a Async / Sync Brigde.
 Could you help me about this problem?
 Thanks for help
 Best regards
 Fábio Ferri
 Consultant XI/ABAP/Netweaver

Hi ,
 I have seen in SDN, this error maybe Sencond Step must be Synchronous e Third Step must be Synchronous too. Is it true? In other hand, I have seen, it is possible to use a Async / Sync Brigde.
 In BPM did u used as
 Recive Step Async
 Synchronous Send Step
 Send Step is Async
 it is possible to use a Async / Sync Brigde.
 No need to use Asyn Sync Step for this
Assign poins if u found hepful
Best Regards.,
V.Rangarajan

Error: ATTRIBUTE_IDOC_RUNTIME FM NLS_GET_LANGU_CP_TAB: Could not determine

Hi All
Production issue
Scenario is: File to IDOC
From 2 days our R3 production server was down. Before R3 went down i didn't stop my Sender File Communication Channels and XI was continuously accepting files to process it and then trying to post it into R3. Now I can see around 500 messages are failed into SXMB_MONI with error "ATTRIBUTE_IDOC_RUNTIME
FM NLS_GET_LANGU_CP_TAB: Could not determine code page with REP_00_301 Operation successfully executed FM NLS_GET_LANGU_CP_TAB".
Now R3 is working fine and IDOCs are successfully getting posted.
Before telling my issue i want to share one information that in Message Mapping i have implemented a concept of duplicate file handling due to this duplicate file cannot be processed again.
Now my issue is: I am trying to restart the failed messages. So, whenever i am trying to do so my request mesasge maaping is called again and it is showing a error of "Duplicate file". So how can i reprocess my failed messages????
Regards
Dheeraj Kumar
Edited by: Dheeraj Kumar on Jul 14, 2010 3:55 PM

Hi Prasanna
I am maintaining the file names in the table and that table is maintained in XI. Through UDF i am sending a query to check whether that file name exist or not if exist then it is duplicate file otherwise it will process normally.
In production environment I cant delete the entry of file name as it is disabled.
Regards
Dheeraj Kumar

No reciever could be determined in BPM scenario

Similar Messages

Maybe you are looking for