Split Idoc

hi,
Please let me know ,How to Split larger Idoc into Multiple Idocs?
Thanks,
Asha

You need to use "packet size" in outbound parameter in WE20.
Check this
http://help.sap.com/saphelp_erp2005vp/helpdata/en/0b/2a6661507d11d18ee90000e8366fc2/frameset.htm
or if you want to split the single IDoc into multiple then probably you need to look into the triggering program
a®

Similar Messages

File- different type of mesages- split- IDOCs

team,
I am working on the above scenario using BPM. I got it working without BPM using Enhanced Interface determination and now trying to get it going with BPM to compare the performance.
1.     File has multiple batch records, based on the data in the batch records two different messages (bulk AP and AR messages ) needed to be generated.
2.      These bulk AP and AR messages need to be split into individual messages and mapped to IDOCs for being posted into ECC as AP and AR IDOCs.
I want to use BPM to split the file into multiple messages ( of differt types - AR and AP).Mapping into IDOC would be done outside BPM.
My BPM has
1.     Receive step ( message received form the file content conversion )
2.     Transformation step with I:N mapping with AP and AR as target message types
3.     A fork without end condition
4.     A Block in each of the branches of folk
5.     A Send step in each of the blocks
My question is whether it is okay to use a folk after transformation step for handling two different interfaces coming out of transformation step.
I am able to see two different messages in the workflow log after the transformation step, but cant see them in the SXMB_MONI. And so the mapping to IDOC is not happening. The config also seem to be okay .

I want to do IDOC mapping outside BPM and use BPM just for splitting the message. I have defined interface mapping for IP+IDOC in the config alomg with rest of the config.
The M1 and M2 are bulk messages. I thought I should use a ParForEach ( or for Each)block with a send inside to generate individuaul messages.This is working when I have only one bulk message generated from 1:n transformation. When I have two interfaces generated from 1:n transformation, I am struggling.
I am going to use two blocks next two each other with sends inside and see what happens
Correct me if this theory is wrong

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

File to idoc scenario (split message)

hello everybody
i have a file (xml) -> XI -> Idoc scenario
sometimes idoc message is so much big and i have problem to process it.
so i would like split message in more idoc but i need decide a cut-point
example in file i have 200 row and i don't want create 200 idocs but example 4.
So i need cut file every 50 rows.
It's possible?
thanks
Alex

Hi Alessandro ,
We had the same problem in HR implementation where we used to get data for thousands of employees in a single file.
As Idoc was not able to hold this much of data,data used to be truncated.
Then we had taken a field (employee number) as a criteria to generate IDocs,and now we have an IDoc generated for each employee record.
This was helpful as for a single employee,there were a number of change records.
The logic used was:
Employeecode -> splitByValue(value changed) -> collapseContexts -> IDoc.
Does it suit your requirement as well?I mean,may be you can find such field for splitting IDocs.
Kindly let us know.
Thanks.
Regards,
Shweta

Splitting to multiple IDoc

hi,
my scenrio is flie to idoc.
i recevie the file and i want to split the message coming from the file to different idoc based on a field(e.g doc. number).
i am using BPM..plz suggest me the steps type that is necessary for this process...
thanks....

please have the steps in bpm as
1. Receive step ( message received form the file content conversion )
2. Transformation step with I:N mapping with AP and AR as target message types
3. A fork without end condition
4. A Block in each of the branches of folk
5. A Send step in each of the blocks
/people/sudharshan.aravamudan/blog/2005/12/01/illustration-of-multi-mapping-and-message-split-using-bpm-in-sap-exchange-infrastructure
File->different type of mesages->split->IDOCs
also we can achieve this with XSLT see the below link may be useful..
/people/anish.abraham2/blog/2005/12/22/file-to-multiple-idocs-xslt-mapping

INBOUND DELFOR02 Idoc Split

Hi,
I got a requirement for an inbound idoc
Idoc type : DELFOR02
message type : DELINS
User exit functional module : IDOC_INPUT_DELINS
My actual reqirement is.......
The DELFOR02 Idoc sent from the subsystem to SAP will have to be split into multiple DELFOR02 Idocs depending upon the number of line items.
The DELFOR02 Idoc is separated into header and item data. The header data will have to be mapped to each split Idoc and then update each Scheduling agreement. The Item detail will have to be split for each occurrence of an E1EDP10 segment. For example if 3 line items are contained on the DELFOR02 Idoc this will have to be split in to 3 Idocs, as shown below:
DELFOR02 Idoc
Header Level          E1EDK09
Item Level                    E1EDP10
                              E1EDP10
                              E1EDP10
How i approach this requirement.......please help me out..its critical req

Hi,
I am just briefing the steps on how you can proceed. The following information may not be complete.
Copy the functional module : IDOC_INPUT_DELINS to new custom FM Z_IDOC_INPUT_DELINS and link this to existing process code.
In FM Z_IDOC_INPUT_DELINS :
store the header data into global structure, also populate T_NEW_IDOCDATA.
Then based on your conditions, i.e. no of segments E1EDP10
case IDOC-SEGNAM.
when 'E1EDP10'.
store the segment data into internal table T_NEW_IDOCDATA.
perform create_new_split_idoc.
endcase.
FORM CREATE_NEW_IDOC.
MOVE-CORRESPONDING IDOC_CONTRL TO S_CONTROL_RECORD_IN.
S_CONTROL_RECORD_IN-MESCOD = 'SPT'.   "new message code SPT for split Idocs
S_CONTROL_RECORD_IN-DOCNUM = SPACE.
S_CONTROL_RECORD_IN-IDOCTYP = IDOC_CONTRL-IDOCTP.
APPEND S_CONTROL_RECORD_IN.
CALL FUNCTION 'INBOUND_IDOC_PROCESS'
     TABLES
          IDOC_CONTROL = S_CONTROL_RECORD_IN
          IDOC_DATA    = T_NEW_IDOCDATA
     EXCEPTIONS
          OTHERS       = 1.
   IF SY-SUBRC = 0.
COMMIT WORK.
endif.
ENDFORM.
For split Idocs create a new message code SPT and do the partner profile setting in WE20.
Thanks,
Savitha

Splitting a Idoc message without BPM

Hi ,
I have seen several posts on this topic splitting Messages with/without BPM. But I think I did not get the currect answer so far. Here is my scenario:
We are using PI/XI 7.0 Sp 09, Idoc-XI-WM (third-party WMS systems)
SAP(Idoc) -
> XI (httpa dapter)-------> 1. Http server (WMs 1 - BS1)
> 2. Http server (WMs 2 - BS2)
> 3. Http Server (WMs 3 - BS3)
I have SAP ECC sender System and 3 receivers-WMs, 3 different Warehouse Management systems running at different warehouse locations and each warehouse is like a different system which has different IP address and etc so we defined each WMs is new Business System in the SLD.
We have a purchase Order Idoc coming from SAP ECC to XI with multiple line items, here each item may belong to one of the above 3 warehouse locations(BS) so based on the certain logic I have to split the incoming 1 PO up to 3 POs and send each PO to each warehouse location with different http adapter.
ECC- IDoc -
>(Idoc xml using Idoc adapter) XI (splitted Idoc xlm(s) using Http adapter)---->WMS
Please give your valuable inputs, I am already working on withBPM scenario but please suggest if have any good solutions with or without BPM.
Thanks,
Laxman Molugu

Laxman,
Multi-Mapping without BPM is possible from SP14. Go through this url which will help you:
/people/jin.shin/blog/2006/02/07/multi-mapping-without-bpm--yes-it146s-possible
Check this threads which will also give you some idea:
Process Integration (PI) & SOA Middleware
Message Split
---Satish

IDoc Split with out BPM using SplitByValue at the LineItem Level

I have an Invoice idoc contains line item and identifier changes into groups, let's say A & B
Using Message Mapping, Will i be able to Split into 2 IDOCs and combine A into one IDOC and B into Another IDOC and send it across to ECC with out using BPM?
Btw the header is commom for both the IDOCs
Source
<Header>
<headertext>headername</headertext>
<lineItem>
<item1>A</item1>
<item2>B</item2>
<item3>A</item3>
<item3>B</item4>
</item>
</lineitem>
</header>
Target
IDOC 1
<Header>
<headertext>headername</headertext>
<lineItem>
<item1>A</item1>
<item2>A</item2>
</item>
</lineitem>
</header>
IDOC 2
<Header>
<headertext>headername</headertext>
<lineItem>
<item1>B</item1>
<item2>B</item2>
</item>
</lineitem>
</header>
Any inputs are appreciated

I actually gave wrong information on the source structure, I am trying to execute scenario with the given examples, meanwhile any help is appreciated
<Header>
               <Date>20100112</Date>
               <Amount>10</Amount>
               <No>20</No>
</Header>
            <InvoiceItem>
               <Line1>10</Line1>
               <Line2>10</Line2>
               <Amount>10</Amount>
               <ActionIndicator>I</ActionIndicator>
            </InvoiceItem>
            <InvoiceItem>
               <Line1>20</Line1>
               <Line2>20</Line2>
               <Amount>20</Amount>
               <ActionIndicator>C</ActionIndicator>
            </InvoiceItem>
            <InvoiceItem>
               <Line1>30</Line1>
               <Line2>30</Line2>
               <Amount>30</Amount>
               <ActionIndicator>I</ActionIndicator>
            </InvoiceItem>
            <InvoiceItem>
               <Line1>40</Line1>
               <Line2>40</Line2>
               <Amount>40</Amount>
               <ActionIndicator>C</ActionIndicator>
            </InvoiceItem>
Target 1
<Header>
               <Date>20100112</Date>
               <Amount>10</Amount>
               <tNo>20</No>
               <ActionIndicator>I</ActionIndicator>
</Header>
               <InvoiceItem>
               <Line1>10</Line1>
               <Line2>10</Line2>
               <Amount>10</Amount>
            </InvoiceItem>
            <InvoiceItem>
               <Line1>30</Line1>
               <Line2>30</Line2>
               <Amount>30</Amount>
            </InvoiceItem>
Target 2
<Header>
               <Date>20100112</Date>
               <Amount>10</Amount>
               <tNo>20</No>
               <ActionIndicator>I</ActionIndicator>
</Header>
               <InvoiceItem>
               <Line1>20</Line1>
               <Line2>20</Line2>
               <Amount>20</Amount>
            </InvoiceItem>
            <InvoiceItem>
               <Line1>40</Line1>
               <Line2>40</Line2>
               <Amount>40</Amount>
            </InvoiceItem>
I know the part of Splitting IDOC, which was executing correctly, with the external data type changes. Please advice

Split File in File Sender

Hi,
I have a source file that can be up to 4MB's and I want to Split it for every 10,000 records in the file. I can't use "Recordsets per Message" because my file has a single Header and multiple Detail records.
Is there any way to split this message in the file sender?

i recommend you to create an xslt mapping and split the source file with it.
in the ESR first resolve all the mapping program, then call the XSLT.
so you ESR configuration will be:
Message mapping: XXXX
Opertation mapping will have two mapping: XXXX and XSLT.
here give you and example or XSL i use to split Idocs. the XSL receive and idoc WPUUMS01 with 1000 record and the XSL split it into Two.
use it as reference to solve your issue
<?xml version="1.0" encoding="UTF-8" ?>
<xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:ns1="http://spsa.com/POS/DailySales">
     <xsl:output method="xml" version="1.0" encoding="UTF-8" indent="yes"/>
     <xsl:template match="ns1:mt_SalesValidation_response">
      <WPUUMS01>
       <xsl:for-each select="row[position() mod 500 = 1]">
         <IDOC>
            <xsl:attribute name="BEGIN">
               <xsl:value-of select="1" />
            </xsl:attribute>
            <EDI_DC40>1
              <SNDPRN>
                   <xsl:value-of select="../OUT_WERKS"/>
              </SNDPRN>
            </EDI_DC40>
            <xsl:for-each select=".| following-sibling::row[position() < 500]">
               <E1WPU01>
                  <xsl:attribute name="SEGMENT">
                     <xsl:value-of select="1"/>
                  </xsl:attribute>
                  <BELEGDATUM>
                     <xsl:value-of select="../OUT_ERSDA"/>
                  </BELEGDATUM>
                  <BELEGWAERS>PEN</BELEGWAERS>
                <E1WPU02>
                         <xsl:attribute name="SEGMENT">
                              <xsl:value-of select="1"/>
                              </xsl:attribute>
                         <QUALARTNR>EANN</QUALARTNR>
                         <ARTNR>
                           <xsl:value-of select="EAN11"/>
                         </ARTNR>
                         <VORZMENGE>-</VORZMENGE>
                         <UMSMENGE>
                           <xsl:value-of select="TOT_CANTIDAD"/>
                         </UMSMENGE>
                         <UMSWERT>
                              <xsl:value-of select="TOT_VTA"/>
                         </UMSWERT>
                </E1WPU02>
                 </E1WPU01>
              </xsl:for-each>
         </IDOC>
     </xsl:for-each>
      </WPUUMS01>
   </xsl:template>
</xsl:stylesheet>
Hope Helps
Edited by: Rodrigo Alejandro Pertierra on May 18, 2011 12:28 PM

BPM process : where in pipeline

Wanted to know where does bpm fit in the PI pipeline ? like we can do som nay steps like collect ,split IDocs etc. But where in pipeline does this kick off? since we can do recv determination also in bpm so does pipeline kick with the bpm rather than recv det?
Thank you.

Hi,
Can you see amars reply in this thread:
pipeline steps
Also see siva and abhisheks reply in this thread:
BPM FLOW
Regards,
---Satish

Duplicate Messages created on target with Multimapping(No BPM)

Hi
I am working on PI7.1 .
My sceniro
IDOC to JMS using message split
Receiving IDOC with Header and Items, PI splitting IDOC and sending to Multiple JMS queues, Header segment data to header queue, Item segment data to Item queue
PI Successfully Posting data to Queues, but duplicate messages creating on target sys(One IDOC with one header and one item date, PI sending 2 header messages , two item messages to target sys) .
I did following steps
ESR
1. Created two target messages
2. Created Two target inbound interfaces
3. Created Message mapping using with multiple target messages, changed signature occurrence to 0 : unbounded , and mapped to source node to target nodes
4. Created operation mapping with one source to two target interfaces
EB
1. Created one business components and assigned one sender and two receiver service interfaces
2. Created Two receiver communication channel
3. Created One receiver determination
4. Created One interface determination , added two inbound interfaces with one operation mapping (Multiplicity is blank )
5. Created two receiver agreement
Please help .

Thanks Gouri ,
My IDOC structure (Source Message Type)
HEADER_SEG Node (0:9999) -
> MT_HEADER ( 0:unbounded) (this one of target message type)
                                                                HEADER_FLDS (Element - Main hierarchy)
         FLDS----
> FLDS
ITEM_SEG Node (0:9999) -
>MT_ITEM(0:unbounded ) (this is another message type)
                                                                ITEM_FLDS (Element - Main hierarchy)
         FLDS----
> FLDS
I tried with the below mappings
                HEADER_SEG Node -
>MT_HEADER
                HEADER_SEG Node -
> HEADER_FLDS (element )
                ITEM_SEG Node -
>MT_HEADER
                ITEM_SEG Node -
> ITEM_FLDS (element )
2. method
                HEADER_SEG Node -
>MT_HEADER
                                                       HEADER_FLDS (element )(not mapped)
                ITEM_SEG Node -
>MT_HEADER
                ITEM_SEG Node   ITEM_FLDS (element )(not mapped)

Problem with multi-mapping

Hello everybody,
we got a problem with multi-mapping.
Source and target message-type are the same:
<xsd:element name="MY_MESSAGE_TYPE">
_<xsd:element name="BUSTRANS">
__<xsd:element name="CHILD_1" maxOccurs="unbounded">
___<xsd:element name="SUB_CHILD_1" maxOccurs="unbounded">
____<xsd:element name="SUB_CHILD_1_NAME" type="xsd:string">
__<xsd:element name="CHILD_2" maxOccurs="unbounded">
___<xsd:element name="SUB_CHILD_2" maxOccurs="unbounded">
____<xsd:element name="SUB_CHILD_2_NAME" type="xsd:string">
The requirements are:
<xsd:element name="MY_MESSAGE_TYPE"> should be created as often as <xsd:element name="CHILD_2"..> occurs
a) so we mapped
CHILD_2 -> MY_MESSAGE_TYPE
BUSTRANS -> CopyValue -> BUSTRANS
CHILD_1 -> CopyValue -> CHILD_1
SUB_CHILD_1 -> CopyValue -> SUB_CHILD_1
SUB_CHILD_1_NAME -> CopyValue -> SUB_CHILD_1_NAME
CHILD_2 -> splitByValue(eachValue) -> CHILD_2
The problem is:
If we duplicated
a) SUB_CHILD_1
b) subtree CHILD_2 (so 2 messages will be generated)
for testing, SUB_CHILD_1 only occurs 1 time! But we need it in every target message as often as it occurs in the source message.
For your testing, here is the datatype:
<?xml version="1.0" encoding="ISO-8859-1"?>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="http://enbw.com/XI/SAPCRMB2B/javamappings_test" targetNamespace="http://mynamespace.com/XI/SAPCRMB2B/javamappings_test">
<xsd:complexType name="MultipleBookingOrderRequest">
<xsd:sequence>
<xsd:element name="BUSTRANS">
   <xsd:complexType>
    <xsd:sequence>
     <xsd:element name="CHILD_1" maxOccurs="unbounded">
      <xsd:complexType>
       <xsd:sequence>
        <xsd:element name="SUB_CHILD_1" maxOccurs="unbounded">
         <xsd:complexType>
          <xsd:sequence>
           <xsd:element name="SUB_CHILD_1_NAME" type="xsd:string">
           </xsd:element>
          </xsd:sequence>
         </xsd:complexType>
        </xsd:element>
       </xsd:sequence>
      </xsd:complexType>
     </xsd:element>
     <xsd:element name="CHILD_2" maxOccurs="unbounded">
      <xsd:complexType>
       <xsd:sequence>
        <xsd:element name="SUB_CHILD_2" maxOccurs="unbounded">
         <xsd:complexType>
          <xsd:sequence>
           <xsd:element name="SUB_CHILD_2_NAME" type="xsd:string">
           </xsd:element>
          </xsd:sequence>
         </xsd:complexType>
        </xsd:element>
       </xsd:sequence>
      </xsd:complexType>
     </xsd:element>
    </xsd:sequence>
   </xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:schema>
Regards
Dominic

Mario,
<i>multimapping (split IDOC into several IDocs) is possible with IDocs. We did it!</i>
Did you use IDOC packaging for this?
AFAIK,when you use multimapping that involves different adapters including one J2EE adapter and a IDOC adapter in the inbound side, multi mapping does not work.
Regards,
Bhavesh

Inbound Delivery: Inbound WHSCON IDoc with Batch Split - HowTo...?

Hello
We have another tricky problem to solve on our ERP 6.0 system.
My colleagues of Lindt UK create manually inbound deliveries (VL33N) which are replicated to the warehouse (DESADV IDoc -> TRADACOMS.ORDHDR).
When the goods arrive at the warehouse they send back a good receipts message (TRADACOMS.DLCHDR -> WHSCON IDoc).
In some cases we have a batch split because the goods have been put into different storage locations. Example:
- item 10: 200 Cases of product 4711, batch 10-2011, in storage location '0001' (free available for Sale)
- item 10:     5 Cases of product 4711, batch 10-2011, in storage location '0004' (damaged)
I am aware that in the inbound WHSCON item 10 is a main position and the two actual batch split positions are sub-items (900001 & 900002 with HIPOS = '10'). I tried to used E1EDL19-QUALF = 'BAS' (= batch split) with the sub-items but failed so far to update the inbound delivery that I can see the batch split.
I have managed to get one sub-item but not 2 of them. Somehow the system aggregates the quantities for both sub-items into the single item that shows up in the inbound delivery.
When we send the inbound delivery to the warehouse the item looks like this:
- item 10: 200 Cases (no batch yet, Putaway quantity = 0, because these data are coming from the warehouse).
QUESTION: Has anybody else been faced with a similar (if not identical) problem and how did you solve it?
Thanks a lot in advance for your valuable input.
Regards
Uwe

Hello Finbarr
I assume that you do NOT send any (suggested) batches to your warehouse. Otherwise you would have the same problem like we have that the WHSCON cannot overwrite a (suggested) batch.
However, if you just send the quantity per item then the batch split is much simpler than you suggested:
"First E1EDL24 segment:
POSNR     50
MATNR     000000000000602006
MATWA     000000000000602006
CHARG     L1519   " <<< first batch
LFIMG     37.000
VRKME     CT
"Second E1EDL24 segment:
POSNR     50
MATNR     000000000000602006
MATWA     000000000000602006
CHARG     L1880   " <<< second batch
LFIMG     37.000
VRKME     CT
Well, and as qualifier we use: E1EDL19-QUALF = 'XYZ' " a dummy
The SAP system is smart enough the realize that these two E1EDL24 segment belong to the same item yet have different batches and, therefore, yield a batch split in the delivery. The system generated the 9xxxxx numbers for this sub-item lines automatically.
Although I believe that it is not possible to change a batch in the delivery using an inbound WHSCON I would appreciate to have a final proof of this assumption. I could imagine that if you first delete the item containing the suggested batch and then add a new item with the actual batch from the warehouse it might works. However, this would require to implement a user-exit which I do not prefer.
Regards
Uwe
PS: It seems I gave an answer to the wrong question (should be EDI (DESADV): Can batches be overwritten by an inbound WHSCON (pick conf)? )

Inbound Delivery Idoc not update PIC and PGI with split batch.

Dear Experts,
Delivery outbound with split batch send to third party Warehouse to PIC and PGI from SAP, then receive the delivery inbound IDOC to update the PIC and PGI in SAP from third party. Basic Idoc DELIVERY03 it's works fine with out split batch, with split batch it's not updating PIC and PGI at the same time no error. Please advice on this
E1EDL24-HIPOS = "HIGHER LEVEL ITEM NUMEBR"
E1EDL24-HIEVW = "VALUE 1"
E1EDL19-QALF = "BAS"
Thanks and Regards,
Thiru.

Hi,
You also have to create a segment with following data as well (for batches).
E1EDL19-QUALF = "QUA".
Cheers,

DELVRY01 via IDoc with batch split

Hi Experts!
Process:
-a supplier sends delivery information via EDI to us
-the supplier cannot do a batch split, so he sends us the delivery like that
Delivery (delivery order, material number, ...)
|
|-Pos 1
|    |
|    |-box 1 (batchnumber)
|    |-box 2 (batchnumber)
|    |-box 3 (batchnumber)
|    |-box 4 (batchnumber)
|
|
|-Pos 2
|    |
|    |-box 5 (batchnumber)
|    |-box 6 (batchnumber)
|    |-box 7 (batchnumber)
|    |-box 8 (batchnumber)
|
|
Technical infos at our side (customer)
-IDoc typeDESADV
-message type: DELVRY01
-FM which perform the incoming IDoc: IDOC_INPUT_DESADV1
Problem:
How can I get the structure above into a IDoc? The problem is that in DELVRY01 (also DELVRY02 and -03, in R/3 4.7 and ERP6.0) I only can insert the batch number once per position of a delivery!
So I try to use the described E1EDL19 segment with control qualifier BAS. I also generated lower positions with the flag HIPOS in E1EDL24, but it doesn't work. The IDoc is processed correctly without errors but when I look into the delivery (via Tcode: VL32N or MIGO) I see just main items - three positions (in case I had insert one main item with two lower items)!!
SAP Documentation for delivery
Does anybody has a hint for me how should I use the DELVRY01 type ?
regards,
Steffen Fröhlich

Steffen -
I have a similar problem and was wondering if the discoveries you made would fall in that space , currently when we are sending the 856(Advanced shipping notification's ) for batch split items the standard SAP functionality is to put a "0" qty at LGMNG (actual delivered qty field)and populate the various batch quantities at the sub level. Currently the edi mapping is such that only the LGMNG is mapped. In the scenario of batch split items we are sending back "0" qty eventhough they have a valid qty ! any idea how to resolve this ?
would this require a custom code to add a new field to cumulative the batch splits ?
Is there another standard field that edi can map to pass this information?
Is there std edi mapping rules for this scenario?

Split Idoc

Similar Messages

Maybe you are looking for