Page tree
Skip to end of metadata
Go to start of metadata

Intention behind this is to pinpoint the reason for the error "Unable to convert the sender service to ALE Logical System". Even though the title name looks like a redundant .Please read this and then later comment. As a learner I have searched the SDN blogs and not able to solve entire scenario with the help of a existent blogs .So I decide to give up this. I will take a scenario of file to IDoc where this error usually occurs.Here I am not going to explain the entire scenario ,I will mainly focus on the ID part where we need to take care of the objects for this error not to occur. For entire scenario search SDN .

While coming to ID part we will be using either business systems which are created in SLD or business services whiich can be created in the ID itself. In case of business systems we need to define the logical system during the creation in the SLD itself .

 In ID we will be importing the business system created in SLD.After importing the same into ID cross check the logical system name by selecting the option Adpater specific identier of business system imported. This is sender business system in the current scenario .
 If the logical system name is not the same configured in SLD we need to select compare with SLD button and then need to press Apply button. If still you are not able to get the logical system name configured in SLD ,then clear the SLD Data cache from Menu ->Environment ->Clear SLD Data Cache tab option.
 In case of business service we need to define logical system name in the ID by selecting adapter specific identifier option of business service. We need to create the receiver business system/service with the same process mentioned above.
Observe that there are R/3 System Id and client , this is my receiver business system which is of type web as abap technical system created in SLD (of course its not mandatory to create same type technical system) . Now we are done with the logical system names of sender and receiver Business systems/services.

During the generation of idoc control record, integration engine will take the values of SNDPRN (from sender business service/system logical name)and RCVPRN (receiver business system/service logical name) .

 If we don't set Logical system name for sender business system we will end up with the error Unable to convert sender service to ALE logical system.
After idoc gets generated it will be sent to R/3 ,provided all the configurations needed are in place. Once the idoc reaches to R/3,One more famous error, 56-EDI Partner profile not found, will occur in R/3 Side if profile is not created .To avoid this error we need to create the sender partner profile in R/3(i.e SNDPRN which is a logicalname of Sender Business System/service). once the profile is created configure the inbound parameter with the appropriate msgtype and processing code .

 Thank you for patience.I hope this article helped you .


  1. Former Member

    A very Good and short document for Practical Scenarios.


  2. Hello,

      The SNDPRN of the inbound idoc is in this case a logical system (LS in WE20), is it possible to change this to a vendor (LI in WE20) ?