Unable to convert the sender service BS_PARTNER to an ALE logical system..!

[Former Member]

Hi All,

File to IDoc scenario.

1. Business system is correct because its working for other scenarios.

2. I checked Adapter Specific attributes in Business service and given Partner number which in maintained in WE20 for the partner in R/3.

3. Refreshed cache.

But still... its showing the below error.

<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>BS_PARTNER</SAP:P1>

<SAP:P2 />

<SAP:P3 />

<SAP:P4 />

<SAP:AdditionalText />

<SAP:ApplicationFaultMessage namespace="" />

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

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

</SAP:Error>

Any idea what might be wrong?

Regards

Deepthi.

[justin_santhanam · Accepted solution]

Deepthi,

I'm sure u did everything correct. Plz don't mind can u re -verify everything according to the blog

/people/michal.krawczyk2/blog/2005/03/29/xi-error--unable-to-convert-the-sender-service-to-an-ale-logical-system

raj.

[Former Member]

Hi,

In SLD check whether u have given logical system name

for business system.If not then u can give tht while u create a Technical system.&if u have given tht then u can see tht in ID.TO SEE PROCEED AS FOLLOWS

DOUBLE CLICK ON BUSINESS SYSTEM

GOTO->SERVICES->ADAPTER SPECIFIC IDENTIFIERS

There u can see the logical system if u have specified in SLD

Also this logical system name should be used during the ALE Settings at R/3 side

Secondly u need to create a business service for FILE

AND GIVE A LOGICAL SYSTEM NAME FOR FILE

FOR THIS DOUBLE CLICLK ON BUSINESS SERVICE

GOTO->SERVICE->ADAPTER SPECIFIC IDENTIFIERS

AND GIVE A NAME

PLZ REWARDS POINTS

VIKAS

[former_member185856]

Hi Experts,

Could you please help me to fix this.

SCENARIO: SAP - IDOC -

---

> XI -

---

> SOAP Adapter (Webservice)

Workaround:

1. Verified Adapter Specific configurations and its fine with same Logical system in SLD and ALE service.

2. Header mapping in Receiver com channel : Sender service and Receiver Service is assigned

3. Identifier Tab in comm channel details: Its empty - no values.

SXMB_MONI :

Error Details:

<?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="1">

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

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

<SAP:P1>CAPTOR3_PRU</SAP:P1>

<SAP:P2 />

<SAP:P3 />

<SAP:P4 />

<SAP:AdditionalText />

<SAP:ApplicationFaultMessage namespace="" />

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

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

</SAP:Error>

Thanks in Advance,

Sunil.

[Former Member]

hi

have you use header mapping in receiver aggrement.

[Former Member]

Hi,

Refer the below link:

/people/michal.krawczyk2/blog/2005/03/29/xi-error--unable-to-convert-the-sender-service-to-an-ale-logical-system

Thnx

Chirag

[Former Member]

Hi,

Please refer this link, which gives an idea to troubleshoot the file to idoc scenario:

/people/venugopalarao.immadisetty/blog/2007/01/24/troubleshooting-file-to-idoc-scenario-in-xi

Also refer this link which will be useful:

https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/46759682-0401-0010-1791-bd1...

Regards,

Nithiyanandam