IDOC to File - Clarification needed while using business service.

[lnirmala]

Hi all,

I have 2 scenarios to be implemented in PI..one is IDOC to File and another one File to IDOC.File systems in the above mentioned scenarios are 2 different legacy applications when business is concerned.So i am creating separate business services for the two legacy apps.I have included ECC in SLD and created proper LS name corresponding to that maintained in partner profile in ECC.File to IDOC scenario is working fine.

In the second scenario (i.e. IDOC to File) also i need to mention adapter-specific identifiers. But since i have already used the R/3 system id and client in the File to IDOC it is throwing an error while trying to activate the buss service.The XML message is failing at Receiver identification step when i have omitted r/3 sys id and client.In the acknowledgement i am getting the message as "Unable to convert the sender service INTEGRATION_SERVER_DEVPI to an ALE logical system"

I have checked entire SDN but didnt find any solution for the same.

Is there any work around for this issue?

Rgds,

Lekshmi.

[udo_martens · Accepted solution]

Hi Lekshmi,

in the IDoc to file scenario the "Logical System Name" = adapter specif identifier is not important, except that there has to be one. Just take any name what wasnt used before.

Regards,

Udo

[lnirmala · Accepted solution]

Hi all,

My issue is solved...didnt use any sys id or client in adapter specific identifiers...it worked fine...

Rgds,

Lekshmi.

[Former Member]

Hi,

Go through these blogs....

/people/rajeshkumar.pasupula/blog/2009/03/16/unable-to-convert-the-sender-service-to-an-ale-logical-system

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

/people/sravya.talanki2/blog/2005/12/02/manipulating-idoc-control-records-from-payload

Also chk these threads also.....

Might help you....

Regds,

Pinangshuk.