Unable to convert the sender service to an ALE logical system

[nisarkhan_n]

I have configured the IDOC receiver adapter........

i am running the File to IDOC scenarion....

this is the error i am getting

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

- <!-- Call Adapter

-->

- <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="IDOC_ADAPTER">ATTRIBUTE_INV_SND_SERV</SAP:Code>

<SAP:P1 />

<SAP:P2 />

<SAP:P3 />

<SAP:P4 />

<SAP:AdditionalText />

<SAP:ApplicationFaultMessage namespace="" />

<SAP:Stack>Unable to convert the sender service to an ALE logical system</SAP:Stack>

<SAP:Retry>M</SAP:Retry>

</SAP:Error>

i have maintained in the correct logical system name of the r/3 in the SLD and it reflects in the Adapter specific attributes in the ID-->BS

Idoc Receiver port are proper.......

what i might be missing?

[bhavesh_kantilal]

You need to also maintain the Logical System Name for the Sender Business System / Service that is being used for the File System.

Have you done this?

Regards

Bhavesh

[nisarkhan_n]

Logical System name for the sender businsess system/ Service that is being used for the file system.......

this is my sender file system BS_Rapper_MT, do i have to maintain the LS name of sender in the Adapter specific attributes for this service? if so what is the LS name i have to maintain......

[bhavesh_kantilal]

Yes you need to maintain the same in the SLD if it is a Business System or manually in the ID if it is a Business Service.

The value has to be the value / logical system name for which the partner profile is created on R3.

Regards

Bhavesh

[nisarkhan_n]

bhavesh,

sender BS is : BS_Rapper_MT

receiver Bs is: MEDCLNT200

i have maintained the LS name for MEDCLNT200 in SLD and In adapter specific attribute in ID for receiver BS....

now i have also maintained the LS (BS-rapper) name for sender System BS_Rapper_MT in SLD and in adapter specific attribute?

correct me if i am wrong,,,,,i was thinking do we really need the LS name for sender if it is of type 3rd party?

[bhavesh_kantilal]

If you are dealing with Idoc's yes.

You also have something called Header Mapping in the Receiver Agreement that can be used to read the Logical System Name from some other Business System and thereby avoid maintaining it for your 3rd party system .

The Idoc reaches R3 with this Logical System Name as the sender partner name and is hence essential.

Regards

Bhavesh

[nisarkhan_n]

thank you very much......

now i am getting this error

<SAP:Category>XIAdapter</SAP:Category>

<SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_IDOC_RUNTIME</SAP:Code>

<SAP:P1>XML IDoc conversion: No known segments identified</SAP:P1>

<SAP:P2 />

<SAP:P3 />

<SAP:P4 />

<SAP:AdditionalText />

<SAP:ApplicationFaultMessage namespace="" />

<SAP:Stack>Error: XML IDoc conversion: No known segments identified</SAP:Stack>

<SAP:Retry>M</SAP:Retry>

</SAP:Error>

[bhavesh_kantilal]

In the mapping of your Idoc, the SEGMENT attributes should have value mapped as constant 1.

The BEGIN attribute should also have a Segment with value 1

All of these are known errors. Please search on SDN!

Regards

Bhavesh