Splitting SHPMNT05 idoc by ship-to

Hi,
I want to create different shipment idocs (SHPMNT05) depending on ship-to (E1EDT44-KUNNR where E1EDT44-QUALI =u2019002u2019 ).
Ex: If i have 3 deliveries in the shipment and delivery 1 and delivery 3 are with same ship-to; then i want to generate two idocs; first idoc with two deliveries( delivery1 and delivery3) and second idoc with delivery 2.
can you please guide me how to do this scenario.
Do i need to copy the print program and do i need to modify NAST table? Do i need to copy IDOC_OUTPUT_SHPMNT FM and modify?
Same time i want to restrict the IDOC creation if the material type in the delivery is 'N100'.
Thanks in advance.

Hi
See Note 753153 - FAQ: Customer-functions in IDOC_INPUT_ORDERS. Check if EXIT_SAPLVEDA_001 gives you any possibility to do it.
I hope this helps you.
Regards
Eduardo

Similar Messages

How to split the IDOCS based on document number change whit out BPM

Hi all,
Thanks,for giving the responce..
Scenario:File to IDoc.
Problum1 : How to Split the IDocs based on document number change in the source file with out BPM.My file contains document numbers like
20000092
20000092
20000092
50000050
50000050
50000065
I want 3 IDocs in target system.i.e 1 for 20000092,20000092,20000092
2 for 50000050,50000050
3 for 5000006
By using external definations i am getting 6 IDOCs insted of 3.
Problum 2:Is there any chnges/modifications in Directory when we are using external definations.
Could u plz provide me the step by step process(Repository/Directory) with using of external definations.
Thanks in advance.
Regards,
KP

HI,
for this no need of BPM.
You can think of Idoc bundling concept to acheive this-just you need to do the external definition to change the idoc occurence
/people/michal.krawczyk2/blog/2005/12/04/xi-idoc-bundling--the-trick-with-the-occurance-change
to achieve for each document no, one idoc, you can write small user defined function in the mapping with context handling you an achieve this.
For this e.g
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/6bd6f69a-0701-0010-a88b-adbb6ee89b34
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/877c0d53-0801-0010-3bb0-e38d5ecd352c
Regards,
Moorthy

Split the IDOC into multiple IDOC if the IDOC has more than 500 records

Hi All,
I developed an outbound IDOC in which we are facing an issue.
There is some limitation on the maximum idoc size it can handle.
If number of records is more than 500, split the idoc into multiple iDoc's, e.g. if it would have 1300 records , the result would be 2 iDoc's with 500 records, and the last one would have 300 records
How can i acheive this.
Regards
Jai

Hi,
1) first you need to know which message type/Idoc type you are triggering.
2) Get the Corresponding processcode from Partner profiles(WE20/ WE41).
3) Then the look for prper user-exit in the related processing FM.
4) write logic to split the IDoc accordingly.
if no proper user exit available then copy the standard processing FM and need to all ALE related configurations.
Catch hold any ABAP expert in your team to do all these.
Suresh

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.

Split one IDoc into two IDocs ?

hello all,
I wanna split one IDoc into two IDocs in XI?
how can implement it?
plx give some suggestions.
thx in advance
best regards
Yaning
Message was edited by:
Yaning Liu

Yaning,
Please find the below blog for changing the ocurrences of IDOC
/people/michal.krawczyk2/blog/2005/12/04/xi-idoc-bundling--the-trick-with-the-occurance-change
Best regards,
raj.

Splitting of idoc

*Please do let me know how to create customize process code and splitting of idoc in edi???*

Hi Abdul,
For outbound Idoc go to Tcode WE41 and for inbound use WE42.
In WE42 just click the change icon, there you will be getting Newentries tab, by clicking that you would be able to add your Custom Func Module in Your Custom Process code.
Thanks.
Note: Reward Points if you find useful.

How to split ACC_DOCUMNET03 IDOC after 100 line items for given posting

Hi Friends,
I need to create an IDOC based on the company code and posting date & a particular company code for a given date has reached 100 line items then create another IDOC for that.
EX:
I have 150 Line Items in file
120 Items are related to Company Code "1100" and remaining 30 related to company code "1200"
For this i need to create IDOC's like this
one IDOC with 100 line items which will contain 1100 company code
second IDOC with 20 line items which will contain 1100 company code
Third IDOC with 30 line items which contain 1200 company code
I assume that this can be done through UDF.
Please can you guys help me this.
Thanks in advance.
Thanks,
Vivek.

chk this:
/people/claus.wallacher/blog/2006/06/29/message-splitting-using-the-graphical-mapping-tool

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

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

Delivery idoc picks ship to contact from ship to party instead of ship-to c

Hi experts,
I have question on idoc.
The idoc is picking ship to contact information from ship to party instead of picking it from ship to contact information.
Following information are given to me.
Message Type: DESADV
Basic Type: DELVRY01
Extension: ZDELVRY
Function Group: ZIHX & Function Module: Z_RFC_IH_DELIVERY_UPDATE.
Where do I make the changes. Please help.
Regards
Vince

Hi Swathi,
Thanks for the information I am able to find the exit, but when I set a break-point in the exit(EXIT_SAPLV56K_002) it does not go to debugging mode. Can you please let me know why...
The field segments exists for ship to contact but pulling data from Ship to party, which I probably think
can set it in exit.
Can you please let me know about qualifiers...
Thanks
Vincent

Splitting of IDOC's

Hi ,
I have a problem in a File to IDOC Scenario, where I have got a IDOC with 10,000 records and I have to split it into 10 IDOCS containing 1000 records each. I have tried changing the "max record set" value but it has not worked.
Can some one help me out to do this in a efficient manner ?
Thanks in Advance,
Hemanthika

hi check the below links for reference
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/e17fdb90-0201-0010-2cb6-fe937f3bfd97
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/43e8e190-0201-0010-3ea1-d6f996cb4124
note: reward points if found helpfull
regards
chandrakanth

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

Triggering IDOCs via Shipping Point

I need to setup an interface with a 3rd party warehouse. We ship approx. 10% of our product through that warehouse, and this product is shipped to all of our customers (EDI and non-EDI). In the partner profiles, I do not see any way to configure IDOC output and input other than through partner numbers. My take on this is that I would need setup every customer in our system for these transactions and then filter out those IDOCs which are not for that warehouses shipping point? Is this correct?
I was planning on using logical message SHPCON or WHSCON and the IDoc type DELVRY01.
Thanks, Rick

Hi Richard,
We had the same situataion.
Your output needs to have the transmission medium 'A' (ALE).if you want to control the output triggering , then you can very well achieve that by using a custom table which has the allowed shipping points and refer those shipping points in the requirement (routine) to control the output.This routine needs to be attached with the output type at the message control procedure level.
Once you done that you need to do all the required ALE settings including setting up logical system,RFC destination,etc.After that you got to maintain the distribution model .This distribution model used to determine the actual receivers.After that create the partner number (refer the logical system).
This is how you can very well meet up the requirement.
Thank you.
Regards,
Karun.M

Batch split in Idoc DESADV.DELVRY01

Hi,
my scenario is non-SAP --> xi --> SAP for dispatch notifications. The sender system provides batch information on line item level, sometimes with batch split.
I am looking for a possibility to post the dispatch advice in R/3 with batch split. I already tried with multiple E1EDL24 segments and with E1EDL15, but with no success.
Does anybody have experience with batch splits in SAP Idocs or can anybody help me with a documentation?
Thanks a lot,
Philipp

hello Philipp, all you have to do is to fill the fields CHARG, HIPOS, HIEVW, only have to fill the fields HIPOS and HIEVW in the sub-items segments, then you have to manually assign these fields to the structure that receives them, for example in the user exit "EXIT_SAPLV55K_011" the structure that receives these fields is DELIVERY_COM.
Example:
IF IDOC_SEGMENT-SEGNAM = 'E1EDL24.'
   l_es_e1edl24 = idoc_segment-sdata.
   it describes table DELIVERY_COM lines reg.
   if sy-subrc = 0 and reg> 0.
      loop at delivery_com into l_ti_delivery from reg to reg.
              l_ti_delivery-charg = l_es_e1edl24-charg.
              l_ti_delivery-lichn = l_es_e1edl24-charg.
              l_ti_delivery-chspl = 'X.'
              l_ti_delivery-uecha = l_es_e1edl24-hiccups.
              modify delivery_com from l_ti_delivery transporting charg lichn chspl uecha.
      endloop.
   endif.
endif.
i hope this information can help you.
best regards.
Cesar Becerra.

Split 1 IDoc into 2

Hi All,
The scenario is SAP MDM --> PI -->SAP ECC,
MDM sends XML Message with 3 segments and a field (Material Number).
The 1st and 3rd segment have a field class type, based on which the splitting is to be done.
The 1st segment has a default class type value as 001, and when splitted the 1st and 2nd segment will go to IDoc1 along with field Material Number.
The class type of 3rd segment needs to be checked, if the value is 002 it will form IDoc2 and the common field Material Number will also be part of IDoc2. Both the resulting IDocs will be sent to ECC. Please help me with this.
Thanks,
NehaSingh

Hi Neha,
Can you kindly explain which multimapping work in your case as for my info for receiver IDOC adapter multimapping does not work for 7.0 is this functionality has been provided in some recent upgrade ? or you are using 2 message mapping and 2 interface mapping and putting a condition on Interface determination to call required mapping .Kindly explain how you achieved your requirement .
Regards,
Saurabh

Splitting SHPMNT05 idoc by ship-to

Similar Messages

Maybe you are looking for