Unable to convert sender service to an ALE logical system

[Former Member]

Hi,

I have been working on a simple issue since long time.

I thought of taking your help in fixing it.

I did a File-IDOC scenario.

When the file is picked up, I see a error message"Unable to convert the sender service to an ALE logical system"

I know that is has to do something with the Sender and receiver systems.

I did following:

1. Checkced Adapter specific identifiers

2. MI on both systems in corresponding sender / receiver systems.

3. I cross verified RFC / port from PI to R3, which is correct.

4. Same way, I cross verified WE21, created a distribution model for this communication in WE20, port also is pointing properly.

I did enterted the Port, RFC destination from BC6 to R3 ( created in PI in the receiver side CC)

Now I dont see any problem in settings. But still I see this error message.

Unable to convert sender service to an ALE logical system

any clues in this case?

Regards,

Venkat.

[MichalKrawczyk · Accepted solution]

hi,

open directory and your receiver agreement

then go for header mapping section and select sender service

and put your XI system name there

try once more

Regards,

Michal Krawczyk

[Former Member · Accepted solution]

Michel, I did as you instructed. Now it shows up a different error message in ErrorID in Moni : ATTRIBUTE_IDOC_METADATA. It was ATTRIBUTE_INV_SND_SERV earlier.

I checked error message in MONI, its "Error: Obligatory node 'E1MAKTM' missing in the structure MATMAS01"

Wow, implies there is some problem while creating MATMAS and the message is passing through.

Michal, you are the champ..

Can you explain why did we need this extra setting?

I never knew that there was Business system for my PI server

anyways, why did this happend? Cant I execute a File-IDOC without a BS being created for PI server?

meanwhile let me make changes in mapping

Will update you when I see Material created in R3

Thanks,

Venkat.

[Former Member · Accepted solution]

Hello Venkat,

this error is due to idoc metadata not in sync with your R/3 idoc

Go to idx2 and delete metadata of your idoc of R/3 system and run your scenario now

it should be fine

HTH

Rajesh

[MichalKrawczyk · Accepted solution]

Hi,

>>>Can you explain why did we need this extra setting?

we don't need that but we can use it

in most cases XI is represented in R/3 as one logical system

and this is the only way to tell XI to use XI's LS instead of any other

>>> Cant I execute a File-IDOC without a BS being created for PI server?

sure you can:)

but then you need:

correct alternetive identifiers

WE20 on R/3 filled for this new BS which represnts file server

Regards,

Michal Krawczyk

[Former Member · Accepted solution]

thanks again

[Former Member]

Check one more time Adapter specific identifier of IDoc business system if not set in SLD while creating Business system go to SLD and add logical system and try do import the same in ID with option import from SLD

Rajesh

[prateek]

I did following:

1. Checkced Adapter specific identifiers

Good. But could you see the Logical system name present there? Is the same name present for the business system in SLD?

Regards,

Prateek