IDOC - XML Mapping

Hi all,
My scenario is to create for each RecordSet from IDOC two RecordSet in Text file (same value are differente).
I tryed to use what is available in Mapping tool but I did not find how!
Thanks
Fouad

Thanks for you answer,
For useOneAsMany doesn't mach to my case because the recordSet number is static and I need to add a static value to a specific field,
The first solution, my outbound document containt lot of field, to replicat this structure it s not optimal.
Any idea!
Thanks,
PS: A good Article: /people/claus.wallacher/blog/2006/04/17/replication-of-nodes-using-the-graphical-mapping-tool
Fouad,

Similar Messages

File to IDoc : XML parsing in ABAP mapping

Hi,
In ABAP mapping I want to parse all of the incoming XML strings to internal table.Later I add few more fields to this table and transfer them to IDOC adapter in IDOC-XML format.In thsi case how do i get all of the input file data(converted from XML) into internal table using XML parsing in ABAP Mapping?
Thansk in advance,
RP

Hi Amil,
I insert into table but not immediately,I want all the parsed xml data into internal table and do something before I insert into DB /send it to IDOC.
I knwo how to get single Xml parsing,but how to get multple records(looping xml parse) to internal table?
Thanks,
RP
Edited by: RP@261 on Jun 3, 2009 2:14 PM

Adapter module in PI 7.1 EhP1 for Falt File Idoc to Idoc xml transformation

Hi Experts,
In PI 7.1 (EhP1) there is a java adapter module that can be added to the file adapter that automatically transforms Flat File representation of IDoc to IDoc XML. Can anyone provide the link to this particular module? Tried searching but could not get the specific module name or parameters.
The same conversion can be achieved using a standard SAP provided ABAP mapping but we need to use the module in this case.
Thanks and regards,
Shiladitya

/people/william.li/blog/2009/04/01/how-to-use-user-module-for-conversion-of-idoc-messages-between-flat-and-xml-formats
FYI~~~

Error: IDoc XML data record

Hi all,
 We have file->XI->idoc scenario and the problem we are facing is like, when the idoc structure is prepared using XSLT mapping, when the idoc is ready to get in thru the idoc adapter we are getting the following error.
Error: IDoc XML data record: In segment
Z1UKGAS_HEADR attribute occurred instead of SEGMENT 
Anyone faced the same issue....if so pls do throw some light into this issue....
We r in XI 3.0 SP13...
Thanks & regards,
Jayakrishnan

Hi,
In an IDOC structure segment attribute is requried. From the error you posted, it looks like seqment attribute is missing.
<Z>
 <IDOC BEGIN="">
 <ED SEGMENT="">
 </ED>
 </IDOC>
</Z>
Naveen

Idoc xml message in JMS adapter

Hi All,
Question 1:
My scenario is MQ series(JMS adaptr) to SAP(IDOC adptr) . In my mapping both source and target structure is same IDOC structure.Where MQ series will send IDOC xml. In such case shall i need to do content conversion at JMS adapter level or not.whthr IDOC xml can be directly handle at Mapping level without doing any content conversion in adapter level.
Question 2(viceversa):
SAP(IDOC adptr) to MQ series(JMS adaptr) . In my mapping both source and target structure is same IDOC structure.Where MQ series expect me IDOC xml. How to handle content conversion at JMS recvr adapter level.
my assumption only in case of (xml to plain) and (plain to xml) require content conversion here my Input and output is IDOC xml.

Saravanan,
As Expert Vishnu Mentioned,
>In such case shall i need to do content conversion
NO need to use
>How to handle content conversion at JMS recvr adapter level
http://help.sap.com/saphelp_nw04/helpdata/en/24/4cad3baabd4737bab64d0201bc0c6c/content.htm
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/xi/xi-adapters/how%20to%20use%20the%20content%20conversion%20module%20with%20xi%203.0%20j2ee%20jms%20adapter.pdf
Cheers
Agasthuri Doss

How to convert IDoc-XML to native Idoc-File with in SAP XI/PI

Hello,
I have a problem to Create an native IDoc-Format for an File-Receiver.
The scenario:
I get an Idoc (ZMATMAS) from a SAP System to an MATMAS-exchange-scenario. One of the non-SAP-receiver-systems needs an other native IDoc-Format as File. So I have to map the ZMATMAS to the receiver Format and write this as File. The problem is, that this file contains the data as IDoc-XML and not as native IDoc-format.
Has anybody an idea for this problem?

U need to use sender idoc adapter and file receiver adapter.
U can do file content conversion at receiver end.
Content Conversion is basically to convert a text file that contains complex structures into an XML source format and vice versa. It is present only in the File Adapter because it is one of the message protocol which will convert the structure to a desired format.
There are many blogs for File Content Conversion. Some of them are listed hereunder:-
Introduction to simple(File-XI-File)scenario and complete walk through for starters(Part1)
Introduction to simple (File-XI-File)scenario and complete walk through for starters(Part2)
How to send a flat file with various field lengths and variable substructures to XI 3.0
Content Conversion (Pattern/Random content in input file)
NAB the TAB (File Adapter)
File Content Conversion for Unequal Number of Columns
Content Conversion ( The Key Field Problem )
The specified item was not found.
You may also check the FCC documentation for Sender and Receiver:-
http://help.sap.com/saphelp_nw04/helpdata/en/2c/181077dd7d6b4ea6a8029b20bf7e55/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/d2/bab440c97f3716e10000000a155106/content.htm

Error : idoc xml record in segment attribute instead of SEGMENT

hi friends
can any one solve my problem. In message mapping I mapped with a IDOC. In message mapping I Mapped all the fields. Still I am getting the error as "IDOC XML RECORD IN SEGMENT ATRIBUTE INSTEAD OF SEGMENT" I dont know about this error.
can any one solve this problem please . I am doing this scenario since 5 days. help me..
thanks in advance
Vasu

Hi Vasudeva,
Can you pls provide little more details on the scenario ?
Also at which place are you getting this error ?
Assuming that you have created a message mapping for some source message to target IDoc message, here are some suggestions.
1) Test the message mapping. (are you getting the error in testing itself ?)
2) Apart from mandatory fields' mapping, are there any constants to be assigned to some IDoc fields ? Or any node to be disabled ? Or any such additional things...
Regards,

Sending IDOC-xml to R/3 system

Hi all
I am doing a bypass File to Idoc scenario.we taking the input file as idoc xml and sending it to R/3 system for IDOC generation.Every thing is normal but in SXMB_MONI its showing Obligatory node E1EDP10 missing while that segment was persent in the input file then we just replaced <E1EDP10> by <E1EDP10 SEGMENT="EIEDP10"> elated! it worked I thought the problem was solved "EUREKA"........But now the client is telling we should not hardcode any value in the input file they have provided i.e we shouldn't add the segment attribute.
Its bypass thats why we can't do mapping also......now we r puzzled ........
can we achieve this by changing the XSD of idoc converting the segment attribute required to optional? or what should be do plz tell us as its urgent.........
Regards
saurabh sharma

Pls avoid creating new threads for the same problem when you have a thread already open for the same issue.
Regards,
Jai Shankar

Convert IDOC XML structure to flat file - and now?

Hi,
we are working with input message ORDERS05 and want to convert it to flat file.
So we used the implementation description from "how to convert an IDOC-XML structure to a flat file....".
Looks like this is a standard procedure described here fitting for all IDOCs.
We followed the guide, making XI ready for Abap-Mapping, implemented the Abap class like described, added an interface mapping with source ORDERS05 to a mess.type dummy destination, added with type Abap-class the class implemented from the guide and completed the Int.Dir. implementation.
For comparism purpose we have two systems as receiver, one with a standard flat file with regular graph.mapping in XI, one with the Abap mapping.
Result:
Error description in SXMB_MONI:
Didn´t expect something like that! The IDOC was delivered successfully to the other simple flat file receiver.
Any idea what we made wrong (we are on SP17) or if there is a standard mistake you can do when following the guide?
Best regards
Dirk

Hi,
I've got the same problem. He the solution in my case:
The problem is:
My IDOC has no element <STDMES>, but the method IF_MAPPING~EXECUTE from the 'HOW-TO Guide' does not check this situation:
el_element = idocument->find_from_name('STDMES').
ls_edidc-stdmes = el_element->get_value().
thows the exception.
Solution:
make shure that the field STDMESis set or change the method to:
el_element = idocument->find_from_name('STDMES').
if not el_element is initial.
ls_edidc-stdmes = el_element->get_value().
endif.
Best regards
Dieter

XI IDoc complex mapping problem - help needed!

Hi all,
I am mapping WPUBON IDoc (sent as IDoc XML file) to WPUBON IDoc in R/3. However, I have a complex mapping requirement that I am trying to use the graphical tool for.
Source segment structure is such that we have:
E1WPB01 (header) has one or many E1WPB02 (items) and E1WPB05 (coupons).
E1WPB02 (items) have one or many E1WPB03 (item conditions).
So for each IDoc, we can have many items (E1WPB02), each item can have many conditions (E1WPB03) and each IDoc can have many coupons (E1WPB05).
For each E1WPB05 received, we need to take the value and divide it proportionately in order to add an extra E1WPB03 discount condition segment to each E1WPB02 item (we are a retailer and this will allow us to break down customer coupon discounts across each item in the basket). For example, if we have 2 E1WPB02 items with values $2 and $3 and the coupon is worth $1, item 1 needs a new E1WPB03 segment with a value of $0.40 and item 2 needs one with a value of $0.60.
This process needs to occur for each E1WPB05 segment (customers could have more than one coupon). No E1WPB05 segments are required in the target IDoc.
I have tried a few things but really am a bit stuck on where to start.... any ideas anyone?
Thankyou.
Stuart Richards

Stefan,
Here's some sample source XML:
<?xml version="1.0" encoding="UTF-8"?>
<WPUBON01>
 <IDOC>
 <EDI_DC40>
 <TABNAM>EDI_DC40</TABNAM>
 <MANDT>104</MANDT>
 <DOCNUM/>
 <DOCREL>620</DOCREL>
 <DIRECT>2</DIRECT>
 <IDOCTYP>WPUBON01</IDOCTYP>
 <MESTYP>WPUBON</MESTYP>
 <MESCOD>ST6</MESCOD>
 <SNDPOR>WPUX</SNDPOR>
 <SNDPRT>KU</SNDPRT>
 <SNDPRN>0799</SNDPRN>
 <RCVPOR>SAPRD1</RCVPOR>
 <RCVPRT>KU</RCVPRT>
 <RCVPRN>0799</RCVPRN>
 <REFINT>00000000000016</REFINT>
 </EDI_DC40>
 <E1WPB01 SEGMENT="1">
 <POSKREIS>0001</POSKREIS>
 <KASSID>1</KASSID>
 <VORGDATUM>20060107</VORGDATUM>
 <VORGZEIT>134512</VORGZEIT>
 <BONNUMMER>120572</BONNUMMER>
 <KASSIERER>4400</KASSIERER>
 <CSHNAME> </CSHNAME>
 <BELEGWAERS>GBP</BELEGWAERS>
 <E1WPB02 SEGMENT="2">
 <VORGANGART/>
 <QUALARTNR>ARTN</QUALARTNR>
 <ARTNR>000005034394436881</ARTNR>
 <VORZEICHEN>-</VORZEICHEN>
 <MENGE>1</MENGE>
 <REFBONNR> </REFBONNR>
 <E1WPB03 SEGMENT="3">
 <VORZEICHEN/>
 <KONDITION>PN10</KONDITION>
 <KONDVALUE>10.00</KONDVALUE>
 <CONDID/>
 <QUALCONDID/>
 </E1WPB03>
 </E1WPB02>
 <E1WPB02 SEGMENT="5">
 <VORGANGART/>
 <QUALARTNR>ARTN</QUALARTNR>
 <ARTNR>000005034394471158</ARTNR>
 <VORZEICHEN>-</VORZEICHEN>
 <MENGE>1</MENGE>
 <REFBONNR> </REFBONNR>
 <E1WPB03 SEGMENT="6">
 <VORZEICHEN/>
 <KONDITION>PN10</KONDITION>
 <KONDVALUE>20.00</KONDVALUE>
 <CONDID/>
 <QUALCONDID/>
 </E1WPB03>
 </E1WPB02>
 <E1WPB02 SEGMENT="8">
 <VORGANGART/>
 <QUALARTNR>ARTN</QUALARTNR>
 <ARTNR>000005034394469131</ARTNR>
 <VORZEICHEN>-</VORZEICHEN>
 <MENGE>1</MENGE>
 <REFBONNR> </REFBONNR>
 <E1WPB03 SEGMENT="9">
 <VORZEICHEN/>
 <KONDITION>PN10</KONDITION>
 <KONDVALUE>30.00</KONDVALUE>
 <CONDID/>
 <QUALCONDID/>
 </E1WPB03>
 </E1WPB02>
 <E1WPB05 SEGMENT="11">
 <VORZEICHEN>+</VORZEICHEN>
 <RABATTART>PTCS</RABATTART>
 <RABVALUE>6.00</RABVALUE>
 </E1WPB05>
 <E1WPB06 SEGMENT="11">
 <VORZEICHEN>+</VORZEICHEN>
 <ZAHLART>PTCS</ZAHLART>
 <SUMME>10.00</SUMME>
 <KARTENNR/>
 <ZUONR>120572</ZUONR>
 </E1WPB06>
 </E1WPB01>
 </IDOC>
</WPUBON01>
So we have one coupon worth $6.00. We have 3 items in the basket worth $10, $20 and $30 respectively. The additional E1WPB03 for each will need to contain $1, $2 and $3 respectively to give:
<?xml version="1.0" encoding="UTF-8"?>
<WPUBON01>
 <IDOC>
 <EDI_DC40>
 <TABNAM>EDI_DC40</TABNAM>
 <MANDT>104</MANDT>
 <DOCNUM/>
 <DOCREL>620</DOCREL>
 <DIRECT>2</DIRECT>
 <IDOCTYP>WPUBON01</IDOCTYP>
 <MESTYP>WPUBON</MESTYP>
 <MESCOD>ST6</MESCOD>
 <SNDPOR>WPUX</SNDPOR>
 <SNDPRT>KU</SNDPRT>
 <SNDPRN>0799</SNDPRN>
 <RCVPOR>SAPRD1</RCVPOR>
 <RCVPRT>KU</RCVPRT>
 <RCVPRN>0799</RCVPRN>
 <REFINT>00000000000016</REFINT>
 </EDI_DC40>
 <E1WPB01 SEGMENT="1">
 <POSKREIS>0001</POSKREIS>
 <KASSID>1</KASSID>
 <VORGDATUM>20060107</VORGDATUM>
 <VORGZEIT>134512</VORGZEIT>
 <BONNUMMER>120572</BONNUMMER>
 <KASSIERER>4400</KASSIERER>
 <CSHNAME> </CSHNAME>
 <BELEGWAERS>GBP</BELEGWAERS>
 <E1WPB02 SEGMENT="2">
 <VORGANGART/>
 <QUALARTNR>ARTN</QUALARTNR>
 <ARTNR>000005034394436881</ARTNR>
 <VORZEICHEN>-</VORZEICHEN>
 <MENGE>1</MENGE>
 <REFBONNR> </REFBONNR>
 <E1WPB03 SEGMENT="3">
 <VORZEICHEN/>
 <KONDITION>PN10</KONDITION>
 <KONDVALUE>10.00</KONDVALUE>
 <CONDID/>
 <QUALCONDID/>
 </E1WPB03>
 <E1WPB03 SEGMENT="9">
 <VORZEICHEN/>
 <KONDITION>PN10</KONDITION>
 <KONDVALUE>1.00</KONDVALUE>
 <CONDID/>
 <QUALCONDID/>
 </E1WPB03>
 </E1WPB02>
 <E1WPB02 SEGMENT="5">
 <VORGANGART/>
 <QUALARTNR>ARTN</QUALARTNR>
 <ARTNR>000005034394471158</ARTNR>
 <VORZEICHEN>-</VORZEICHEN>
 <MENGE>1</MENGE>
 <REFBONNR> </REFBONNR>
 <E1WPB03 SEGMENT="6">
 <VORZEICHEN/>
 <KONDITION>PN10</KONDITION>
 <KONDVALUE>20.00</KONDVALUE>
 <CONDID/>
 <QUALCONDID/>
 </E1WPB03>
 <E1WPB03 SEGMENT="9">
 <VORZEICHEN/>
 <KONDITION>PN10</KONDITION>
 <KONDVALUE>2.00</KONDVALUE>
 <CONDID/>
 <QUALCONDID/>
 </E1WPB03>
 </E1WPB02>
 <E1WPB02 SEGMENT="8">
 <VORGANGART/>
 <QUALARTNR>ARTN</QUALARTNR>
 <ARTNR>000005034394469131</ARTNR>
 <VORZEICHEN>-</VORZEICHEN>
 <MENGE>1</MENGE>
 <REFBONNR> </REFBONNR>
 <E1WPB03 SEGMENT="9">
 <VORZEICHEN/>
 <KONDITION>PN10</KONDITION>
 <KONDVALUE>30.00</KONDVALUE>
 <CONDID/>
 <QUALCONDID/>
 </E1WPB03>
 <E1WPB03 SEGMENT="9">
 <VORZEICHEN/>
 <KONDITION>PN10</KONDITION>
 <KONDVALUE>3.00</KONDVALUE>
 <CONDID/>
 <QUALCONDID/>
 </E1WPB03>
 </E1WPB02>
 <E1WPB06 SEGMENT="11">
 <VORZEICHEN>+</VORZEICHEN>
 <ZAHLART>PTCS</ZAHLART>
 <SUMME>10.00</SUMME>
 <KARTENNR/>
 <ZUONR>120572</ZUONR>
 </E1WPB06>
 </E1WPB01>
 </IDOC>
</WPUBON01>
The 3 new segments required are highlighted in bold. Note that coupon segment can be repeating but is not required in the target message.
Cheers

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

IDOC XML to 3rd Party WebService

Hello,
I am new to XI. I want to now the possiblity and effort involved in using XI to receive an IDOC from an R/3 system and forward that IDOC as IDOC-XML to a WebService on a target 3rd Party application. The 3rd Party WebService would have as oe of its input the IDOC-XML and will return a status of success or failure of RECEIPT.
Is this a complex map in XI?
Thanks in advance for any information here.

Hi,
>>>>>Is this a complex map in XI?
the mapping itself - depends how many values you
need to change (materials, partners ) and how
lookup etc.
the process - if you want to use the web service
in a sync way (to know the status) you will need
to use a BPM:
IDOC - BPM - sync WS
if the mapping will be easy (or non at all - just IDOC-XML) then the dev should take 1 day
+ tests etc...
Regards,
michal

How to send IDOC as IDOC XML with out touching IR

Hi Guru's,
I have a scenario, where i need to transfer IDOC into Just IDOC XML..
No Mapping is done...
I know v can do without touching repository objects..
As Per Bhavesh said in one of the blog.....no need to import idoc into repository..
I am just wondering how will it possible?
My Understanding is as follows.........
First Go to ID.
Step 1)
As sender is IDOC we will not create sender agreement & sender communication channel..
Step 2)
Goto Receiver Determination
Sender:
Service : Business System for SAP R/3
Interface : IDOC
NameSpace: urn:sap-com:document:sap:idoc:messages
Receiver:
Service : Receiver Business system.
Interface Determination
Configured Inbound Interfaces:
InboundInterface : IDOC
Interface Mapping : NIL
ReceiverAgreement :
Sender Service : SAP R/3 Business system Name.
ReceiverService: will give receiver Business system.
ReceiverInterface : IDOC
Receiver Namespace:urn:sap-com:document:sap:idoc:messages
As Bhavesh said there is no need to import IDOC into Repository.
main intention is no need to touch Repository..
we are giving IDOC name in Receiver Interface and sender Interface.
Here my doubt is from where this IDOC will come as u are not importing IDOC into Repository.
Please need clarification..
Thanks in Advance..........
Regards,
Reehan.

Reehan,
First of all thanks for following everything I had mentioned. I remember the thread quite well.
Asnwering your question,
>Here my doubt is from where this IDOC will come as u are not importing IDOC into Repository.
Please need clarification..
When the Idoc is triggered from the SAP system , the first thing that happens is that it tries to locate the Business System registered in the SLD for it. It uses the logical system name to be able to do this.
After it locates the bsuiness system, this is used as the sender service and the idoc name and the idoc namespace are used as the Sender interface and interface namespace.
Next, using these details, the runtime integration engine of XI is now able to fill the SOAP header for these details and these details are used in the pipeline steps of XI ( Receiver determination ) to determine the receiver and so on.
The idoc imported in the IR is used just to allow us to have the Idoc metadata for mapping in the IR . The actual runtime metadata is not dependent on the Idoc improted in the IR.
Regards
Bhavesh
PS : Did this scenario work?

Error : IDoc XML data record: In segment attribute occurred instead of SEGM

hi friends
i am doing the file to idoc scenario. in message mapping i had done the static test. but what ever the fields i mapped in the idoc it was not populated in the idoc. and i am getting the error as
error :IDoc XML data record: In segment attribute occurred instead of SEGMENT
can any one solve the problem please
thanks in advance
Vasu

Hi Vasudeva,
Pls do check the nodes which you have mapped to. Also make sure that your SEGMENT field in the target structure is mapped properly.
Cheers
JK

Error : idoc xml data record : in segment attribute instead of SEGMENT

hi all
i am doing the file to idoc scenario. in that i am getting the error
error : IDOC XML Data record : In segment attribute instead of SEGMENT
i am doing this scenario since 4 days.
can anyone help me
thanks a lot
Vasu

in ref. to my post in your earlier thread.
>>>>
in your mapping check, in your IDOC if Begin , segment etc are mapped to a constant say '1'.
Also ref: In segment IDOC attribute I occurred instead of SEGMENT

IDOC - XML Mapping

Similar Messages

Maybe you are looking for