XI - IDOC: ATTRIBUTE_INV_SND_SERV

Dear all,
I had a FILE - XI - IDOC scenario in which some vendor data was communicated. The scenario worked like a charm.
Now I have to use a multi-mapping: FILE - XI - 2*IDOC. So, I created the multimapping, the abstract interfaces, and the integration process. Now, the sender has changed from the system to the integration process. And now I get the following error at the IDOC adapter.
ATTRIBUTE_INV_SND_SERV
I have read some blogs and forum messages concerning LS names, however, it does not make sense to me as the previous scenario worked fine.
Can anyone help out?
Cheers.

> Hi,
>
> Now, your original business system is no longer the
> sender of the IDoc, but your Integration Process is
> the IDoc Sender.
>
> To resolve the error, either assign a Logical System
> Name to the Integration process in the Directory
> (under Service -> Adapter specific identifiers in the
> Integration Process), or assign the original business
> system as the sender in the receiver agreement.
>
> Kind regards,
>
> Koen
Hi Koen,
When I adjust the Adapter specific identifiers -which was empty- for my Integration Process, and I fill out an arbitrary name, the distribution model of r/3 cannot find a partner profile. Do I need to create then a new logical system in r/3 and corresponding partner profile for each Integration Process?
What am I doin' wrong???
Cheers
Message was edited by:
        A. Schotanus

Similar Messages

  • Idoc-to-File Scenario ATTRIBUTE_INV_SND_SERV Error

    Hi All,
    I am working on PI 7.1. I have an Idoc-to-File scenario. The scenario is working fine, but there is an 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>FILE_BC</SAP:P1>
      <SAP:P2 />
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText />
      <SAP:Stack>Unable to convert the sender service FILE_BC to an ALE logical system</SAP:Stack>
      <SAP:Retry>M</SAP:Retry>
      </SAP:Error>
    PI is trying to send an acknowledgment back to the Sender ECC system. But in the IDX_NOALE, 'Do not request acknowledgement' is already checked. Still there is this error. It doesnt show up in MONI unless the Acknowledgement message is clicked, but alerts are  getting triggered for these cases. Can anybody please help me in resolving this? I do not want the acknowledgements to be sent back to the ECC system.
    Thanks,
    Geetha

    Thanks everybody! It has got fixed. I just requested No acknowledgements.
    Geetha
    Edited by: Geetha on Nov 11, 2009 5:45 PM

  • Problem adapter idoc - file ATTRIBUTE_INV_SND_SERV

    Hello All,
    please help me for my problem on adapter in my system XI for a scenario idoc -> file an I have an message error.
    <b>xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
      <SAP:Category>XIAdapter</SAP:Category>
      <SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_INV_SND_SERV</SAP:Code>
      <SAP:P1>BS_ADONIX</SAP:P1>
      <SAP:P2 />
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText />
      <SAP:ApplicationFaultMessage namespace="" />
      <SAP:Stack>Unable to convert the sender service BS_ADONIX to an ALE logical system</SAP:Stack>
      <SAP:Retry>M</SAP:Retry>
      </SAP:Error></b>
    Please help if you have some idea BS_ADONIx is a business service.
    Thanks for your reply

    Steps IDOC to File.
    IN IR
    1. Import the IDOC in XI (input).
    2. Create a Data type of (output) i.e. file.
    3. Create a Message type of (output) i.e. file used the above data type.i.e.Step 2
    4. Create a Message interface of(output) .i.e file used the above messagetype. i.e.Step3.
    5. create Mappping select source as IDOC and target as Message type you created.
    6, In Interface mapping select source as IDOC and Target Interface Message Interface of file i.e.Step 4.
    In ID.
    Select the recevier determination of .
    1.select sender system as R/3 system recivr as File Bunisees system
    2. create interface determination select sender system as R/3 Sender interface as IDOC . in interface determination select inbound message whihc createdin step 4
    and message interface we created in step 5.
    3. create recevier determination sender r/3 interface IDOC and reciver File business system . so create reciver file adapter and assign to file business system
    Please reward points
    Thanks
    Sreeram.G.Reddy

  • IDOC Adapter error"ATTRIBUTE_INV_SND_SERV'

    I am doing small example like Using HTTP Client to submit Order Response XML from my browser and Converting Order Response XML file to an order response IDOC of type ORDERS05 idoc.  I have developed  all the necessary objects in Integartion Repository & Integration Directory and posted the Order Response XML file through HTTP client.
    I am getting the error message(in SXMB_MONI)like "Unable to convert sender service OrderResponse to an ALE logical system".
    Appritiate, if some one help me On this .
    Thanks
    Sudha

    For the business sytem you have to mention the adapter specific identifiers in the Integration Directory.
    Go to Int. Directory -> Double Click on your IDoc Business System -> Menu -> Service -> Adapter Specific Identifiers
    Maintain Logical System name and System ID and Client number.
    Check the following blog.
    /people/michal.krawczyk2/blog/2005/03/29/xi-error--unable-to-convert-the-sender-service-to-an-ale-logical-system
    regards
    Shravan

  • Error in IDOC - File scenario

    Hi Experts,
    This is my 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>INTEGRATION_SERVER_XID</SAP:P1>
      <SAP:P2 />
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText />
      <SAP:ApplicationFaultMessage namespace="" />
      <SAP:Stack>Unable to convert the sender service INTEGRATION_SERVER_XID to an ALE logical system</SAP:Stack>
      <SAP:Retry>M</SAP:Retry>
      </SAP:Error>
    OTHER ERROR  FOR  PAYLOAD OF  SENDER PART IS AS BELOW :
    The XML page cannot be displayed
    Cannot view XML input using XSL style sheet. Please correct the error and then click the Refresh button, or try again later.
    The character '>' was expected. Error processing resource 'file:///C:/Documents and Settings/ABC/Local Settings/Tempor...
    <?xml version="1.0" encoding="UTF-8" ?><ZZ/AFS/FUNACK><IDOC BEGIN="1"><EDI_DC40 SEGMENT="1"><TABN...
    Please Help,
    Regards,
    Study SAP

    Hi,
    The problem occurs when sender and receiver business system or business service does not have a logical system name.
    ID - Integration Directory
    Posting the IDOC'S into SAP R/3 System, sender and receiver business system or business service requires the logical system name. If the business system (Web As ABAP) does not have the logical system name, then add the logical system for business system.
    In technical system browser
    If business system type = Web AS ABAP, then add the Logical system in Technical System level and Save.
    If business system type = Third-Party, then add the logical system in business system level and Save.
    If the business service does not have the logical system name in ID, it needs to be configured as follows.
    Check the below screen shot which shows how to add the logical system for business service.
    Go to ID and click the Business service -> Services -> Adapter Specific Identifiers. Enter the logical system name and Save.
    Apply and activate.
    Hope this will help you.
    regards
    Aashish Sinha
    PS : reward points if helpful

  • Error in IDOC to SOAP

    I am doing IDOC to SOAP(3rd party) scenario and I get 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>
    I have searched the forums and there is lot of info on this,
    According to this blog
    /people/michal.krawczyk2/blog/2005/03/29/xi-error--unable-to-convert-the-sender-service-to-an-ale-logical-system
    He says Click on the Business System and see the adapter specific Identifiers,So do I have to click on my 3rd pary Business System here? since for IDOC sender there will be no BS.Am I correct.
    Thanks

    Hi  Guest
    first login to SDN with good name
    This problem occurs due to  INVALID SENDER SERVICE
    kindly check in your configuration whether you have given a valid name to your sender service and also check the conditions in RCVR deetermination
    if not modify that and activate again .Make a CACHE refresh
    hope this will work for you
    Regards
    sandeep
    PS if helpful kindly reward good points

  • Http - iDoc scenario - ID

    Hi,
    HTTP - XI - iDOC  is my scenario.....
    i am facing problem in iDoc adapter...
    the error category is idoc adapter and the error id is "ATTRIBUTE_INV_SND_SERV"
    Which RFC destination and port should in mention in Communication Channel? Either the receiver or XI?
    forward your suggestions....
    Thanks,
    RPN

    hi rpn,
    check this links
    Go to Int. Directory -> Double Click on your IDoc Business System -> Menu -> Service -> Adapter Specific Identifiers
    Maintain Logical System name and System ID and Client number.
    Check the following blog.
    The specified item was not found.
    Unable to convert sender service to an ALE logical system
    ATTRIBUTE_INV_SND_SERV
    XI 3.0, Party and Service problems (IDoc inbound)
    Trouble shooting file to IDOC and IDOC to file
    Troubleshooting  File-to-IDOC Scenario in XI.
    https://www.sdn.sap.com/irj/sdn/wiki?path=/display/xi/error%2bhandling%2bin%2bfile-idoc%2bscenario
    see the below links
    ALE configuration for pushing idocs from SAP to XI
    Introduction to IDoc-XI-File scenario and complete walk through for starters.
    idoc settings Configuration steps required for posting idoc's(XI)
    Also
    /people/sravya.talanki2/blog/2005/10/27/idoc146s-not-reaching-xi133-not-posted-in-the-receiver-sap-systems133
    IDOc testing - Generate Test Case for an IDOC Scenario
    regards
    srinivas

  • File to IDOC scenario error...

    Hi all,
    we hhave created an File to Idoc scenario .
    we are getting the following error in SXMB_MONI t-code.
    <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    - <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>BUS_SENDER</SAP:P1>
      <SAP:P2 />
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText />
      <SAP:ApplicationFaultMessage namespace="" />
      <SAP:Stack>Unable to convert sender service BUS_SENDER to an ALE logical system</SAP:Stack>
      <SAP:Retry>M</SAP:Retry>
      </SAP:Error>
    can any one plz say wat this error might be..
    TIA
    Regards,
    Raj

    Hi,
    The problem occurs when sender and receiver business system or business service does not have a logical system name.
    ID - Integration Directory
    Posting the IDOC'S into SAP R/3 System, sender and receiver business system or business service requires the logical system name. If the business system (Web As ABAP) does not have the logical system name, then add the logical system for business system.
    If business system type = Web AS ABAP, then add the Logical system in Technical System level and Save.
    If business system type = Third-Party, then add the logical system in business system level and Save.
    If the business service does not have the logical system name in ID, it needs to be configured as follows.
    Go to ID and click the Business service -> Services -> Adapter Specific Identifiers. Enter the logical system name and Save.
    Apply and activate.
    hope this will help you.
    regards
    Aashish Sinha
    PS : reward points if helpful

  • XI 3.0, Party and Service problems (IDoc inbound)

    Hi,
    The scenario is:
    Flatfile (J2SE plain adapter) => XI => IDoc => R3
    The basic functionality <b>Service Without a Party</b> works ok. But I run into a restriction when trying to have more than one <b>Business System</b> having the
    same <b>Logical System Name</b> (XI doesn’t allow it). Basically I don’t want to have one unique <b>Logical System Name</b> for every business scenario, especially when they come from the same legacy system (<b>Technical System</b>).
    Is it possible to have only one <b>Logical System Name</b> for all the interfaces that comes
    from the same legacy application (or even from all the legacy systems)?
    Tried even to do the same with <b>Party</b> objects, but there I run into errors (can’t even get the IDoc through):
    <b>"IDOC_ADAPTER">ATTRIBUTE_INV_SND_SERV</b>
    or
    <b>"IDOC_ADAPTER">ATTRIBUTE_INV_RCV_PARTY</b>
    depending on the configuration.
    Is there any documentation about how these configurations
    should be made?
    br.samuli

    Hallo Samuli,
    i guess, you have the same problem that has already been discussed in here. That is if you create a new Business Scenario in the Configurator you can not see your business system you want to use. But that is not an error and also not a restriction of XI as you will discover in the post "can't assign business system twice". It is possible to use the logical system name of a legacy system for all interfaces coming from this system, everything else would not make sense.
    Here the link to the message: can't assign business system twice
    Best Regards
    Christine

  • Problem sending IDoc

    Hi all,
    I'm trying to sent an IDoc from XI to R/3 via the IDoc Adapter
    should I create a partner profile (we30) on the XI system like I have done on the R/3 system?
    I get the following Error:
    "Unable to convert the sender service to an ALE logical system"
    IDOC_ADAPTER">ATTRIBUTE_INV_SND_SERV
    Thanx - Thomas

    Hi Thomas,
    The Partner Profile should be with respect to the Logical System Name.
    Internally, during runtime, IDOC adapter fills up the IDOC control record with the corresponding Logical system names for the sender partner (SNDPRN) and Receiver Partner (RCVPRN) . If your Business Systems have the correct logical system name assigned to them and you can see the same in Business System--> Adapter Specific Identifiers.
    These links will definitely help you to get the Concept right.
    Check Michel Krawczyk’s
    Mastering IDoc Business Scenarios with SAP XI
    And
    /people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters
    /people/ravikumar.allampallam/blog/2005/02/23/configuration-steps-required-for-posting-idocsxi
    Cheers...
    Vasu
    <b>** REward POints if found useful **</b>

  • IDOC Ack from BPM to SAP R3 runs into an error

    Hi All,
    I have a scenario which sends an DEBMAS IDOC to an Integration Process "IP_SPLIT_Site" which process the IDOC and sends it to multiple systems.
    When the IDOC is sent from SAP R3 to the receiving Integration Process "IP_SPLIT_Site" in XI, it is processed successfully.
    Since the SAP system is expecting an acknowledgement from the receiver of the IDOC, the integration process "IP_SPLIT_Site" tries to send back an acknowledgement for the IDOC which runs into an error because it is not able to convert "IP_SPLIT_Site" into an ALE logical system.
    The error displayed is :
    Unable to convert the sender service IP_SPLIT_Site to an ALE logical system
    Error code : ATTRIBUTE_INV_SND_SERV
    I am getting this error in all my scenarios where an IDOC is sent to an Integration Process.
    Is there any solution avoid this error?
    Thanks & Regards;
    Bbnu

    Hi Michal
    The 1st approach seems to be helpful.
    about the 2nd approach if i am sending the Ack through a separate send step in BPM then i suppose it would show the same error "Unable to convert the sender service IP_SPLIT_Site to an ALE logical system".
    OR
    Do you mean to say that we could send a separate message of type ALEAUD to the SAP system?
    for 3rd approach, i wouldn't wanna handle many partner profiles.
    Thanks for your reply,
    Rgds;
    Bbnu

  • Acknowledgement from a BPE fails inside an IDoc to BPE-scenario

    Hi,
    we have PI/7.0 SPS 10.
    My scenario is quite simple: IDOC --> BPE (in XI) --> IDOC back to R3
    Everything works good ... besides the acknowledgements.
    I'm getting the error message
    <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>IP_KVVKS_CONTRL</SAP:P1>
      <SAP:P2 />
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText />
      <SAP:ApplicationFaultMessage namespace="" />
      <SAP:Stack>Unable to convert the sender service IP_KVVKS_CONTRL to an ALE logical system</SAP:Stack>
      <SAP:Retry>M</SAP:Retry>
      </SAP:Error>
    I know, that the integration process has no logical system - that's true!
    I know, that for "normal" IDocs sending from a BPE to SAP/R3, I can use a header mapping to enter a correct logical system.
    But how can I do it with acknowledgements. Inside the PE I wanna send a transport acknowledgement back to R3.
    Where can I enter a logical system for a BPE?
    I tried to enter the logical system in the "adapterspecific ident." of the BPE - but it's not possible to enter a logical system two times (the logical system was already in use).
    Afterwards I run the report IDX_NOALE to disable acknowledgements - works fine, but my boss wanna see the acknowledgements
    What can I do?
    Thank you all!
    regards
    Wolfgang Hummel

    Hi,
    There is an option in the Receiver IDOC adapter called,<b> Restore Original Parties For Idoc Acknowledgements</b> . Have not tried this, but I think this option wil be able to help you out.
    <i>Restoring Original Partners for Acknowledgments
    If you set the relevant indicator, the original partners from the IDoc request message are used for acknowledgments. This means you no longer have to maintain the alternative identifiers (for party conversion) in the Integration Directory.</i>
    http://help.sap.com/saphelp_nw04/helpdata/en/96/791c42375d5033e10000000a155106/content.htm
    Regards
    Bhavesh

  • Reg:Receiver IDOC Adapter

    Hi Guys,
                I am doing File to IDOC Scenario ,i got error as
    IDOC_ADAPTER">ATTRIBUTE_INV_SND_SERV
    Unable to convert the sender service BS_ITSC_QASFTP_D to an ALE logical system
    in MONI, can anybody give me solution
    Thnaks

    goto Service--> Adapter specific identifiers.
    You should see Logical system, and R/3 system ID.
    If not, press Compare with system landscape directory.
    If this does not help, check the definition in the SLD .
    Did you define the correct logical system for the client in the technical system/business system?
    If not please define the correct logical system in SLD> delete Business system in ID> re import business system.
    regards,
    pradeep A.

  • Problem with File to IDOC scenario

    Hello,
    I try to implement our first scenario to IDOC.
    In TOC SXMB_MONI I have to errors
    1. <SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_INV_SND_SERV</SAP:Code>
    2. <SAP:Stack>Unable to convert sender service aaa_Sender_Service to an ALE logical system</SAP:Stack>
    Any idea how I can solve this problems?
    Elad

    HI,
    I think u have not done the configuration at the R3 end....
    Just go through the below step by step process of FILE to IDOC. and check whether u have done the same configuration for ur scenario....I dont know what all configuration u have done....
    File To IDOC - Part1 (SLD and Design):
    https://www.sdn.sap.com/irj/sdn/wiki?path=/display/profile/2007/05/11/fileToIDOC&
    File To IDOC - Part2 (Configuration):
    https://www.sdn.sap.com/irj/sdn/wiki?path=/display/profile/2007/05/11/fileToIDOC-Part2+(Configuration)&
    File To IDOC - Part3 (Steps required in XI and R3):
    https://www.sdn.sap.com/irj/sdn/wiki?path=/display/profile/2007/05/11/fileToIDOC-Part3(StepsrequiredinXIandR3)&
    Thnx
    Chirag

  • Gettin error in msg monitoring --webservice to idoc

    Hi all,
    While sending the data from webservice to Idoc I am gettin error like this.
    <?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>BS_Exten_Wrnty</SAP:P1>
      <SAP:P2 />
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText />
      <SAP:ApplicationFaultMessage namespace="" />
      <SAP:Stack>Unable to convert the sender service BS_Exten_Wrnty to an ALE logical system</SAP:Stack>
      <SAP:Retry>M</SAP:Retry>
      </SAP:Error>
    checked with soap-its working fine .i think problem  with idoc.
    Please suggest
    Abhishek

    hi
    for this error
    Unable to convert the sender service BS_Exten_Wrnty to an ALE logical system,check blog
    The specified item was not found.                              
    regards
    kummari

Maybe you are looking for

  • Pop List and Developer Toolbar

    Hi every body, I love HTML DB , It a cool and nice thing I need your help folks, 1. How can I hide the developer toolbar for some user. 2. How can I build one page showing master-detail rel, I need to show Depts as a select list then when I select a

  • ALV GRID Using oo abap example

    Hi Friends, I am new to oo abap, Can any one give me a basic example how i can create alv grid in oo abap. regards, DVNS

  • Requisition for approval using - Restricted Recruiter role

    Hi, We have implemented SAP eRec EHP4. As of EHP3 the restricted recruiter was only able to create requesition in Draft mode and release the requisition for approval. We are using WD on SAP EHP4. We have provided SAP_RCF_RES_RECRUITER_ERC_CI_2 role i

  • Checking for cancel in a JOptionPane

    Hey, I've been learning Java for about 2 months or so now, know quite a lot of the basics but i'va ran into a problem. Im doing a program which takes in some user input using: double d = Double.parseDouble(JOptionPane.showInputDialog("Enter a number"

  • Using Lightroom Mobile to sync photos to desktop – proper workflow?

    Just wondering what people suggest as a workflow for importing photos taken on a cameraphone into a Lightroom library. I want the photos to be saved into the same folders on my hard drive that the rest of my photos go into (Pictures > 2014 > 8 > 3 et