ALE logical systems for business service or process

Hi,
I am trying to send an IDOC into my R/3 system. It is the same IDOC type that I have sucessfully sent out to parties. All the config is in place for communicating with the system, because I have sent others IDOCs in the past. However, they always were sent from another R/3 business system. They processed sucessfully.
I am now trying to sending IDOC's from a BPM,as well as, from a business service. They are under the "With Party" section of the directory. These obviously do not have logical systems, so when I try to send the IDOC I get
"Unable to convert the sender service Purchase_Orders to an ALE logical system", where purchase_Orders being the name of the business serice.
How can I handle this problem?
Should I hard code values somewhere?
Which ones?
I have read the other posts for the error above, but my situation seems to be different.
Help!
Chris

Hi,
To solve your problem, here my solution:
1/ In your Business Process of your ID (configurator), go to menu "Service > Adapter-specific identifier" and in the part "IDoc Adapter", write your Logical System.
2/ Create this Logical System on your target system (R/3).
WARNING: XI allows you to used a Logical System for only one service (Business Process). Thus, if you are several interfaces, you must used different Logical Systems.
Mickael.

Similar Messages

  • Logical system for business service!!!!!!!!!

    Hi all,
    I send a file from filesystem to XI which inturn converted to IDOC and posted to SAP system. Filesystem i've added as a business system(which has a logical system in R/3).
    now i've added the filesystem as a business service(assinged to a party). So if send the file i'm getting the error as "Unable to convert sender service to an ALE logical system".
    How can i resolve this problem?
    can we assign the business service a logical system name ?(as business system)
    What could be the procedure for processing this kind of b2b scenario where we dont have information about systems or sevices in SLD?
    Thanks in advance for your replies........
    Santhosh.

    Hi just check this Bolg for Help
    /people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions
    Ques.3
    Or refer to this link
    <b>/people/michal.krawczyk2/blog/2005/03/29/xi-error--unable-to-convert-the-sender-service-to-an-ale-logical-system
    if u want to learn more bout
    How to configure Idoc adapters
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/d19fe210-0d01-0010-4094-a6fba344e098
    reward if helpful
    Regards
    Sachin Dhingra
    Message was edited by: Sachin Dhingra

  • Logical system with business service

    hi,
    can we have a logical system with business service just like we have with business system?? If yes,how can we create logical system for business service??
    Ratna.

    Hi,
    If you intend to use it with IDoc adapter it might be also necessary to set up corresponding Logical System (tcode: BD54) in adequate backed system.
    Refer conversion routine (logical system vs. service) in this presentation [Using the IDoc-Adapter|https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/b2b4035c-0d01-0010-31b5-c470d3236afd] - page no 6.
    Regards,
    Jakub

  • Already used Logical System in Business Service?!

    Hi, well i am facing a JMS2IDoc-Scenario.
    As sender i configured a Business Service (K15) with the CC_JMS. The receiver is a business system (HRT) with the CC_IDoc.
    While i test the scenario i received following error:
    "Unable to convert sender service to an ALE logical system"
    Thats fine so far, therefore i checked the Adapter-Specific Identifiers and entered the Logical-System name. This is already in use at the business system (HRT) because of some CC for other Scenarios.
    Now there is the problem that i can't use this logical system name at K15, no idea why.
    Because of not having the technical details of the source-system (JMS) i choose to use business service. Is there another idea?! Party?!
    br, Jens

    Hi,
    The issue is with the fact that this Logical System Name has been assigned to another Business System ( say Buss System X) .And you want to use this same Logical System Name for the sender JMS service( Buss System Y) as well , correct?
    Solution is,
    In the Receiver Agreement , Select Header Mapping and for the Sender Servicce, select the Correspodning Sender Service  ( Sleect Buss System X )to which the Logical System Name is assigned.
    Now in the runtime this will be used as the Sender Service from which the Logical System Needs to be taken.
    Regards
    Bhavesh

  • Logical Systems in Business Services

    Hi
    In Business Service creation, for Adapter Specific Identifiers, the parameter for the Logical System. It is only possible to assign one logical system to one Business Service ?.
    i.e. to do
    MyBusServ1, Z_LS_1 
    MyBusServ2, Z_LS_1
    is not possible ?
    When trying to assign Z_LS_1 to MyBusServ2 I get the error that Z_LS_1 is already assigned. Is there a way to circumvent ?, I do not want to create two logical systems in R/3 as the IDOCS types submitted by the Business Services are the same.
    Thanks
    Damien

    Thanks for the replies
    Sarvesh - The Business service is the sender of the information \ IDOC. If I remove the Adapter specific config then how will XI know what Logical system to apply to the IDOC ?.
    Jaishankar - I am creating two IDOC's in SAP. MATMAS and PORDCR. The input file are coming from two different source systems. lets say sys1 and sys2. Both of thse for clarity are created in my scenario as Business Services. sys 1 creates MATMAS and PORDCR IDOC's int he syatem, sys2 creates PORDCR IDOC's in the system. As sys1 and sys2 are related in that they created the IDOC's as part od the same project then I would like to collect in the same partner profile in SAP e.g. Partner Profile ZPP_IDOC with IDOC types MATMAS PORDCR that serve as input for both systems. Logically I would assume that I can assing the logical system ZPP_IDOC to both the adapter specific parameter in both sys1 and sys2.
    Thanks
    Damien

  • Same ALE logical system for multiple BP

    Hello,
    we are using two processes to deal with the messages we receive from an external partner.
    For our system this partner is a logical system.
    My problem is now that we cannot give the same name to to processes.
    Do you have an idea how to solve it?
    Greets,
    Helge

    Hi,
    I now tried a bit with your input and the result is that I know gave the adapter specific identifier to one process (A) and in the receiver agreement I used a header mapping with A as the sender.
    I dunno why but now its working. Whatever the difference with the external partner my be ...
    Greets,
    helge

  • Logical System for R/3 IDoc processing

    Is there a way to use one logical system when data is coming from multiple sender communication channels?
    We get data from several MQ Queues via JMS Sender Communication Channels.  There is a separate queue per plant.  No matter which queue a file comes in on, it needs to create the same IDoc type in R/3.  So, they all need to be assigned the same logical system.  Is this possible?

    It is possible in the reciever agreement to define which service the message should come from.
    See http://help.sap.com/saphelp_nw04/helpdata/en/14/80243b4a66ae0ce10000000a11402f/frameset.htm
    Here you can make a header mapping and define which service you want the message to come from.

  • ERROR"Unable to convert sender service to an ALE logical system,(Urgent)

    Hi All when i am not giving the sender service address in the Receiver Aggrement i am getting this perticular error .
    <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    - <!--  Call Adapter
      -->
    - <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
      <SAP:Category>XIAdapter</SAP:Category>
      <SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_IDOC_METADATA</SAP:Code>
      <SAP:P1>Transaction IDX1: Port SAPRP1, client , RFC destination contain errors</SAP:P1>
      <SAP:P2 />
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText />
      <SAP:ApplicationFaultMessage namespace="" />
      <SAP:Stack>Error: Transaction IDX1: Port SAPRP1, client , RFC destination contain errors</SAP:Stack>
      <SAP:Retry>M</SAP:Retry>
      </SAP:Error>
    ==========================================
    And if i am giving this one then i am not getting any such error rather i am getting another error "Unable to convert sender service to an ALE logical system" for this also i have checked the LS system name in the Adapter specific Identifier and the logical name are exactly same. But still i am getting this error
      <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    - <!--  Call Adapter
      -->
    - <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
      <SAP:Category>XIAdapter</SAP:Category>
      <SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_INV_SND_SERV</SAP:Code>
      <SAP:P1 />
      <SAP:P2 />
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText />
      <SAP:ApplicationFaultMessage namespace="" />
      <SAP:Stack>Unable to convert sender service to an ALE logical system</SAP:Stack>
      <SAP:Retry>M</SAP:Retry>
      </SAP:Error>
    =============================================
    Still i am getting this error can anyone please let me know what to do now..??
    Please treat this as urgent

    Hi,
    This error is caused when Sender System name does not match the logical system name of partner. As you mentioned you have done all the steps to ensure that, here's a checklist that could be helpful:
    1. Check adapter specific parameters for sender system.
    2. Maintain header mapping in receiver agreement and ensure that sender service name provided is same as business partner name required in R3 and business partner type is LS.
    3. This may sound very basic, but ensure that checkbox for 'Apply control record from payload' is not checked and if it is then the values passed through payload are appropriate.
    Hope this would be helpful.
    Thanks,
    Bhavish

  • ERROR" unable to convert the service as an ALE logical system"

    Hello All,
    In SOAP to IDOC scenario I tested the webservice with the client tool. Its hitting the integration engine but its throwing up an error" unable to convert the service as an ALE logical system". How can I maintain a logical system for a service as its outside our landscape. Can any one let me know how to proceed with this.
    Looking forward to expert comments.
    Thanks and regards,
    Neelima

    Hi,
    Check this blog by Michal.
    /people/michal.krawczyk2/blog/2005/03/29/xi-error--unable-to-convert-the-sender-service-to-an-ale-logical-system
    Regards,
    Sudheer.

  • Logical System for Integration Process

    I am getting a error message for my Integration Process: "Unable to convert sender service IP_Kleinschmidt_Shipments to an ALE logical system"
    I am confused as to what i need to put in the IP -> Service -> Adapter Specific Identifires ->Logical System.
    I won't let me enter either the R3 system nor the XI system.
    What value do I need to put here so my acknoldgement can go back to the R3 system?

    Use header mapping in receiver agreement to apply a business system as sender of the Idoc message.
    That business system must have a logical system aplied and this should be maintained in R/3 as well.
    if you use XI system as logical system as IDoc receiver in R/3, then you can apply also XI as sender here.
    But you have to load the PI as business system to ID for this reason.
    You cannot apply a logical system to the business system, which already used elsewhere.
    I discused that issue with the developer a couple of years ago. He told me to use the workaround.

  • Unable to convert the sender service to an ALE logical system

    Hello,
    file adapter > XI 3.0 > Idoc adapter > r/3 system
    In sxmb_moni I receive "Unable to convert the sender service to an ALE logical system".
    In we05 in r/3 system no Idocs are arrving. I have no problem with idoc > XI >  idoc scenario to this same r/3 system (using same sld business system)
    I read other topics on this error but it seems they all talk about an IDOC outbound interface.
    What should I check?
    Thanks
    Boaz

    I do have the same problem as Boaz Paz
    When I try :
    file adapter > XI 3.0 > Idoc adapter > r/3 system
    > This is a B2B scenario where "AVTItalia" is the external party trying to send via its "AwayOrders" business service (a file pickup) an idoc to business system "UPG" (non party service)
    I get an error while XI tries to call its IDoc Adapter:
    <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
    <SAP:Category>XIAdapter</SAP:Category>
    <SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_INV_SND_SERV</SAP:Code>
    <SAP:P1>AwayOrders</SAP:P1>
    <SAP:P2 />
    <SAP:P3 />
    <SAP:P4 />
    <SAP:AdditionalText />
    <SAP:ApplicationFaultMessage namespace="" />
    <SAP:Stack>Unable to convert sender service AwayOrders to an ALE logical system</SAP:Stack>
    <SAP:Retry>M</SAP:Retry>
    </SAP:Error>
    With the following trace logs :
    <Trace level="1" type="T">Party normalization: sender</Trace>
    <Trace level="1" type="T">Sender scheme external = XIParty</Trace>
    <Trace level="1" type="T">Sender agency external = http://sap.com/xi/XI</Trace>
    <Trace level="1" type="T">Sender party external = AVTItalie</Trace>
    <Trace level="1" type="T">Sender party normalized = AVTItalie</Trace>
    I ve tried to (cf. /people/saravanakumar.kuppusamy2/blog/2005/01/20/configuration-tips-for-a-business-serviceintegration-process-to-send-back-ale-audit-idoc ):
    1. add a logical system name "ACYAVTFBC1" in "Adapter specifier Id" of "AwayOrders"
    In the runtime cache > services an entry appears for " ... Logical System | AVTItalia | ACYAVTFBC1...".
    2. declare "AVTItalia" as a business partner in SLD with the logical system name
    Plz help!

  • Unable to convert the sender service PPG to an ALE logical system

    Hello all,
    maybe anybody can help or give me further information.
    I have set up a scenario  to send IDOC from a business system  ( ERP )  to a business service ( EXT ).
    Receiver is a linux system so I use the FTP-FILE adapter as communication channel.
    The send-process is so far ok.
    Here my tests:
    1)  exclude the specific IDOC  in  IDXNOALE table  (  means no technical acknowledgment for this IDOC ) 
         result :
         a)  message in SXMB_MONI:   status-flag: processed,   acknowledgment-flag:  not in use
         b)  message in RWB-Monitor:  Sender ERP  -->   Receiver EXT   ok 
    2) But I would like to have a system status.....   here  now the problem
        add specific IDOC into IDXNOALE table   ( for request acknowledgments )
        result: 
        a)  message in SXMB_MONI:  status-flag: processed,   acknowledgment-flag:   acknowledgment not possible
                                                   -->  error message:  unable to convert the sender service EXT to an ALE logical system
        b)  message in RWB-Monitor:  there are now two message, 
             first:        Sender ERP  -->   Receiver EXT   =   ok 
             second:   Sender EXT --->   Receiver ERP  =   system error 
                             Receiver-Interface is :  http/ww.ahlstrom.com/EXT/ MI_IN
       3)  furhter tests:
            a)  change FTP apdapter channel  ( put some wrong settings )
                  message in SXMB_MONI:   status-flag: processed,   acknowledgment-flag:   contains system errors
                  message in RWB-Monitor  3 messages  (  one ok,  and two error messages )
             b)  changed only the receiver communication channel to HTTP  ( other extisting scenario )
                  then the acknowledgment works fine wihout errors.
                  I'm  wondering, but here Receiver-Interface  is:   http://sap.com/xi/xI/Message/30/Acknowledgment
    Summary:  The process works,  but strange:
                      message in SXMB_MONI: unable to convert the sender service EXT to an ALE logical system
                      message in RWB:  system error
                      No problems with HTTP adapter
    Regards,
    Reinhard Doeker

    Hi,
    Addition to the above said by Udo...
    for routing the ack back to the sender system you need to create communication channel of type idoc with name as Ack.....
    http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/f6d2d790-0201-0010-9382-b50b499b3fbe?quicklink=index&overridelayout=true
    Check the above link section 3.2
    HTH
    Rajesh

  • Unable to convert the sender service ABC_Service to an ALE logical system

    Hi,
    I have a JMS (Party) --> PI --> IDOC scenario.
    Party: ABC_Party
    Service: ABC_Service
    I am getting the error Unable to convert the sender service ABC_Service to an ALE logical system when I test the scenario using RWB -> Component Monitoring -> Integration Engine -> Test Message.
    I have already done the below settings:
    1) Defined Header Mapping in Receiver Agreement for IDOC (Sender Party, Sender Service and even Receiver Service are specified)
    2) Business Component (ABC_Service) -> Adapter Specific Identifiers -> mentioned details for SAP (IDOC) system.
    The scenario works perfectly fine for a party-less communication JMS -> PI -> IDOC
    Have already seen:
    /people/michal.krawczyk2/blog/2005/03/29/xi-error--unable-to-convert-the-sender-service-to-an-ale-logical-system
    /people/rajeshkumar.pasupula/blog/2009/03/16/unable-to-convert-the-sender-service-to-an-ale-logical-system
    Thank you,
    Pankaj.

    You need to create party if its a B2B scenario
    Under Identifiers
    under agency select any standard agency , scheme name will automatical;ly get populated and name you can give manually as sender name
    Please refer this for more details
    http://help.sap.com/saphelp_nwpi71/helpdata/en/b9/64663c7a6c2545ae292fb26d8c33c4/frameset.htm
    http://help.sap.com/saphelp_nw04/helpdata/en/81/104bb1fbab254c8644877c7f856bbf/content.htm
    Re: Party Configuration
    In case of cross company process it is required
    Regards
    Ninad
    Edited by: Ninad Sane on Nov 18, 2010 11:17 AM

  • Once again: Unable to convert sender service to an ALE logical system

    Hi,
    I know there's a lot of threads regarding that error but I didn't find one that fits to our current scenario:
    IDoc -> XI -> File
    We have checked if the logical system name in SALE (of sending system) fits to the one in the business system and it does now.
    It didn't fit at first but we've changed it in the SLD and reimported the business system.
    We still get the same message:
    <SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_INV_SND_SERV</SAP:Code>
    <SAP:Stack>Unable to convert sender service to an ALE logical system</SAP:Stack>
    There is no logical system entered in the receiver business system. Do we need that? But of which logical system?
    Thanks for any advice
    Karsten

    Hi,
    Acknowledgments
    Receiver adapters that run on the Adapter Engine support system acknowledgments if they are requested by the sender.( Ex : Idoc----File). Here by default Idoc has the inbuilt feature of requesting the Ack.
    Acknowledgments are triggered when a message is successfully processed by the adapter or if an error occurs while it is being processed. Receiver adapters do not support application acknowledgments.
    Sender adapters of the Adapter Engine do not request any acknowledgments
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/903a0abc-e56e-2910-51a8-9dc616df56eb
    Regards
    Seshagiri

  • Unable to convert sender service BPM_Name to an ALE logical System

    Hello ,
    While sending from BPM to R/3 ( IDOC) i am getting the following error :
    "Unable to convert sender service <BPM_Name> to an ALE logical system"
    Please kindly advice,
    Reddy

    Hi Bujji,
    I just remembered that you have to maintain your adapter specific parameters for your business process. The side effect however is that you have to define the business process name as logical system in your receiving SAP system and that you have to maintain partner profile settings.
    The answer to your question is there in this Blog:
    /people/michal.krawczyk2/blog/2005/03/29/xi-error--unable-to-convert-the-sender-service-to-an-ale-logical-system
    If the above solution doesnot work.....
    You can also try this, don't enter the "adapter specific settings" on the Integration Process. Instead enter a "Header Mapping" Sender Service in the Receiver Agreement. this should be the real sending system.
    When you enter "adapter specific settings" in a BPM, the receiving SAP systems ALE layer thinks the sending system is your BPM - using the method discussed here we are overriding that so that ALE see's that its communicating with the real sending system.
    I hope it helps....
    Regards,
    Abhy
    Message was edited by: Abhy Thomas

Maybe you are looking for