Same IDOC to two receiver system

I must send same IDOC to two receiver system..I am succeded to send an IDOC to abapProxy for only one system but i need to send it to two different system..I created two XI communication channels but i cannot create second receiver aggrement with same mapping.It gives an error "object already exists". But how can i assign this second communication channel without creating second receiver aggrement.
Our scenario like this
IDOC --> systemA abapProxy
         --> systemB abapProxy
how can i overcome this situation?Could you explain step by step
Thanks

Hi,
in reciver determination, have SysA and SysB both as recivers by adding one more line in reciver section for SysB..........create a second interface determination with  sender IDOC system and this SysB  and create a XI comm channel for this SysB and create a reciver agreement for it also........
Regards,
Rajeev Gupta

Similar Messages

  • Can IDoc sender and receive system be the same client?

    thanks.
    I think one client can't assign to two logical system.so?

    <i>Can IDoc sender and receive system be the same client?</i>
    yes
    Regards,
    Prateek

  • Multiple Message Mapping with same Idoc, Sender and Receiver

    Hi,
    We have one Interface sending INVOIC02 Idoc from SAP R3 4.6C to SAP R3 4.6C through XI 3.0.
    On Inbound side we are using SAP standard configuring one Partner Profile with inbound INVOIC MM process code INVL.
    In customizing, we have defined one invoic type for the EDI partner.
    Now we have to integrate another type of inbound invoic, but in customizing it's not possible to assign more than one invoic type to the same Partner EDI.
    So, we have a restriction in SAP 4.6C inbound standard. On the other hand, we can't desing two Integration Scenarios in XI 3.0 with the same idoc INVOIC02, for the same sender service and receiver service because Integration Directory doesn't allow to create two interface determination for them.
    We are thinking on using header mapping in XI (receiver agreement to avoid use the same EDI partner profile for the inbound invoic, but we can't assign the same client and technical system with the same ALE Logical System in SLD for two different business systems.
    Does anybody have any solution for this problem, SAP side or XI side?.
    Thank you
    Best regards
    Luis

    Hi!
    In XI configuration  - interface determination, you can specify more than one Inbound interface. If you identify more than one, you get a new column where you specify condition (xpath) for selecting between the different inbound interfaces.
    In 4.6c, you can have more than one inbound invoic for the same EDI partner profile, if you separate between them using message function. Just add a new inbound parameter with a different message function, or copy the one you have and specify another message function, i,e. "DIFF".
    Hope this helps.
    Regards,
    Oeystein

  • Error while posting idoc in the receiving system.

    i have processed idoc in the same system( sending and receiving idoc in the same system ) by creating a dummy logical sys and uploading a text file for customer details.The outbound processing is succesful and it shows a status message 3. But duriing the inbound processing it shows status as 51 with error as 'ENTER VALID VALUE'. but when testing using we19 it is posted sucessfully without any error..is there anything that i have to configure to process inbound idoc sucessfully?? can any suggest me the correct method for doing this.. suggestions please..
    thanks
    vidya sagar

    Hi,
    you need to make sure that in WE20 inbound processing parameters for you LS is maintained propperly. You need to give correct function module and enter whether IDoc should be processed immediately or IDocs should be collected and processed as batch. Also you may check whether the distribution model (BD64) is maintained correctly for the specific message type in the system for inbound processing.
    Regards,
    Kai

  • Get idoc number of receiver system in a SAP-to-SAP scenario

    Hi,
    In a my custom program i create cremas idoc that i send to another SAP system to create the vendor in the second SAP.
    How can i do to get the inbound idoc number created in the receiver SAP to get and show its status in the sender SAP without to use the ALEAUD process?
    My scenario is SAP-SAP without anything between the two .
    Thanks lot.
    Matteo Vernile.

    Hi,
         Hi,
    The inbound IDoc is usually created by middleware system i.e. SAP XI, Gentran and etc.
    Once the IDoc created, you can use the inbound function module to post to the application. The function module is usually starting with 'IDOC_INPUT_xxxxx' where normally the xxxxx is the name of the IDoc message type.
    You can find the associated inbound process code/function module with the IDoc message type via transaction WE42.
    FM like IDOC_INBOUND_FROM_FILE...
    Check the Function module idoc_inbound_aysnchronous
    <b>Reward points</b>
    Regards

  • Difference in LOCL print preview for same script in two different systems

    Hi All,
    When I am testing a dunning letter ( Custom sapscript) in my testing system the LOCL print preview is correct...When I am testing  it in my development system by taking print preview from LOCL it is not printing a uline and some line item headers...
    There is one text element for printing line item header.
    U1....ULINE(73)
    T0    &vline& ....&T_MATNR&..
    T3    &vline&
    UL   &ULINE(73)
    IN Development sytame in print preview every thing is perfect except the above portion the first uline and vline are not getting printed and as a result next vline and uline are dispalyed a bit above .. I am unable to understand why one uline is not printed but the othe one is printed as we are using HELVE12 in both cases and above all  why in test system this problem is not occuring..
    I checked and am 100% sure there is no difference between the layout versions in the two sapscripts...Also checked most of the SPAD configs in two systems and found them same..
    Can you give me any idead about the reason for the diffrence in print preview as in both cases it will consider the printer installed on the local desktop....
    Just we use citrix metaframe to log in SAP but that should not be the reason as thne problem would be in both system..
    Please help me out...
    Thanks and Regards
    Sweta

    Hi ,
    I already mentioned that I am selcting LOCL ( Device type Sapwin)  in both cases so in both cases it is considering the printer installed on the local system...
    Can anyone tell me specific spad config or anything else which I need to compare in both systems..

  • IDOC -IDOC BETWEEN TWO  XI SYSTEM

    Hi iam Doing a scenario, 
    where i need to post an idoc from one system to another that travells through 2 xi system..
    The Scenario is like this:
    ISU --> XI1 > XI2>  isu2
    while doing this i used XI adapter between the Xi system.
    And i am getting an error as Loop in Message Control in the  MONI.
    Please Do the Need Full Its urgent....
    DId Any One Tried For this Type Of Scenario.. Please LET Me Know..
    ITS URGENT
    Thanks
    Praveen
    Edited by: pravin kk on Feb 20, 2008 6:38 PM
    Edited by: pravin kk on Feb 21, 2008 12:53 PM

    Hi,
    The communication via web service may have advantages, if you want communicate with non XI systems.
    In your scenario, there is direct communication between XI engines, so you can go for XI adapter. The XI adapter which is normally used to configure the exchange of messages with in an Integration Server, canbe extended to exchange messages between the two Integration Servers in the scenario.
    Please verify if if you have the common SLD for both XI systems. its preferable to go for seperate SLDs
    Check out the similar threads, XI to XI scenarios:
    Re: XI -> XI scenario
    Re: XI to XI connectivity
    connection XI to XI
    Re: XI to XI connectivity
    These links will definitely give you an idea about the current situation.
    Thanks
    Swarup

  • Query : Send same data to two different systems

    Hi,
    We are getting data from BI to PI through proxy. And using soap adapter we are sending the data to non sap system.
    Now my query is : I want to send the data which came from BI to PI to two non sap (Prod and Quality) systems. How can we do that? Waiting for your help me on this.

    Hi,
    You have to add 2 receivers in receiver determination (one for quality & one for prod).
    After that, create 2 interface determinations separately one for each, also 2 receiver agreement & 2 receiver channels.
    -Supriya.

  • How to trace idoc in receiving system

    Hi
    We are sending an idoc from solution manager to an SAP system. I have the idoc number in the solution manger.
    Using this, how can we trace this idoc in the receiving system?
    Many Thanks
    Sridhar

    hi!
    Define the logical system names in both the systems.
    Logical system names :SAP001
    SAP002
    SAP001 FOR 001 CLIENT
    SAP002 FOR 002 CLIENT
    These two logical system definitions should be present in both the systems.
    Assign the logical systems to the client. (in both the systems)
    Assign SAP001 to 001 CLIENT
    Assign SAP002 to 002 CLIENT
    you can See these in transaction SALE.
    After this define the rfc DESTINATION IN sm59. (in both the systems)
    In 001 client create the RFC destination name SAP002
    In the tab log on security, give the user name and password and client of the 002 client and save it.
    Similarly do the reverse in the 002 Client.
    In 001 client create the port.(Transaction WE21)
    Specify the RFC destination name as SAP002.
    Now you can define the ports, (both the systems)
    Create the partner profile for partner(ie gve logical system name of partner) , so give as SAP002.
    partner profile in both the systems.
    Now create the distribution model in BD64 and goto edit>model view>distribute.
    The same model view will be visible n distributed to the partner system also..which in this case is sap002.
    U may trigger the idoc from we19 and chk its status in we05.
    try if it helps n kindly reward points.

  • EREC: Multipal IDOC are getting created in receiver system for one IDOC

    Hello Experts,
    I ran in to one wearied issue in IDOC creation in Receiver system. I am running PFAL in sender system for only Person but 10 IDOC are getting created in receiver system. I don't know why is this happening.
    This issue started popping up after we ran RBDAPP01-Inbound Processing of IDocs Ready for Transfer. We ran this to change IDOC to 53 status. Now I don't know what went wrong but Perner distribution is behaving
    Appreciate your help.
    Regards,
    Krishna Bidwai
    Losangeles USA.
    818 527 0204.

    Yes, employee is getting created after adding 0003 into the filter, but can u please answer my another question, i.e. PERNR in sender and receiver system should be same.
    So in Receiver system (ECC) do i need to maintain external number range for PERNR?
    Thanks

  • How to get the Status of an Idoc of successfully received in remote system

    Hi,
    I have created a report which post an idoc from system1 to remote SAP system2.
    But i want to get the final staus of posted idoc in system1 that the idoc posted was reached successfully to SAP system2  with status 53 only.
    Actually i need to show the final staus of the posted idoc in system 1.
    Is there any kind of acknowlegement can be received for an idoc posted that idoc has been reached to reamote system(SAP system in my case) sucessfully?
    If yes then how we can do that.
    Kindly reply.

    HI,
    you need IDoc Type ALEAUD.
    1. BD64 and maintain ALEAUD Messagetype to your distribution model
    2. WE20 - assign ALEAUD messagetype to your partner profile (in sending and receiving system)
    3. call report RBDstate to send ALEAUD message IDoc.
    note: the receiving system from the source IDoc sends the ALEAUD to the sending system.
    Another way:
    BDM2 - you can see IDoc number and status from sending and receiving system
    Regards,
    Gordon
    Edited by: Gordon Breuer on Oct 8, 2008 2:35 PM

  • Segment creation for outbound Idocs to non-SAP system

    Hi,
    I need to create a custom idoc for outbound interface to a non-SAP system. Here I need to create segments. So, should I create the fields in the segment with the attributes of fields in non-SAP system or fields attributes should be of SAP system.
    For example:
    There is a field invoice number which is of 10 Chars in SAP but in legacy it is divided into 2 fields: invoice prefix of 2 chars and invoice no. of 8 chars. Should my segment contain one invoice field of 10 chars or should it be two fields with 2 and 8 chars?
    In general, always should the segment fields contain field attributes based on receiving system?
    Thanks in advance.
    Sriram.

    Hi
    Should my segment contain one invoice field of 10 chars or should it be two fields with 2 and 8 chars?
    I think it shoild be better to have 2 fields, but probably the result will be the same if you send the idoc by a text file, because both informations should be contiguos, I mean if you have file with a record like this:
    1234567890
    This record can be obtained downloading a segment with 2 fields:
    FIELD1 = '12'
    FIELD2 = '34567890'.
    or single field:
    FIELD = '1234567890'.
    So it'll be the same for tje target system
    In general, always should the segment fields contain field attributes based on receiving system?
    It depends on who has to convert the idoc to the right format for the target system
    I mean you can create a "SAP" Idoc, so the receiving system will have to convert it to the right format
    or
    you can send the idoc in the right format, so the receiving system doesn't need to convert it
    Max

  • XI system idoc transfer to SAP system.

    hi ,
    this is parthasarathi,i am using ALE/IDOC.basically i need to transfer idoc from XI system to SAP system.
    can any one help me out in this case.
    my system is SAP system ie inbound system.
    i am using message type HRMD_A and idoc type is HRMD_A04.
    1)what are the steps i need to take in the inbound system..?
    2)what is the function module i need to use?
       how this is reflecting SAP system.
    3) idoc will be generated in XI system with employee master data and the same idoc generated in  XI system ,that idoc should be send to SAP system ie inbound system.
    can any help me out ..
    thanks.
    partha.

    Hi parthasarathy,
    To connect the two systems u need a connection called as RFC.(sm59)
    medium of transaction is port (we21)
    IDOC Intermediate document - travelling (or) data carrying from 1 - 2
    create partner profiles for sharing the appln. (we20)
    application linking and enabling (ALE)--used to generate an idoc in sender side and post it in the receiver side.
    r3 - r3 -use ALE - transactional rfc
    r3 - non r3 - use EDI (electronic data interchange) - file port
    bridge (bd64) - distribution model view
    to view idoc's (we05,we02)
    types of data
    1. master data -- ale -- eg. send materail(bd10),customer(bd12),vendor(bd14)
    2.transactional data -- ale
    3.control data -- cts(correction and transport systems)
    Hope this gives u overall idea of how to use idoc's.
    Regards,
    Nagarajan.

  • Missing document items in Sales Order in the receiving system

    Hello.
    We're doing passing of message type ORDERS (ORDERS05) from one system to another. Idocs were posted successfully but we can't find the document items in the receiving system if we view a particular sales order in VA03. Document items are present in the sending system.
    I checked segment E1EDP01 (document items segment) for the inbound idocs and found all items attached to the sales order but we can't see them in VA03 display.
    Appreciate help on how to proceed/check this issue.
    Thanks. =)

    If you have verified that the IDOC was complete in the receiving system, I would use WE19 to copy the IDOC in the receiving system (or copy to a development instance of that system) and run the process in debug....someone will have to watch the process, I think and see what is happening to the VBAP table during sales order build.

  • Can Same IDOC be sent to same Receiver with two different Message Mappings

    Hello Experts,
    Wierd doubt but want to confirm from you people.
    Scenario:
    One R/3 Sender
    SAP XI :
    One external Receiver :
    IDOC is sent from R/3 to external receiver via SAP XI.
    One interface has already been developed for the above scenario.
    Now client wants another interface to be developed for the same IDOC. Might be the values would be different for some specific fields.
    Doubt:
    Is it possible to send one similar IDOC to one target system with two different Message Interfaces?
    Ex: Created Message Interface 'A'  and correspoding Message Mapping with an IDOC
          Created Message Interface 'B' and correspoding Message Mappingwith an IDOC
    Values would be different in the IDOC and would be triggered from SAP R/3. Basing on the specific value of a field in the IDOC , can we trigger a different Message mapping for the same receiver?
    I donot see any reason in developing a new interface for the same IDOC but as per the situation mentioned above, can it be done?
    Thank you
    Alex.

    Create two interfaces for target side.
    If you want only one target interface should get data.
    You can use simple interface determination. Use the condition tab and specify the field there but the value should be constant. e.g. if field has value EN it should go to First interface and if Field has value != EN it should go to second interface.
    If you want to divide your message in to both target interfaces.
    Multimapping also can help but only if both of your target interface need idoc data.
    You can use ifexist standard node functions from UDF to choose between the field.
    For multimapping you can go to messages tab in the message mapping and can add interfaces using + sign.
    then when you see the design part you will see two messages.
    Now Start with receiver determination in ID and create one receiver determination for the sender and receiver, this shows you have only one receiver.
    In interface determination you have to choose extended and choose your mapping designed.
    then both your interfaces automatically would appear.
    Create two receiver agreements and one sender agreement.
    thanks
    hemant
    Edited by: Hemant on Aug 28, 2008 12:29 AM

Maybe you are looking for