Unable to convert the sender service to an ALE logical system

[Former Member]

Hi All,

I know this error is very common and there were posts regarding this.I have gone threw most of the posts and tried to solve this problem from this thread.

my scenario is File to Idoc and i configured sender/ receiver as business service.I tried to maintain logical system name for send and receiver in Adapter specific identifies but its giving an processing error "already exists" in another service when I tried to activate.

When I run my scenario,still i am getting the error "Unable to convert the sender service to an ALE logical system ".

Pls advise.

Thanks,

Nivas

[Former Member · Accepted solution]

HI

Refer this:

[Former Member]

Hello,

Identify your Logical system (which is onfigured as partner profile to accept the Idoc) in R/3 . Check which business system is associated with this logical system in XI.

In the receiver agreement of reciver Idoc, enable the 'Sender Service' in the Header mapping and provide the value of the above business sytem.

Regards,

Akshay

[Former Member]

Hi Akshay,

Thanks. I am using communication component as 'Business service" not business system for both file sender and Idoc receiver.I ve checked LS for both sender sys and receiver sys and they are Ok.

Now when I was trying to add Adapter specific identifires,getting an error as already exists in other service.There are other business service where these identifires are already maintained.

Thanks.

Nivas

[Former Member]

Hello,

You must use Business sytems as your Idoc receiver. And this business systems has to registerd in the SLD. You have to import this in the Integration Directory from SLD.

Regards,

Akshay

[Former Member]

Hi Akshay,

Can't we use Business Service for recr Idoc CC.There is an existing scenario for the same IDoc with business service which is working fine. I am also using the same Idoc in different scenario and also target system is same.I dont know where i am going wrong.The difference b/w existing and my current scenario is only sender sys and Adapter identifiers as i couldnt able to enter them bcoz of error message" LS,Clent and SID already exists with Business service <XXXXXX>".

Thanks,

Nivas

[Former Member]

Hello,

In that case, in the header mapping put the earlier sender business service. The reason it is giving this error is that a logical system at any time can be associated with only one service. So, since you have provided the LS in the adapter specific identifiers of earlier sender service, use this service in the header mapping.

Regards,

Akshay

[Former Member]

Hi Akshay,

Thanks for ur quick reply.

Om Fine,In the recr agreement, i will put sender service as 'the service which has LS name in the identifier'.

what abt recr business service identifires?

Thanks,

nivas

[Former Member]

Hello,

The receiver service in the header mapping should have the name of the business system which has the that logical associated with it which is configured in the IDX1 of the XI system.

See the idea of using Header mapping is that if the sender and receiver business systems used to configure the interface in the Integration Directory does not have associated logical systems which are used in the ALE configuration (used in the target application system i.e. R/3), then you override these systems with the systems which has their assocaited logical systems configured in the target system.

So, this is the reason you explicitly specify the sender and the reciver systems in the header mapping of the reciver agreement.

Regards,

Akshay

[Former Member]

hi,

try working with out giving logical system name in adapter specific identifiers, but for reciever side(use ABAP business system) which is associated with u r ECC server.

hope it works for u

Thanks,

Madhav

Note:Points if useful

[Former Member]

Hi Madhav,

Currently I didnt mention any LS name in Adappter spec identifier for both as it's not taking it and giving an error saying its already exists in other serivces.

Do I need to use Busines syestem instaed of business serice for receiver CC?

Thanks,

Nivas

[Former Member]

correct, and Business system is ABAP business sytem associated with that perticular ECC server.

Thanks,

Madhav

Note: points if useful

[Former Member]

Ok Thanks, I will do it and come back with update.

Thanks,

Nivas

[Former Member]

Hi,

When I tried to add LS in adapter spec identifires,I am getting an error "LS,SID and client already exists in other service".If i dont add, I am getting "Unable to convert the sender service to an ALE logical system" when i run scenario.

Is there any solution for this?

Thanks,

nivas