File to Idoc (message split)

Hi Gurus,
I have a incoming xml file which is split into multiple debmas idoc for ecc.
In message-mapping, message-tab
source message occurance is set as '1' and target is set with "0...unbound"
On target:idoc
There is NO mapping for Messages and Message1 nodes. DEBMAS06 is mapped to source-field to create as many idocs. IDOC has NO map and BEGIN is set as constant(1).
When i run the test, my result is as below: (NO Idoc)
<?xml version="1.0" encoding="UTF-8"?>
<ns0:Messages xmlns:ns0="http://sap.com/xi/XI/SplitAndMerge">
<ns0:Message1></ns0:Message1>
</ns0:Messages>
When i ran the scenario with a test-file, got following error message:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_IDOC_RUNTIME</SAP:Code>
<SAP:P1>MSGGUID C834F5D4235B44BD373F9F12AA5B0674: Tag found instead of tag IDOC BEGIN=</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Error: MSGGUID C834F5D4235B44BD373F9F12AA5B0674: Tag found instead of tag IDOC BEGIN=</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>

Hi,
IDOC multimapping (it's called bundling) is supported please fallow that Michal's blog:
[/people/michal.krawczyk2/blog/2005/12/04/xi-idoc-bundling--the-trick-with-the-occurance-change|/people/michal.krawczyk2/blog/2005/12/04/xi-idoc-bundling--the-trick-with-the-occurance-change]
You need to modify the xsd definition. It works perfect. E.g. in my company we are splitting 1000 idocs in one run.
Best regards,
Wojciech

Similar Messages

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

IDOC Message Splitting with Logic

Hi, I have a business requirement for IDOC to IDOC mapping where the incoming IDOC line item should be split in to multiple line items based on a field value and also the resulting IDOC will be split in to multiple IDOCs based on a limitation on the number of line items. Without using BPM, have anybody used SAP XI to efficiently perform the above logics with proper check logics and error controls ? Appreciate your responses.

Hi Raj,
Try this:
You can use Split by Value node function and set the properties of the split by value as: Each Value.So the for every different number,different item will be created.
Using the Node Functions you can solve your problem.
1.SplitByValue:
The SplitByValue() function is the counterpart to removeContexts(): Instead of deleting a context, you can insert a context change in the source value queue. You then receive this element for each inserted context change instead of a top node element. However, for this to be possible, the top node source field must be assigned a top node target field and minOccurs must be >0. You can insert a context change in the queue after each value, after each change to the value, or after each tag without a value.
2.RemoveContexts:
You use removeContexts () to delete all the top contexts for an element. This removes all top hierarchy levels, so that all elements of the target queue are assigned to a root element of the source queue.
Advanced user-defined functions can import either just one context into the input arrays, or complete queues. Make your selection by selecting or deselecting the Save Entire Queue in Cache checkbox in the function editor.
3.CreateIf:
CreateIf node function is used to create a node if true value is passed to it otherwise suppress it.
4.collapseContext
To remove the context in between the value and transfer only one value at a time
5.useOneAsMany
First Input:
The value which is needed to be repeated.
Second Input:
It defines how many times the first input should be repeated.
Third Input:
It define when the context should be changed (on the basis of the required output
Please go through the given link hope it will be helpful to you.
/people/sravya.talanki2/blog/2005/12/08/message-mapping-simplified-150-part-ii
Message Mapping Simplified Part II
/people/sravya.talanki2/blog/2005/12/08/message-mapping-simplified-150-part-ii
Replication of Nodes Using the Graphical Mapping Tool
/people/claus.wallacher/blog/2006/04/17/replication-of-nodes-using-the-graphical-mapping-tool
Message Splitting Using the Graphical Mapping Tool
/people/claus.wallacher/blog/2006/06/29/message-splitting-using-the-graphical-mapping-tool
Also check this weblogs:
/people/sravya.talanki2/blog/2005/08/16/message-mapping-simplified--part-i
/people/sravya.talanki2/blog/2005/12/08/message-mapping-simplified-150-part-ii
Split by value
http://help.sap.com/saphelp_nw04/helpdata/en/21/3bb8c495125e4eb5969f0377885fe0/content.htm
For value mapping check this video presentation and weblog:
/people/sreekanth.babu2/blog/2005/02/23/value-mapping-replication
/people/community.user/blog/2007/01/08/valuemapping-using-the-graphical-mapping-tool
https://www.sdn.sap.com/irj/sdn/docs?rid=/webcontent/uuid/110ff05d-0501-0010-a19d-958247c9f798#xi [original link is broken]
/people/claus.wallacher/blog/2006/04/17/replication-of-nodes-using-the-graphical-mapping-tool
Function formatByExample:
/people/sundararamaprasad.subbaraman/blog/2006/02/21/real-example-for-formatbyexample
Split by value, remove context and collapse context:
/people/sravya.talanki2/blog/2005/12/08/message-mapping-simplified-150-part-ii
Reward points if this helps
Regards
Pragathi.

File to IDoc (Message Type - FLIGHTBOOKING_CREATEFROMDAT01) Error

Hi all,
Error i'm getting -- "Error: IDoc XML data record: In segment attribute occured instead of SEGMENT"
Tried removing SEGMENT value to 1 for both segments and for individual segments with no luck ....
Awaiting your invaluable replies on this thread.
Thanking you in advance
Sreedhar Kurella
Message was edited by:
Sreedhar Kurella

Hi Sergio,
Though i couldnot find exact menu as per your suggestion i followed
rwb -> comp. monitoring --> Clicked Adapter engine server
clicked button 'Adapter Monitoring' which popped up another window where in which upon clicking 'File' , I found following error information :
Retry interval started. Length : 600000.000s
Error: File 'C:\Flight01.xml' - deleting after processing failed
Processing started
I rechecked the file name (including any accidental spaces) in C drive and again copied the file name from Comm Channel and renamed the file in C drive with same and reactivated comm channel with no luck ....
file has no 'read-only' attribute checked .....XI is running on windows 2003 and rechecked the persmission of the file where in which i made sure my user id (nwwadm) has got all permissions on this file...
still now luck
btw -- scenario is converting XML to IDoc to 106 client ....as i haven't filled any EDI_DC40 segment, idoc failed in 106 client .... will that failure be any cause of this anamoly behavior on file deletion ? i believe it shouldn't ?
any pointers pls ?
Thanks

How to split messages without using Message split (BPM)

In file to file scenario how to split messages coming from file without using Message split (BPM)

Thank you very much.

Scenario:file to idoc

dear experts
here my scenario is file to idoc
message is sent successfully from sender but which is not received in receiver i.e,in r/3.
the error which i found id
error category:idoc_adopter
error code:attribute_inv_rcv_serv.
plz any one can help me?????????
regards
somesh

hi
Receiver service cannot be converted into an ALE logical system
/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions
In Business System(R/3) 'Adapter specific identifiers' chooset 'Compare System Landscap Directory' refersh cache and activate objetcs
Note: reward points if solution found helpfull
Regards
Chandrakanth.k

Message Split -- File to Idoc Scenario - ( Without BPM )

I have multiple records coming to XI in a File and I have to create Multiple Idocs to R/3.
Due to Complexity of mapping I'm splitting Maaping step into 2 message Mappings.
A-->B
B-->C
In the 2nd Mapping step I'm doing message Split meaning for each Source record I'm creating multiple Idocs ( To be precise each record on the source becomes 4 idocs in the Target.
2nd Mapping step is as follows
Source 1..1
Sourcerecord 0.. Unbounded
    field1 0..1
    field2 0..1
    filed3 0..1
Target
Message 1
    Idoc   1.. Unbounded
      Idoc Structure..
Message 2
      Idoc   1.. Unbounded
Message 3
      Idoc   1.. Unbounded
Message 4
      Idoc   1.. Unbounded
So based on some criteria each record of Source will be mapped to 4 Messages ( 1 each under each Message )
Is it possible to do this without BPM?. Iam sending all these Idocs to same R/3 System.
Thanks for any help..RK

Hi,
See the blog
/people/michal.krawczyk2/blog/2005/12/04/xi-idoc-bundling--the-trick-with-the-occurance-change
<i>Basicly we have 2 ways of handling such scenarios:
- we can use a block step and send multiple IDOCs from our BPM
- we can also do a little trick and send multiple IDOCs from the XI without a BPM
The first approach is a standard XI approach. It involves the use of a BPM
so the speed of this transfer many not be very good in case you'd like to send
hundreds or thousands of IDOCs in just one call.
The second approach uses a little trick that was mentioned several times
on the XI Froum by a number of XI developers but is still not very clear to the XI newbies.
It allows us to send multiple IDOCs without the use of a BPM. Most probably this will be your choice
if you'd like to use such 1:N (IDOCs) scenarios effectively.</i>
Please see the bwlow threads also..
IDOC Splitting
File To IDOC Thru XI
Multi-Mappings in BPM (XI 3.0)
Please let me know , your prob..is solcev or not..
Regards
Chilla..

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

Message Split: File to Multiple IDOC Types

Hi,
I'm attempting to perform a multi-mapping using BPM where I have File -> XI -> IDOC.
The result will be 3 DIFFERENT IDOC types, but depending on the payload of the file, not all will be created. I have followed the steps in this weblog: https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/2748. [original link is broken] [original link is broken] [original link is broken] [original link is broken]
This works fine as long as all 3 messages are being created, however if only 2 of 3 IDOCs are to be created, I receive an error in the PE.
I have set the occurances of the target messages as 0...1 in the Message and Interface Mappings.
Any ideas would be greatly appreciated.

><i>This works fine as long as all 3 messages are being created, however if only 2 of 3 IDOCs are to be created, I receive an error in the PE.</i>
Just noticed this
The reason is when you have a 1:N mapping inside the BPM, all messages need to be compulsorily be created. If you have 3 messages in the target side all 3 messages / idoc's need to be created as the output of your multimapping.
As a workaround, if the condition which you want to check does not exist and you do not want the idoc to be created, in the mappingcreate the idoc, use some dummy flag and then use a switch in the BPm to decide if the idoc is to be sent to the target system or not.
Regards
Bhavesh

File to multiple IDOC(message)

Hi
I need to map file to multiple IDoc type that means on source message have two target message . Any ideas how to achieve that
Thanks in advance
Regards
Swatantra

refer these weblogs that will give you an idea;
Multi Mapping -
BPM involved:
/people/sudharshan.aravamudan/blog/2005/12/01/illustration-of-multi-mapping-and-message-split-using-bpm-in-sap-exchange-infrastructure
/people/narendra.jain/blog/2005/12/30/various-multi-mappings-and-optimizing-their-implementation-in-integration-processes-bpm-in-xi
Without BPM:
/people/jin.shin/blog/2006/02/07/multi-mapping-without-bpm--yes-it146s-possible

Message has error status at outbound side File To Idoc Scenario

hi ,
In my File to Idoc scenario , when i go to sxmb_moni , i found that its showing red flag at Outbound Status Tab and showing message "Message has error status at outbound side".
When i go to IDX5 and and select my idoc and click on Transaction Id it shows "Password logon no longer possible - too many faile" .
Please suggest what may be the problem ?
Regards,
Rohit

1. First check the RFC destination name used in receiver Idoc adapter communication channel.
2. As i said earlier, in sm59 transaction in XI gui, u can check same rfc destination under type 3. There check the logon credentials and the username.
3. Now goto the R3 system GUI and check in su01 that same user is locked or not. If locked unlock it.
4. And if u change the password of that user, then do the similar change in XI -> sm59 -> rfc destination logon credential
Regards,
Prateek

File to IDOC scenario-no messages in SXMB_MONI

Hi all,
   I know this is asked so many times ,I checked some links but couldn;t find out the gap where it happened.
I am doing a File to IDOC scenario through XI mapping.
I am not getting any messages in SXMB_MONI.
When I check Communication Channel monitering in Runtime Workbench, it shows processing successfully, then it should generate messages in SXMB_MONI and intimate whether the scenario created is correct or not right!
Please help.
My scenario goes like this:
Sender : Business service(Some file location)
Used File adapter for sender communication channnel.
Receiver : Business system(SAP R/3)
Used IDOC Adapter for receiver communication channel.
One more thing is,do I need to create logical system for Business service also?If so, where do I maintain it?(In SAP R/3 or in XI system?)
Till now,I maintained my XI system as logical system in WE20 and I didn't create any logical system for business service in any system.Does it create main problem?

Hi , I am able to poll the files from file location now.and I am receiving IDOC into SAP R/3 with status 56.I already created partner for file path as a logical system and assigned inbound parameters with respective message type . Even the status shows :
An inbound partner profile could not be found with the following key:
/LSDEMO/LS//DEBMAS////
This involves the key fields of table EDP21:
-SNDPRN partner number of sender
-SNDPRT partner type of sender
-SNDPFC partner function of sender
-MESTYP logical message type
-MESCOD logical message code
-MESFCT logical message function
-TEST    test flag
I already manitained following data and there is one record in EDP21.
SNDPRN = LSDEMO
SNDPRT = LS
SNDPFC = LS
MESTYP   = DEBMAS
MESCOD = space
MESFCT = space
TEST = space
EVCODE   = DEBM
SYNCHK = X
METHOD = space
USRTYP = space
USRLNG = space
INMOD = space
DCART = space
And please let me know whether I have to maintain outbound parameters also for my partner in XI system.I didn't see any difference even I maintained it.
And my IDOC takes another port rather than I mentioned in my SNDPRN(sender port) of my IDOC control record in message mapping.Let me know whether it's mandatory to maintain port name with SAP<XXX>convension,because IDOC in R/3 is picking the port with that naming convension.
Edited by: Jaya on Feb 26, 2010 10:17 AM
Edited by: Jaya on Feb 26, 2010 10:27 AM

Doubt in fields - message mapping (file 2 idoc scenario)

while doing message mapping in file 2 idoc scenario, i could not able find the values for some field names
( i am following this wiki help
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/profile/2007/05/11/fileToIDOC& )
cremas04 idoc
vendorNo LIFNR
vendor name Name1
Pur_org ? ( I could not able locate field with the similar desc in idoc MT side)
Company code ?
Acc_Grp ?
Search term MCOD1
Address ADRNR
City ORT01
Pin_code PSLTZ
could you help me out with this?
Message was edited by: praba
praba

hi,
I got the answer.

Idoc(receiver) message splitting using BPM

Hi,
could you provide some blogs which is useful for Idoc (as a Receiver) message splitting (1:N scenario) using BPM.
I have gone thru some of the Blogs, i didn't find good one according to this scenario.
Thanks
Praba

Hi Michal,
Thanks for ur reply.
You said " if you have one message and want to have multiple IDOCs
there is no need for a BPM -
you just need to change IDOC occurance - that's all"
I agree to your point.
My scenario is more or less same but "With single message , i need to generate multiple Idocs" based on synchronous proxy response from R3. That is the reason we already gone with BPM.
Already i used the BPM in my interface due to req. It was working. Earlier i was posting single Idoc to R3 with multiple Header segment (each Header segment has one quantity)
Now due to req. change, for each single quantity (quantity is my source Message Type field), i need to post single Idoc to R3 if i get response from R3.
My XI version PI 7.0 SP14
Idoc structure:
   <xsd:attribute name="SEGMENT" type="xsd:string" fixed="1" use="required"
xmlns:xsd="http://www.w3.org/2001/XMLSchema" />
   </xsd:complexType>
- <xsd:complexType name="WPUWBW.WPUWBW01";>
- <xsd:annotation>
   <xsd:documentation>POS interface: Upload goods movements</xsd:documentation>
   </xsd:annotation>
- <xsd:sequence>
<xsd:element name="EDI_DC40" type="EDI_DC40.WPUWBW.WPUWBW01"; />
   <xsd:element name="E1WPG01" type="WPUWBW01.E1WPG01"; minOccurs="0"
   maxOccurs="9999999999" xmlns:xsd="http://www.w3.org/2001/XMLSchema" />
   </xsd:sequence>
   <xsd:attribute name="BEGIN" type="xsd:string" fixed="1" use="required"
xmlns:xsd="http://www.w3.org/2001/XMLSchema" />
   </xsd:complexType>
   </xsd:schema>
Already I am using this Idoc structure in various interfaces also. If i edit the occurance of the this Idoc and import in External definition with same name, I feel it afffect mapping in other interfaces also.
Inputs are highly appreciated.
Edited by: Prabaharan Rangasamy on May 22, 2009 4:14 PM

Message split - XML to IDOCs - (1:n) mapping

I have to split an incoming XML(in idoc DEBMDM format) from MDM to 2 Idocs (ADRMAS & DEBMAS).
Target message set to occurences "0:unb".
Have tested my graphical-mapping in IR and its working fine. Tested the configuration and got error in IB.
In SXMB_MONI i find the error message,
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="OUTBINDING">CO_TXT_MMF_ENGINETYPE</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Messages in multi-message format can only be sent to one Adapter Engine</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Read in few threads about creating a "custom adapter module"...is this right? if so.... how to proceed ?
Appreciate any help.

Ram,
Message Split using Graphical Mapping that ur using now supports adapter which are on same J2EE engine .
In ur case Ur trying to post IDOCS ( I suppose ) which is not
supported in using Graphical mapping.
U need to change the design.
-- Kavitha

File to Idoc (message split)

Similar Messages

Maybe you are looking for