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

Similar Messages

Idocs not getting posted from XI to R/3

Hi guys,
We have set up a file-to-Idoc scenario that seems to work fine, but when the number of idocs to be posted in R/3 reaches a certain number, (3,500) all idocs are getting rolled back and nothing happens in R/3.
It seems to me that there should be a parameter to set this up.
Any ideas?

Hi,
report RSEOUT00. To determine the package size, specify the maximum number of IDocs.
The number of IDocs in a file is specified by the parameter Maximum number of IDocs in the program RSEOUT00.
see SAP Note 814393
Please refer
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/30ea2fdf-f047-2a10-d3a2-955a634bde6b
Example Program for Mass Processing IDocs
http://help.sap.com/saphelp_nw04/helpdata/en/78/21760251ce11d189570000e829fbbd/frameset.htm
Thanks
Swarup

IDoc error in posting salaried headcount IDoc type is ACC_STAT_KEY_FIG

Hello Experts,
We created an Idoc for uploading headcount from peoplesoft to SAP. When we tried to post the statistical key figures, it gave a message "XXXX doesnt exist in the controlling are ABC". we edited the document and mapped it to existing SKF. When we try to post it, the status is 51 with the message "Multiple posting of same key figure to one object is redundant". Please help in how to correct this error.
I have a suspicion that the statistical key figure is parked somewhere. If so Please help me try to retrieve that
Thanks a lot
PC

what is message number and ID ?

Write multiple partions to a disk from single image?

Is it possible to restore a disk image of a single drive with multiple partitions to another drive in one go? I've create a single disk image of the drive on my iMac (which has three partitions) using disk utility. I'm hoping to use the disk image to restore a different drive so that it ends up with the three partitions just like the first. Had a bit of a play but couldn't get ay where. Trying to save a bit of time instead of doing each partition as a separate disk image.

Richard Blinco wrote:
A bit crazy that you cant use this to restore a drive but thats the way it is I suppose.
Not as crazy as it seems (I think), but explaining why might drive me a little crazier than I already am. Anyway, here goes….
From what I can tell, at least using the cdr format will copy all the partitions of the drive to the image file if a drive is the image target. However, this does not necessarily include the partition scheme info -- only the Apple Partition Map (APM) scheme actually stores that in a partition. Other partition schemes like the GUID Partition Table (GPT) 'native' to Intel Macs store this in designated sectors of the drive that are not part of any partition. Moreover, this info is not entirely "portable." IOW, some of it references specific sectors that might vary from drive to drive.
Thus, a full drive restore involves more than just copying data from the volumes of the image file. It also would have to do the equivalent of formatting the drive with the appropriate partition scheme info, which may not even be included in the image, & even if it is may need some modification.
I suppose Disk Utility could guess about the desired partition scheme, but this would limit its usefulness -- users may not necessarily want the drive formatted with that scheme -- & I'm not sure asking users about this is a good idea, since many won't even know what a partition scheme is.

Multiple invoice line items posted as single line item in FI

Dear Gurus,
My client has a specific requirement.
We are required to maintain a rebate condition at item level. In the invoice the values of rebate conditons are appearing as per the line item. This rebate condition has been maintained as statistical and accrual key has been assigend to it. Respective configuration has been done in VKOA. Accural check box has been activated for the rebate condition type.
Now when we are posting the invoice to FI, client requires that instead of line item wise posting of accrual amount it should post entire accrual amount in the single line item. In other words it is like posting of header amount directly, without any line item wise splitting.
Please help me ASAP.
Thanks in advance.
Regards
Piyush Ranpura

Dear Friends,
I am thankful for your replies. But probably I was not able to put the issue is the proper manner. Let us consider this example -
Mat. codes - M1, M2, M3 & M4   Rebate cond. - ABCD    Accrual key - ABC    GL - 12345678
In the invoice, rebate values are determined as follows for the each line item -
For Line item 10, Material M1
ZSHA   -   100
For Line item 20, Material M2
ZSHA   -   125
For Line item 30, Material M3
ZSHA   -   100
For Line item 40, Material M4
ZSHA   -   75
While the invoice is released for accounting follwing entries are there
xx 1 xx
xx 2 xx
xx 3      100 12345678
xx 4      125 12345678
xx 5      100 12345678
xx 6        75 12345678
xx 7 xx
xx 8 xx
But my requirement is
xx 1 xx
xx 2 xx
xx 3    400 12345678
xx 4 xx
xx 5 xx
How it could be done?
Thanks & Regards
Piyush Ranpura
Edited by: Piyush Ranpura on Sep 1, 2010 9:10 AM

Idoc no of 500 from other Idoc no 800

Hi
In 800 i have created an idoc and idoc no is xxxxxx and hence it created another idoc yyyyyy in 500. Now with idoc no. yyyyy in 500, in which database table can i find the idoc no xxxxx...
Regards
Sajid

Hi Shaik,
If you only want to know corresponding idoc number genrated( for client 500), then go to we02 in reciever system ( client 500) and mention youe message type and other matching details.
Another way is in outbound system( client 800) go to bd87 and give the outbound idoc number, you will find there corresponding inbound idoc number. Givet his idoc no. in we02 of recieving system and execute it. Now double click on idoc, there in control record you will find idoc no. and other control information, in data record, segments will be there which will contain data.
EDID4 table stores data in segments
EDIDC table stores control information like idoc number, current idoc status, reciever and sender information
EDIDS stores information about all statuses through which an idoc has passed.
Regards
Vinod

How to generate multiple idoc's from single appl document

All,
Iam looking for a way to generate multiple idoc's from single appl document (sales order). Based on the plant details on line items in the sales order i have to generate multiple idocs, i.e., send one idoc to each plant entered in sales order line items. any help will be appreciated.
Thanks

Hi,
You can create a Z-program and call Function Module <b>MASTER_IDOC_DISTRIBUTE</b>.
You can make a call to this FM to send the Idoc as many times as u have plants in your Sales Order.
You can call FM <b>IDOC_OUTPUT_ORDRSP</b> to fill the IDoc structure.
Then u can keep the materials of only that plant for which u want to pass on the information.
Thanks,
Utsah Garg.

Collect Multiple IDOC(Single IDOC type) to single file using BPM

Hi All,
When i am generating multiple IDOC for the same message type, i am getting multiple payload for the same as a result i used to get multiple files generated in application server.
Now if i use BPM only to collect multiple IDOC to a file then what all the steps that i need to follow for the same.
Ex: I want to post 10 IDOC for a single IDOC type,, Now using BPM in XI i want to collect all the 10 IDOCs with multiple payload into one single message and then want to process this in XI to generate the file.
It would be glad if anyone refer me a good step by step blog for the same.
Thanks in advance,
Jay

Thanks a lot Abhisek.
I have also got a blog explaining the exact thing. But in the blog the ID part was missing which is present in the link you have provided.
I will be glad if you can through some light on the ID part,, however the IR part and the BPM part is now mostly okay to me.
I will configure this today only,, and may seek your help for any huddle.
Thanks a lot once again.
Regards,
Jay.

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

Multiple Rows into single IDoc in LSMW

Hi.
I am using on_change_transfer_record for header record. have succesfully done this for header and item segment level records.
but not able to done the same at IDoc control record level.
My problem is, Multiple IDocs are created for single record. There is no processing points available for IDoc control record to use on_change_trasfer_record.
I want single IDoc for single record from multiple rows.
Please help me out in this regard.
Thanks
Rajesh

For u need to change the file format into the below structure.
H,<filed1>,<filed2>,.........................
I,<filed1>,<filed2>,.............................
I,<filed1>,<filed2>,...........................
I,<filed1>,<filed2>,.............................
H,<filed1>,<filed2>,.............................
I,<filed1>,<filed2>,................................
sepcify an indicator "H" for header record, and "I" for item record.
once u prepare the file as above.
now in ur LSMW Source structure, declare a filed called "Identifier" both for header structure and Item structure as the first field.
Specify the "Identifying field content" as "H" for header record and "I" for item record.
Continue the remaining mapping as usual.
Hope this helps.
Edited by: Poorna Chandrasekhar on Mar 5, 2009 10:13 AM

How to Read multiple material master data in single idoc

Iam working inbound material master custoum idoc .IN a single idoc i am receiveing multiple materials data .
i want to read each material data in idoc that data need to pass BAPI(perform REC_CREATION_MM Iin side this perform material posting bapi is there.).
Please provide any suggestion <removed by moderator>.this below logic is not working if idoc contain single material and last record in multiple material is not posting
lOOP AT idoc_data WHERE docnum = idoc_contrl-docnum.
if sy-tabix NE 1.
      If idoc_data-segnam = 'E1MARAM'.
        perform REC_CREATION_MM.
      endif.
    endif.
    CASE idoc_data-segnam.
      WHEN 'E1MARAM'.
        wa_E1MARAM = idoc_data-sdata .
        APPEND wa_E1MARAM TO it_E1MARAM.
        MOVE-CORRESPONDING wa_E1MARAM TO it_BAPIMARA.
        APPEND it_BAPIMARA.
        MOVE wa_E1MARAM-MATNR TO it_TABFILD-MATNR.
        MOVE wa_E1MARAM-MEINS TO it_TABFILD-MEINH.
        APPEND it_TABFILD.
      WHEN 'ZMM_C_CLFMAS01'.
        wa_ZMM_C_CLFMAS01 = idoc_data-sdata.
        APPEND wa_ZMM_C_CLFMAS01 TO it_ZMM_C_CLFMAS01.
      WHEN 'E1MAKTM'.
        wa_E1MAKTM = idoc_data-sdata.
        APPEND wa_E1MAKTM TO it_E1MAKTM.
        MOVE-CORRESPONDING wa_E1MAKTM TO it_BAPIMAKT .
        APPEND it_BAPIMAKT.
      WHEN 'E1MARCM'.
        wa_E1MARCM = idoc_data-sdata.
        APPEND wa_E1MARCM to it_E1MARCM.
        MOVE-CORRESPONDING wa_E1MARCM TO it_BAPIMARC .
        APPEND it_BAPIMARC.
     WHEN 'E1MVKEM'.
        wa_E1MVKEM = idoc_data-sdata.
        APPEND wa_E1MVKEM to it_E1MVKEM.
        MOVE-CORRESPONDING wa_E1MVKEM TO it_BAPIMVKE .
        APPEND it_BAPIMVKE .
      WHEN 'E1MLANM'.
        if NOT idoc_data-sdata is INITIAL.
          wa_E1MLANM = idoc_data-sdata.
          if NOT wa_e1mlanm is INITIAL.
            APPEND wa_E1MLANM TO it_E1MLANM.
            MOVE-CORRESPONDING wa_E1MLANM TO it_BAPIMLAN .
            APPEND it_BAPIMLAN .
          ENDIf.
        endif.
    ENDCASE.
ENDLOOP.
Thanks
VIJAY
Edited by: Thomas Zloch on May 4, 2010 3:09 PM - priority normalized

Check the material available in MARC table in SE11 transaction against your plant.If it is not available please maintain through MM01 transaction.

Error determining posting period(infostructure S008,Variant Z2,RC3) while creating Sales orders from Inbound IDOCS

Hello,
I am getting this Error message"error determining posting period(infostructure S008,Variant Z2,RC3)" while creating Sales order from Inbound Idocs in the IDOC,which is affecting sales order creation.
While viewing this Info structure S008, I could see no records have been maintained. Wanted to know the reasons behind this Hard error?
Is it something related to Date Field used in the Update Rules for this Infostructure which is causing this posting period error?
Appreciate your inputs on this.
Thanks and Regards
Mohammed Roshan

Thank you Jelena,I checked the Ship. Delivery dates in the IDOC which are for Current Fiscal Year- 20140703 and 20140711,Could there be any other reason for this error?
Could it be an issue with e Update rule in this Infostructire S008
Secondly when we try change the update rule thru MC25 for this Infostructure S008,It gives a message"
"Maintenance of SAP standard updates not allowed"
Kindly advice
Thanks and Regards
Mohammed Roshan

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.

Append or combine multiple IDOCs into a single IDOC file

Hi All,
We are implementing multiple new payment types that will generate IDOC files for us to send to the bank. To keep the cost to the minimum, the requirement is to combine multiple IDOCs to a single file.
I'd like to know the most efficient way to complete this task. Also, I am new to this forum, please let me know if I need to include additional information.
Your help will be deeply appreciated.
Thank you,
Joanne T.

Hi Milind,
One way you can do this is generate each report in PDF or Postscript, and then use Adobe Acrobat Distiller to combine the files into one PDF document.
Regards,
Stewart

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

Multiple IDocs to be posted from single IDoc

Similar Messages

Maybe you are looking for