"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

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.

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

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,

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

Proxy to File--- NO_RECEIVER_CASE_ASYNC

I have a proxy to xml file scenario getting data from ECC. I am getting the following 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 noticed one thing in my error in SXMB_MONI. The sender Service appears to be incorrect from what my SLD and configuration is set to. We actually create an entry in the SLD that we actually deleted and re-created. The old entry (deleted one) is still showing up in the moni-error. We have cleared all the cache. We have deleted everything in ID and IR and rebuilt everything twice. Test configuration is also working fine. Any help would be greatly appreciated.

Hi Tanuja,
Make sure if it is deleted from deleted from ID, not just from the configuration scenario(check in objects tab also).
If it is also deleted there just refresh the cache in SXI_CACHE and also CPACACHE.
Also check if the cache is clear in R/3 side also.
Regards,
Naveen.

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

RCVR_DETERMINATION

Hi,
Iam getting the following error message when the XI interface is run. Can someone help in understanding the problem.
<?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>
Best Regards
Suresh

Hi,
This error occurs only when ever there is problem in Receiver Determination configuration.
The error NO_RECEIVER_CASE_ASYNC indicates that your scenario is not working due to unavailability of Receiver Determination.
1. If all the receiver determination and interface determination are correct, just make some dummy changes on your receiver determination and reactivate it.
2. There may be a mismatch in sender, sender interface, sender interface namespace (and optionally any conditions for content-based routing) values between your configured receiver determination and in the actual message header.
Check your acutal message header at runtime - SXMB_MONI, then Inbound Message->SOAP Header->Main. Check values within <SAP:Sender> for Service, Interface and namespace. These have to match those configured in your receiver determination.
refer
Strange error
No receiver could be determined. (File to Idoc)
XI 3.0 No receiver could be determined
Thanks
Swarup

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 in sender channel:

When activating changes in IR I used to get system message as NoClassDefFoundError.Even then the componenets used to get activated.
Initially every thing was working fine with the sender channel.
It was successfully picking up the file and sending the same to receiver channel.
Suddenly after a day I sarted getting this error (below).And the file was not getting picked up.
Error in channelError: javax.ejb.TransactionRolledbackLocalException: nested exception is: java.lang.RuntimeException: java.lang.NoClassDefFoundError: com/sap/aii/af/app/mp/impl/ModuleProcessorCategories; nested exception is: javax.ejb.EJBTransactionRolledbackException: nested exception is: java.lang.RuntimeException: java.lang.NoClassDefFoundError: com/sap/aii/af/app/mp/impl/ModuleProcessorCategories
sxmb_moni 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:Stack>No receiver could be determined</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
There was no such error: And I had not made any changes since it was working fine.
Is this error because of the message I used to get in IR.?Was might be the cause

Hi,
Please check you message first properly all conditions supporting or not.Is message is having any exceptional chars , and Check whether your are using Async or Synch communication , respectivly the sender and receiver communication mode supporting both sides. and check your J2EE is working fine or not, Check your interface is having the module processors in sender side/receiver side is yes , those are working fine or not , those are properly imported properly or not.
these diffects may not effect the activation of components.
Also check your receiver Business system is working fine or not
And also check your receiver agreement is configured,receiver determination and interface determination all are refered same business systems or not.
,please see the following threads
Error RCVR_DETERMINATION
No Receiver Determination
Re: NO_RECEIVER_CASE_ASYNC
XPATH and RECEIVER DETERMINATION
XI 3.0 No receiver could be determined
Regards
Chilla..

Problem in idoc to file scenario

hi
while creating the idoc to file scenario i am facing few problems.
1) My design time objects are working fine. i have checked my message mapping, message interface etc.. (all design time objects are in active mode).
2) In ID, i have tested my configuration in test configuration, its working fine there as well (in ID i am using 2 business service one for sender, one for receiver)
3) i am using my ecc6 training server as my sender and using my XI server as receiver.
4) i am sending idoc from ecc6 and converting it to file in XI server and saving it in XI server itself(my receiver in this case).
my error:
i send my idoc from we19 transaction, and i see a error message stating
that 'RCVR_DETERMINATION.NO_RECEIVER_CASE_ASYNC'
my doubts.
1) while sending the idoc from ecc6, is it mandatory to give process code in partner profile ( that is, assign an outbound function module to push the created idoc to the mentioned destination).
2) also is it mandatory to have a partner profile on the receiver side( XI in this case) along with inbound process code.
3) in my receiver adapter ( file adatper in this case ) i have used NFS protocal. is it rite?
kindly help me with this issue.
regards
manoharan

>
manoj murugesan wrote:
> 1) while sending the idoc from ecc6, is it mandatory to give process code in partner profile ( that is, assign an outbound function module to push the created idoc to the mentioned destination).
>
> 2) also is it mandatory to have a partner profile on the receiver side( XI in this case) along with inbound process code.
>
> 3) in my receiver adapter ( file adatper in this case ) i have used NFS protocal. is it rite?
>
>
> kindly help me with this issue.
>
>
> regards
> manoharan
and to 1 & 2 ref. below,
Configuration steps required for posting idoc's(XI) -
/people/ravikumar.allampallam/blog/2005/02/23/configuration-steps-required-for-posting-idocsxi
ALE configuration for pushing idocs from SAP to XI -
/people/swaroopa.vishwanath/blog/2007/01/22/ale-configuration-for-pushing-idocs-from-sap-to-xi
3. NFS protocol is used to read/write files to the XI server itself. If you have to write to a local machine then use FTP

Doubt in Idoc To File Scenario

Hi Experts,
I didn't created any scenario in XI, i have created an idoc in R/3 and i have send it to XI system using tcode we19, i could able to see the idoc in XI system in tcode IDX5, when i double click on the xml message in IDX5, i am getting the follwoing 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>
Actually without creating the scenario in XI also i shouldn't get any error, i should get the xml message without any errors. Please correct me if iam wrong. Kindly suggest me what might be the problem for getting this sort of error.
U'r help will be greatly appreciated.
Thanks & Regards,
Venkat.

Hi Venkat,
>> Actually without creating the scenario in XI also i shouldn't get any error, i should get the xml message without any errors.
If you check in the inbound message payload u can see the xml message with out errors. But the error is due to non availability of receiver determination path to send the xml message to the desired target system from XI.
So create all the design objects in IR and configuration objects in ID and then try to trigger idoc from r/3 and check the mapping flow and check whether the desired file is created in the target folder.
For more info refer the below blogs:
https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/1819. [original link is broken] [original link is broken] [original link is broken]
Regards,
Prasanthi.

"RCVR_DETERMINATION" NO_RECEIVER_CASE_ASYNC

Similar Messages

Maybe you are looking for