cancel
Showing results for 
Search instead for 
Did you mean: 

ERROR"Unable to convert sender service to an ALE logical system,(Urgent)

Former Member
0 Kudos

Hi All when i am not giving the sender service address in the Receiver Aggrement i am getting this perticular error .

<?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_IDOC_METADATA</SAP:Code>

<SAP:P1>Transaction IDX1: Port SAPRP1, client , RFC destination contain errors</SAP:P1>

<SAP:P2 />

<SAP:P3 />

<SAP:P4 />

<SAP:AdditionalText />

<SAP:ApplicationFaultMessage namespace="" />

<SAP:Stack>Error: Transaction IDX1: Port SAPRP1, client , RFC destination contain errors</SAP:Stack>

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

</SAP:Error>

==========================================

And if i am giving this one then i am not getting any such error rather i am getting another error "Unable to convert sender service to an ALE logical system" for this also i have checked the LS system name in the Adapter specific Identifier and the logical name are exactly same. But still i am getting this error

<?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 sender service to an ALE logical system</SAP:Stack>

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

</SAP:Error>

=============================================

Still i am getting this error can anyone please let me know what to do now..??

Please treat this as urgent

Accepted Solutions (0)

Answers (5)

Answers (5)

Former Member
0 Kudos

Thanks,

Former Member
0 Kudos

Thanks to you all for your valuable responce.

Any way i have solved my problem.

Former Member
0 Kudos

Hi,

This error is caused when Sender System name does not match the logical system name of partner. As you mentioned you have done all the steps to ensure that, here's a checklist that could be helpful:

1. Check adapter specific parameters for sender system.

2. Maintain header mapping in receiver agreement and ensure that sender service name provided is same as business partner name required in R3 and business partner type is LS.

3. This may sound very basic, but ensure that checkbox for 'Apply control record from payload' is not checked and if it is then the values passed through payload are appropriate.

Hope this would be helpful.

Thanks,

Bhavish

Former Member
0 Kudos

Thanks For ur input but i have already tried with all these things but still i am faceing the problem...

former_member614185
Contributor
0 Kudos

Hi jay,

go thru the following link, the same error has been solved,