How to IDOC-to-2 files

hi, i have an scenario that receive and IDOC and create two flat files. I did it using two BS and two Communication channels. but possible create my two flat file using one BS and one CC??
Regards
Rodrigo Pertierra

u will also be able to create two different files using one communication channel. this is possible using dynamic file naming. but if u want to have that stored in two different servers then it is possible to have created two BS. split mapping might be used here in this reference.
u may refer to:
/people/jayakrishnan.nair/blog/2005/06/20/dynamic-file-name-using-xi-30-sp12-part--i
/people/michal.krawczyk2/blog/2005/11/10/xi-the-same-filename-from-a-sender-to-a-receiver-file-adapter--sp14
http://help.sap.com/saphelp_nw04/helpdata/en/bc/bb79d6061007419a081e58cbeaaf28/frameset.htm
if u have any queries do post on the same
Message was edited by:
        Prabhu  S

Similar Messages

  • How to create Inbound Idoc from XML file-Need help urgently

    Hi,
    can any one tell how to create inbound Idoc from XML file.
    we have xml file in application server Ex. /usr/INT/SMS/PAYTEXT.xml'  we want to generate inbound idoc from this file.we are successfully able to generate outbound XML file from outbound Idoc by using the XML port. But not able to generate idoc from XML file by using we19 or we16.
    Please let me know the process to trigger inbound Idoc with out using  XI and any other components.
    Thanks in advance
    Dora Reddy

    Hi .. Did either of you get a result on this?
    My question is the same really .. I am testing with WE19 and it seems SAP cannot accept an XML inbound file as standard.
    I see lots of mention of using a Function Module.
    Am I correct in saying therefore that ABAP development is required to create a program to run the FM and process the idoc?
    Or is there something tht can be done with Standard SAP?
    Thanks
    Lee

  • How to Split Single Idoc into 2 files and put some delay

    Hi,
    I have a IDoc to file Scenario. Invoice Idoc to Flat file scenario
    this is a reuse Interface
    Current Scenario we have graphical mapping(used for lookup and dynamic filename, mostly all the field mappings are 1-1) and ABAP Mapping to convert Idoc to flat file, 1 Idoc will generate 1 file.
    In addition to the above case, there is 1 more requirement
    Correction Invoice case. where in I get single Idoc with Multiple Item categories (Original data and Correction data)
    In this case always I need to send two files(2 Idoc data), first Idoc is for Original Idoc and 2nd is Corrected Invoice, these 2 idocs should be sent with some delay.
    In Correction Invoice case, I should generate 2 idocs based on Item category (PSTVY) value.
    Suppose I have 4 E1EDP01 segments out of which PSTVY has value "AA" and "BB" repeated twice as shown below
    <PSTYV>AA</PSTYV>
    <PSTYV>AA</PSTYV>
    <PSTYV>BB</PSTYV>
    <PSTYV>BB</PSTYV>
    So I need to generate 2 Idoc 1 for AA and other for BB.
    If there is no correction Invoice, 1 idoc for 1 file will be generated.
    Am planning to use BPM to delay the idocs and identigy bpm based on Document type else no bpm...
    How do I split the mapping of single Idoc to 2 files based on Item category.
    Thanks,
    Varun

    You can use the multi-mapping to split the message payloads according to business requirement (AA and BB segments values)
    /people/jin.shin/blog/2006/02/07/multi-mapping-without-bpm--yes-it146s-possible
    And then send to different receivers by adding the conditions on the Receiver Determination (for example, "field = AA" go to Receiver1, and "field = BB" to to Receiver2).
    http://help.sap.com/saphelp_nwpi71/helpdata/en/26/5ccd3bb4560f01e10000000a11402f/frameset.htm
    Or even Extended (enhanced) receiver determination, should the scenario be more complex:
    http://wiki.sdn.sap.com/wiki/display/XI/EnhancedReceiverDeterminationinSAP+XI

  • How to convert IDOC to flat file in XI

    Hello SDNers
    I have a scenario IDOC --> XI  --> Flat file. My question is how to conver IDOC to flat file. At least there are two ways to do that:
    1) Define a flat structure in PI that reflects the IDOC structure, then using content conversion to convert the flat structure to flat file in hte receiver communication channel.
    2) There is a [document |https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/46759682-0401-0010-1791-bd1972bc0b8a] talking about using a generic ABAP mapping to map any IDOC to flat file.
    For the option 1, I don't want that way, because I would need to define a flat structure in PI for each IDOC which is too much effort. (I would have dozens of IDOC scenarios)
    The second one is very attractive. However the document is not complete to follow. Basically it does not explain how the inbound flat structure looks like. I guess the generic ABAP mapping is used to map any IDOC_XML structure to a flat structure, then in the file receiver communication channel to convert the flat structure to flat file format. But the document does not mention how the flat structure looks like. Has somebody tried this scenario? If yes, can you please let me know the steps to do in ESR (IR) and ID? Basically what structure the IDOC_XML should be mapped to using the generic ABAP mapping class?
    Or somebody has other ideas on how to convert IDOC to flat file?
    Thank you so much
    Eric

    > 1) You are saying that for Java mapping and abap mapping, the target data type (messag type) is just a dummy one, the real (XML) message the receiver will recieve is the one (stream) produced by the java or abap mapping. Is that correct?
    Definitely yes!
    >
    > 2) For the abap mapping option, I would define a dummy target data type. Do I need to do any content conversion in the receiver adapter (communication channel)?
    None wat so ever.The output of your Java Mapping will be the Native Idoc Format.
    >
    > 3) I tried with a dummy target data type as mentioned in my second post, can you see any clue in the error message what is wrong?
    Dats one thing I cant help much. Just make sure that the ABAP report is valid and take the help of a ABAP'er to debug what is going wrong. Not much of a ABAP guy, can read ABAP code, but cant write one myself
    Try to test the program standalone to see how it works. Maybe take some Idoc XML file as input and then dump the output to a .txt file and so on.
    Regards
    Bhavesh
    PS : All this is from what I have read of this guide. I have not convert Idoc XML to Native Idoc but have used this guide to convert Native Idoc to Idoc XML .

  • How To Convert IDOC to FLAT File ?

    Dear Expert,
            My requirement is to convert the IDOC to FLAT File using XI. How can i do this. I have gone thru the Guide How to convert IDOC to Flat file using ABAP mapping but it does not talk about what are all the stpes i need to do in IR & ID.
    I am ready to use ABAP mapping since i am an ABAPER.
             Is it recommended to use ABAP mapping since we expect daily 500 IDOCs to be converted to a flat file & transfer this flat file to some FTP location.
             Can anybody tell me the stpes how to do this in XI. The steps i am expecting like how to define the Data Type / Message type / Mapping etc & how to configure the channel ?
             The Flat file i want to convert should look like the way IDOC file gets created in FILE FTP port in SAP.
    Regards,
    Umesh

    I think there is some confusion... Let me explian my problem once again.
    I want to convert the Shipment IDOC as it is the moment the shipment documents gets created in R/3. I dont want to collect many IDOCs & make as single file. For each IDOC it should create a Flat File.
    Secondly if i have to MAP the whole IDOC the graphical mapping is too difficult.
    So instead of that can i use ABAP/XSLT/JAVA whichever is easy. ?
    Since i am ABAPER i can use ABAP mapping.
    The Output file should look like as below.
    EDI_DC40  9000000000011785526620 3012  OILSHI01                                                    OILSH1                                           SAPP01    LS  SAPCLNT900                                                                                A000000018LS  WBIMQSI                                                                                20071031161506                                                                                20071031161506     
    E2OILSH001                    90000000000117855260000010000000250 1011537344 1101                1 300X1 TRKGMKG 0202KG KG X        ZTLF  X XX 000   BLX X        X60002200710310000002007103100000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000        E2OILSA                       9000000000011785526000002000001031011537344000001SP          0000201496000000000000000000                                           00                                        00 V                                                                                E2OILSA                       9000000000011785526000003000001031011537344000002SP          0000201496000000000000000000                                           00                                        00 S
    E2OILSV                       900000000001178552600000400000103MH04CG6052        LPBW50D62401033       000020149601KG KGM   35200.00000             17200.00000             18000.00000                               0.000          0.000          0.000          DLLPGB220071031000000 00000000000000000000000000000000000                    0000XX    6000AAAA0.00000                 0.00000                 17200.00000             35200.00000             18000.00000             MH04CG6052 new bulk tender approved rs                                          LPG Bulk Lorry - WR                     Refinery TPP                                                                                BABA TRANSLINES                     kg        kg        0.000             0.00           0.00                                                                                E2OILSC                       9000000000011785526000005000004041  001                                                 18000.000000           18000.000000           35200.000000           0.000000               0.000000                  KG                                                                                E2OILSQ001                    9000000000011785526000006000005050011  MH04CG6052MH04CG60521J          05041089055000                        00000118000.0000000  KG 18000.000000           18000.000000           6000V04 18000.000      KGM18000.000      KGM00000000  V        0.000000                  0.000000               0.000000                  0.000000                           0.000000               0.000000               0.000000               0.000000                          0001                                                                                E2OILS2                       9000000000011785526000007000004040001000001000200020000.000000               0.000000               0.000000               0.000000               0.000000               0.000000               0.000000               0.000000               0.000000               XX0000000000000000000000000000 XX0504108905J5000              PUNE LPG BOTTLING PLANT            START     0001 1END       0001 10.000000               0.000000               0.000000               0.000000               0.000000               0.000000
    Pl. Help me its Urgent.
    Regards,
    Umesh

  • IDOC writing to file takes a while.

    Hello, I would like to request if anyone can advice how can we analyze why the creation or writing of an IDOC to a file takes a long while, say it takes 15 minutes to be created. Wherein in production system, it only take 1 or 2.
    Thanks very much and appreciate the help!

    Yes, actually that is the problem. In an example idoc, below is the technical info for the idoc, it took 15 minutes to create the file.
    Time of creation
    Date                   08.11.2011
    Time                   10:35:30
    Last database update
    Date                   08.11.2011
    Time                   10:50:26
    Can you advice how can we know or check the background processing? or is there a way? thanks.

  • How IE works for  flat file

    Hi all:
         As we all know that, when IE gets a idoc's service name from SLD, then use it with idoc's message type and Idoc type to do receiver determniation, what about flat file ? how can we know its Service name and interface name  if there is only a flat file on FTP?  how IE works for Flat file ?
         Couldn't thank you more

    Hi,
    For any idoc scenarious, you would use business systems rather than business service which is stored in SLD. So the IE would fetch it from SLD at runtime.
    For file based scenarious also, you can create business system as type third party and use the same.
    Is that answer your question?
    Regards
    Krish

  • IDOC to xml file

    hi,
    my name is avinash.i m new to xi.i have few qs regarding it.
    1.what is third party?
    2.what are adapters?where are they located?
    3.what is IDOC?
    4.how is IDOC converted to xml file?
    pls reply.its urgent.
    thanks in advance.
    Message was edited by:
            avinash s

    Hi avinash s  ,
    >>1.what is third party?
    third party is middleware or intermediate software which takes data from sender & transfers to a reciever in his understandable format.
    For Example
    Suppose think that there r 3 different people who speak different languages.
    Say User A understands french language,
           User B understands french , german, english language
           User C understands german language
    & User A and C want 2 communicate . Hence their languages r different they can't understand. If they take the help of User B, He undertands the language of User A & converses to User C in german.
    User B is the 3rd Party here.
    This example can be viewed in terms of systems who r having different platforms & they want 2 exchange messages with each other.
    Examples of 3rd party include:
    TIBCO,XI,EDI.....
    >> 2.what are adapters?where are they located?
    Adapters enable communication between the XI integration engine and an application system. This leads to the compatibility between heterogeneous systems.Adapters convert the XI protocol (SOAP with attachments over HTTP) to the protocol spoken by the application system and vice-versa.The key purpose of XI is to integrate heterogeneous systems and adapters are the key enabler to achieving this goal
    Adapter Categories
    Application adapters provided by SAP (IDoc and RFC) and 3rd party vendors (Seeburger, Siebel, Oracle, ...)
    Technical adapters relate to specific protocols
    File systems (FTP / File)
    RDBMS systems (JDBC)
    Messaging systems (JMS)
    Web services (SOAP)
    Mail servers (SMTP)
    SAP Business Connector
    Marketplaces
    Industry standard adapters
    RosettaNet
    CIDX
    The Adapter Engine
    The XI Adapter engine is the home of the majority of the XI adapters. Only the IDoc adapter and the plain HTTP adapter do not reside on the adapter engine. They reside on the Integration Server.
    It is fully integrated in to the XI landscape with tools provided for configuration, logistics and monitoring. It's Adapter Framework is based on the JCA.
    SAP XI requires an adapter framework to communicate outside of the SAP system. These adapters translate code from external applications to an XML message for NetWeaver processes using the Java Connector Architecture.It is a part of the Adapter Engine, which provides interfaces for configuring, managing, and monitoring adapters.
    The following r good websites which give complete overview of Adapter:
    Structure of the Adapter Framework
    http://help.sap.com/saphelp_nw04/helpdata/en/fd/16e140a786702ae10000000a155106/content.htm
    Adapter for SAP XI environment
    http://publib.boulder.ibm.com/infocenter/wbihelp/v6rxmx/index.jsp?topic=/com.ibm.wbia_adapters.doc/doc/sap_xi/sapximst11.htm
    List of all adapters compatible with XI 3.0
    http://searchsap.techtarget.com/expert/KnowledgebaseAnswer/0,289625,sid21_gci1229988_tax304527,00.html
    Adapter and Module Development
    http://help.sap.com/saphelp_nw04/helpdata/en/8b/895e407aa4c44ce10000000a1550b0/content.htm
    Legacy Integration with the SAP XI Adapter
    http://www.makdata.de/www_makdata/sites/www.makdata.de/en/solutions/solutions02/downloads/SAP_XI_Adapter_mak_data_news_23_en.pdf
    Installing the SAP XI Integration Components of the XI Adapter
    http://documentation.softwareag.com/crossvision/xio311/install/sapXiInstall.htm
    >>3.what is IDOC?
    IDoc is a container that carries the data thru 2 methods : either thru ALE or EDI.
    >> 4.how is IDOC converted to xml file?
    Pls go thru the following websites :
    A Step-by-Step Guide on IDoc-to-File Using Business Service in the XI Integration Directory
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/e07dcaa0-a92b-2a10-3a96-b3d942bd1539
    How to convert an IDoc-XML structure to a flat file and vice-versa in XI 3.0
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/46759682-0401-0010-1791-bd1972bc0b8a
    Introduction to IDoc-XI-File scenario and complete walk through for starters.
    /people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters
    cheers!
    gyanaraj
    ****Pls reward points if u find this helpful

  • IDOC to flat File----Problem in File Content Conversion at receiver

    hi experts,
    I am doing a IDOC to flat file secnario.
    My requirment is IDOCXI-Flat file
    Format of flat file is like:--
    Every segment in the IDOC will be converted into a single line of file(without any delimiter). So number of lines in flat file will be equal to number of segments in IDOC.
    I am facing problem in File Content conversion. 
    Please help me out..
    Thanks
    Jaideep

    Check this doc...
    [How To...Convert an IDoc-XML structure to a flat file and vice versa in XI 3.0 |https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/46759682-0401-0010-1791-bd1972bc0b8a]

  • Idoc to flat file using Integration process does not show up at all

    Hello All,
    I created a scenario IDOC to Flat File using Integration Process and one without IntegrationProcess. I am able to execute the one without Integration Process easily.
    However when I send the IDOC from SAP then the Integration Process scenario just does not work.
    I Checked SXMB_MONI  There is no entry for the Integration Process.I can see entry for other without Integration Process.
    SXI_CACHE : I can see my Integration Process active
    SWEQADM :  I have activated the Event Queue and Background job
    SWF_XI_ADM_BPE :  ALL BPE is showing green status.
    All syntax check on IP are fine.
    There is no Basis Help for me so  there could be some additional basis steps which need to be configured.  Has anyone faced such an issue with Integration Process?
    Regards
    Prashanta

    Hope this might help you. when u configure an IDoc as Sender with BPM this is how you proceed.
    <b>1<b>. let us split the scenario into two</b>.</b>
    a. <b>Sender to BPM</b> ( Integration Process).
    b. <b>BPM to Receiver</b>.
    <b>2. First let us configure the first Sender to BPM.</b>
    a. Sender Agreement( <b>Not required</b> ).
    b. Receiver Agreement( <b>NOT Required</b>).
    c. Receiver Determination( Sender Service, Outbound Interface, Receiver Service(<b>Integration Process</b>).
    d. Interface Determination( Inbound Interface(Sender Abstract Interface), Message Mapping(NOT Required if your using transformation stepin Integration Process)).
    <b>3. Now let us configure the Second BPM to Receiver.</b>
    a. Sender Agreement( <b>NOT Required</b>)
    b. Receiver Agreement( Sender Service(<b>Integration process</b>), Receiver Abstarct Interface,Receiver service, Inbound Interface).
    c. Receiver Determination( Sender Service(Integration Process), Receiver Abstarct Interface,Receiver Service).
    d. Interface Determination( Inbound Interface, Message Mapping(<b>NOT Required</b>)).
    So Finally we have <b>One Receiver Agreement</b>, <b>Two Receiver Determinations</b>, <b>Two Interface Determinations</b>.
    Please let me know if you have any more queries.
    Regards
    Gopi

  • File-to-IDoc, but the file structure is equal to the IDoc structure

    hi,
    we have a scenario where the incoming message has to be picked up by FTP. The incoming message is a flat file, no delimiters, no separators, nothing, however is exactly the IDoc structure.
    Since the file adapter does not know how the structure is set up, because no tags are present, it can not translate the filestructure into any format. Therefore it can not be processed further.
    Is there a way for a fileadapter to convert this plain file to an IDoc format, or to call the file-to-IDocadapter up front, the same way as if you would use in SAP the fileport in IDoc processing ??
    thanks!

    Hi Alexander,
    XI understands ONLY XML. All messages to and from XI are always XML messages.
    Now, if the file being placed by your Legacy System is not going to be an XML file, then you can use the content conversion of your sender File adapter to convert this non XML file to an XML file.
    Same way, if the file that is required by your 3rd party application should not be in a XML format, you can use content conversion of the receiver adapter to convert XML to text and so on.
    Basic point, all messages that reach the inegration engine of XI need to be in XML format and so you need content conversion to conevrt non xml to xml and vice versa.
    To make note mapping cannot be performed with a flat file as XI understands only XML. Hence content conversion required.
    Please go thru these links for step by step procedure to do the same:
    /people/venkat.donela/blog/2005/06/08/how-to-send-a-flat-file-with-various-field-lengths-and-variable-substructures-to-xi-30
    /people/sap.user72/blog/2005/01/06/how-to-process-csv-data-with-xi-file-adapter
    /people/michal.krawczyk2/blog/2004/12/15/how-to-send-a-flat-file-with-fixed-lengths-to-xi-30-using-a-central-file-adapter
    /people/anish.abraham2/blog/2005/06/08/content-conversion-patternrandom-content-in-input-file
    http://help.sap.com/saphelp_erp2005/helpdata/en/2c/181077dd7d6b4ea6a8029b20bf7e55/content.htm
    /people/venkat.donela/blog/2005/06/08/how-to-send-a-flat-file-with-various-field-lengths-and-variable-substructures-to-xi-30
    I hope I have answered your query.
    Regards,
    Abhy

  • IDOC to EDI file in PI 7.0. ( exchange infrastructure)

    i have to do one application
    SAP ECC 6.0 -> SAP XI -> Non SAP File Server
    Non SAP file server accepts only .edi format files.
    m trying IDOC to File scenario. IDOC generated is not giving exact EDI format which needs to send. How to transfer EDI format file from this scenario.
    if its done by file content conversion, pls describe more.
    eg . file output(.edi file) should be in below form
    EDI_DC40 100000000000027837646C 3012 O
    E2EDK01005 100000000000027837600000100000001 XSEK 5.23120

    Hi,
    There are two ways:
    1. You can find out if an EDI provider (3rd party) which supports XML EDI Messages  so you can just send XML EDI messages You can use Seeburger Adapter to conver into EDI Format.
    In general , If sender side is File the that file must be generated by EDI mappers tool like BIC.
    If file is in receiver side you have to use some Adapter to conver into EDI format.
    -you can use FILE/FTP Adapter with Seeburger modules.
    -you can use Seeburger OFTP Adapter.
    See the following documents to help you ..
    /people/william.li/blog/2006/03/17/how-to-get-started-using-conversion-agent-from-itemfield
    /people/alexander.bundschuh/blog/2006/03/14/integrate-sap-conversion-agent-by-itemfield-with-sap-xi
    /people/paul.medaille/blog/2005/11/17/more-on-the-sap-conversion-agent-by-itemfield
    /people/bla.suranyi/blog/2006/06/08/sap-xi-supports-edifact
    /people/william.li/blog/2006/03/17/how-to-get-started-using-conversion-agent-from-itemfield
    /people/paul.medaille/blog/2005/11/17/more-on-the-sap-conversion-agent-by-itemfield
    http://www.stylusstudio.com/edi/XML_to_X12.html
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/b0b355ae-0501-0010-3b83-8f2bb566fa47
    Details on XI EDI adapter from seeburger
    Check this for Conversions-
    /people/bla.suranyi/blog/2006/06/08/sap-xi-supports-edifact
    http://www.seeburger.it/fileadmin/it/pdf/2005_04_sapphire_Ferrero_transcript.pdf
    http://www.seeburger.com/fileadmin/com/pdf/Butler_Group_SEEBURGER_Technology_Audit.pdf
    http://www.seeburger.com/fileadmin/com/pdf/AS2_General_Overview.pdf
    SAP Adapters
    2. You can use EDI 834 Enrollment messages with XI you don't need an adapter - you can use adapter module:
    a) you can develop the adapter module for file adapter yourself
    for one message it will ont be that difficult
    b) you can use SAP conversion agent to create the EDI adapter module
    (it has many EDI messages included)
    Thanks
    Swarup

  • IDOC to flat file and vice versa

    Dear community,
    we should send IDOCs to flat files and read plain files and map them to IDOCs.
    Is there any comfortable way to do this without doing a huge content conversion for
    IDOCs? Exist a SAP standard for such process?
    We receive the IDOC as normal IDOC. Would it be more easy to save the IDOCs
    directly as flat file on ERP file system??
    System PI 7.11
    IDOCS: WHSCON, WHSORD and WMMBXY
    Regards
    Chris
    Edited by: Christian Riekenberg on Feb 1, 2012 2:41 PM

    Hey folks!
    We have a PI 7.31 SPS5 Java-only installation here and are using the module IDOCFlatToXmlConvertor. For single IDocs with one line for the EDC_DC40 header and the others for the IDoc payload the conversion works. But when we want to process multiple IDocs from the same type within one file, we see this error in the log:
    Module Exception 'com.sap.aii.af.idoc.exception.IDOCModuleException: No data segments for DOCNUM = ' found, cause: <null>
    Are there any requirements how the multiple IDocs have to be structured within the file?
    Best regards
    Heinrich
    Update:
    I found out that the module wants each record to contain the corresponding DOCNUM to find the matching records. The non-SAP sender system normally does not set this value. Is there a way to "convince" the module to convert the IDocs nevertheless?

  • IDOC to (multiple) file design help

    Hi all,
    i am trying to do a IDOC to multiple file scenario.
    Requirement:
    An outbound idoc has 4 segments.
    now i want the output of first 2 segments in one file and second 2 segments in another file.
    How to approach this design (without BPM).
    Waiting for reply,
    Senthilprakash.

    Hi,
    Use multimapping (use external definition of Idoc in source side) in which target message occurance should be 0..unbounded.
      write one UDF like below
    for(int i=1;i<=4;i++)
         if(i==2||i==4){
         result.addValue("");;
                     so that it will split the target structure 2 time(when i=2 and i=4). so that you map all the source fields to target fields(all one to one mapping except UDF).
    start doing this so that you will get the required output easily.
    thanks,
    madhu

  • IDOC to flat file without XML conversion

    Hi,
    I want to implement a scenario like this:
    IDOC --> XI --> flat file
    The flat file has to have the IDOC structure as you have when you write an IDOC to the R/3 file port. But we want to have this process running through XI.
    When you use the IDOC Adapter the IDOC is converted to XML first, which is time consuming. So this I want to skip this step.
    So is it possible to receive the IDOC directly in XI without converting it to XML? How should this process be designed.
    Ron

    Ron
    Looks like you need IDOC tunneling. It is possible by making a configuration parameter.
    You can find more information in http://help.sap.com/saphelp_nw04/helpdata/en/ab/bdb13b00ae793be10000000a11402f/content.htm
    While you try it, I will try to simulate this requirement in our system and let you know the result.
    KK

Maybe you are looking for