Single IDOC to Multiple Interface Mapping

We have a requirement in our project where one masterdata IDOC will be sent from a SAP MDM box and will be transformed to a target IDOC and be sent to an SAP SNC box. However, the scenario is that depending on the contents of the IDOC, there can be multiple IDOCs that need to be created. For example, the single MDM IDOC has V1, V2 and V3 values then the IDOCS that should be sent to the SAP SNC box should be three.
The IT head of the customer decided against using Enhanced Interface Determination (since the problem can be easily solved using a 1:n mapping) due to the complexity especially when the solution is rolled out to other regions as each region has it's own logic (currently, the other implementation has only 1:1 mapping so there is no problem). I had developed a 1:n mapping but the resulting map is too big and very complex.
What I tried to do is to create separate mappings for each scenario that an IDOC needs to be generated out of the values from the received IDOC in XI and then define rules in the Interface Determination. Problem is that XI throws an error stating that multiple interfaces are found. So I cannot use Interface Determination to trigger creation of multiple IDOCS of the same type with different values from a single IDOC sent by the same SAP box.
Question is, is there any way to solve this requirement without using Enhanced Receiver Determination. I was thinking of BPM but not really sure how to do it.
Thanks in advance!
Best Regards,
Rommel Mendoza
Hewlett Packard Asia-Pacific, Ltd.

Thanks a lot for that.
For example, We have this input Message:
<ZMATMA>
  <IDOC>
    <E1MARAM>
       <E1MARMM>
           <MEINH>IT</MEINH>
       </E1MARMM>
       <E1MARMM>
           <MEINH>CS</MEINH>
       </E1MARMM>
       <E1MARMM>
           <MEINH>SW</MEINH>
       </E1MARMM>
    </E1MARAM>
  </IDOC>
</ZMATMA>
then there should be an output of:
<SAVEMULTIPLE204>
  <IDOC>
    <BUOM>IT</BUOM>
  </IDOC>
</SAVEMULTIPLE204>
<SAVEMULTIPLE204>
  <IDOC>
    <BUOM>CS</BUOM>
  </IDOC>
</SAVEMULTIPLE204>
<SAVEMULTIPLE204>
  <IDOC>
    <BUOM>SW</BUOM>
  </IDOC>
</SAVEMULTIPLE204>
The logic is when the MEINH field of the ZMATMA02 IDOC has the values: IT, CS and SW, create one IDOC for each.
Thanks in advance!
Edited by: Rommel Mendoza on Nov 6, 2008 7:30 PM

Similar Messages

  • Split Single IDOC into Multiple IDOC's Based on Segment Type

    Hi Experts,
    I have a scenario IDOC to FILE ,  Split Single IDOC into Multiple IDOC's based on Segment Type
    Outbound:
    ZIdocName
    Control Record
    Data Record
    Segment 1
    Segment 2
    Segment 3
    Status Record
    I should get output like below
    Inbound:
    ZIdocName
    Control Record
    Data Record
    Segment 1
    Status Record
    ZIdocName
    Control Record
    Data Record
    Segment 2
    Status Record
    ZIdocName
    Control Record
    Data Record
    Segment 3
    Status Record
    Please suggest me step by step process to achieve this task.
    Thanks.

    Thanks a lot Harish for reply.
    I have small doubt. According to your reply , If we have N number of segments in single IDOC with same fields in all segments then for splitting Single IDOC into Multiple IDOC's based on Segment Type we need to duplicate N number of target IDOC tree structure.
    Is that possible to Split single IDOC into Multiple IDOC's based on Segment Type using only one Target IDOC structure without duplicating the Target IDOC structure tree.

  • Idoc to multiple interfaces in XI

    Hi,
    how can we handle same Idoc ( MATMAS.MATMAS03) sending to multiple interfaces in XI otherthan using multi mapping?
    If we develop one scenario now and in future if you want to send same idoc to different systems, do we have to change the existing interface?. Alternatively is it possible to add another interface?. Please clarify.

    ok, as it's case 1, I think it's easier.
    You have two ways:
    1. Inside <b>ID</b>, use your previous Scenario:
    => after that, you will have 1 scenario...
    1.1 Create a new Business Process (BPM_2)
    1.2 Inside your <u>existing</u> Receiver Determination, add your new BPM_2 as a receiver (use righ-click + "insert above").
    1.3 with your triplet "Sender_name + Sender_interface + BPM_2", create your Interface Determination
    1.4 As receiver is a BPM, Receiver Agreement is not needed.
    Then, you need to configure the step "BPM_2 -> Receiver_2"
    1.5 Create a Receiver Determination between your BPM_2 (sender) and your receiver_2.
    1.6 create your Interface Determination
    1.7 create your Receiver Agreement (receiver adapter)
    2. Inside <b>ID</b>, use a new Scenario:
    => after that, you will have 2 scenarios which use the SAME Receiver Determination "Matmas -> Receiver_1 + BPM_2"
    2.1 create a new Scenario
    2.2 <b>ADD</b> to this scenario your existing Receiver Determination ("Matmas -> Receiver_1").
    2.2 do the same steps than "1.1 -> 1.7"
    At the end, you will have:
    Matmas --> | Receiver_1              => File_1 with single Idoc
                | BPM_2
                  BPM_2 --> Receiver_2    => File_2 with collected IDocs
    Mickael
    Message was edited by: Mickael Huchet

  • Single iDOc to multiple files based on a condition

    Hi Friends
    need your help in one scenario which is something like this:
    there is one iDOC as the sender and this iDOC has to be mapped to files based on a condition means let us say if there is a particular field "R" in iDOC(WPDBBYY01) than it should go and create the file "ABC"
    and if the particlar field is P or G or M than it should create another 2 files named "XYZ" and "WUV" .
    Please guide me how can i put this condition ?
    Any help would be rewarded with points
    Thanks

    Have a single receiver and 2 inbound interfaces.
    So you will have 2 different mappings. In the first mappng source is IDOC and the target is file ABC.
    In the second mappping the source is IDOC and the target is 2 files XYZ and WUV.
    In Interface determination, add both the inbound interfaces and put the condition for each interface.
    Regards,
    Jaishankar

  • IDoc to IDoc Scenario - Correct Interface Mapping configuration

    Hello All,
    i have to configure an Interface Mapping for an IDoc to IDoc scenario.
    IDoc Type for sending and receiving already imported and located under Imported Objectes\IDocs in respective Software Component Version.
    Now, how is the correct configuration? Add the sending respectively receiving IDoc Type directly to Source Interface/Target Interface under Display Interface Mapping or create first a sending Message Interface and a receiving Message Interface and add the IDoc type under configuration Message Types. Then add the Message Interface to the Interface Mapping.
    The selection for direct import of the IDoc structure under the Interface Mapping (Source Interface/Target Interface) is possible.
    Many Thanks in advanced!
    Jochen

    hi,
    for IDOCs (if you don't use a BPM)
    you don't need any message interface
    so if you have already created a message mapping
    you can put the IDOCs directly to your interface mapping
    then click on read interfaces
    and select your message mapping program
    if you want to learn more about IDOCs and XI
    have a look at my book:
    <a href="/people/michal.krawczyk2/blog/2006/10/11/xi-new-book-mastering-idoc-business-scenarios-with-sap-xi"><b>Mastering IDoc Business Scenarios with SAP XI</b></a>
    Regards,
    michal
    <a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions"><b>XI / PI FAQ - Frequently Asked Questions</b></a>

  • Dual uplinks with single 5400 and single 6509 (with multiple interface cards)

    I have a single 5400 with two gige ports and a single 6509 with dual gige line cards.
    What would be the best method for running them with dual connections in case an interface or line card goes bad?
    Thanks in advance.

    Thank you for the reply Joseph. I swear I've ran SLA on 6500's before. This box is running IOS 12.2 so maybe that's the culprit.
    I found a simple way to configure both devices redundantly using administrative distanced routes pointing through a specified interface. On the 6509, the routes point to a loopback address on the 5400, on the 5400 it's configured as default routes. Like this document explains:
    http://www.cisco.com/c/en/us/support/docs/ip/border-gateway-protocol-bgp/27082-ip-static-routes.html
    Seems to work like a champ.

  • Splitting single idoc into multiple xml's

    Hello,
    My requirement is such that, i need to split an custom IDoc into three xml which will be picked up by MDM, as i am new to PI 7.1 kindly guide me through the process.
    and the second requirement is, i need to map the same custom IDoc into three different MDM repositories pls guide me through the process

    Hi Abhishek,
    [quote]My requirement is such that, i need to split an custom IDoc into three xml which will be picked up by MDM, as i am new to PI 7.1 kindly guide me through the process
    For this, you have to go for multimapping.
    The links for it are already provided in the above posts.
    and the second requirement is, i need to map the same custom IDoc into three different MDM repositories pls guide me through the process
    Can you please explain this requirement further?
    -Supriya.

  • Odi-row wise insertion of single source into multiple interfaces in package

    hi,
    i have an issue.My source table is emp(empno(pk),name,job,mgr,sal,deptno,comm).And my target tables are
    emp1(name,empnoa(pk),deptno),emp2(empnob(pk),job,sal).
    i have two interfaces: interface1----emp to emp1
    interface2-----emp to emp2.
    I have 100 rows in my source table.
    Requirement is :in my package i put interface 1 after interface 2.
    For each row of the sorce emp.The data should go into targets emp1,emp2.If a particular row isnt getting into either emp1 or emp2.That particular should rollback[i.e it should enter into either emp1 or emp2].
    The insertion should be row wise and not the whole of source data.
    How do i go about this?

    Perhaps this will work:
    Keep interface 1 as is - run it first in the package.
    for interface 2, join emp to emp1, only update/insert into target (emp2) if: emp.empno = emp1.empnoa - this way, you will not add anything to emp2 that is not in emp1.
    then, create a simple procedure to
    delete *
    from emp1
    where not empnoa in (select empnob from emp2)
    They may be a better solution, but this is easy and should work just fine.

  • Single idoc generation for multiple sales orders

    Hi,
    Pls let me know how do we generate single idoc for multiple sales orders.
    Its not collecting idoc. As we know we can generate an idoc for one sales order correspondingly
    my requirement is to generate single idoc number for multiple sales orders.
    Do we need to write a program.

    Amar,
    To understand take HRMD_A04 as example. Root segment has Maximum 9999999999 defined.
    Segm.type       E1PLOGI
    Minimum number  1
    Maximum number  9999999999
    Parent segment
    Hier.level      2
    This means that this IDOC types has capability to hold multiple HR Master data objects. PFAL program creates this IDOC and it has facility to mention the Objects per process, check selection screen.
    I checked for INVOICE01/02 its not possible there. Hope this clarifies.

  • Multiple IDocs to be posted from single IDoc

    Hi,
    I am using ORDERS05 Basic type. I have copied a IDOC_INPUT_ORDERS to a custom FM and using the same for the inbound IDoc. Now my requirement is to split a single incoming IDoc into number of IDocs based on the sales orders to be posted.
    Can anyone please suggest me to achieve this. I also need to send a reconfirmation to Biztalk system.
    Thanks,
    Bipen

    Hi BreakPoint,
    What I understood from you is to do below points.
    create a custom process code and a Funtion Module to read the incoming IDoc
    Based on each header found, I should split the IDOC_DATA internal table into new internal
    tables(each headerwise) and pass this to IDOC_INPUT_ORDERS with all the necessary
    parameters.
    I did not get your point to storing in the system. Please clarify me if I am wrong.
    Hi Clemens,
    Appolozies for the confusion. I am not quite sure why business has decided to send a single
    IDoc with multiple Orders details(1 IDoc for each sales order) inspite of complexities like BreakPoint has mentioned.
    The xml file content shared by Biztalk was something like:
    <sales Order type = ZZ45 Sales Document Number = 10000010 date = 2010.10.12 Item number= 00000010 Quantity = 1 Net Amount = 100 />
    <sales Order type = ZZ45 Sales Document Number = 10000011 date = 2010.10.12 Item number= 00000010 Quantity = 1 Net Amount = 110 />
    <sales Order type = ZZ45 Sales Document Number = 100000102date = 2010.10.12 Item number= 00000010 Quantity = 1 Net Amount = 120 />
    From this example, I need to create 3 IDocs for these 3 sales orders. Needless to say here, the content above is passes as a single IDoc.
    Looking forward for your suggestions.
    Thanks and Regards,
    Bipen

  • How to Split Single Idoc into 2 files and put some delay

    Hi,
    I have a IDoc to file Scenario. Invoice Idoc to Flat file scenario
    this is a reuse Interface
    Current Scenario we have graphical mapping(used for lookup and dynamic filename, mostly all the field mappings are 1-1) and ABAP Mapping to convert Idoc to flat file, 1 Idoc will generate 1 file.
    In addition to the above case, there is 1 more requirement
    Correction Invoice case. where in I get single Idoc with Multiple Item categories (Original data and Correction data)
    In this case always I need to send two files(2 Idoc data), first Idoc is for Original Idoc and 2nd is Corrected Invoice, these 2 idocs should be sent with some delay.
    In Correction Invoice case, I should generate 2 idocs based on Item category (PSTVY) value.
    Suppose I have 4 E1EDP01 segments out of which PSTVY has value "AA" and "BB" repeated twice as shown below
    <PSTYV>AA</PSTYV>
    <PSTYV>AA</PSTYV>
    <PSTYV>BB</PSTYV>
    <PSTYV>BB</PSTYV>
    So I need to generate 2 Idoc 1 for AA and other for BB.
    If there is no correction Invoice, 1 idoc for 1 file will be generated.
    Am planning to use BPM to delay the idocs and identigy bpm based on Document type else no bpm...
    How do I split the mapping of single Idoc to 2 files based on Item category.
    Thanks,
    Varun

    You can use the multi-mapping to split the message payloads according to business requirement (AA and BB segments values)
    /people/jin.shin/blog/2006/02/07/multi-mapping-without-bpm--yes-it146s-possible
    And then send to different receivers by adding the conditions on the Receiver Determination (for example, "field = AA" go to Receiver1, and "field = BB" to to Receiver2).
    http://help.sap.com/saphelp_nwpi71/helpdata/en/26/5ccd3bb4560f01e10000000a11402f/frameset.htm
    Or even Extended (enhanced) receiver determination, should the scenario be more complex:
    http://wiki.sdn.sap.com/wiki/display/XI/EnhancedReceiverDeterminationinSAP+XI

  • DHCP and multiple interfaces

    Is it better to list each machine and interface as a separate entry in 10.5.7 DHCP or make a single entry with multiple interfaces?
    I am looking at grouping my Wireless AP, instead of having to list each one separately.
    For example:
    MAIN-MDF00-01
    XX:XX:XX:XX:XX:XX 10.0.2.1
    Or
    MDF-AP
    XX:XX:XX:XX:XX:XX 10.0.2.1
    XX:XX:XX:YY:YY:YY 10.0.2.2

    Joe,
         Currently you cannot base the anchoring on the AP group.  It is only based on the SSID.
    Now, do you really need to split up the guest into different subnets?  Or are you concerned about the AP groups?
    If you truly need to break up the guest to different subnets, then you would need to create different SSID on the internal and anchor controller.  Then on the anchor, link to the appropriate interface.
         If you are concerned about the AP group, don't be.  Just because you are using the AP group, doesn't meant that all the guest ssid can't link to the same interface, they can.  You can even create a dummy interface on the internal WLC, so that if the anchoring doesn't work, they do not get an address.
    Cheers,
    Steve
    If  this helps you and/or answers your question please mark the question as "answered" and/or rate it, so other users can easily find it.

  • Splitting multiple IDoc XML files into single IDoc messages for R/3

    Hi all. I have a problem splitting IDoc XML files coming in to XI. I currently have an interface that takes in single store sale IDoc transactions (type WPUBON01) in an IDoc XML file. I then have some complex graphical mapping on the IDoc before sending to R/3 via the IDoc adapter. This works fine. However, we now wish to include multiple sales in one file i.e. many WPUBON01 IDocs. I could use message splitting to do this BUT the mapping is so complex, I do not wish to have to change it to enable the processing of many IDocs in one file instead of just one.
    What I want to do: have one mapping splitting a multiple IDoc XML file into single IDoc messages and then another taking these single messages as before and performing the mapping. I cannot find a way to do this in one interface; the main problem I'm having is getting XI to split the multiple IDocs into many single IDoc messages within XI itself. I'd be very grateful for any advice on the best way to do this.
    Thankyou.
    Stuart Richards (Halfords, UK)

    Bhavesh,
    Thanks again for a clear explanation... I'm moving forwards but still struggling. I've been on this all afternoon today (after a break on other things) and just cannot get my message to split properly (though the SOAP adapter problem I had earlier is now fixed!). If my initial IDoc XML file contains this format:
    <WPUBON01><IDOC>....</IDOC>
                          <IDOC>....</IDOC>
                          <IDOC>....</IDOC></WPUBON01>
    .. I'm not sure what the cardinaility on the first message mapping and interface mapping should be. I'd have thought the source interface would be 1 and the target would be 0..unbounded but this isn't working. I'm trying different things but I get different errors each time. Currently, I have the above cardinality in my first interface and I'm passing in the following data:
    <WPUBON01><IDOC><EDI_DC40><TABNAM>EDI_DC40</TABNAM><MANDT /><DOCNUM /><DOCREL>620</DOCREL><DIRECT>2</DIRECT><IDOCTYP>WPUBON01</IDOCTYP><MESTYP>WPUBON</MESTYP><MESCOD>ST6</MESCOD><SNDPOR>WPUX</SNDPOR><SNDPRT>KU</SNDPRT><SNDPRN>0518</SNDPRN><RCVPOR /><RCVPRT>KU</RCVPRT><RCVPRN>0518</RCVPRN><REFINT>00000003832292</REFINT></EDI_DC40><E1WPB01 SEGMENT="1"><POSKREIS>0518</POSKREIS><KASSID>29</KASSID><VORGDATUM>20071029</VORGDATUM><VORGZEIT>160633</VORGZEIT><BONNUMMER>1001</BONNUMMER><KASSIERER>100</KASSIERER><CSHNAME> </CSHNAME><BELEGWAERS>GBP</BELEGWAERS><E1WPB02 SEGMENT="2"><VORGANGART /><QUALARTNR>ARTN</QUALARTNR><ARTNR>000000065601301390</ARTNR><VORZEICHEN>-</VORZEICHEN><MENGE>1</MENGE><AKTIONSNR>0000000000</AKTIONSNR><REFBONNR> </REFBONNR><E1WPB03 SEGMENT="3"><VORZEICHEN /><KONDITION>PN10</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03><E1WPB03 SEGMENT="4"><VORZEICHEN></VORZEICHEN><KONDITION>ZPN1</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03></E1WPB02><E1WPB02 SEGMENT="5"><VORGANGART /><QUALARTNR>ARTN</QUALARTNR><ARTNR>000000065601301390</ARTNR><VORZEICHEN>-</VORZEICHEN><MENGE>1</MENGE><AKTIONSNR>0000000000</AKTIONSNR><REFBONNR> </REFBONNR><E1WPB03 SEGMENT="6"><VORZEICHEN /><KONDITION>PN10</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03><E1WPB03 SEGMENT="7"><VORZEICHEN></VORZEICHEN><KONDITION>ZPN1</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03></E1WPB02><E1WPB02 SEGMENT="8"><VORGANGART /><QUALARTNR>ARTN</QUALARTNR><ARTNR>000000065601301390</ARTNR><VORZEICHEN>-</VORZEICHEN><MENGE>1</MENGE><AKTIONSNR>0000000000</AKTIONSNR><REFBONNR> </REFBONNR><E1WPB03 SEGMENT="9"><VORZEICHEN /><KONDITION>PN10</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03><E1WPB03 SEGMENT="10"><VORZEICHEN></VORZEICHEN><KONDITION>ZPN1</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03></E1WPB02><E1WPB02 SEGMENT="11"><VORGANGART /><QUALARTNR>ARTN</QUALARTNR><ARTNR>000000065601301390</ARTNR><VORZEICHEN>-</VORZEICHEN><MENGE>1</MENGE><AKTIONSNR>0000000000</AKTIONSNR><REFBONNR> </REFBONNR><E1WPB03 SEGMENT="12"><VORZEICHEN /><KONDITION>PN10</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03><E1WPB03 SEGMENT="13"><VORZEICHEN></VORZEICHEN><KONDITION>ZPN1</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03></E1WPB02><E1WPB02 SEGMENT="14"><VORGANGART /><QUALARTNR>ARTN</QUALARTNR><ARTNR>000000065601301390</ARTNR><VORZEICHEN>-</VORZEICHEN><MENGE>1</MENGE><AKTIONSNR>0000000000</AKTIONSNR><REFBONNR> </REFBONNR><E1WPB03 SEGMENT="15"><VORZEICHEN /><KONDITION>PN10</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03><E1WPB03 SEGMENT="16"><VORZEICHEN></VORZEICHEN><KONDITION>ZPN1</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03></E1WPB02><E1WPB06 SEGMENT="17"><VORZEICHEN></VORZEICHEN><ZAHLART>PTCS</ZAHLART><SUMME> </SUMME><KARTENNR /><ZUONR>1001</ZUONR></E1WPB06></E1WPB01></IDOC><IDOC><EDI_DC40><TABNAM>EDI_DC40</TABNAM><MANDT /><DOCNUM /><DOCREL>620</DOCREL><DIRECT>2</DIRECT><IDOCTYP>WPUBON01</IDOCTYP><MESTYP>WPUBON</MESTYP><MESCOD>ST6</MESCOD><SNDPOR>WPUX</SNDPOR><SNDPRT>KU</SNDPRT><SNDPRN>0518</SNDPRN><RCVPOR /><RCVPRT>KU</RCVPRT><RCVPRN>0518</RCVPRN><REFINT>00000003832293</REFINT></EDI_DC40><E1WPB01 SEGMENT="1"><POSKREIS>0518</POSKREIS><KASSID>29</KASSID><VORGDATUM>20071029</VORGDATUM><VORGZEIT>160634</VORGZEIT><BONNUMMER>1002</BONNUMMER><KASSIERER>100</KASSIERER><CSHNAME> </CSHNAME><BELEGWAERS>GBP</BELEGWAERS><E1WPB02 SEGMENT="2"><VORGANGART /><QUALARTNR>ARTN</QUALARTNR><ARTNR>000000065601301390</ARTNR><VORZEICHEN>-</VORZEICHEN><MENGE>1</MENGE><AKTIONSNR>0000000000</AKTIONSNR><REFBONNR> </REFBONNR><E1WPB03 SEGMENT="3"><VORZEICHEN /><KONDITION>PN10</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03><E1WPB03 SEGMENT="4"><VORZEICHEN></VORZEICHEN><KONDITION>ZPN1</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03></E1WPB02><E1WPB02 SEGMENT="5"><VORGANGART /><QUALARTNR>ARTN</QUALARTNR><ARTNR>000000065601301390</ARTNR><VORZEICHEN>-</VORZEICHEN><MENGE>1</MENGE><AKTIONSNR>0000000000</AKTIONSNR><REFBONNR> </REFBONNR><E1WPB03 SEGMENT="6"><VORZEICHEN /><KONDITION>PN10</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03><E1WPB03 SEGMENT="7"><VORZEICHEN></VORZEICHEN><KONDITION>ZPN1</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03></E1WPB02><E1WPB02 SEGMENT="8"><VORGANGART /><QUALARTNR>ARTN</QUALARTNR><ARTNR>000000065601301390</ARTNR><VORZEICHEN>-</VORZEICHEN><MENGE>1</MENGE><AKTIONSNR>0000000000</AKTIONSNR><REFBONNR> </REFBONNR><E1WPB03 SEGMENT="9"><VORZEICHEN /><KONDITION>PN10</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03><E1WPB03 SEGMENT="10"><VORZEICHEN></VORZEICHEN><KONDITION>ZPN1</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03></E1WPB02><E1WPB02 SEGMENT="11"><VORGANGART /><QUALARTNR>ARTN</QUALARTNR><ARTNR>000000065601301390</ARTNR><VORZEICHEN>-</VORZEICHEN><MENGE>1</MENGE><AKTIONSNR>0000000000</AKTIONSNR><REFBONNR> </REFBONNR><E1WPB03 SEGMENT="12"><VORZEICHEN /><KONDITION>PN10</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03><E1WPB03 SEGMENT="13"><VORZEICHEN></VORZEICHEN><KONDITION>ZPN1</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03></E1WPB02><E1WPB02 SEGMENT="14"><VORGANGART /><QUALARTNR>ARTN</QUALARTNR><ARTNR>000000065601301390</ARTNR><VORZEICHEN>-</VORZEICHEN><MENGE>1</MENGE><AKTIONSNR>0000000000</AKTIONSNR><REFBONNR> </REFBONNR><E1WPB03 SEGMENT="15"><VORZEICHEN /><KONDITION>PN10</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03><E1WPB03 SEGMENT="16"><VORZEICHEN></VORZEICHEN><KONDITION>ZPN1</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03></E1WPB02><E1WPB06 SEGMENT="17"><VORZEICHEN></VORZEICHEN><ZAHLART>PTCS</ZAHLART><SUMME> </SUMME><KARTENNR /><ZUONR>1002</ZUONR></E1WPB06></E1WPB01></IDOC><IDOC><EDI_DC40><TABNAM>EDI_DC40</TABNAM><MANDT /><DOCNUM /><DOCREL>620</DOCREL><DIRECT>2</DIRECT><IDOCTYP>WPUBON01</IDOCTYP><MESTYP>WPUBON</MESTYP><MESCOD>ST6</MESCOD><SNDPOR>WPUX</SNDPOR><SNDPRT>KU</SNDPRT><SNDPRN>0518</SNDPRN><RCVPOR /><RCVPRT>KU</RCVPRT><RCVPRN>0518</RCVPRN><REFINT>00000003832294</REFINT></EDI_DC40><E1WPB01 SEGMENT="1"><POSKREIS>0518</POSKREIS><KASSID>29</KASSID><VORGDATUM>20071029</VORGDATUM><VORGZEIT>160634</VORGZEIT><BONNUMMER>1003</BONNUMMER><KASSIERER>100</KASSIERER><CSHNAME> </CSHNAME><BELEGWAERS>GBP</BELEGWAERS><E1WPB02 SEGMENT="2"><VORGANGART /><QUALARTNR>ARTN</QUALARTNR><ARTNR>000000065601301390</ARTNR><VORZEICHEN>-</VORZEICHEN><MENGE>1</MENGE><AKTIONSNR>0000000000</AKTIONSNR><REFBONNR> </REFBONNR><E1WPB03 SEGMENT="3"><VORZEICHEN /><KONDITION>PN10</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03><E1WPB03 SEGMENT="4"><VORZEICHEN></VORZEICHEN><KONDITION>ZPN1</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03></E1WPB02><E1WPB02 SEGMENT="5"><VORGANGART /><QUALARTNR>ARTN</QUALARTNR><ARTNR>000000065601301390</ARTNR><VORZEICHEN>-</VORZEICHEN><MENGE>1</MENGE><AKTIONSNR>0000000000</AKTIONSNR><REFBONNR> </REFBONNR><E1WPB03 SEGMENT="6"><VORZEICHEN /><KONDITION>PN10</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03><E1WPB03 SEGMENT="7"><VORZEICHEN></VORZEICHEN><KONDITION>ZPN1</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03></E1WPB02><E1WPB02 SEGMENT="8"><VORGANGART /><QUALARTNR>ARTN</QUALARTNR><ARTNR>000000065601301390</ARTNR><VORZEICHEN>-</VORZEICHEN><MENGE>1</MENGE><AKTIONSNR>0000000000</AKTIONSNR><REFBONNR> </REFBONNR><E1WPB03 SEGMENT="9"><VORZEICHEN /><KONDITION>PN10</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03><E1WPB03 SEGMENT="10"><VORZEICHEN></VORZEICHEN><KONDITION>ZPN1</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03></E1WPB02><E1WPB02 SEGMENT="11"><VORGANGART /><QUALARTNR>ARTN</QUALARTNR><ARTNR>000000065601301390</ARTNR><VORZEICHEN>-</VORZEICHEN><MENGE>1</MENGE><AKTIONSNR>0000000000</AKTIONSNR><REFBONNR> </REFBONNR><E1WPB03 SEGMENT="12"><VORZEICHEN /><KONDITION>PN10</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03><E1WPB03 SEGMENT="13"><VORZEICHEN></VORZEICHEN><KONDITION>ZPN1</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03></E1WPB02><E1WPB02 SEGMENT="14"><VORGANGART /><QUALARTNR>ARTN</QUALARTNR><ARTNR>000000065601301390</ARTNR><VORZEICHEN>-</VORZEICHEN><MENGE>1</MENGE><AKTIONSNR>0000000000</AKTIONSNR><REFBONNR> </REFBONNR><E1WPB03 SEGMENT="15"><VORZEICHEN /><KONDITION>PN10</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03><E1WPB03 SEGMENT="16"><VORZEICHEN></VORZEICHEN><KONDITION>ZPN1</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03></E1WPB02><E1WPB06 SEGMENT="17"><VORZEICHEN></VORZEICHEN><ZAHLART>PTCS</ZAHLART><SUMME> </SUMME><KARTENNR /><ZUONR>1003</ZUONR></E1WPB06></E1WPB01></IDOC></WPUBON01>
    In the message monitor, I get a chequered flag. Great. However, I get the dreaded error 500 in the SOAP receiver comm channel:
    SOAP: response message contains an error XIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 500 Internal Server Error
    Exception caught by adapter framework: SOAP Error
    Delivery of the message to the application using connection AFW failed, due to: SOAP Error.
    Any ideas as to what this might be?! I'm getting there.... if I get a solution out of this, I promise to write the blog myself!
    Cheers
    Stuart

  • Single file to multiple IDOC's

    I have a scenario (File to IDOC) where single file creates multiple IDOC's.
    I got message mapping error in production for record 622.
    Question here is will the IDOC's till entries 621 be created in the ECC system or the entire messaged failed.?
    It is sure that from 622 nothing was processed.
    Thanks.

    So, in Mapping Mapping, in outbound interface, you certainly used an external definition with option "maxOccurs=Unbounded". is that right?
    Anyway, as in moni, you have only one XML message, and as you said to us that this message is in error in moni (so red flag), it's the wole message (file) which has been rejected.
    Have you check the WE02 (ECC) and IDX5 (PI) ?... because you will have directly your answer of your question "does my file is treated partially ? or completly rejected?" !
    regards.
    mickael

  • Multiple Interfaces on a single web service URL

    we have a scenario where we have a multiple interfaces that are related to SD that needs to be exposed to another system. When we generate the WSDL from XI - it seems we can do only for one interface at a time.
    Is there a way - where in we can expose a single URL and treat these interfaces as web methods on that single URL? (similar to .Net or Java)
    If yes - how do we do that?
    Thanks.

    That will not be possible. Instead you have to expose only one interface which takes generic data as input. In the mapping, depending on dat, you should map them to various other interfaces which would definetly make your scenario complex..
    In XI each outbound interface is a separate web service (method).
    VJ

Maybe you are looking for