Unable to convert partner to IDoc sender partner

In XI 2.0,we are facing a problem while trying to send idoc out of XI to SAP R3 system.We created Business Systems without specifying ALE logical system name,but later we corrected this.
Even then we are getting this error:
<SAP:Code p1="I::000" p2="SRMSUS_BUSS_SYS" p3="" p4="">IDOC_ADAPTER.SENDER_BSI_INCORRECT</SAP:Code>
  <SAP:Text language="EN">Unable to convert partner to IDoc sender partner</SAP:Text>
We have created port in IDX1 in XI for R3 system.
Suggest us ?
regards
Vishal

Vishal,
Add your agency and schema values in both party and receiver idoc channel (tab identifiers),
it should be something like
BS_ (your R/3 system system), Schema ALE#KU# (KU if its customer)
Thanks,
Pavan

Similar Messages

  • IDoc adapter inbox: IDoc sender partner is initial

    Hi,
       I have requirement to read the IDOC flat file and post IDOCs to SAP. As suggested in the following guide I am using report RSEINB00 to post IDOCS. This report basically calls the function module IDOC_INBOUND_FROM_FILE.
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/xi/xi-how-to-guides/how%20to%20convert%20between%20idoc%20and%20xml%20in%20xi%203.0.pdf
    While executing the IDOC_INBOUND_FROM_FILE I am getting error:
    "IDoc adapter inbox: IDoc sender partner is initial".  
    Please advise.
    Thanks
    Rajeev Gupta

    Hi,
    Idoc will be processed in SAP ECC based on the sender details (snprn,sndpor,sndpfc...) of idoc control record..
    instead of different partners name sending in the sender details of control record ...pass the value of the PI logical system name in SNDPRN.... (use only one and this is common for all partners...) any how data records of idoc will have the needed partner details...
    In SAP ECC you need to have this logical system ...to process the received idocs..
    thats it... Hope you got
    Regards
    Rajesh

  • IDOC Sender Partner has changed after transporting Integration Directory ob

    Greetings,
    After we did a transport from QA to PR for a new interface (Intergration Directory) objects were transported,
    The sender partner has changed to QA in all outbound IDOCs generated in XI PR.
    I checked the adapter-specific identifiers and it is showing as production.
    Any hint where I should check?

    Found it in the filesystem communication channel as QA and changed it to PR

  • HT4864 unable to convert Outlook 2007 to send or receive email

    I have postponed until almost the last moment (June 2012) conversion of my mobile me email address to the iCloud.  Alas, Apple has now forced me to abandon my quite functional MacBook Pro (which won't run Lion and thus is not compatible with iCloud).
    But I digress.  I am now relying upon my PC laptop with Windows 7 and Outlook 2007.  I have followed the instructions on the Apple support site and various alternatives suggested on other websites (e.g. use "p01-imap.mail.me.com" or "p02...." instead of "imap.mail.me.com" as the incoming mail server).  However, none of the variations works.  I always get error messages including "Log onto incoming mail server (IMAP):  Your server unexpectedly terminated the connection...." and "Send test email message.  None of the authentication methods supported by this client are supported by your server."
    What else should I try?
    Perhaps I should just abandon my iCloud/mobileme/mac.com address?
    Bob

    Maybe your firewall is blocking the ports
    I would troubleshoot by making a hotmail or gmail account and connect to to see if that works

  • Unable to convert sender XI party  to an IDOC Partner

    Hi,
         We are doing a IDOC-File scenario for which we got this error Unable to convert sender XI party http://sap.com/xi/XI / XIParty / UK to an IDoc partner .The receiver is a party. We have already set the adapter specific atttributes for the receiver service.

    R u using partner type customer.
    can u check the configuration refer the below blog.
    Wanna Party ?
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/b0b355ae-0501-0010-3b83-8f2bb566fa47
    chirag

  • Unable to convert sender party to IDoc partner

    Hi guys!
    I have read a lot of threads to this topic, however, I can't make my scenario working...
    I use Party as sender of document and need to send it to target (our) R/3.
    I have set up:
    Sender party: Cocoon, Sender Business SERVICE: IslandSys
    To target IDoc XML I map:
    SNDPRT - KU
    SNDPRN - D600
    SNDPOR - IslandLS
    In Party Identifiers:
    Agency: IslandSys
    Scheme: ALE#KU
    Name: D600
    Pertner profile - WE20 (target R/3)
    type: KU, No. D600
    In Business Service's Adapter Specific Identifiers: Logical System: IslandLS
    But the scenario doesn't work..
    What's wrong with the config?
    Thanx a lot for help!
    Olain

    <?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_PARTY</SAP:Code>
    <SAP:P1>http://sap.com/xi/XI</SAP:P1>
    <SAP:P2>XIParty</SAP:P2>
    <SAP:P3>Cocoon</SAP:P3>
    <SAP:P4/><SAP:AdditionalText/>
    <SAP:ApplicationFaultMessage namespace=""/><SAP:Stack>Unable to convert sender XI party http://sap.com/xi/XI / XIParty / Cocoon to an IDoc partner
    </SAP:Stack><SAP:Retry>M</SAP:Retry></SAP:Error>

  • Unable to convert sender service for IDoc to SOAP Scenario

    Hi,
    I tried to find the solution my way and by using the search function but without any success. I have the folowing scenario:
    SYS(my sap system) => IDoc => PI (Process Integration) => SOAP => XML
    When i send the IDoc to the PI System and open SXI_Moni the folowing error is shown:
    "Unable to convert the sender service receiver_service to an ALE logical system"
    I read about Adapter Specific Identifies so i go to ID->Service without partner->Business System->MyBusinessSystem(SYS) then in Menü on Services and checked Adapter Specific Identifies. They are like maintained in SLD.
    Next is a Cache refresh i tried a full one but no impact
    Then i tried a header mapping in receiver agreement. I mapped there the receiver party to the definied receiver party and the receiver_service to the service.
    I have no idea
    Thanks for help, be sure that helpful answers will be awarded
    regards
    Matthias
    P.S. What causes this error ? For my opinion ALE has already done all neccesary things (The Idoc is in PI System and the data is available in mesaage payload) so why didn't the pi map it and send it via Soap?

    Hi Matthias
    >>I dont know if its helpful but in SLD are only the system of our landscape so i have no entry for the external Party.
    Party information is generally not required to be maintained in SLD
    >>Adapter Specific Identifies
    What is the value you have given for sender Business system->adapter specific identifier. Is it the same as the partner profile name in sender SAPECC. if not try making them same.
    Regards
    Suraj

  • Partner profile to send Idoc to PI 7.4 system from ECC

    Dear Experts ,
    Do we need a partner profile to send Idoc to PI 7.4 system from ECC.
    or Just Port on TRFC is enough ..?
    if i need to create a Partner profile ...how to define a logical system and how Assign Logical System to Client... when there is no client for JAVA only PI system ..?
    thanks
    Shakif

    Hi Mohamed,
    You need to create a tRFC port on sending ECC system. The RFC destination selected in this port os the one created for IDOC transfer.
    Also you need a logical system, use client 000, i.e. PI1CLNT000.
    At last you have to create a partner profile to define the IDOC type used.
    Best Regards
    Harald

  • BPM -  IDoc to SOAP problem (Unable to convert sender service)

    Hi,
    I have a BPM scenario where I'm sending an Idoc from r/3 to XI to SOAP.  As part of my scenario I'm sending an acknowledgment (ALEAUD) back to R/3. 
    I'm getting Unable to convert sender service IP_BPEL_INBOUND_ORDER to an ALE logical system on the Ack back.
    So I usually know what to do when I get this, I do the SLD settings on the r/3 service and I'm OK.  But in this case, it's asking for those ALE settings on the Integration Process?
    I tried adding a logical system on it but now I'm getting the error that this is already used by the r/3 service.  So I'm not to sure what to do next???
    Rgds,
    Yves

    Ok do one thing, in you mapping take one field at target side (may be u can create one or use which is not been used yet) just map the standard function called Sender to this field in target.
    Now in Intergration Directory when you do the header mapping by using F4 do not map the business systems this time, just press the button "Etended Path" (m not sure abt the exact name of this button) not use the X-Path here and select that target field which you mapped with Sender function in mapping.
    How To Handle Acknowledgments for IDoc
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/903a0abc-e56e-2910-51a8-9dc616df56eb
    I hope this will solve your problem.
    Regards,
    Sarvesh

  • File-idoc     Unable to convert the sender service  to an ALE logical syste

    Hi experts
    iam working on file-idoc scenario ,iam getting the below error in sxmb_moni and RWB
    "Unable to convert the sender service  to an ALE logical system"
    i checked the partnetr profile, RFC(sm59) and IDX1 t codes.
    the connection is ok. but still i could figureout the problem.
    please suggest me
    Thanks
    vasavi

    Hi,
    Have u checked the logical system is added in the Sender Business service in the Integration Directory?
    Open the Buiness Service/System --> EDIT-ADAPTER SPECIFIC IDENTIFIERS
    then specify the logical system name.
    Go throgh the following link
    Troubleshooting  File-to-IDOC Scenario in XI.
    Regards
    Sridhar Goli

  • SOAP to IDOC: Unable to convert sender service BS to an ALE logical system

    Hello everyone,
    I have this scenario where i receive web services calls and have to integrate the received xml messages (idocs) into SAP R3 system.
    I allready reveive the message in my XI engine, but i'm getting this error (being  BS the name of my Business Service included in my external party):
    "Unable to convert sender service BS to an ALE logical system"
    I allready tried everything that is specified in this blog:
    The specified item was not found.
    Probably it doesn' fit my requirements. I'm not sure...
    Can anyone help ?
                                 Thank you in advance for any help
                                       Nuno

    - do u have the same logical name defined in the BS and in the Adapter specific attributes.
    also check if u have defined the logical system (SALE ) with the same name.

  • IDOC Receiver - Unable to convert sender service to ALE

    Hi!!!
    I am trying to configure the following scenario: FILE - XI - IDoc to R/3. 
    A business service called IDOC_Demo recovers from the server the file, and after mapping it, it tries to send it to IBP, the R/3 system using a IDOC Receiver comunication channel.
    IBP is configured in SLD.
    I have in XI System the RFC conexion, and I have define the port via TCODE IDX1.
    But it does not work, I am geting the following error:
    "Unable to convert sender service IDOC_Demo to an ALE logical system"
    I have checked the adapter specific identifiers, but I can not see anything wrong...
    I do not know what can I check! Could someone help me?! What can I do?
    Thank a lot!!
    Araitz.

    Thank you very much, but I still get the error message! Of course, I read your blogs Michal before posting the question, and they have been very useful, but still...
    In SLD I only have the R/3 system, the name is IBP and the business landscape and the logical system name (I do not know if this could cause a problem…).
    The connexion is IBP, and it works, and in idx1 I have configured a port, and its name is SAPIBP, using the IBP connexion.
    Design… I have imported the CREMAS.CREMAS03 IDOC, and I have done a mapping interface, I have disabled the EDI_DC40, and set “begin” and “segment” to 1.
    Configuration… I have created a business service, IDOC_Demo, that has a communication channel, sender, file type.
    And I have the IBP service. In adapter specific I can see: logical system IBP, and R/3 System IBP, client 100. If I push the “Compare with SLD” button, nothing happens… what should happen?
    IDOC_Demo receives the file, and via an Outbound, async interface, calls IBP, that receives the IDoc using a receiver IDoc type adapter…
    Now the receiver agreement has information in the header mapping, sender service, IDOC_Demo, receiver service, IBP.
    And I do not know why, but it does not work… any idea?
    Than you!
    Araitz.

  • IDOC control record mapping - Sender Partner number defaulted to log. sys.

    My PI scenario is file to IDOC scenario.
    I have ticked "apply values from payload" checkbox, so Sender Partner Number is being defaulted to logical system assigned to my business system.
    Logical system name has to be unique in PI. My understanding is that I can not have more than 1 business system with  the same logical system assigned to it.
    In SAP, I need to have idocs, coming from different businees systems through PI, set to have the same sender partner number,
    which is not possible when "apply values from payload = 'X' and messages are coming from different business systems.
    Calling all PI Gurus, have you got a workaround ?

    Hi,
    Idoc will be processed in SAP ECC based on the sender details (snprn,sndpor,sndpfc...) of idoc control record..
    instead of different partners name sending in the sender details of control record ...pass the value of the PI logical system name in SNDPRN.... (use only one and this is common for all partners...) any how data records of idoc will have the needed partner details...
    In SAP ECC you need to have this logical system ...to process the received idocs..
    thats it... Hope you got
    Regards
    Rajesh

  • Unable to convert sender XI party ... to an IDoc party

    Hi folks,
    I'm trying to implement the following scenario: Supplier (http) -> XI -> R/3 (IDoc).
    In order to realise this, we are using a scenario with a party. Sender party, scheme and Agency are identified correctly and i can even send the data to my mailadress by changing the routing to a mail adapter.
    But as soon as i try to send the received IDoc to the R/3 via an IDoc adapter i get the above error message.
    I also searched the SDN for corresponding entries but unfortunately most solutions will only work with a scenario without a party.
    I'd be glad if anyone could help me out.
    Regards,
    Stefan

    Thanks a lot for your answers. I tried different settings within the we20, but i always receive the same error.
    I've got the following information at hand:
    The supplier sends via an URL that specifies supplier name and service. In additon the suppliers backend and sending system are named inside the IDoc. In the end, i got the following information:
    URL-Sender:             ABC
    URL-Service:             http_integration
    Sender-Scheme:        XIParty
    IDoc-Sender:              XYZ
    IDoc-Receiver:            123
    Sender namespace:   urn:sap-com:document:sap:idoc:messages
    Any suggestion how to configure the we20 inside the backend system?
    Regards,
    Stefan

  • 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!

Maybe you are looking for

  • Is there a way to open a several paged document?

    hi, was just wondering if anyone knew how to access the rest of a documents pages from a PDF with out having to open each page separatly  when in illustrator? as whenever I try to open it I can only get to each page individually

  • CRM_ORDER_MAINTAIN and ACTIVE_SWITCH

    Hi experts, I am working as ABAP developers in CRM 5.0. We often use FM CRM_ORDER_MAINTAIN in our development, to create (or modify) several order types. I have heard about the ACTIVE_SWITCH input parameter of CRM_ORDER_MAINTAIN. It seems this parame

  • Phone memory not visible with USB, but visible wit...

    Hi, I just installed the latest Ovi Suite 2.1. My phone is the Nokia E72 with the latest firmware. When connecting the phone via USB, i get an S60 handset icon under My Computer, if i click it i see the memory card available as drive, but no trace of

  • [solved] dwm unicode problem

    My dwm 5.7.2 (also happens for a recent hg pull) statusbar fails to display unicode characters for window titles. Tested with Firefox, Sakura, urxvt and xterm. xprop gets it right however. I've tried with terminus and fixed. static const char font[]

  • Portal MSS Issues

    Hello People, I have been troubleshooting a Business Package Implementation for MSS on Portal 6.0. We have been getting Portal Runtime Exception whenever we click on Talent Development Specialist > Overview > services > Succession Planning > Maintane