Once again: Unable to convert sender service to an ALE logical system

[Former Member]

Hi,

I know there's a lot of threads regarding that error but I didn't find one that fits to our current scenario:

IDoc -> XI -> File

We have checked if the logical system name in SALE (of sending system) fits to the one in the business system and it does now.

It didn't fit at first but we've changed it in the SLD and reimported the business system.

We still get the same message:

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

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

There is no logical system entered in the receiver business system. Do we need that? But of which logical system?

Thanks for any advice

Karsten

[Former Member · Accepted solution]

There is no logical system entered in the receiver business system. Do we need that? But of which logical system?

Yes..you have to give in the other business sytem also.create another logical system in SALE and use the same in other business system.

[Former Member · Accepted solution]

Hi Sekhar,

Okay, so you mean in the SALE of the sending SAP system? We have to create another logical system there? But where is the point in that?? This logical system stuff really confuses me. Especially with a sending IDoc.

//Karsten

[Former Member · Accepted solution]

You have to create 2 logical systems in SAP and XI with same names in SALE transaction and you have to assign that logical system to their respective clients in SAP and XI.

Check these steps also...

https://www.sdn.sap.com/irj/sdn/wiki?path=/display/xi/sapR3%28Idocs%29ToXI--Steps+Summarized

[Former Member · Accepted solution]

Hi Hoffmann,

The thumb rule is every bussiness system should have one logical sys name,

Reason is XI is SAP application or Tool which needs one Bussiness system for cross application or company integrations..Runtime environment will recognise BS with the help of Logical systems only.

so if it is R3 sys you need to maintain that LS name at SALE and also SLD of XI.

If these are 3rd Party BS then you need to maintain that at SLD ..need not to maintain at SALE.

If not clear pls come again.

Regards,

Ramesh.

[Former Member · Accepted solution]

It's really hard to understand for me that the third party receiver system needs to have a logical system name since the error message is convert sender service to an ALE logical system. It should now in fact be able to convert sender service to ALE logical system. What has the receiver system to do with that??

Anyway, we'll assign a logical sys. name to the receiver system an see what happens.

Thanks for your deteiled answer. That's much better than just sending links

//Karsten

[Former Member · Accepted solution]

Hi Karsten Hoffmann,

You are doing Idoc---File scenario

I think you are using the Business system for Idoc side And the Business Service For File system Side. Is this Correct???

IF YES means,

1) As you have already one LS for Idoc sender side & it is refelcted at Integration Directory also.(Doublec click on Business system-ServiceAdapter Specific Identifiers)

2)Now check for your Receiver side Business Service is having the LS or not, If not present means Enter the LS by going above mentioned path and SAVE

IF NO means, and you are using the Business System at Receiver File side also

1) Open the Technical system created in SLD for Third party (File ststem)

2) there we can enter the LS for the Third party Business system & SAVE( We can enter any Name)

Regards

Seshagiri

[Former Member · Accepted solution]

Hi,

as far as we could see it is not possible to enter a logical system name in third party systems in SLD. Is that right?

Anyway the message status in the sxmb_moni is "processed succesfully". Do we have to care for the acknowledgements with the error messages then?

Thanks for your help!

Karsten

[Former Member · Accepted solution]

Hi,

Acknowledgments

Receiver adapters that run on the Adapter Engine support system acknowledgments if they are requested by the sender.( Ex : Idoc----File). Here by default Idoc has the inbuilt feature of requesting the Ack.

Acknowledgments are triggered when a message is successfully processed by the adapter or if an error occurs while it is being processed. Receiver adapters do not support application acknowledgments.

Sender adapters of the Adapter Engine do not request any acknowledgments

https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/903a0abc-e56e-2910-51a8-9dc616df...

Regards

Seshagiri

[Former Member · Accepted solution]

@All,

thanks so far for your help.

It turns out now that the IDoc's/ messages are processed successfully even though we still get these acknowledgements with the famous error message.

Question:

Is it even possible to enter a logical name in a third party technicial-/ business system?

Next Question: Can we ignore the acknowledgements or even disable them?

Thanks!

/Karsten

[Former Member · Accepted solution]

hi

It's really hard to understand for me that the third party receiver system needs to have a logical system name

If Logical system name hasn't maintained in SLD for 3rd party system..Runtime environment can't catch excact system.

since the error message is convert sender service to an ALE logical system.

For this not maintaining LS for 3rd party sys is not only the reason.Other Configurations also may be the reason.

Question:

Is it even possible to enter a logical name in a third party technicial-/ business system?

Yes, possible and have to give.

Can we ignore the acknowledgements or even disable them?

Yes, we can ignore acknowledgements ..if we are not very perticuler about it.

BestRegards,

Ramesh.

[Former Member · Accepted solution]

Hi,

Question:

Is it even possible to enter a logical name in a third party technicial-/ business system?

Yes, it shld be

Next Question: Can we ignore the acknowledgements or even disable them?

Yes, We can Ignore the Ack for the Particular Message type

goto XI's SE38--IDXNOALEExecute

Provide Message type( Ex: MATMAS) , Port( Created in SAP R/3)

REgards

Seshagiri

[Former Member · Accepted solution]

Hi N V Seshagiri,

Yes, it shld be

Well, I checked that several times together with my support guy and we couldn't find a field to input an LS. Strange, isn't it?!

On the other hand the "Unable to convert.." Error (comes as Acknoledgement) doesn't effect the message processing. The message is processd correctly and the file on receiver side is created. So e decided to suppress acknowledgements for that certain IDoc.

By the way: There is a way to enter a LS for a third party system. It's by using a business service instead of business system.

It's just that I don't want to change to business service and redo the configuration and I'm not shure that solves the problem (which is not really a problem since everything works fine).

What would you do?

//Karsten

[Former Member · Accepted solution]

Hi,

Open Your Business System of third Party in SLD

goto Integration TAB and here you will be able to enter the LS name & SAVE

Regards

Seshagiri

[Former Member · Accepted solution]

Hi N V Seshagiri,

Now we found it. There was no "Integration Tab" though. We opened the business system in SLD and clicked on "Change..." behind the tec. system. We had never tried that link before...

We couldn't test yet but I'm quite positive that the Ack. will be gone. Otherwise we suppress the Ack.

Thanks for helping me to solve the problem!

/Karsten

[Former Member]

In SLD, make sure that the sending business system has a logical system name.

Then in Integ.Builder(Config), go to the business sytem in change mode, then pull up menu Service-Adapter Specific Identifiers. If Idoc adapter LS is blank, click the button to get it from SLD. Then Apply.

Check the last two posts in this thread...

Note: reward points if solution found helpfull

Regards

Chandrakanth.k

[former_member556603]

Hello Karsten.

XI Error - Unable to convert the sender service to an ALE logical system

Go through the Micheal's Blog

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

ALE Config of Pushing IDOC's

/people/swaroopa.vishwanath/blog/2007/01/22/ale-configuration-for-pushing-idocs-from-sap-to-xi

Thanks,

Satya

Edited by: SATYA KUMAR AKKARABOYANA on May 15, 2008 12:01 PM

[Former Member]

hi,

Go through the links

Trouble shooting file to IDOC and IDOC to file

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

https://www.sdn.sap.com/irj/sdn/wiki?path=/display/xi/error%2bhandling%2bin%2bfile-idoc%2bscenario

Refer below links for indepth troubleshooting

Regards

[Former Member]

refer this one also....

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

[former_member859847]

Hi,

Please check the adapter specific identifiers of sender business system in ID.

i.e system->adapter specific identifiers->logical system.

if not, please assign at SLD and reimpot.

regards

mahesh.

[Former Member]

HI ,

There is no logical system entered in the receiver business system. Do we need that?

YES

But of which logical system?

Just name something as logical system.

Regards,

Ramesh.