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

Similar Messages

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.

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,

RCVR_DETERMINATION" NO_RECEIVER_CASE_ASYNC error while monitering

hi every body....
<?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>
all my configuration steps are perfect in ID...
why ian gting this error while moniteriong..
JOhn

Hi,
This error occurs brcause of
1.Message will stay in XI for no receiver found
Solution
1.     Check whether it has been configured correctly (Receiver Determination step also check if you are using XPATH in it, ie for conditional receiver determination and check it for correct info)
2.     It has correct receiver agreement.
3.     If its receiver determination includes the conditional receiver then make sure that it satisfies the condition.
4.     Also make sure that its value for funloc is the same.
regards
Aashish Sinha
PS : rewrd points if helpful

"RCVR_DETERMINATION" NO_RECEIVER_CASE_ASYNC

Hi all,
I am doing an interface Siebel to SAP, the inbound adapter is RFC and i am getting an error in the MONI as :
<?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>
and when i checked adapter monitoring: it is showing as below with a green signal:
"Receiver channel 'RFC_OCC_120' for party '', service 'BS_R3D_120' (internal name 'RfcClient[RFC_OCC_120]')
Client data: {jco.client.lang=en, jco.client.snc_mode=0, jco.client.client=120, jco.client.passwd=******, jco.webas.ignore_jdsr_error=1, jco.client.user=sapdev05, jco.client.sysnr=00, jco.client.ashost=sapdev2}
Repository data: {jco.client.lang=en, jco.client.snc_mode=0, jco.client.client=120, jco.client.passwd=******, jco.webas.ignore_jdsr_error=1, jco.client.user=sapdev05, jco.client.sysnr=00, jco.client.ashost=sapdev2}
Current pool size: 0, max pool size : 10"
and
Is a user defined for component AF? is showing red signal and the details are as follows:
Details for 'Is a user defined for component AF?'
com.sap.aii.adapterframework.serviceuser.name = null
com.sap.aii.adapterframework.serviceuser.pwd = null
com.sap.aii.adapterframework.serviceuser.language = null
Any inputs plz!!!!
thanks & regards
viji

Vijaya,
If you have already tried many things -- i suggest you try one more thing....as sometimes we overlook minor changes for very similar message types ....
1) You copy the Sender Interface from Receiver determination...
paste that in a notepad...
then you copy the sender interface from SXMB_Moni and paste just below it .. and see if they are exactly identical and no change of spelling or anything....
2) Try this for Sender Service and namespace as well .....
Check if you can notice any difference ... we once faced this issue and the difference was 0 and O in the interface name....
Thanks,
Himadri

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

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

Error:- Idoc2 file (Sender KU - Recevier LS)

Hi,
I am using Idoc to file Scenario ( Sender KU - Recevier LS)
I have set up 2 parties:- Sender Party and Recevier Party with Identifier Settings.
1. It is throwing below error :-
RCVR_DETERMINATION">NO_RECEIVER_CASE_ASYNC
No receiver could be determined
2. Do I need to use one party or both, because recevier is LS.
Please suggest.
Thanks,
Anshul

Udo,
But in earlier thread you only suggest me to use Parties: as I have [Sender KU - Recevier LS]
Idoc2File - Sender R/3 KU (Customer) Configuration
Prateek,
My scenario is Idoc- File ( Customer KU to File LS)
If I create SLD - Business System , so where I will mention Partner no (1100024) and PartnerType (KU)
For example -- Logical system is option there
Because I am using this in Party ---> Identifers settings.
Please syggest.
Anshul

Alerts not getting triggered for invalid receiver receiver

Hello,
My scenario is IDoc to HTTP.I have defined alert rules for my scenario.
I have condition mentioned in receiver determination.Depending on vendor number data is sent to corresponding receiver.
But when i send IDoc is sent with invalid vendor number,it is failing in XI system with error as :No receiver could be determined but not alert is being thrown or triggered.
Same situation is working in Dev and quality but not in production.
I ahve checked the alert rules thorughly in all the 3 environments and they are all perfe

does the error"RCVR_DETERMINATION.NO_RECEIVER_CASE_ASYNC" gets triggered only when reciever service is not
mentioned in alert rule condition?
This error gets triggered when no receiver matching with the mentioned Condition is found.....the Condition in Receiver Determination OR if no receiver service exists.
I hope you have created a rule in Alert Rule section of RWB and have unchecked the Suppress Multiple Alerts options.
When you get the above error in SXMB_MONI you should get an alert
Regards,
Abhishek.

ABAP Proxy in PI System

HI all,
i have a scenario :
my source system is PI (App.sys)(client 01) from where i am sending the data to my PI (IS)(client 02 ) using ABAP Proxy. And from there i have send the data to my 3rd party Business system using JUDD adapter.
i am able to send the data from my 01 client(AS) to 02 client(IS), but i am not able to send it to my 3rd party system, i can see sucess message in 01 client(AS).
i am getting error RCVR_DETERMINATION">NO_RECEIVER_CASE_ASYNC
i have checked SLDCHECK it is good.
my Configuration in ID is also good.i have Checked in Test Configuration of my ID.it is showing success.
is there any other Configuration required
pl help me out in finding the Solution..
thanks.
kalyan

Hi
Test configuration not works always.
Check with your ID configurations for receiver determination and check whether system or service defined has the expected ASYNC interface.
If you are using service then you have added the target interface or not?
Thanks
Gaurav

Multiple sender file

Hi,
I have a file to file scenario a bit particular.
There is a unique receiver file communication channel.
Howerver, I must to create multiple file sender communications channels because sender ftp servers are different (and very numerous ! ).
There is any way to avoid configurate so many receiver determination and interface determination, to implement a multiple sender scenario ?
Thanks, in advance

Hi, Udo,
I'm trying your solution, but I must have an error and i don't find it.
In an scenario N senders (N business service) to 1 receiver (business system called TPV):
Receiver Determination
Sender service : *
Sender interface : MI_OUTB
Receiver party :   (none)
Receiver service : TPV
Configured receivers: Service TPV
Interface Determination :
Sender service : *
Sender interface : MI_OUTB
Receiver party :   (none)
Receiver service : TPV
Inbound interface: MI_INB
Receiver Agreement :
Sender service : *
Receiver party :   (none)
Receiver service : TPV
Receiver interface: MI_INB
Also I have created several Business Services with CC and Sender agreements.
And I have 2 problems:
Receiver determination doesn't recognize Interface Determination and REceiver agreement in Configuration Overview
Error RCVR_DETERMINATION">NO_RECEIVER_CASE_ASYNC in Monitor.
Please, I need your help.
Thanks, in advance
Carme

Getting error when testing Proxy to File interface

Hi Guru's,
While I am testing a Proxy to File Interface, using SPROXY transaction i am sending a message from R/3 to PI.
the message showing successful in R/3 Moni,but in PI moni I am getting the following Error..
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error SOAP:mustUnderstand="" 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_ASYNC</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:Stack>No receiver could be determined</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
In this inreface, I am suppose to send the mesasage to only one Target system(ftp server) . i have checked in ID part also,
every thing is clear in ID. Can any body please tell where the mistake might exists...
Thanks in advance..
Regards
Raj

Hi,
No receiver could be found means Check your Receiver Determination. Activate and update cache. Asysnchronous messages can be manually restarted.
have you seen this threads,
NO_RECEIVER_CASE_ASYNC
No receiver could be determined
regards,
ganesh.

JDBC to IDOC Error

Hi Guys
On my Scenario Jdbc to Idoc (Asynch) I am using FLCUSTOMER_CREATEFROMDATA.FLCUSTOMER_CREATEFROMDATA01
as a Receiver Interface, now when testing on the sxmb_moni I get two flags the Black and While and the Red the one the is Back and While shows that the Sender is my JDBC Adapter which is right
but now the Red flag show that the Sender is IDoc(FLCUSTOMER_CREATEFROMDATA.FLCUSTOMER_CREATEFROMDATA01) is also Sender of which I used it as a Receiver Interface, I dont know how to stop this IDoc Adapter not to send but to receiver.
Basical my scenario is meant to create an IDoc but is is not doing it when going to TCode WE02/WE05 I get message : "No IDocs selected"
Thanks
Yonela

Hi
I don't have any conditions, to Send and Receive, by the way I went to TCode IDX5 my Outbnd is right but Inbound thats where I get the below 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 have done these:
SM59- To Create RFC Destinations
WE21- To Create IDoc Ports
SALE- To Create Logical System
WE20- To Create Partner Profiles
IDX1- Port Maintenance in IDoc Adapter
IDX2- Metadata Overview for IDoc
On the ID I created the the IDoc Receiver:
RFC Destinatin: IDOC_RECEIVER
Interface Version: SAP Release 4.0 or Higher
Port: SAPPI1
SAP Release: 701
What could be the problem
Thanks,
Yonela

File receiver error

Hi Experts,
Here my scenario is proxy to file.(asy).
Today and yesterday we tested it was worked fine.
here around 30 interfaces are there.
for all interfaces i am getting same error
it was showing reciver determination error for all interfaces but i configured currectly.
*in this error category is XI server it was showing inblow XML error file*
Just now i am tested again I am getting below error in SXMB_MONI
*<?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>

Yes, Ichecked in all caches,
I refreshed throgh SXI_CACHE ( delta cahche comlete cahche is running in backgrund)
<SAP:Category>XIServer</SAP:Category> (this message i saw in SXMB_MONI)
is above one is serverrelateed Error?
still same errror.
let me know the problem.
Edited by: srinivasreddy p on Jun 5, 2009 12:39 PM

ABAP Mapping for Error handling in Proxy to JDBC

Hi All,
I am working on a proxy to jdbc scenario in which we have to throw validation errors to NWPM(Net Weaver Process Monitor Tool)
I am following the below steps,
step 1 - In message mapping a UDF is created to catch errors and store them in a variable using dynamic configuration
step 2 - writing abap mapping for handling this thrown exception and im reading the dynamic configuration in the abap class and raising exception. The exception format expected is
SAP:Error SOAP:mustUnderstand="" 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_ASYNC</SAP:Code>
<SAP:P1>ZPI_THROW_EXCEPTION</SAP:P1>
<SAP:P2>001</SAP:P2/>
<SAP:P3>Mandatory field is missing[BUKRS] </SAP:P3>
   <SAP:AdditionalText />
<SAP:Stack>No receiver could be determined</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
I have written the following ABAP code to achieve this:
method IF_MAPPING~EXECUTE.
DATA l_record type mpp_dynamic.
DATA error type String.
getting dynamic configuration value
filled in by any previous mapping
CALL METHOD DYNAMIC_CONFIGURATION->GET_RECORD
EXPORTING
    NAMESPACE = 'http://sap.com/xi/XI/System/ERROR'
    NAME      = 'ERROR'
RECEIVING
    RECORD    = l_record.
error = l_record-value.
*raising exception with our message
RAISE EXCEPTION TYPE CX_MAPPING_FAULT
EXPORTING
   TEXTID =
   PREVIOUS =
    ERROR_CODE = '001'
    ERROR_TEXT = error .
RAISE EXCEPTION TYPE CX_MAPPING_FAULT
EXPORTING
   TEXTID =
   PREVIOUS =
    ERROR_CODE = '003'
    ERROR_TEXT = error .
endmethod.
I am gettign the following message for our code:
SAP:Error SOAP:mustUnderstand="" 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_ASYNC</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:Stack>No receiver could be determined</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Could you please help in finding the solution for getting currect error message from ABAP class?
Edited by: SwethaC on Jan 21, 2011 8:18 AM

The error is due to RFC Call fail from PI system to your ECC Application System.
Check your RFC Destination for ECC System type 3 in PI System.
When you are receiving data from ECC System using Proxies & again you are going to ECC System for Validation.
Why you are not doing this validation on ECC System only in your proxy code ?
In your proxy code, it will be much better for performance to check your data there on same system.

Error: RCVR_DETERMINATION:NO_RECEIVER_CASE_ASYNC

Similar Messages

Maybe you are looking for