cancel
Showing results for 
Search instead for 
Did you mean: 

IDoc2File Error

Former Member
0 Kudos

Hi ,

I am testing my scenerio Idoc2File from R3 side using we19,Idoc is getting generated successfully and sent to XI but there I am finding error as below

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

Here while configuration I have created everything correctly and it looks fine with receiver part also.

Please do suggest me for the above errors

The message at R3 side in SM58 for IDOC is

Import container contains errors (are any obligato....)

Thanks

Sudharshan

Accepted Solutions (0)

Answers (5)

Answers (5)

Former Member
0 Kudos

thanks

Former Member
0 Kudos

Hi,

Error code NO_RECEIVER_CASE_BE or NO_RECEIVER_CASE_ASYNC

􀃎 Inspect receiver determination area in SXI_CACHE

􀂄 If necessary, adjust the routing information in the Integration Directory

􀂄 If the message is asynchronous, it can be restarted manually, and manual

changes in the SOAP header are permitted

􀂄 Common causes of error are discrepancies between the configuration

and the SOAP header of the incoming message

􀂄 Sender service does not match (case-sensitive!)

􀂄 Sender interface name or namespace does not match (case-sensitive!)

􀂄 Condition for content-based routing has not been met

􀂋 Double-check message content

􀂋 Double-check condition (XPath expression or context object)

AND ALSO CHECK THESE FORUM LINKS

Reward points if solution found helpfull.....

Thanks

Vikranth

Former Member
0 Kudos

Hi Sudharshan,

Make sure that your Logical System Name for Business System in SLD is same as the Logical Name for Business System in ID by setting adapter specific identifiers( Service->Adapter Specific Identifiers)

Regards

B.Dheepa

Former Member
0 Kudos

Hi,

Check these forum replies, They had the same problem.

and check this too..

/people/shabarish.vijayakumar/blog/2006/09/13/wanna-party

Thanks,

Vijaya.

former_member556603
Active Contributor
0 Kudos

Hi,

First check ur Config with test tool

/people/paul.medaille/blog/2005/06/24/test-your-xi-configuration-with-the-new-test-tool

1. Check whether it has been configured correctly .

2. It has correct receiver agreement.

3. If its receiver determination includes the conditional receiver then make sure that it satisfies the condition.

Former Member
0 Kudos

hi

check your 'ReceiverDetermination' in configuration. It is not matching with IDoc/Sys

The error is bcoz of tht.

rgds,

Arun