Handling acknowledgement for sender idoc from multiple receivers

Hi,
Problem: Sender IDOC mapped to multiple FILE receivers. So sender system is SAP, receivers are BS_SYS1, BS_SYS2 and BS_SYS3. The partner profile for IDOC is set as BS_SYS. Due to this, I can enter BS_SYS in the Adapter-Specific Identifiers of one of the services say BS_SYS1. But all three will send acknowledgements and the ack messages for BS_SYS2 and BS_SYS3 error out in MONI due to
'Unable to convert sender service BS_SYS2 to an ALE logical system' and 'Unable to convert sender service BS_SYS3 to an ALE logical system'. How do I solve this since I am not able to set BS_SYS in all three services/adapter-specific identifiers box at the same time.
Anyone have this issue before? I am guessing one option is to create logical systems BS_SYS2 and BS_SYS3 in SAP and have the aleaud messages routed to these logical systems. But when there are say scores of receivers, it is a clumsy solution.
Thanks
JB

007,
nice to have here
You have alternatives:
1. Just use one business system with different inbound interfaces / receiver agreements / communication channels and conditions at interface determination
2. Create a Business Process which is doing the split. This could lead to some minus performance but you would be able to handle the acknowledgements in a senseful way (you get 3 ackn for one send msg)
Regards,
Udo

Similar Messages

  • QRFC/TRFC for sending idocs from SAP system to XI

    Hi experts,
    The standard program RFFOEDI1 generates payment orders - first PEXR2002 and then EUPEXR idocs. These idocs are to be sent to the bank from SAP through XI. Bank partner profile is maintained. But these idocs because of TRFC are not getting sent in the order in which they are generated by the SAP system. So I changed the bank partner profile settings from TRFC to QRFC and gave the rule name as first 16 of mes type. But the idocs are struck in the SAP system. Is there any standard program to be run to send the idocs out from SAP system or is it automatic.
    Please suggest a standard method which is to be followed to send the idocs in the same order in which they are getting generated for the scenairo above.
    Regards,
    Asha

    Hi Asha,
    As you said Idocs are stucking,
    To send Idocs to XI, you must have maintain some settings in XI to receive Idocs. Once they are done properly .in R3 side standard way to send idocs to XI is Maintaining<b> <i>Change Pointers</i></b> and shedule the programe to trigger that most of Standard idocs will have standard programs to catch change pointers and send them to external system.
    and to maintain the same order of idocs there is a setting called Quality Of Service in XI side ,that option should be set to Exactly Once In Order .
    Regards,
    Ramesh.

  • How to configure queues for sending IDOCs from XI in the same order receive

    Hi,
       We are collecting IDOCs and sending them to XI using a background job (RSEOUT00) from R/3. When XI receiving these collected IDOCs, it's forwarding the received IDOCs into different queues for processing them and sending them to receiver system. Some times some queues are taking longer time to process the received IDOC and in the mean time the latest IDOC received getting processed and sent to receiver system. When the information related to this old IDOC is sent out to receiver system after the latest IDOC information is  sent to due to delay in Queue processing, we are getting errors in the receiver system. Can somebody explain the steps to configure queues to process the IDOCs in the same order they received from R/3.

    Hi,
    Why not tunnel all the IDOCs to one queue for processing ?
    Cheers
    Colin.

  • Sending meesages to multiple receivers

    Hi All,
    Is it psossible to send an output messages to mutiple receivers without using BPM. If so then how to do it.
    Thanks
    Abinash

    Hi Abinash,
        For sending this to multiple receivers you dont have to use BPM. You can do it by putting the condition in deciding your receiver business system in your receiver determination. For each business system which is there as a receiver you need to provide individual interface determination also...
    Cheers
    JK

  • Message SR 053 when i send idoc from SAp R/3 4.6C to PI 7

    Hi,
    I try to send idoc from SAP r/3 4.6C to PI 7. I had made  ALE configuration in my sender system ( SAP 4.6C) but idocs are not sent to PI. In SM58 i have message "Name or password is incorrect (repeat logon)". Yet i'm sure that user and password are correct because if i test RFC destination using SM59 , test is OK.
    Is somebody can help me ?

    Hi,
    In R/3 :
    my RFC destination is type 3 and point to XI. The port in the partner profile  point to this RFC destination. ( all seems good !).
    In Xi : i created a port and i load manually idoc in idx2 to be sure that RFC destination was OK. Nothing in IDX5.
    When i send idoc MATMAS using BD10 from R3 to Xi i have something very strange: first the message B1 038  "1 master IDocs set up for message type MATMAS" and just after
    the XI logon screen  appears !! Then message "1 communication IDoc(s) generated for message type MATMAS" and this idoc stay in SM58 with message "Name or password is incorrect (repeat logon)".
    Somebody can give me requires caracteristics for XI user used in R/3 RFC destination ?

  • Unable to send IDOCs from SAP PI 7.3 system to a NON-SAP system

    Hi Experts,
       We have a simple file to IDOC scenario in our SAP PI system. There is no mapping as the file is already in the IDOC-XML format.
    However , the target system is a NON-SAP system. We are using a TCP/IP RFC destination to connect to it.
    Here are the settings we have done,
    1) Creates a 3rd party technical system and business system in SLD.
    2) We have assigned a logical system name for the business system (LSKABA100).
    3) Created a port in IDX1 with the same name LSKABA100 and assigned the TCP/IP RFC destination. The RFC destination is pinging fine.
    4) Imported the metadata for the IDOC from a SAP port and copied the same to LSKABA100 port.
    5) Created the sender agreement, receiver determination, interface determination and receiver agreement in ID.
    When we send the file, there is an error on SM58 transaction of our PI system. It says "RFC_ERROR_SYSTEM_FAILURE: IDocException occurred."
    Other than that it does not provide a lot of details.
    We have seen this thread and this blog but did not get any break through.
    Please help us, if someone has any ideas.
    Best Regards,
    Ravikanth Talagana

    Hi all,
        I am not using any SAP Jco user either in my config or in the RFC destination.
    What is the user id that needs to have the authorization?
    I am using a TCP/IP RFC destination and it does not have any user id/pwd.
    There is also, no problem while doing a connection test to the RFC destination.
    Best Regards,
    Ravikanth Talagana

  • Send IDoc to Multiple Ports

    Hi,
    I have a custom IDoc message type YYY17101[Custom Type]. I need to send IDoc using this message type to 2 different rfc destination. The two RFC are
    1. SAP R/3 system
    2. XI system
    My question is which partner profile type i have select to send IDoc using message type YYY17101.
    Can i use partner profile type LS for sending IDoc to SAP R/3 and Partner pofile type US for XI system?
    Thanks
    aRs

    Hi aRs,
    Your challenge is in fact not so very difficult.
    First you define both R/3 and XI as an LS-type partner in your system, since both systems need to receive a message from your target system.
    Then you must use transaction BD64 to create a modelview (or choose in SALE the path Modelling and Implementing Business Processes --> Maintain Distribution Model and Distribute Views).
    Create your own NEW model.
    Use Add message type to add your specific message and supply your own LS system as source and the first target LS system (R/3).
    Use again Add message type to add again your specific message and supply your own LS system as source and the second target LS system (XI).
    If you view your model you will see ONE source system (your own) and TWO target systems (each with the same message below it).
    You can add filters to the message (to prevent incorrect messages to be send) if these are defined in your own IDoc.
    Now you can distribute this model to the target systems (in the menu choose: Edit --> Modelview --> Distribute.
    If the partners in question can be reached this goes OK.
    If all went well, go to the target systems and start transaction BD64 and select the model there. Then choose from the menu: Environment --> Generate partner profiles.
    At this point your ALE customization is complete and communication has been setup.
    So as you see, it is possible.
    Regards,
    Rob.

  • Sending IDoc from R/3 to XI -ongoing

    Hi,
    With reference to my previous errors while sending IDoc to XI from R/3 system. I have resolved errors with help of Seshagiri and Kummari advise and help. But now I am getting new kind of error, while sending IDoc from R/3 its getting passed from R/3, but while checking it in XI throug SXMB_MONI I am getting below error:
    <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    - <!--  Request Message Mapping
      -->
    - <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
      <SAP:Category>Application</SAP:Category>
      <SAP:Code area="MAPPING">EXCEPTION_DURING_EXECUTE</SAP:Code>
      <SAP:P1>com/sap/xi/tf/_MM_POCreateIdoc_</SAP:P1>
      <SAP:P2>com.sap.aii.utilxi.misc.api.BaseRuntimeException</SAP:P2>
      <SAP:P3>RuntimeException in Message-Mapping transformatio~</SAP:P3>
      <SAP:P4 />
      <SAP:AdditionalText />
      <SAP:ApplicationFaultMessage namespace="" />
      <SAP:Stack>com.sap.aii.utilxi.misc.api.BaseRuntimeException thrown during application mapping com/sap/xi/tf/_MM_POCreateIdoc_: RuntimeException in Message-Mapping transformatio~</SAP:Stack>
      <SAP:Retry>M</SAP:Retry>
      </SAP:Error>
    Can any one advise me on this?
    Thanks & Regards
    Manish

    Hi,
    There were so many Mapping Objects under different Namespaces and under that different Message Mapping trees.
    Under one tree I have tested the XML message and found the below error:
    Cannot produce target element /ns0:MT_POFile/POItem/Price. Check xml instance is valid for source xsd and target-field mapping fulfills requirements of target xsd Cannot produce target element /ns0:MT_POFile/POItem/Price. Check xml instance is valid for source xsd and target-field mapping fulfills requirements of target xsd
    Kindly check if this is the correct error I am getting related to SXMB_MONI error message.
    Regards,
    Manish

  • Sending IDOC from R/3 to MII error

    Hi,
    We are trying to send IDOC from R/3 4.7 to MII 12.1 (SP8 patch 9 on NW CE 7.11).
    We followed the guide below:
    http://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/3861e693-0e01-0010-e791-9b44d2693e6c
    Connection of message listener to R/3 works fine.
    RFC connection test from R/3 to message listener was successful.
    But when we try to do model distribution we get this error " - Communication error occured. Server repository could not create function template for 'MODEL_VIEW_REPLICATE'.
    Maybe someone encountered this error and can help to resolve it.
    Thanks in advance.

    Hi Michael,
    What do you mean by "manually registered the ProgID"? The message listener configuration property is as below:
    ProgramID:  MII_IDOC_CONNECT_5
    MaxReaderThreadCount:  1
    SAPClient:  800
    UserName: GAOMX
    Password: xxxxxxxx
    Language:  EN
    ServerName:  blade01a.memc.com
    PortNumber: 00
    BindingKey:  XMIIIDOC
    And also, following is error message found from LOG VIEWER of the MII server:
    here is one
    Message: not supported FunctionModule MODEL_VIEW_REPLICATE for IDocActivationSpec
    Date: 2011-07-21
    Time: 15:30:18:060
    Category: /System/Server/Connector/Rfc
    Location: com.sap.mw.jco.jra
    Application: sap.com/sapjra~xMIIIDOC05
    Thread: Thread[Managed_Application_Thread_20,5,Managed_Application_Thread]
    Data Source: j2ee/cluster/server0/log/system/server_00.log
    and another one
    Message: Server repository could not create function template for 'MODEL_VIEW_REPLICATE' caused by: java.lang.RuntimeException: not supported FunctionModule MODEL_VIEW_REPLICATE used with IDocActivationSpec registered for MII_IDOC_CONNECT_5 on system blade04a_MIT_00
    Date: 2011-07-21
    Time: 15:30:18:061
    Category: /System/Server/Connector/Rfc
    Location: com.sap.conn.jco
    Application: sap.com/sapjra~xMIIIDOC05
    Thread: Thread[Managed_Application_Thread_20,5,Managed_Application_Thread]
    Data Source: j2ee/cluster/server0/log/system/server_00.log
    Thanks,
    Mike

  • Error sending IDOC from external Java application to Sap ERP system

    Hi Experts!
    When I try to send Idoc from Java application to XI an error occurs : no service for system CLNTJAVA, client in Integration Server.
    My question is: What value the setSenderPort() is excepting?The Java third party business system's logical name or the ERP business system's logical name where the JCO can be found?I tried both of them, but still have the problem.
    Please help. I read all threads about this error, but non of those can help me.
    My relevant java sourcecode:
                doc.setSenderPort("CLNTJAVA");
    The XI documentation says that:In the case of non-SAP senders, the entry in the SNDPOR field is interpreted as a logical system name, and the corresponding business system is searched for in the runtime cache.
    Both case(third party business sytem and erp business system) I have configured the ID    i think correctly. I  made a business systems,I configured the adapter specific identifies,I  made the IDX1 port,I made the RFC destination,I polled the IDOC type with IDX2 transaction, I have made full cache refresh,I configured the INTEGRATION_DIRECTORY_HMI rfc destination,but I do not made any communication channels, receiver determinations, receiver agreement.
    My configurations if it can help for you.
    Hostname:sapsp5
    System name: NE2
    Clients:
    000 ERP
    001 Integration Server
    <b>SLD configurations:</b>
    Third Party Technical system name: Java_sytem
    Business System:CLNTJAVA
    Logical system name: CLNTJAVA
    <b>ID configurations:</b>
    Business System:CLNTJAVA
    adapter-specific identifiers:logical system:CLNTJAVA, <u>the rest is initial</u>,because I cant change it.
    IDX1 port name: CLNTJAVA the client is 001. the rfc destination is client_001.
    I think the IDX1 port and the adapter specific identifiers are wrong. is it?
    my java source if the sender is the JCO
    doc.setSenderPort("INTSERV");
    My configurations if the sender is the JCO.
    <b>SLD configurations:</b>
    Technical system name: NE2
    Business System:INTEGRATION_SERVER_NE2
    Logical system name: INTSERV
    <b>ID configurations:</b>
    Business System:INTEGRATION_SERVER_NE2
    adapter-specific identifiers:logical system:INTSERV,system NE2,client 001.
    IDX1 port name: INTSERV the client is 001. the rfc destination is client_001.
    Could this error be an autorization error?I tired to connect to the xi from the Java, with the user PIISUSER extended with PISUPER roles.
    Thank very much.

    Hi!
    My SNDPOR already set to my source business system's logical name if you check my configurations(JAVACLNT), so there is another problem unfortunately. I set SNDPRN to JAVA, but it still does not work.
    Check this configuration please(posted here:
    No service for system ... in Integration Directory)
    doc.setMessageType("ACC_DOCUMENT");
    doc.setRecipientPort("SAPSE1"); // get stuck in XI mapping if not set
    doc.setRecipientPartnerType("LS");
    doc.setRecipientPartnerNumber("SE1CLNT500");
    <b>doc.setSenderPort("SAP3MA");</b>
    doc.setSenderPartnerType("LS");
    <b>doc.setSenderPartnerNumber("TREMACLNT");</b>
    doc.setClient("100");
    Inside XI configuration integration builder
    <b>Business Service: Service: TREMACLNT</b>
    Under the menu Service - Adapter specific identifiers
    Idoc Adapter Logical system: TAPPMAN (This thing is important when sending idoc XI -> SAP and should match the logical sys in the receiving SAP system)
    IDoc Adapter and RFC adapter R/3 Sysytem ID: 3MA
    Client: 100
    In IDX1 trans
    <b>Port: SAP3MA</b> (Note that the 3MA here is matched against the IDoc Adapter and RFC adapter R/3 Sysytem ID: 3MA)
    (a not so well documented feature)
    Client: 100
    RFC Destination: SE1 (A SAP test system from where IDOC def can be imported, rfc dests are setup in SM59)
    I guess that your idx1 port name is the same as the SNDPOR value. I think it should be, because the XI is whatching the IDOC traffic in the idoc adapter port, so you should send the IDOC from external system to the adapter port. Is it right?
    My idx1 port is the same as my SNDPOR value in Java,but still came the error.

  • Issue in sending IDOC from BODS to SAP

    I am getting issue while sending IDOC from BODS to SAP.
    Job is getting failed with error : "No authorization to send Idoc with message type CREMAS"
    I have checked last authorization in SU53 and it is Successful !!
    What would be reason because of which job is getting failed with Authorization error?

    Go to sm58-->Select IDOC_INBOUND_ASYNCHRONOUS this function module, in menu mar select edit--> execute LUW.
    or take help from sap basis team, can you please check user in the source system have authorizations profile. 'S_BI-WX_RFC' for this u can refer sap note :150315.
    if you need more information refer this document:
    How to check a BW - SAP source system connection - SAP NetWeaver Business Warehouse - SCN Wiki

  • Sending IDocs from R/3 to XI

    Hello,
    I try to connect a R/3 system to an XI system. I have made the SLD configuration, created RFC destinations, ports and so on. Sending IDoc from XI to R/3 was successful.
    No I would like to send IDocs from R/3 to XI. I did the necessary steps at R/3 as described in several blogs etc.:
    SM59 rfc dest to XI
    WE21 tRFC port
    I also read about this step: Create receiver sys as logical system in BD54. What is this for? I am not sure if this step was done in my case, cannot check it at the moment.
    I am trying to send an IDoc via transaction WE19 (Idoc Test tool). I think there is no need to create a partner profile?
    Now I am wondering: Which values must be set in the control record? I inserted the port pointing towards XI, but I am not sure about the other fields.
    I know there are several blogs on this topic but for me there are some details missing. I am also interested in some kind of explanation not just WHAT steps have to be done, but WHY they have to be done.
    Thanks in advance, point will be awarded.
    CHRIS

    > 1. The process is like this: The Logical system is
    > defined (as its name suggest ) just for Logical
    > definition of the communicting parties. The technical
    > details are not provided here.
    > 2. Then RFC Destination is maintained where actual
    > connection parameters r maintained.
    > 3. Port here act as the medium through which the
    > transmission is done.
    > 4. To identify ur particular message, Partner Profile
    > is maintained.
    >
    > Now in we19 test tool, the port provides the medium
    > where the data should be sent. Through this medium,
    > the connection to the receiver is checked via RFC
    > destination.
    Also thanks to you. I understand that the message is sent to a port, which points to a certain RFC destination. But still I don't get it: I thought thats exactly what WE19 is for: To send IDocs for testing purposes to ports, while there is no partner profile needed? I thought there is no partner profile necessary as I can set all fields manually in the control record (receiver port, sender port, message type, receiver type and so on).
    Kind regards
    CHRIS

  • Problem when sending IDOC from ECC to MII 12.0

    Hi all,
       I have followed the document "[How to Send an IDoc from SAP ECC to the SAP MII IDoc Listener|http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/50775783-6cb1-2b10-90b0-e6bc2c0b8563]" to configure the scenario to send IDOC from SAP ECC 6.0 to MII 12.0.
       But when sending 53 IDOCs by Tcode POIT to MII, I have problem as below:
       - 53 IDOCS were successfully outbounded (list in WE02).
       - 8 IDOCs were successfully sent to MII IDOC listener (these 8 IDOCs messages exist in list of Message Monitor).
       - 45 IDOCS were error with message in SM58: "Bean IDOC_INBOUND_ASYNCHRONOUS not found on host xxx, ProgId=yyy".
       I'm wonder why some IDOCs were successful while some others were error. If the bean  IDOC_INBOUND_ASYNCHRONOUS don't exist in EJB, why some IDOCs successful found this bean?
       I have another wonder: in this scenario document, all IDOC message type (SYNCH, LOIPRO) is configured in outbound parameters of RECEIVER (receiver logical system), why they weren't configured them in outbound parameters of SENDER (sender logical system)?
       If some have the same problem and know how to resolve it, could you please help me?
    Thank a lot in advance,
    Vinh Vo

    Hi Vinh,
    Please read the following document:
    [IDOC Listener|https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/bpx-community/manufacturing/how%20to%20send%20an%20idoc%20from%20sap%20ecc%20to%20the%20sap%20mii%20idoc%20listener.pdf]
    If you explicitly defined a Prog ID in NW, then you have done an extra step and are confusing NW with the real destination.  
    In basic terms, you set up an RFC destination (with an assigned ProgID) in ERP, then configure MII to point to it. 
    I suggest that you follow the document completely and do nothing else to set up a new listener. 
    If you are not using ECC 6.0, you may find the paths are different,  but the transactions codes are generally the same.  However, you may want to check with some of the older installation instructions regarding specific modifications.  Look in the Wiki for MII under Connectivity.
    Good luck,
    Mike

  • Sending IDoc from ERP to PI

    Hi all,
    I am trying to sent IDoc's from the ERP (SAP ECC) side to PI. But the IDocs are not arriving at the PI side. In ECC tc:we05 they seem to be successfully sent.
    The Partner Type in we20 is "LI". I added the IDoc to the Outbound parameters and set the PORT to the Port we use for PI. But unfortunately it is not working.
    Any idea why?

    When sending IDoc from ECC System to PI.
    some settings needed on ECC System & PI System
    On ECC System
    Create Port in WE21 type LS (Logical System) use RFC Destination TYPE ABAP in that port.
    Create Partner Profile using PORT in WE20.
    Add the Idoc as Outbound in that Partner Profile.
    Now on PI System
    PI System does not have structure / matadata of IDoc.
    Create Port in IDX1.
    Import IDoc Matadata in IDX2 use Port created in IDX1.
    Create complete scenario & send IDoc from ECC, it will reach at PI System, if successful at ECC.

  • Send idoc from one version of R/3 to different version

    Hi All,
    I have a scenario to send idocs from one R/3 system to another (both have different versions) .Can anyone tell me the step by step way to configure. Do I need to program anywhere to send or receive idocs Any help is really appreciated
    Thanks
    Michael

    Hi michael,
         The version change technique allows you to exchange idocs with systems using the older version of idocs.
    For this v have to configure the sending system to generate back level idoc for receiving system using the partner profile. configuring the partner profile is enough to send idocs in this scenario.
    Regards....
    Arun.
    Reward pts if useful.

Maybe you are looking for