IDoc to Flat File in SAP PI 7.11

Hi Experts,
I am working on PI 7.11 and I have scenario from Idoc to Flat File.
Idoc is posted from source side R/3 system.My requirement is "With out Converting the Idoc structure to XML Structure  i want to send the data to Target system i.e. File system.
But the structure of the target structure is different from source structure.
My questions are:
1). Is it Possible to send the data to Target system without converting Idoc structure in to xml format through our PI 7.11 ?
2). If possible please provide me the way that executes in the Interface is?
Could you please provide the Inputs.
Best regards,
satya.T
Edited by: satyatanuku on May 24, 2010 3:26 PM
<Moved from Trial, Preview~ forum>
Edited by: Prateek Raj Srivastava on May 25, 2010 1:02 PM

Hello Folks ,
I am also facing the same scenario please provide me any options to achieve this scenario .
I am searched in Forums of SDN but no inputs or blogs available.
Let me know i am having one solution is it right or wrong ?
we have to achieve this IDOC Tunneling .... is it right  friends ?
Still inputs required....
Regards,
Ravi.

Similar Messages

  • Packaging IDOCs - SAP R3(IDOCs) - XI - Flat File

    Hi,
    I've got the scenario SAP R3(IDOCs) -> XI -> Flat File.
    The IDOCs are sent from R3 with the Option Send by Packet. There is 10 Idocs per packet.
    What I want to do is create one flat file for each packet.
    So one packet of 10 Idocs must create 1 flat file.
    Is it possible to do that whithout BPM ?
    Regards,
    Vincent

    Hi,
    Refer to this weblog which gives step by step process for IDoc to file scenario.
    /people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters
    Use BPM to collect tyhe Idoc, standard pattern is available for the same.
    http://help.sap.com/saphelp_nw04/helpdata/en/08/16163ff8519a06e10000000a114084/content.htm
    This following weblog explains the collection of Idoc.
    /people/pooja.pandey/blog/2005/07/27/idocs-multiple-types-collection-in-bpm - Collection of IDoc to Single File
    This also explains the IDoc package.
    /people/sravya.talanki2/blog/2005/12/09/xiidoc-message-packages
    Thanks,
    Prateek

  • Doubts in SAP(Idoc)-XI-Flat file scenario

    Dear All,
    I am sending Delivery Idoc from R/3 and I am able to view the Idoc in XI in transaction IDX5. Also i m able to see the XML structure with the data of the idoc in SXMB_MONI.
    Now as per my scenario I have to download this to a flat file from XI.
    My question is, should I have to do the creation of Data types, message types, mapping interface & interface mapping in IR or should I directly do the designing in the ID.
    waiting for your reply.
    Warm regards,
    N.Jain

    Hi,
    DT, MT, MI  : you will create these things for receiver flat file only.
    First create
    In Integration Repository :
    1.     Import structure of IDOC in your scenario, In imported objects &#61664; IDOCs
                  a.     In Interface Objects
    1.     Create Data type for your flat file
    2.     Create Message Type
    3.     Create Message Interface (inbound Asy.)
                  b.     In Mapping Objects
    1.     Message Mapping :  IDOC  to  Message Type of Flat File.
    2.     Create Interface Mapping  : IDOC to Flat file by using Message Mapping which you have created.
    Make activate all these things.
    In Integration Directory :
    1.     Create Communication channel for File Receiver.
    2.     Sender Communication channel is not required.
    3.     Create Receiver Agreement.
    4.     Sender Agreement is not required.
    5.     Interface Determination
    6.     Receiver Determination
    At sender side you will take your IDoc and at receiver side you will take your flat file.
    It can help you,
    Regards,
    Sandeep Kaushik

  • How to upload  schedule line from flat files to sap file

    dear all,
    i want to upload the schedule lines from flat files to sap schedulle lines
    but the flat files have 15 schedule lines and the data is as per date
    so how to upload that and the fields available in flat files are more than the sap screen
    we are having more than 6 items
    and 15scedule lines its abt 90data to be upload
    for one customer in every 15 day
    so how to do this
    is there any direct use in functional side
    with out the help of any abap
    but my user will do it
    so he need a permanent solution
    with regards
    subrat

    Hi Subrat ,
    u can upload the data either ( Master /Transaction) data with the help of lsmw. for that all u need to do is go through the lsmw and do it. in that u can go Batch input recording/ BAPI/ IDOC any of that. here i am sending the LSMW Notes go through it and do the work.
    once u create the LSMW project then u can ask the data from user or u can explain the user about the program and can run the flat file to upload the data.
    if u require LSMW material Just send me blank mail from u. my mail id is [email protected]
    Reward if Helpful.
    Regards,
    Praveen Kumar.D

  • Build daily Big flat file using SAP R/3 material master data

    Hi all,
    I must build an interface between SAP R/3 4.7 and an external application
    Daily a flat file must be generated contaning Material data in full exchange mode
    (volume 100 000 materials, <10 fields => ~ File of 30Mo)
    No complex mapping, only format mapping (Ex : Price quantity...)
    I don't know yet if I will use Idocs or BAPI to extract data. However, I'm sure I must use multiple inbound messages because of volume
    After reading documentation, I consider the both following solutions to manage it :
    1) A simple asynchronous interface with a file adapter in construction mode APPEND to build flat file progressively with arrival of SAP messages
    =>
    viable solution ?
    Is there problem of concurrent access to file in such a solution  ?
    (idocs or bapi data will be processed ones following the others )
    2) BPM Collecting and Bundling Messages - One Interface
    (Unlimited Loop with Deadline trigger correspondint to time I must build flat file)
    =>
    Each SAP message is a small message but the outbound XML will represent a 30 Mo flat file => Is it a problem ??
    Which solution do you advise ?
    Is there another ?
    Last question : (more general one)
    In such scenario, I can't see XI-value added comparing a creation of flat file directly with R/3.
    I will generate a big number of idocs, use a big part of XI memory ...
    Can you give me your opinion about it ?
    Thanks a lot
    Best regards
    Jean-Charles
    Message was edited by:
            Jean-Charles
    Message was edited by:
            Jean-Charles

    Hi Jean-Charles,
    >>>volume 100 000 materials, <10 fields => ~ File of 30Mo
    You have a performance task...
    >>>Is there problem of concurrent access to file in such a solution ?
    No, the adapter framework has its own queueing, the message would be stored and executed later. If sequence is important, you can use EOIO as well.
    >>>BPM Collecting and Bundling Messages - One Interface
    BPM is not required in your case, you should avoid becoz of performance task. You can append at file adapter, no problem. Bundling and splitting is even possible at Integration Server without BPM.
    >>>Each SAP message is a small message but the outbound XML will represent a 30 Mo flat file => Is it a problem ??
    Avoid using BAD words
    >>>Each SAP message is a small message but the outbound XML will represent a 30 Mo flat file => Is it a problem ??
    Use the <a href="https://websmp110.sap-ag.de/quicksizing">Quick Sizer</a> for sizing the hardware.
    Regards,
    Udo

  • 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

  • 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 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

  • 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 .

  • Data Extraction  or IDOC to flat file

    hi,
    I have a project to create a flat file from SAP, for an external legacy system. There are 3 requirement.
    What approach should I take. Simple data extraction OR Idoc to flat file.
    There are 4 requirements:
    1. first time extract all data.
    2. on subsequent run, extract only changed & new records
    3. if in SAP table, a record is deleted, then marked deleted in flat file.
    What approach should I take if I use data extraction.
    Thanks.

    I read your question, my first thought would be to look at where the data is going?
    What are the data requirements of the legacy system. IDOCs can speed up the development related to pushing the data out from SAP. Using ALE and change pointers you can automatically pass out the delta with a limited amount of development.
    However, the receiving system then needs to parse the IDOC data. depending on the IDOC you are working with this can be a challenge especially if the legacy developer doesn't get IDOCs.
    Sometimes its easier to collect and write the data from SAP using "simple data extraction". The data is more readily organized into a format the receiving system is expecting.
    You can also pass the idoc to a middleware maping application if one is available and do the SAP to legacy mapping there.
    Cheers

  • 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

  • Inbound IDOC Format (Flat File)

    Hi,
    I'm using SAP CRM Middleware for communication between CRM and Legacy System.
    I have configured Outbound IDOCs and I see something like this:
    EDI_DC40  2200000000000000023700 3012  CRMXIF_PARTNER_SAVE_M01                                     CRMXIF_PARTNER_SAVE_M
    E201CRMXIF_PARTNER_COMPLEX000 220000000000000002300000100000001CRMXIF_PARTNER_COMPLEX
    E201CRMXIF_PARTNER_HEADER000  220000000000000002300000200000102CRMXIF_PARTNER_HEADER         BusinessPartner                 U
    E201CRMXIF_PARTNER_KEYS000    220000000000000002300000300000203CRMXIF_PARTNER_KEYS           0000000014488DDB8AD891249EE10080010A6CA883
    The questions are:
    I need to know how do the following information must be filled in an Inbound IDOC:
    The first characters I understand that corresponds to the Structure name, IDOC Number, IDOC Line...
    So I need how do fields like IDOC number must be filled in an Inbound IDOC
    Thanx in advance..
    BTW. I'm expecting IDOCs as flat files so I need to explain to the Legacy Technician how to fill this fields.

    Hi,
    Go to transaction WE30 and give the IDoc basictype name CRMXIF_PARTNER_REL_SAVE_M01 and press the view-button (or press F7 key).
    This information you will need.
    The records are builded using the following structure:
    1st record contains control record information and follows the structure of table EDIDC.
    Starting at where "220" is given (this is the CLIENT), it is followed by the IDoc number field DOCNUM (16 digits) and so on. Not all fields must be filled, only those that are used for inbound messaging. Keep here in mind: Less fields filled will probably work better (because SAP will add its own details on arrival of the IDoc).
    All following records follow the structure of table EDID4 upto the field: HLEVEL (Hierarchy level, identical to the level found in WE30).
    Thereafter it is followed by the name of the segment (including spaces) and after this it will follow the exact structure of the segment.
    To view a sample, just generate a dummy (test) IDoc and use transaction WE19 to fill in the fields after changing to the correct IDoc type.
    Hope this helps you out.
    Regards,
    Rob.

  • Multiple idoc to flat file

    Hi,
    i have  a scenario from idoc to flat file.There is two idoc that send message in same file.Without flat file content messages come succesfully.the format should be following:
    at the first  row should be the first idoc,
    at the second row should be the second idoc
    01  1FONEX0045               FONEX0045               FONEX SIVI SABUN 400+850ML FLOWERS                    =>1.idoc
    02  1FONEX0045               8691988000162           8691988000162                                                             =>2.idoc
    01  1DOVE0199                DOVE0199                   DOVE SAC DOKULMELERINE COZUM SAC BAKIM M     =>1.idoc
    02  1DOVE0199                8718114638348           8718114638348                                                               =>2.idoc
    Thanks in Advance
    Nurhan

    Hi,
    You have to MessageTransformBean Module.
    The MessageTransformBean module enables conversion of XML files to flat files and vice versa. You can use this module in the sender and receiver communication channels.
    In receiver communication channel, specify MessageTransformBean module before standard adapter module CallSapAdapter and use
    Module Name: localejbs/AF_Modules/MessageTransformBean
    Module Key : XML2Plain
    Please see the below links, it might be useful to you.
    /people/gabrielsagayaselvam.panneerselvam/blog/2009/12/07/standard-adapter-framework-modules-afmodules-in-pi-71-150part-2
    http://help.sap.com/saphelp_nw04/helpdata/en/24/4cad3baabd4737bab64d0201bc0c6c/frameset.htm
    Regards,
    P.Rajesh

  • Develop IDOC to FLAT FILE

    Hi friends,
    I need help do develop a new interface using IDOC -> FLAT FILE scenario.
    Please send exemples and links.
    In found only XML file formats, i need FLAT FILE.
    Thanks,
    Marco

    new interface using IDOC -> FLAT FILE scenario.
    idoc to flat file scenario is very simple but you have to provide FCC Parameters in Receiver File Communication channel based on target structure and remain ecvery thing is same what was you found idoc to xml scenario.
    ex for Fcc Parameters in Receiver File Communication channel :
    http://www.riyaz.net/sap/xipi-file-content-conversion-for-complex-structures/79/

Maybe you are looking for

  • Sub-items settled to main items in Sales Order

    Guys, There is a business requirement that all cost and revenue in sub-items are settled to main item in a sales order. Is there a standard SAP solution for this? Thanks in advance Cheers, Jim

  • MX 920 Printer Not Responding - One Solution That Worked For Me

    I phoned Canon customer support and they walked me through fixing my problem.  We use wireless LAN at the house. Background: I have a mac, my wife an iPad.  We would be able to print a document, then after aprx 10 minutes I'd have to enter our router

  • Remove duplicate records in Live Office, caused by CR Groups

    hello all i have a CR with groups. all works well, until i use the report in live office, were it is duplicating the group data for each of the detail records i have removed the details from the CR report, leaving only the group data, but it still ha

  • JDBC adapter connection

    Hi Gurus, My user has a web based system where goods receipt details are entered and it gets updated in mySql DB. In return the user would gather information from sap and displayed back on web at real time. They do not have option for web services or

  • Random slides in captivate 7

    Is there a way to make the slides random in captivate 7 that is available for use with .exe files not swf or html5. These slides are not for a quiz. I am trying to make a sight word application for younger children so they will not learn the words in