File (xml) xi IDoc

The messages in the messeage monitoring are showing an general error and the error type is XI_J2EE_ADAPTER_XI_HANDLER.
Can you please suggest what needs to be done?
Best Regards
Fatih

Hi Fatih
Can you provide the details of setting you did for File and Idoc adapter
for IDOC on reciever side you need to create partner profile
Regards
Mitesh

Similar Messages

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 to FILE(xml) graphical mapping using node function createIf

Greetings All,
            My Scenario is Idoc to File(XML)
Target Structure is
                       MO_MAT_LAN....................(0: unbound)
                            LAN_KEY.......................(0 :1)
                            DESCRIPTION.................(0 : 1)
Source MATMAS Idoc
                       E1MAKTM.........................(0 : 99)
                            SPRAS_ISO..................(0 :1)
                            MAKTX..........................(0 :1)
initially i had mapped E1MAKTM----->MO_MAT_LAN but i dont want target node MO_MAT_LAN to be created when the SPRAS_ISO is equal to EN
I have tried using node function createIf but the node is geting created only once although the input stucture is having occurance more than 5.
Can anyone please help me to achive this.
Many thanks,
Rohit

U have to use:-
SPRAS_ISO mak the context to E1MAKTM compare (Use equals) it with Constant function EN out put to be given to If without else and in then Give E1MAKTM and map out put of If node to MO_MAT_LAN.
chirag

I need one XML File containing one Idoc fields Say Orders01

hiall,
i need one XML File containing one Idoc fields Say Orders01
bye
satish

hi,
<?xml version="1.0" encoding="iso-8859-1"?>
<ORDERS02>
<IDOC BEGIN="1">
 <EDI_DC40 SEGMENT="1">
 <TABNAM>EDI_DC40</TABNAM>
 <MANDT>800</MANDT>
 <DOCNUM>0000000000213213</DOCNUM>
 <DOCREL>46B</DOCREL>
 <STATUS>30</STATUS>
 <DOCTYP>ORDERS02</DOCTYP>
 <DIRECT>1</DIRECT>
 <RCVPOR>A000000032</RCVPOR>
 <RCVPRT>LS</RCVPRT>
 <RCVPRN>sell</RCVPRN>
 <RCVSAD/>
 <RCVLAD/>
 <STD/>
 <STDVRS/>
 <STDMES/>
 <MESCOD/>
 <MESFCT/>
 <OUTMOD>4</OUTMOD>
 <TEST/>
 <SNDPOR>SAPSID</SNDPOR>
 <SNDPRT>KU</SNDPRT>
 <SNDPRN>23334</SNDPRN>
 <SNDSAD/>
 <SNDLAD/>
 <REFINT/>
 <REFGRP/>
 <REFMES/>
 <ARCKEY/>
 <CREDAT>20061019</CREDAT>
 <CRETIM>205734</CRETIM>
 <MESTYP>ORDERS</MESTYP>
 <IDOCTYP>ORDERS02</IDOCTYP>
 <CIMTYP/>
 <RCVPFC/>
 <SNDPFC/>
 <SERIAL></SERIAL>
 <EXPRSS/>
 </EDI_DC40>
 <E1EDK01 SEGMENT="1">
 <KZABS>X</KZABS>
 <CURCY>USD</CURCY>
 <WKURS>1.000</WKURS>
 <ZTERM>ZZZZ</ZTERM>
 <BSART>EC</BSART>
 <BELNR>300024455</BELNR>
 <RECIPNT_NO>misssa</RECIPNT_NO>
 </E1EDK01>
 <E1EDK14 SEGMENT="1">
 <QUALF>014</QUALF>
 <ORGID>1000</ORGID>
 </E1EDK14>
 <E1EDK14 SEGMENT="1">
 <QUALF>009</QUALF>
 <ORGID>001</ORGID>
 </E1EDK14>
 <E1EDK14 SEGMENT="1">
 <QUALF>011</QUALF>
 <ORGID>1000</ORGID>
 </E1EDK14>
 <E1EDK03 SEGMENT="1">
 <IDDAT>012</IDDAT>
 <DATUM>20061019</DATUM>
 </E1EDK03>
 <E1EDKA1 SEGMENT="1">
 <PARVW>LF</PARVW>
 <PARTN>000002344</PARTN>
 <TELF1></TELF1>
 <BNAME></BNAME>
 </E1EDKA1>
 <E1EDKA1 SEGMENT="1">
 <PARVW>WE</PARVW>
 <LIFNR>1000</LIFNR>
 <NAME1></NAME1>
 <STRAS></STRAS>
 <ORT01></ORT01>
 <PSTLZ>4444</PSTLZ>
 <LAND1>EN</LAND1>
 <TELF1></TELF1>
 <SPRAS>D</SPRAS>
 <ORT02></ORT02>
 <REGIO>02</REGIO>
 </E1EDKA1>
 <E1EDK02 SEGMENT="1">
 <QUALF>001</QUALF>
 <BELNR>600060324</BELNR>
 <DATUM>20061019</DATUM>
 <UZEIT>205736</UZEIT>
 </E1EDK02>
 <E1EDK17 SEGMENT="1">
 <QUALF>001</QUALF>
 <LKOND>EXW</LKOND>
 <LKTEXT>london</LKTEXT>
 </E1EDK17>
 <E1EDK18 SEGMENT="1">
 <QUALF>001</QUALF>
 <TAGE>12</TAGE>
 <PRZNT>4.000</PRZNT>
 </E1EDK18>
 <E1EDK18 SEGMENT="1">
 <QUALF>002</QUALF>
 <TAGE>30</TAGE>
 <PRZNT>2.000</PRZNT>
 </E1EDK18>
 <E1EDK18 SEGMENT="1">
 <QUALF>003</QUALF>
 <TAGE>45</TAGE>
 </E1EDK18>
 <E1EDP01 SEGMENT="1">
 <POSEX>00010</POSEX>
 <PSTYP>0</PSTYP>
 <KZABS>X</KZABS>
 <MENGE>1.000</MENGE>
 <MENEE>EA</MENEE>
 <BMNG2>1.000</BMNG2>
 <PMENE>EA</PMENE>
 <VPREI>3</VPREI>
 <PEINH>1</PEINH>
 <NETWR>3</NETWR>
 <MATKL>001</MATKL>
 <BPUMN>1</BPUMN>
 <BPUMZ>1</BPUMZ>
 <E1EDP20 SEGMENT="1">
 <WMENG>1.000</WMENG>
 <EDATU>19</EDATU>
 </E1EDP20>
 <E1EDP19 SEGMENT="1">
 <QUALF>002</QUALF>
 <IDTNR>100</IDTNR>
 </E1EDP19>
 <E1EDP19 SEGMENT="1">
 <QUALF>001</QUALF>
 <KTEXT>some text</KTEXT>
 </E1EDP19>
 </E1EDP01>
 <E1EDS01 SEGMENT="1">
 <SUMID>002</SUMID>
 <SUMME>3</SUMME>
 <SUNIT>USD</SUNIT>
 </E1EDS01>
</IDOC>
</ORDERS02>
Regards,
michal
<a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions">XI / PI FAQ - Frequently Asked Questions</a>

Mapping from nested to one table (sales order) XML to IDOC

Hello,
I have to map a xml file to the IDOC SALESORDER_CREATEFROMDAT2.SALESORDER_CREATEFROMDAT202.
How I can map the the longtext from the XML file to the IDOC struktur.
Part of the XML file, there could be n times BPosition with n times longtext. The longtext must be map with a table. I some case its a mapping from nested to mornal table.
 <BPosition>
 <lpos>1</lpos>
 <bbl_sap_nr/>
 <milvonr/>
 <kurztitel/>
 <anzbest/>
 <anzliefer/>
 <kostenpflichtig/>
 <longtext>
 <line>pos1 zeile1</line>
 <line>pos1 zeile 2</line>
 </longtext>
 </BPosition>
thanks for your help.

Hi, I have to map this 1 XML to 1 IDOC
XML:
<?xml version="1.0" encoding="UTF-8"?>
<ns0:MT_Milver xmlns:ns0="http://ccssap.bfi.admin.ch/milver">
 <bestellung>
 <besteller>
 <bestellnr/>
 <auftragdefit/>
 <wempfdebit/>
 <bestelldat/>
 <lieferdat/>
 <anzpos/>
 <language/>
 <adrzeile1/>
 <adrzeile2/>
 <adrzeile3/>
 <adrzeile4/>
 </besteller>
 <Kopf>
 <Lkopf>Kopf1 zeile1</Lkopf>
 <Lkopf>Kopf1 zeile2</Lkopf>
 </Kopf>
 <BPosition>
 <lpos>1</lpos>
 <matnr/>
 <milvonr/>
 <kurztitel/>
 <anzbest/>
 <anzliefer/>
 <kostenpflichtig/>
 <bemerkung>
 <line>pos1 zeile1</line>
 <line>pos1 zeile 2</line>
 </bemerkung>
 </BPosition>
 <BPosition>
 <lpos>2</lpos>
 <matnr/>
 <milvonr/>
 <kurztitel/>
 <anzbest/>
 <anzliefer/>
 <kostenpflichtig/>
 <bemerkung>
 <line>pos2 zeile1</line>
 <line>pos2 zeile 2</line>
 </bemerkung>
 </BPosition>
 </bestellung>
</ns0:MT_Milver>
IDOC:
The Idoc have a segment for the longtext (table).I have to map, lpos, line into E1BPSDTEXT from SALESORDER_CREATEFROMDAT2. Its now more clear?

Xml of IDOC in R/3

Scenario is IDOC to File. My ABAP team given some ref Idoc numbers which are there in R/3 system for test data.They are not posting Idoc from R/3 system to XI.They are asking me to take the data from R/3 system and post it thru XI RWB.
So,how can I get xml (of Idoc) from R/3 system.so that i can the xml(of idoc) from RWB.

Hi Naresh,
Hasnt ALE configuration been done?
I think you cant download XML if you have IDoc numbers.
If ALE Configuration has not been done. Do the same. Wont take more than 10-15 minutes to do.
Then using WE19 you can send the idocs.
Regards,
Sumit

Idoc to file scenaro ( sending IDOC as it is to NON-SAP)

Hi Experts,
I am doing idoc to file scenario.
I am having SAP R/3 system with 3 clients(100, 200 & 300), IDOC is comming from SAP R/3( any one of the client)
In this is scenario, I am sending IDOC-XML as it is to the NON-SAP system.
I heard that, i can do in 3 ways. those are
1. Without any repository objects: you can go ahead with No interface mechanism on the target side.
2. Without message type: create a message interface whose message type would be idoc itself
3. With message type: export the IDOC as xsd file and re import the xsd file as an external definition.
If i go without IR objects,Please tell me whether i need to create Interface objects(i.e. DT,MT & MI) & Mapping objects (MM & IM) or not for the reciever.
MY ASSUPTION:
step1: I will import the IDOC into IR.
step2: Directly i will go to the ID without desiging any object in IR ( is it ok).
Is my assuption or correct or not?, please tell me.
So please tell me the entire scenario how to achieve this.
Please help in this issue.

Hi Laxmi
1. Without any repository objects: you can go ahead with No interface mechanism on the target side.
-- Not Possible
2. Without message type: create a message interface whose message type would be idoc itself
-- No need for the Message Interface for IDOC. You will directly import the IDOC and do the Mapping
3. With message type: export the IDOC as xsd file and re import the xsd file as an external definition.
-- This is Possible. you are export the IDOC as XSD File and reimport the same. so there is no difference. If you are going to change the IDOC Structure then this is possible.
Here I am sending some links which are useful for IDOC to File Scenario. Please go thru the links given below..
While doing an IDOC -> XI -> File scenario, The Points to noted are:
1. You dont need a DT, MT or a message interface for the IDOC as it itself acts as the Message Interface.
2. You import the IDOC and use the same in your mapping.
3. In this configuration note that you dont have a sender agreement as you dont have a sender IDOC adapter.
If it is that you wanted to send an IDOC from XI (File to IDOC) , then in this case:
points 1 and 2 will remain, but the 3 will not. You will need a sender agreement for the file and a receiver agreement for the IDOC.
IDOC -> File scenario ref:
IDoc-XI-File scenario
File -> IDOC ref:
File to IDOC
To be able to trigger your IDOC from the SAP ISU system, you will have to set the partner profile in we20. Select your Business System (mostly under Logical system) and then create Outbound entries for whichever IDOC you want to trigger.
You define your basic type also in your partner profile settings, Please go thru the following links to get a better idea about partner profile:
http://help.sap.com/saphelp_nw04/helpdata/en/dc/6b833243d711d1893e0000e8323c4f/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/dc/6b7cd343d711d1893e0000e8323c4f/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/32/692037b1f10709e10000009b38f839/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/5e/b8f8bf356dc84096e4fedc2cd71426/frameset.htm
Also, I would suggest that you go through this blog by michal if any issue arises,
/people/michal.krawczyk2/blog/2005/03/29/xi-error--unable-to-convert-the-sender-service-to-an-ale-logical-system
/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions
I hope this answers your query.
Award the POINTS if it is useful **
Cheers
Vasu

How to encode XML to Idoc and decode Idoc to XML in business connector?

Hi all,
first of all: thanks for all, who are reading and perhaps responding this question!
Here some facts and my question(s):
The facts:
- I have the business connector version 4.6!
- I'm not working with any SAP Netviewer!
- I have XML files on an FTP-server and Idoc-files on an FTP-server --> so no connection between SAP and business connector, meaning: the files are just on the ftp-server!
What am i doing and what is working properly:
- Business connector logs in into the FTP-server (with FTP-service: pub.client.ftp:login)
- gets the file (with FTP-service: pub.client.ftp:get) (the idoc-file, when i want to convert it into XML or the XML-file, when i want to convert it into idoc-format)
- puts the file into another place in the server (with service wm.PartnerMgr.gateway.transport.FTPTransport:OutboundProcess)
!!!So far only getting and putting of the file works!!!
What is missing between getting the file in one format - for example idoc-format - and putting the file into the server in the other format - for example XML-format is:
CONVERSION FROM XML INTO IDOC AND VICE VERSA
My question:
- which services i have to use between getting and putting the files?
Thanks to all,
Tamer

Hi,
I have the same problem. I do fix it?
Thanks
Wilson Xavier
Brazil

File to multiple IDOCs error

Dear All,
 I am trying to create customer master using FILE-To-Multiple IDocs.Idoc generated with 2 errors.
1.First one is status 51...Specify the Account Group.
2.Second one is it's generating only single idoc(not multiple).
I have mapped Account Group source field to KTOKD(Idoc).is this mapping problem?I have given IDOC occurence unbounded but not generating multiple idocs.below is my message mapping structure.
mt_customer Debmas01
customer (1...1)
 customer_master(1..unbounded)----
>IDOC (1..unbounded)
below is my input xml file with data.
<?xml version="1.0" encoding="UTF-8"?>
<ns0:mt_customer xmlns:ns0="urn://fenestacustmast">
 <Customer>
 <Customer_master>
 <AccountGroup>0004</AccountGroup>
 <CustomerNumber/>
 <CompanyCode>1000</CompanyCode>
 <SalesOrg>DBPM</SalesOrg>
 <DistributionChannel>PS</DistributionChannel>
 <Division>WD</Division>
 <Title>Mr</Title>
 <Name>Preethi</Name>
 <SearchTerm>Mat</SearchTerm>
 <SearchTerm2>V6CUSTNO</SearchTerm2>
 <StreetNumber>Street 6</StreetNumber>
 <City>Bangalore</City>
 <Country>IN</Country>
 <Region>KAR</Region>
 <TransporationZone>ASCHTS01</TransporationZone>
 <Fax>251662546</Fax>
 <Telephone>9658965236</Telephone>
 <VATRegNo>ABCG1254</VATRegNo>
 <LegalStatus>01</LegalStatus>
 <ReconAccount>36023901</ReconAccount>
 <SortKey>001</SortKey>
 <TermsOfPayment>S028</TermsOfPayment>
 <ToleranceGroup>1000</ToleranceGroup>
 <PaymentHistRecord>TRUE</PaymentHistRecord>
 <SalesDistrict>A1KAKA</SalesDistrict>
 <SalesOffice>BPBL</SalesOffice>
 <SalesGroup>SEN</SalesGroup>
 <Currency>INR</Currency>
 <CustPricingProc>1</CustPricingProc>
 <CustStatsGroup>1</CustStatsGroup>
 <DeliveringPriority>01</DeliveringPriority>
 <ShippingConditions>01</ShippingConditions>
 <Plant>DBBG</Plant>
 <AccountAssGroup>01</AccountAssGroup>
 <TaxClassification>1</TaxClassification>
 <InvoicingDate>IN</InvoicingDate>
 <InvoicingListDate>IN</InvoicingListDate>
 <IncoTerms>FCA</IncoTerms>
 <IncotermsPart2>Bangalore</IncotermsPart2>
 <CreditControlArea>FENE</CreditControlArea>
 </Customer_master>
 </Customer>
</ns0:mt_customer>
I did very simple mapping one to one without any functions.All are string types.I couldn't find what is the error?any help would be appreciated.
Thanks in advance.
Vinay

Hi,
 I would like to know whether you have mapped your customer_master(1..unbounded) node to IDOC(1..unbounded) node???Please check it once.Depending on that only the multiple IDOCs will be generated. I think it is mapping problem only. Have you changed the occurrence of IDOC to unbounded by exporting & then reimporting it to external definitions???? I've already done it & i got multiple IDOcs generated. Please check it and let me know the response so that I can help.
Please follow th below links
http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/877c0d53-0801-0010-3bb0-e38d5ecd352c
/people/michal.krawczyk2/blog/2005/12/04/xi-idoc-bundling--the-trick-with-the-occurance-change
Thanks & Regards
Priyanka Anagani

File to Multiple Idocs, Error: Tag MESSAGE1 found instead of tag IDOC BEGIN

Hi,
I have configured my file to multiple idocs scenario using the following blog -
/people/claus.wallacher/blog/2006/06/29/message-splitting-using-the-graphical-mapping-tool
Now when i try to execute this scenario it is scenario it is giving me the following error at "Call Adapter" Stage in runtime-
"Tag MESSAGE1 found instead of tag IDOC BEGIN="
My message looks like this at "Request Message Mapping" Stage in runtime -
<?xml version="1.0" encoding="UTF-8" ?>
- <ns0:Messages xmlns:ns0="http://sap.com/xi/XI/SplitAndMerge">
- <ns0:Message1>
- <ZDR009>
- <IDOC BEGIN="1">
- <Z100901 SEGMENT="1">
<RUNDATE>20080220</RUNDATE>
<RUNTIME>0037</RUNTIME>
<CONSTANT1>PYRLINCST</CONSTANT1>
<CONSTANT2>CSC</CONSTANT2>
- <Z100902 SEGMENT="1">
<RECTYP>2</RECTYP>
<SSN>641381239</SSN>
Kindly assist me in solving this error, Thanks in Advance!!
Regards.
Sudheer

Hi Sudheer,
Just the check the message mapping. Check the parant node mappings to create two different messages.
It seems that the mapping done on IDOC Node to create the IDOCs is getting failed.
Copy the content from inbound payload and test it in message mapping.
Remember, when you load the test data into your test tab you will get the error of structure mismatch coz in your mapping you have additional message.
Do the change with original data as shown below befor testing.
<?xml version="1.0" encoding="UTF-8" ?>
<ns0:Messages xmlns:ns0="http://sap.com/xi/XI/SplitAndMerge">
<ns0:Message1>
Original message will be here.
</ns0:Message1>
</ns0:Messages>
Regards,
Sarvesh

XML to IDOC

HI....PI Experts
I am early bird on PI space,
My boss just given me a XML file and asked to convert into XML using PI System.
We have a readily installed PI System in place.
What other information i have to get , know, discover to convert the XML to IDOC.
I understand ...some explicitly mapping to my XML to IDOC document structure is required. ..am i right ?
if some explain more about this, We will be greatful and move further in this requirement.
I tried this but was really not useful
http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/46759682-0401-0010-1791-bd1972bc0b8a
Regards
PR

which is your target IDoc ?
How you are picking this XML ?
If you are picking that from folder as ABC.xml, so scenario is XML file to IDoc.
If you are picking up that directly from MQSeries, so you will make connections between MQSeries & SAP PI.
Take help for that from the link for making connection between MQSeries & SAP PI :
How to use MQseries with PI?
make scenario using XSD Schema of sender side IDoc.

Flat file to multiple IDOCs

Hi experts,
I have a bit of a problem here wit a flat file to IDOC interface.
My input CSV file structure (shortened) is as follows -
<?xml version="1.0" encoding="UTF-8"?>
<ns0:POINBOUND_MT xmlns:ns0="urn:xx:xi:dwn:xx:pf:xxx:poinbound:100">
 <Record>
 <Row>
 <PO_HEADER_ID/>
 <TYPE_LOOKUP_CODE/>
 <LINE_NUM/>
 <AMOUNT_LIMIT/>
 </Row>
 </Record>
</ns0:POINBOUND_MT>
the target side is an idoc - PORDCR1.PORDCR102.
in the input file, for each row the PO_HEADER_ID field will have repeated values. the structure for eg.-
PO_HEADER_ID < other fields> < otherfields> ...
12345 <other fields>..<.. >
12345 <other fields>..<..>
12345 <other fields>..<..>
56789 <other fields>..<..>
56789 <other fields>..<..>
Now i need two idocs ( 2 distinct header values) on target side - the 1st idoc will have first 3 line items and 2nd idoc will have the last 2 line items. have already edited the IDOC in xsd format to make it unbounded.
Problem - i am able to create two idocs by handling contexts(splitbyvalue and a UDF), but with the line items its not working i.e. the first idoc gets the 3 line items created but the 2nd idoc does not have any!
my mapping for line items is -
PO_HEADER_ID <-> splitbyvalue(value changed) <-> count <---> UDF (for result.addvalue using count) <-----> lDOC LINE_ITEM node.
This logic does not work incase i need to create more than one idoc on the target side, it only works for the first idoc..so wat can i do??
Plz help.
thnx in advance!
Raju.

Hi Raju,
check these links...
/people/anish.abraham2/blog/2005/12/22/file-to-multiple-idocs-xslt-mapping
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/877c0d53-0801-0010-3bb0-e38d5ecd352c
Sachin

How to convert XML into idocs and post in ECC using PI

Hello All,
I want to configure the scenario like this MDM->PI->ECC. Using FTP I am getting able to fetch the xml file from MDM Server Ready folder. Now, I need to convert this XML file into Idocs and post it in ECC. Can anyone provide me step by step configuration in PI to achieve this. I have configured communication channel with adapter type Idoc in Itegration Builder. But, I am not sure where it will do the conversion of XML into Idoc and how do post it to ECC. I am working first time on PI 7.1. I have worked on XI 3.0 in 2006-2007. Any help to configure this step by step shall be appreciated.
Thanks & Regards,
Hemal

In you have the XML from MDM you have to use the mapping provided by the funtionals in the Funtional specification documents. once you did it you must configure the Receiver IDoc Adapter. and later dont fonget to configure properly the ReceiverAgreement.
as you receive the docuement from MDM via FTP, thats not a SAP System that means that you have to define PI as the sender of the IDoc,otherwise you will have the Error "Unable to convert the sender service to an ALE logical system"
to do that in the receiver Agreement>Header Mapping>Sender System-->Select PI server.
Take in mind to send IDocs to any SAP System, the system that send it must be a SAP system too. thats why you configure it
http://help.sap.com/saphelp_nw04/helpdata/en/5d/112d20f6ce6c46ba66afb98d278fbd/frameset.htm
Another thing is you have configure the ALE distribution Model.
se this:
http://wiki.sdn.sap.com/wiki/display/XI/FileToIDOC
/people/michal.krawczyk2/blog/2005/03/29/xi-error--unable-to-convert-the-sender-service-to-an-ale-logical-system
/people/venugopalarao.immadisetty/blog/2007/01/24/troubleshooting-file-to-idoc-scenario-in-xi
Let us know
Rodrigo P-.

Multimapping n:1 (XML to IDOC) Issue - Cannot use map in the scenario

Hi! I have created a multimapping in the directory. Source message is 0...unbounded and destination message is 1. The intention is to bring a single file into XI that contains mutliple XML messages. I then need to map this into a single IDOC. I have the mapping working. However, when I try and bring this into my integration scenario, XI cannot find the message interface.
I am not 100% convinced that this will all hang together =) But Cannot even prove that 'cos I cannot set this up in the scenario.
Any ideas would be greatly appreciate and rewarded.
Thx
Duncan

Apologies for getting all my terminology screwed up. Here is what I have:
Integration Repository
Imported Objects - Target IDOC
Interface Objects : External Definitions - XML schema of source message
Interface Objects : Message Interface - For source XML; Outbound + Asynch
Message Objects : Message Mapping - XML (0..unbounded) to IDOC (1) map
Message Objects : Interface Mapping - XML message interface (0..unbounded) -> XML to IDOC mapping -> IDOC (1)
Integration Directory
Interface Determination...
I select Type of Interface Determination = Extended but when I pull down the dropdown I do not see the multimap.
I have this working OK for one IDOC to multiple XML messages, doing the same as above. I have checked SCV, namespace etc... and they are correct. I am sure I am missing something very simple.
Again, any ideas appreciated.
Thx
Duncan

Idoc-xml to Idoc

Hi,
Sender is a 'party' which generates an Idoc. Some of the fields from this idoc has to be fetched by XI and passed to the receiver R/3 system.
Requirement :
Party -
> Idoc-xml -
>XI--> Idoc--
> R/3
(XI - Adapter Sender) ( IDOC Recevier Adapter)
1) what are the initial setting to be done in Xi & R/3 systems?
2) Any authentication details of the party is needed? ( as the XI sender adapter doesn't have many parameters to eneter in comm channel)
Also, here party is an 'R/3 system', who sends the data as an Idoc.
3) How should i convert the idoc to Idoc-xml? In other words how would i create my source DT,MT and MI ?
Appreciate Ur comments,
Thanks,
Raggy

Hi,
Here are the answers pointwise.
1) what are the initial setting to be done in Xi & R/3 systems?
Initial settings are Port and partner configuration in both XI and R/3 systems. You have to configure the RFC destication also.
2) Any authentication details of the party is needed? ( as the XI sender adapter doesn't have many parameters to eneter in comm channel)
Also, here party is an 'R/3 system', who sends the data as an Idoc.
Why are you using XI - adapter???any specific reason?
If party is an R/3 system then you can use IDOC adapter and if not then you can use FILE adapter to pick up the IDOC-XML file.
3) How should i convert the idoc to Idoc-xml? In other words how would i create my source DT,MT and MI ?
You do not need to convert the idoc to idoc-xml. IDOC adapter will do it automatically.
IDOC will act as a MT and also as a MI.
Hope it clarifies your doubts.
Br,
Madan Agrawal

File (xml) xi IDoc

Similar Messages

Maybe you are looking for