XML IDOC to Native IDOC Conversion

Hi,
We have a scenario, where we need to convert XML idoc into native idoc and write to a file. I am doing this based on
How To Convert an IDoc-XML structure to a flat file and vice versa in XI 3.0.
When I first executed the scenario, I was getting the following error
Z_ABAP_MAPPING_IDOC_TO_FLAT (type SAP-ABAP, kernel error ID UNCAUGHT_EXCEPTION) An exception with the type CX_SY_REF_IS_INITIAL occurred, but was neither handled locally, nor declared in a RAISING clause Dereferencing of the NULL reference.
After including the try-catch block, now i am just getting a blank file without any conversion.
Can anyone help me on this?
Regards,
Ravi

Hi,
It looks to be error in ABAP mapping
To test ABAP mapping in XI use the transaction SXI_MAPPING_TEST after creating a little scenario in the directory.
Or even you could do this with below sample code
Lets create one ABAP mapping class with the method IF_MAPPING~EXECUTE
data: obj type ref to zcl_abap_mapping_test.
data: source type xstring,
result type xstring.
data: param type ref to IF_MAPPING_PARAM,
trace type ref to IF_MAPPING_trace.
create object obj.
try.
CALL METHOD obj->IF_MAPPING~EXECUTE
EXPORTING
SOURCE = source
PARAM = param
TRACE = trace
IMPORTING
RESULT = result.
CATCH CX_MAPPING_FAULT .
ENDTRY.
This is a link very useful for ABAP Mapping :
http://help.sap.com/saphelp_nw04/helpdata/en/86/8280ba12d511d5991b00508b6b8b11/frameset.htm
Or may be  think this exception you need to catch it in the ABAP..
This may help u- http://help.sap.com/saphelp_47x200/helpdata/en/55/bff20efe8c11d4b54a006094b9456f/content.htm
just cross verify with this guide-
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/e3ead790-0201-0010-64bb-9e4d67a466b4
Thanks
swarup

Similar Messages

  • 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

  • XML IDoc file to IDOC .

    Hi,
    I am receiving XML idoc (Orders05) file from 3rd party to PI system , PI needs to create sales order IDoc ( Orders05) in ECC system. 
    1) Do I need to create source structure for XML IDoc file ? If yes should I create the structure as Orders05 ?
    2) How to map line items of xml file to Orders05 IDoc line items ?
    Please help.
    Thanks - Vinay.

    Hi Vinay,
    Please see Mikes reply in this thread. You may follow the same procedure:
    XML to FlatFile IDOC
    Regards,
    ---Satish

  • 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 for Batch Master Conversion

    Hi,
    Is there any IDOC for Batch Master Conversion (Transaction : MSC2N) ?
    The data being maintained is in Basic data 1 and classification tabs.
    Regards,
    Esha Raj

    Hello,
    I faced the problem with BATMAS03.  When drilling down to F'tn BAPI_BATCH_SAVE_REPLICA I could that one and similar BATMAS03 get to work with filling following set of fields.  Adapt of course the values to you're system.
    BAPIBATCH_SAVE_REPLICA_
    MATERIAL = 000000000000033001
    BATCH = 12543872
    PLANT = D010
    CLASSALLOCATIONS
    CLASS_TYPE 023
    OBJECTKEY 00000000000003300112543872 (in our case MATNR&BATCH combination, dependend on system setting Plant could also be needed)
    CLASSNUM FROZEN_FINISHED (Classification Class)
    OBJECTTABLE MCH1
    CLASSVALUATIONSCHAR
    CLASS_TYPE 023
    OBJECTKEY 00000000000003300112543872
    OBJECTTABLE MCH1
    CHARACT LOBM_ZUSTD
    VALUE_CHAR X
    This works now fine and similar for the BATMAS IDOC
    Hope this is helpfull for you.
    Dirk

  • 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"><b>XI / PI FAQ - Frequently Asked Questions</b></a>

  • Idoc to idoc scenario with idoc tunneling

    IN idoc to idoc scenario with idoc tunneling  the XML_CONVERSION parameter to value 2  is set whish means An IDoc is converted to IDoc-XML if requested by the service
    I want to know where we specify this and how we specify?

    1. /people/michal.krawczyk2/blog/2005/11/21/xi-idoc-to-idoc-tunneling--how-fast-and-easy-can-you-get
    2. /people/alessandro.guarneri/blog/2006/03/05/managing-bulky-flat-messages-with-sap-xi-tunneling-once-again--updated
    ref these weblogs.
    It is given under;
    <i>TCODE - SXMB_ADM
    - Integration Engine configuration
    - set the XML_CONVERSION parameter to value 2</i>

  • Flat-Idocs via the IDOC-adapter

    Hi All,
    I want to send a flat-IDOC via the IDOC Adapter to a SAP R/3 system. The IDOC adapter does not accept flat-IDOC, but wants xml-IDOC. Does anyone know how to send this flat-IDOC to the SAP R/3 via ALE, but without XML-lizing the IDOC?
    I am looking in to the principle of tunneling, but that will involve some ABAP coding.
    Cheers,
    Frank

    Hi Bhavesh,
    I tried, but the IDOC adapter wants XML. The receiver IDOC adapter checks the type of the payload and determines if IDOC tunneling is used or not. I don't know yet how to change the type of the payload:
    <i>method CL_IDX_IDOC_SERVICE-GET_PAYLOAD, part of package SIDOC_ADAPTER
    test if idoc is in tunnel-payload-format
        l_content_type = l_payload->getcontenttype( ).
        IF l_content_type = if_xms_resource=>mimetype_idoc.
          l_idoc_resource ?= l_payload->getdata( ).
          l_tunnel_flag    = 'X'.
        ELSE.</i>
    and with tunneling the idoc must be stored in certain tables where the receiver idoc adapter will get the IDOC instead of the payload. And our flat-idoc is in the actual payload. So the direction I am looking into is an abap mapping, which will change the payload type and stores the flat idoc in these tables, so the idoc adapter is "fooled" to believe it is IDOC tunneling.
    Cheers,
    Frank

  • IDoc Status "& & & &" in IDoc posting in BD87 - ALE

    hi,
    I am integrating two R3 servers and posting the datas from HR to cProjects server.
    In Outbound I can send the IDocs and In Inbound IDocs are getting into destinations (cProjects) servers along with status "& & & &" in BD87.
    Can anyone help me to know..Where the cause of problem..
    Thanks in advance
    Regards,
    Srinivasan.R

    Hi.,
    In we02 its OK..
    Its showing ...
    Status Message for Selected IDoc                                                               
    Status Text:   IDoc: 0000000000036306 Status: IDoc ready to be transferred to application       
    T100 Text:     No filters , No conversion , No version change .                                 
    But., in place of BD87 I am getting status only "& &, &, &".
    Regards,
    Srinivasan.R

  • Why we use IDOC adapter for IDOC as reciever?

    hello,
    Why we use IDOC adapter while using IDOC as receiver, whereas we don't use IDOC adapter while IDOC is sender?
    I am clear about why we don't use adapter for sender IDOCs.
    Thank you.
    Sarika

    Hi Sarika,
    >>>>Why we use IDOC adapter while using IDOC as receiver,
    maybe the easiest answer would be that we use
    IDOC adapter as receiver to tell the XI where he should
    send the data - there are many systems to which we can
    connect our XI and somewhere there has to be an object
    which will tell thx XI "where to" -> which RFC destination should it use
    BTW
    I believe IDOC apdater is also used as sender
    although you don't configure it in AF:
    "Once the IDoc has left the application through the RFC interface and has reached the <b>IDoc adapter</b> at the Integration Server inbound channel, the system converts it from IDoc format to IDoc XML format"
    from:
    http://help.sap.com/saphelp_nw04/helpdata/en/b9/c5b13bbeb0cb37e10000000a11402f/content.htm
    Regards,
    michal

  • Convert IDoc outbound to IDoc Abstarct

    Hello Friends,
    Can any please tell me how to convert IDoc outbound to IDoc Abstarct type so that it can be used in BPM.
    Thanks
    Sam

    Hi Woj,
    Below is the xml message displayed.It says No Interface found .But I have all the objects at the right place.
    <Trace level="1" type="T">Version 000</Trace>
      <Trace level="1" type="T">Message status 000</Trace>
      <Trace level="1" type="T">Interface action INIT</Trace>
      <Trace level="1" type="T">(must be INIT for a new determination)</Trace>
      <Trace level="1" type="T">start CHECK_INTERFACE</Trace>
      <Trace level="1" type="T">--start sender interface action determination</Trace>
      <Trace level="1" type="T">select interface MATMAS.MATMAS04*</Trace>
      <Trace level="1" type="T">select interface namespace urn:sap-com:document:sap:idoc:messages</Trace>
      <Trace level="1" type="T">no interface found</Trace>
      <Trace level="1" type="T">end CHECK_INTERFACE</Trace>
      <Trace level="1" type="T">Set interface action INIT into MAST</Trace>
      </Trace>
    - <Trace level="1" type="B" name="interface activity determination">
      <Trace level="1" type="T">Version 000</Trace>
      <Trace level="1" type="T">Message status 000</Trace>
      <Trace level="1" type="T">Interface action INIT</Trace>
      <Trace level="1" type="T">(must be INIT for a new determination)</Trace>
      <Trace level="1" type="T">start CHECK_INTERFACE</Trace>
      <Trace level="1" type="T">--start sender interface action determination</Trace>
      <Trace level="1" type="T">select interface MATMAS.MATMAS04*</Trace>
      <Trace level="1" type="T">select interface namespace urn:sap-com:document:sap:idoc:messages</Trace>
      <Trace level="1" type="T">no interface found</Trace>
      <Trace level="1" type="T">--start receiver interface action determination</Trace>
      <Trace level="1" type="T">Loop 0000000001</Trace>
      <Trace level="1" type="T">select interface MIAbA_MATMAS_Req*</Trace>
      <Trace level="1" type="T">no interface found</Trace>
      <Trace level="1" type="T">--no sender or receiver interface definition found</Trace>
      <Trace level="1" type="T">Hence set action to DEL</Trace>
      <Trace level="1" type="T">end CHECK_INTERFACE</Trace>
      <Trace level="1" type="T">Set interface action DEL into MAST</Trace>
      </Trace>
    Also I have mapped IDoc_original_outbound to IDoc_asy_Abs _ED in my message mapping 1:1.I have selected original IDoc (not ED) in the receiver determination.
    I don't think we need to explicitly maintain IDoc outbound asy in the MI..? should I..?
    Kindly suggest me if you find any solution for this happening.
    Please send me if you have any scenario of similar type else please mention the steps to be carried out for this scenario so that I can cross check with your steps.
    Thanks alot for your valuable time.
    Regards
    Sam
    Message was edited by: Sam
            Guest

  • Doubt while importing idoc (file 2 idoc scenario)

    hi,
    In IR, Imported objects..>Idocs
    while importing idoc there are two options to import
    according to software componet version,
    Overwrite sever info temporarily
    which one i have to use ? what circumstances i have to each option?

    Praba,
    Also please check this SAP help for the difference between these two:
    http://help.sap.com/saphelp_nw04/helpdata/en/2b/a48f3c685bc358e10000000a11405a/content.htm
    Regards,
    ---Satish

  • IDoc included in IDoc packet containing an error: transfer it separately

    Hi Gurus,
    I'm having this problem in our ECC side. I already did what Michal said in his blog:
    /people/michal.krawczyk2/blog/2005/12/04/xi-idoc-bundling--the-trick-with-the-occurance-change
    I have bundled the multiple IDOCs into 1 MATMAS.
    But I'm still having the error IDoc included in IDoc packet containing an error: transfer it separately.
    I've searched in the forums and none of them worked for me.
    Thanks in advance!

    Disable packaging or change the Partner Profile on WE02 transaction to "process immediately" the IDOCS.
    When you process the IDOCS in background mode, it will create packages (it is enabled by default), and in case any of them fail you won't be able to see the root cause, but will have to go to BD97 transaction to process them again. Therefore, please use the "process immediately" or disable packaging and then you will be able to either see the error or process it because it won't fail because of another IDOC.

  • IDoc Packaging in IDoc 2 IDoc Scenario

    Hi every one,
    Can anyone please throw some light on the following:
    Use of Idoc packaging in an Idoc2Idoc scenario. I dont have any clue about this.
    Reg,

    This should be rather straight forward, if you are using XI to pass IDocs from system to system then you actually don't really have to do any mapping.  There are some other good discussions on this topic:
    idoc to idoc
    IDOC packaging
    Re: IDOC to IDOC Scenario
    This is a good document on the topic:
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/cdded790-0201-0010-6db8-beb9bb2b2660
    You can import the IDoc data types and go about creating the rest of your scenario, usnig the IDoc adapters and ALE
    I would definitely also check out this document on configuring the IDoc adapter:
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/d19fe210-0d01-0010-4094-a6fba344e098

  • IDoc Collection Scenario (IDoc to Mail Interface)

    Hi,
    I am configuring IDoc to Mail Scenario using BPM.
    I gone through following link for develop the scenario. I am still unable to complete the scenario.
    Collect Idoc
    /people/pooja.pandey/blog/2005/07/27/idocs-multiple-types-collection-in-bpm
    I have done following steps in my configuration. Please correct my steps if i am wrong.
    Source is Outbound Invoice IDoc (SAP System).
    Target is Inbound EDI 810 format send as a email(Mail System).
    1. Create an Abstract Interface for Invoice IDoc(MI_IDoc_ABS)
    2. Create a Message Interface for EDI 810 for Inbound(MI_EDI810_IN)
    3. Create an Abstract Interface for EDI 810(MI_EDI810_ABS)
    4. Message Mapping between Outbound IDoc and Abstract Invoice IDoc.  I did this as per one of the above link. but did not understand the importance of this. On Message tab of Message Mapping, it shows the occurance as 1 for both source and target. I did not see the mention of this mapping in the BPM. Not sure if this was required?(MM_IDoc_ABS)
    5. Message mapping between Abstract Invoice IDoc to Abstract EDI 810. On the message tab of message mapping, occurance of Source message is changed to 0-unbounded and occurance of target is kept as 1.(MM_EDI810_ABS)
    6. Define Interface Mapping for above mappings
    a) IM_IDoc_ABS - Outbound Invoice IDoc + MI_IDoc_ABS
                                  MM_IDoc_ABS
    b) IM_EDI810_ABS - MI_IDoc_ABS + MI_EDI810_ABS
                                 MM_EDI810_ABS
    7. Create a BPM in Integration process. Define 3 Containers namely
    a) collectIDoc - Abstract Interface - MI_IDoc_ABS
    b) collectIDocList - Abstract Interface - MI_IDoc_ABS(Multiline)
    c) targetFile - Abstract Interface - MI_EDI810_ABS
    8. Create a Block and define a infinite while loop with Block. Condition to be defined as (1=1)
    9. Define a deadline block withing Block with duration = 5minutes
    10. Define a Correlation in Correlation editor as SNDPOR as a ID.
    11. Define a recieve step inside infinite while loop with following properties
    Message = collectIDoc
    Start Process = Checked
    Use Correlation = Correlation
    Activate Correlation = Correlation
    Correlation
    SNDPOR = collectIDoc./INVOIC02/IDOC/EDI_DC40/SNDPOR
    12. Define Container operation next to recieve step. properties are
    Target = collectIDocList
    Operation = Append
    expression = collectIDoc
    13. Outside the block, there is Transformation Step with following properties
    Interface Mapping = IM_EDI810_ABS
    Source message = collectIDocList
    Target message = targetFile
    Acknowledgement = None
    Reciever From = Send Context
    Now the next step is to define Communication Channel and Receiver determination, Interface determination in the Integration Directory.
    I don't know, how to go further on these steps.
    In addition, could you please validate my above steps.
    I appreciate your help.
    Thanks,
    Gowri

    Hi Bhavesh,
    Thanks for the directions and help. I appreciate your help. I understand the steps but i am unable to implement it.
    I have few more questions on above answer.
    a) Do i have to create Sender Agreement?
    b) Do i have to import bmp process in Integration Process in Integration Directory?
    The steps that i carried out in Integration Directory.
    1. Create a Scenario EDI810_Scenario
    2. Create a party called EDI810_Party and EDI810_Service.
    3. In EDI810_Service, Receiver tab has interfaces defined. MI_EDI_IN and MI_IDoc_ABS. In sender tab, it is INVOIC.INVOICE02 (IDoc) and MI_EDI810_ABS.
    4. Define a receiver communication channel CC_EDI810_Receiver(RFC).
    5. Business System for SAP is defined in Service without Party.
    6. Defined Sender communication channel CC_IDoc_Sender(IDoc)
    7. Create Interface Determination (First)
    Properties are
    Sender Service : SAP Business System
    Sender Interface : INVOIC.INVOICE02 (IDoc)
    Sender Namespace : IDoc namespace
    Receiver Party : EDI810_Party
    Receiver Service : EDI810_Service
    Configured Inbound Interface is
    MI_IDoc_ABS and IM_IDoc_ABS
    8. Create Interface Determination Determination (Second)
    Properties are
    Sender Service : BPM_IP (Bpm process is imported in Integratio directory)
    Sender Interface : MI_EDI810_ABS
    Receiver Party : EDI810_Party
    Receiver Service : EDI810_Service
    Configured Inbound Interface is
    MI_EDI_IN. I do not see IM_EDI_ABS in the list. How do i get that.
    What step did i miss?
    Thanks,
    Gowri

Maybe you are looking for

  • BlackBerry Desktop v6.1.0 B38 Won't install and hangs on Windows 7 64 bit

    I'm new here and would be very grateful for your help. When i try to install v6.1.0 B38 on my Windows 7 64 bit PC I have problems and it will not install. It goes as far as telling me that it has installed and would i like to run it.  I then click ye

  • XMLTYPE and International Characters

    Database: Oracle9i Characterset: US7ASCII I am trying to insert a very small xml document into an XMLTYPE column in a table. My xml document, however, contains international characters like French and Spanish letters with their accompanying accent ma

  • Premiere Elements Pro 5.5  How to Burn a DVD

    I am a newby in this world. Since a 2 months I bought  Pro 5.5 and made my first vacation movie. Total length 1.04.30. Now I want to burn the movie on a DVD to show family and friends. But were is the "Burn Button"?? How and what to do after the comp

  • It won't let me update!

    When I check on my macbook air if there is any software update it says there is one. When I click on 'update' its starts checking files and stuff but then it says, ' An unexpected problem has occurred' or something - what can I do, It won't let me up

  • Xfce4 won't load xfwm4 on start up.

    For some reason xfwm4 isn't starting when I log in after uninstalling beryl. What do I have to do to get xfwm4 back? (it's still installed and re-installing it hasn't helped) I've tried deleting the ~/.config/xfce4* directories but that hasn't helped