Errors about 'No receiver could be determined'

[Former Member]

Hi all:

I am setting up one scenario about ' IDOC to file '.

When I send IDOC from one R3 system to XI , I meet with the following errors.

No receiver could be determined

The SOAP Error is

<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>

- <!-- Receiver Grouping

-->

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

The trace is

<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>

- <!-- Receiver Grouping

-->

- <SAP:Trace xmlns:SAP="http://sap.com/xi/XI/Message/30">

<Trace level="1" type="B" name="IDX_INBOUND_XMB" />

- <!-- ************************************

-->

<Trace level="1" type="T">User: KEN</Trace>

<Trace level="1" type="T">Language: E</Trace>

<Trace level="1" type="T">ALE-AUDIT-IDoc-Inbound Handling</Trace>

<Trace level="1" type="T">IDoc-Inbound-Handling</Trace>

<Trace level="1" type="T">Syntax-Check-Flag X</Trace>

<Trace level="1" type="T">IDoc-Tunnel-Flag X</Trace>

<Trace level="1" type="T">Queueid</Trace>

- <Trace level="1" type="B" name="IDX_IDOC_TO_XML">

<Trace level="1" type="T">Get the Metadata for port SAPDEV</Trace>

<Trace level="1" type="T">Convert Segment-Definitions to Types</Trace>

<Trace level="1" type="T">Make Syntax check of actual Idoc</Trace>

</Trace>

<Trace level="1" type="T">Set Receiver Routing-object</Trace>

<Trace level="1" type="T">----

---

</Trace>

<Trace level="1" type="B" name="CL_IDX_IDOC_RESOURCE-SET_IDOC" />

<Trace level="1" type="T">Exit Function IDX_INBOUND_XMB</Trace>

- <Trace level="1" type="B" name="CL_IDX_IDOC_RESOURCE-GETBLOBDATA">

<Trace level="1" type="B" name="CL_IDX_IDOC_RESOURCE-ITAB_TO_BINARY" />

</Trace>

<Trace level="1" type="T">COMMIT is expected by application !</Trace>

<Trace level="1" type="B" name="CL_XMS_MAIN-ENTER_XMS" />

- <!-- ************************************

-->

<Trace level="1" type="B" name="CL_XMS_MAIN-SET_START_PIPELINE" />

- <!-- ************************************

-->

<Trace level="1" type="B" name="SXMBCONF-SXMB_GET_XMB_USE" />

<Trace level="1" type="B" name="CL_XMS_TROUBLESHOOT-ENTER_PLSRV" />

<Trace level="1" type="T">****************************************************</Trace>

<Trace level="1" type="T">* *</Trace>

<Trace level="1" type="T">* *</Trace>

<Trace level="1" type="T">XMB entry processing</Trace>

<Trace level="1" type="T">system-ID = XID</Trace>

<Trace level="1" type="T">client = 800</Trace>

<Trace level="1" type="T">language = E</Trace>

<Trace level="1" type="T">user = KEN</Trace>

<Trace level="1" type="Timestamp">2006-03-06T13:55:08Z CET</Trace>

<Trace level="1" type="T">* *</Trace>

<Trace level="1" type="T">* *</Trace>

<Trace level="1" type="T">****************************************************</Trace>

<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_UC_EXECUTE" />

- <!-- ************************************

-->

<Trace level="1" type="T">Message-GUID = 2B74B179E6789D40BCC4A22D826EBDEF</Trace>

<Trace level="1" type="T">PLNAME = CENTRAL</Trace>

<Trace level="1" type="T">QOS = EO</Trace>

<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_ASYNC" />

- <!-- ************************************

-->

<Trace level="1" type="T">Get definition of external pipeline = CENTRAL</Trace>

<Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID" />

<Trace level="1" type="T">Get definition of internal pipeline = SAP_CENTRAL</Trace>

<Trace level="1" type="T">Queue name : XBTI0012</Trace>

<Trace level="1" type="T">Generated prefixed queue name = XBTI0012</Trace>

<Trace level="1" type="T">Schedule message in qRFC environment</Trace>

<Trace level="1" type="T">Setup qRFC Scheduler OK!</Trace>

<Trace level="1" type="T">----

---

</Trace>

<Trace level="1" type="T">Going to persist message</Trace>

<Trace level="1" type="T">NOTE: The following trace entries are always lacking</Trace>

<Trace level="1" type="T">- Exit WRITE_MESSAGE_TO_PERSIST</Trace>

<Trace level="1" type="T">- Exit CALL_PIPELINE_ASYNC</Trace>

<Trace level="1" type="T">Async barrier reached. Bye-bye !</Trace>

<Trace level="1" type="T">----

---

</Trace>

<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />

- <!-- ************************************

-->

<Trace level="1" type="B" name="CL_XMS_MAIN-PERSIST_READ_MESSAGE" />

<Trace level="1" type="T">Note: the following trace entry is written delayed (after read from persist)</Trace>

<Trace level="1" type="B" name="SXMS_ASYNC_EXEC" />

- <!-- ************************************

-->

<Trace level="1" type="T">----

---

</Trace>

<Trace level="1" type="T">Starting async processing with pipeline CENTRAL</Trace>

<Trace level="1" type="T">system-ID = XID</Trace>

<Trace level="1" type="T">client = 800</Trace>

<Trace level="1" type="T">language = E</Trace>

<Trace level="1" type="T">user = KEN</Trace>

<Trace level="1" type="Timestamp">2006-03-06T13:55:08Z CET</Trace>

<Trace level="1" type="T">----

---

</Trace>

<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_SYNC" />

- <!-- ************************************

-->

<Trace level="1" type="T">Get definition of external pipeline CENTRAL</Trace>

<Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID" />

<Trace level="1" type="T">Corresponding internal pipeline SAP_CENTRAL</Trace>

<Trace level="1" type="B" name="PLSRV_RECEIVER_DETERMINATION" />

- <!-- ************************************

-->

- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">

<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL" />

- <!-- ************************************

-->

- <Trace level="1" type="B" name="CL_RD_PLSRV-ENTER_PLSRV">

<Trace level="1" type="T">R E C E I V E R - D E T E R M I N A T I O N</Trace>

<Trace level="1" type="T">Cache Content is up to date</Trace>

<Trace level="1" type="T">No Relation found - accept given receivers.</Trace>

</Trace>

</Trace>

<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />

<Trace level="1" type="System_Error">Application-Error exception return from pipeline processing!</Trace>

<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />

- <!-- ************************************

-->

</SAP:Trace>

Could anybody give me some clue to debug this problem ?

[former_member181955]

Hi

1.Check whether your logical system name is assigned to your techincal system in SLD.

2.In Integration Directory open your business system (service)double click it .From the menu go to service

then go to adapter specific identifiers. Now you can see one popup window there just check your logical system is appeared.

your problem can be solved.

If any concerns you can call me on my mobile..

Thanks

N.P.Babu

[Former Member]

Hi all.

Thanks for your great help.

I am really moved about your help and advice.

[former_member91687]

Hi Jianhong,

Since you are doing an idoc to file scenario, you would not require a sender idoc adapter, you would have to configure only a receiver file adapter. Since i guess this is your first idoc to file scenario refer this blog to check if you have followed the steps correctly in the repository and directory:

https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/1819. [original link is broken] [original link is broken] [original link is broken] [original link is broken] [original link is broken] [original link is broken] [original link is broken] [original link is broken] The blog does not talk about partner profile setup, and i hope you are aware of how to do this.

Configure your receiver file adapter according to this:

http://help.sap.com/saphelp_nw04/helpdata/en/95/bb623c6369f454e10000000a114084/content.htm

Do ask if you require further information.

Regards,

Chandra

[Former Member]

Hi,

Have you done a receiver determination for this scenario in the integration directory?

If yes, then recheck the sender service, sender interface and the receiving service parameters.

In an IDOC to file scenario, You need to have a receiver determination, interface determination and receiver agreement. Have you created all of these?

Regards,

Smitha.

[Former Member]

Hi,

Your reciver agreement is missing. Please check for the same.

Regards

Vijaya

[Former Member]

Hi all:

In Intergration Directory, I have defined the receiver determinations.

But I do not have a scenario defined in ID.

I have checked, there is IDOC sent from R3 to XI, but it cannot be transfered into File.

[Shabarish_Nair]

Did you create a Configuration Scenario in ID ?

All the receiver det., interface det., receiver agereement etc has to be added to your Configuration Scen.

You Business systems or Business services also needs to be included in your Conf. Scenario.

Note : You dont need to create a sender agreement in case you are sending an IDOC.

[Former Member]

Oh, I didnot create any configuration scenario in ID.

I will create it and try it.

Thanks.

I am really a rookie guy in XI.

[Shabarish_Nair]

Glad to be of help

Between if the suggestions helped you, you can assign points and even close the thread.

ShaBZ

[Former Member]

Hi Shabarish.

I created one scenario, but it still throws out the same error.

Where can be the problem ? Could you tell me the clue to debug ?

[Shabarish_Nair]

Steps involved:

1. Once you have created you scenario, assign your Business Systems or Business Service to it.

2. Create or assign (if already created) the communication channel for the file to the corresponding BS.

3. Follow the same for Receiver determination , interface det. and Receiver Agreement. (ie . if already created , right click the particular object and say assign to Scenario else create it in the scenario itself)

[Former Member]

Hi,

Have you created a business service or a business system?

In case you have created a business service - double click on your business service, and under the sender and receiver tabs, specify the required parameters.

This should solve your problem, in case you have created a business service.

Regards,

Smitha.

[Shabarish_Nair]

Can you do the following checks :

1. Partner profile for IDOC (outbound - specified in R3)

2. <b>No</b> sender agreement created.

3. Receiver agreement + receiver determination + interface determination is done

ShaBZ