cancel
Showing results for 
Search instead for 
Did you mean: 

Unable to convert the sender service to an ALE logical system

balaji_pichaimuthu
Active Participant
0 Kudos

Hiii

when im doing file to idoc.. in SXMB_MONI im getting a error msg like

"Unable to convert the sender service to an ALE logical system" ... so i followe the

https://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/13562. [original link is broken] [original link is broken] [original link is broken]

As per blog said i did adapter specific identifier... i clicked the Compare SLD button and apply.. but still the problem exist.

But when i check my configuration through CHECH CONFIGURATION tool.. im not getting any error..

what is the problem here?

Regards,

Balaji

Accepted Solutions (1)

Accepted Solutions (1)

abhijitbolakhe
Advisor
Advisor
0 Kudos

Hi Balaji

Your sender business system does not have a logical system name.

go to SLD and give any name as logical system for your third party sender business system.

After cache refresh do compare SLD in adapter specific identifier.

If you can see logical system name in adapter specific identifier...issue is resolved.

Otherwise create new business system with logical system name and do the configuration according to new B.S.

Regards

Abhijit

balaji_pichaimuthu
Active Participant
0 Kudos

Hiii abhijit

My sender business system is type of stand alone , so logical system is not mandatory.

Regards,

Balaji S.L.P.

balaji_pichaimuthu
Active Participant
0 Kudos

Hiii abhijit

My sender business system is type of stand alone , so logical system is not mandatory.

Regards,

Balaji S.L.P.

abhijitbolakhe
Advisor
Advisor
0 Kudos

ya.. For a third party non sap system, logical system is not mandatory..

But for file to idoc scenario..you need aa logical system name for B.S.

give any name..

Abhijit

balaji_pichaimuthu
Active Participant
0 Kudos

Hii my Receiver Business system do have a logical system.. since i gave the logical system is SLD itself.. i mean once i assigned the client no.. the logical system for the client automatically assigned to my receiver business system.. i also created partner profile for inbound added the idoc type in inbound parameter..... i used IDX1 IDX2 for port configuration from xi. sm59 for receiver r/3 system from xi system...

When i check my congirutaion in ID using "TEST CONFIGURATION" its was successfully processed.. but SXMB_MONI showing the same error.. and IDOC not generated in R/3 system...

Regards,

Balaji

prateek
Active Contributor
0 Kudos

What type of system is your sender system? Could you try Third Party business system instead of Standalone? Is it a Party related scenario?

Regards,

Prateek

balaji_pichaimuthu
Active Participant
0 Kudos

My Sender System is type of Stand alone... And NO this is not a B2B ... so there is no party...

MichalKrawczyk
Active Contributor
0 Kudos

hi,

just do this:

1. open receiver agreemnt

2. go to the change mode of it

3. click on sender service (header mapping section) and select your business system

that represents XI business system

4. save, activate and run the scenario

Regards,

Michal Krawczyk

balaji_pichaimuthu
Active Participant
0 Kudos

Hi Michael,

Nice to see your reply,

In your reply what do u mean by "click on sender service (header mapping section) and select your business system

that represents XI business system"

I couldnt understand the term xi business system here..

My scenario has stand alone type sender business system and web As Abap type receiver business system.

Regards,

Balaji

Former Member
0 Kudos

Hey that means

in the receiver agreement there is a section called Header Mapping under which there are four elements are there

1. Sender party

2. sender service

3. receiver party

4. receiver service

there select sender service and set value

HTH

Rajesh

balaji_pichaimuthu
Active Participant
0 Kudos

Hii Rajesh,

Should i create a CC for that PI business system..If yes what are the parameters we should give there?

Regards,

Balaji

former_member200962
Active Contributor
0 Kudos

you dont need to create a separate CC

In the Receiver Agreement of your FIle to IDOC scenario, where you have included the IDOC receiver CC, give the details as mentioned.....select the sender system as the XI system

balaji_pichaimuthu
Active Participant
0 Kudos

Hiii Michael,

You are great!! i select the sender servive as my Pi business system.. now the IDOC transformed successfully..

But i dont understand the concept.. Can u explain.. whats the logic behind your suggestion.. please explain

Regards,

Balaji

MichalKrawczyk
Active Contributor
0 Kudos

Hi,

>>>But i dont understand the concept.. Can u explain.. whats the logic behind your suggestion.. please explain

more details you can find in my book

http://www.sap-press.de/katalog/buecher/titel/gp/titelID-2086?GalileoSession=50249550A39Xd..iZgI

Regards,

Michal Krawczyk

balaji_pichaimuthu
Active Participant
0 Kudos

Hiii Michael,

Thank you for the information.. but could u tell the exact reason for giving sender service in Header Mapping..

Regards,

Balaji

Doug_Munford
Participant
0 Kudos

Saw this was unanswered...

In the code inside PI around Logical Systems (after all other logic), it has a habit of clearing the Party (and only retaining the Component Name) before looking up Adapter Specific Info... so it tries to look up your Component with a BLANK Party to find the Adapter Specific Logical System config. And it doesnu2019t find it because you have a Party defined.

So you either overwrite the sender component with an identity that has no party (like Michael suggested), or if you want and or need to keep the Sender Logical System there is an alternative:

Copy the Component and erase the Party on the Component Copy. This will still have the Sender Specific Adapter details in it. A Message can then be reprocessed and you should find it works correctly.

Regds Doug.

Answers (1)

Answers (1)

0 Kudos

Hi PI Experts,

I am getting same error 'Unable to convert the sender service to an ALE logical system' for the scenario SOAP --> PI --> IDOC.

I have tried giving Sender communication component and Receiver Communication component in Receiver Agreement under Header mapping, but still am getting the same error.

Could you please let me know, if i need to do some thing else to fix this issue.

Thanks in advance.

Chakradhar