IDOC to spreadsheet

Hi,
Please go through following requirement.
Scenario : Idoc to csv/spreadsheet.
The spreadsheet will have 2 tabs, first will be containing configuration info and the 2nd will contain data.
Can you please help me with the ways it can be implemented.
I am able to produce 2 different files but unable to generate single spreadsheet with 2 tabs.
Regards,
Vishal K

Hi Vishal,
If you are going for idoc to csv, it wont help directly as csv doesn't allow to have multiple sheets. For idoc to spreedsheet having multiple sheets, there are basically 3 ways :
1. Java Mapping or Adapter module - For help, you can check this [wiki|http://wiki.sdn.sap.com/wiki/display/XI/CODE%20-%20Create%20an%20Excel%20File%20via%20the%20JExcel%20API?bc=true]
WritableSheet sheet = workbook.createSheet("Page1", 0);
2. XSLT Mapping - /people/michal.krawczyk2/blog/2005/12/10/xi-generating-excel-files-without-the-java-nor-the-conversion-agent-not-possible
<Worksheet ss:Name="Arkusz1">
3. Conversion agent - /people/alexander.ong/blog/2009/03/30/how-to-handle-excel-documents-with-sap-pi
Regards,
Sunil Chandra

Similar Messages

  • How to download an IDOC in XML or spreadsheet with well structured.

    Dear Experts,
    I am currently display an IDOC in WE02.
    May i know how to download this IDOC into XML format or spreadsheets format and well structured with Hierarchy level..
    Thank you very much

    Hi,
    Good question my friend,
    Follow below process:
    - Input t-code IDOC
    - In selection screen, select 'Analyse IDOC field values
    - Press F8
    - Input your IDOC number
    - Check mark on 'Also evaluate empty fields
    - Click on 'Output in internal form' : this is very much important thing
    - The execute
    - You will see all the data
    - Then go to 'List'>Save/send option from where you can achieve your purpose.
    Hrishi

  • Sales Order Creation using LSMW IDOC method.. ( Custome Interface)

    Hi ABAP'rs,
                     Please provide me LSMW steps for creating Sales Order using IDOC method.
                            Thanks and Regards,
                                                  Param.

    LSMW-IDOC in General
    LSMW – Step by Step Guide: Legacy System Migration Workbench is an R/3 Based tool for data transfer from legacy to R/3 for one time or periodic transfer.
    Basic technique is Import data from Spreadsheet / Sequential file, convert from source format to target format and import into R/3 database. LSMW not part of standard R/3, if we need this product email [email protected]
    Advantages of LSMW:
    • Most of the functions are within R/3, hence platform independence.
    • Quality and data consistency due to standard import techniques.
    • Data mapping and conversion rules are reusable across projects.
    • A variety of technical possibilities of data conversion.
    • Generation of the conversion program on the basis of defined rules
    • Interface for data in spreadsheet format.
    • Creation of data migration objects on the basis of recorded transactions.
    • Charge-free for SAP customers and partners.
    Working With LSMW:
    Use TCODE LSMW
    Objects of LSMW:
    •Project – ID with max of 10 char to Name the data transfer project.
    • Subproject – Used as further structuring attribute.
    • Object – ID with max of 10 Characters, to name the Business object .
    • Project can have multiple sub projects and subprojects can have multiple objects.
    • Project documentation displays any documentation maintained for individual pop ups and processing steps
    User Guide: Clicking on Enter leads to interactive user guide which displays the Project name, sub project name and object to be created.
    Object type and import techniques:
    • Standard Batch / Direct input.
    • Batch Input Recording
       o If no standard programs available
       o To reduce number of target fields.
       o Only for fixed screen sequence.
    • BAPI
    • IDOC
    o Settings and preparations needed for each project 
    Preparations for IDOC inbound processing:
    • Choose settings -> IDOC inbound processing in LSMW
    • Set up File port for file transfer, create port using WE21.
    • Additionally set up RFC port for submitting data packages directly to function module IDoc_Inbound_Asynchronous, without creating a file during data conversion.
    • Setup partner type (SAP recommended ‘US’) using WE44.
    • Maintain partner number using WE20.
    • Activate IDOC inbound processing.
    • Verify workflow customizing.
    Steps in creating LSMW Project:
    • Maintain attributes – choose the import method.
    • Maintain source structure/s with or without hierarchical relations. (Header, Detail)
    • Maintain source fields for the source structures. Possible field types – C,N,X, date, amount and packed filed with decimal places.
    • Fields can be maintained individually or in table form or copy from other sources using upload from a text file
    • Maintain relationship between source and target structures.
    • Maintain Field mapping and conversion rules
    • For each Target field the following information is displayed:
    o Field description
    o Assigned source fields (if any)
    o Rule type (fixed value, translation etc.)
    o Coding.
    o Some fields are preset by the system & are marked with Default setting.
    • Maintain Fixed values, translations, user defined routines – Here reusable rules can be processed like assigning fixed values, translation definition etc.
    • Specify Files
    o Legacy data location on PC / application server
    o File for read data ( extension .lsm.read)
    o File for converted data (extension .lsm.conv)
    • Assign Files – to defined source structures
    • Read data – Can process all the data or part of data by specifying from / to transaction numbers.
    • Display read data – To verify the input data being read 
    Convert Data – Data conversion happens here, if data conversion program is not up to date, it gets regenerated automatically.
    • Display converted data – To verify the converted data
    Import Data – Based on the object type selected
    • Standard Batch input or Recording
    o Generate Batch input session
    o Run Batch input session
    • Standard Direct input session
    o Direct input program or direct input transaction is called
    BAPI / IDOC Technique:
    • IDOC creation
    o Information packages from the converted data are stored on R/3 Database.
    o system assigns a number to every IDOC.
    o The file of converted data is deleted.
    • IDOC processing
    o IDOCS created are posted to the corresponding application program.
    o Application program checks data and posts in the application database.
    Finally Transport LSMW Projects:
    • R/3 Transport system
    o Extras ->Create change request
    o Change request can be exported/imported using CTS
    • Export Project
    o Select / Deselect part / entire project & export to another R/3 system
    • Import Project
    o Exported mapping / rules can be imported through PC file
    o Existing Project data gets overwritten
    o Prevent overwriting by using
    ‘Import under different name
    • Presetting for Inbound IDOC processing not transportable.
    Reward if useful.
    regards
    santhosh reddy

  • IDOC for Equipment master

    Hi,
    I am new to IDOC concept and need to transfer Equipment master from a SAP system to non SAP system.
    please let me know the following:
    1. Is there any standard message type and Idoc type available
        for Equipment master ?? ( For example we have
        MATMAS05 for material master)
    2. Is there any standard transation available for equipment 
        trasfer???( For example BD10 for sending material)
    3. Is change pointer facility available for equipment master??
        If yes please provide me the details
    Thanks

    Hi Preethi
    Please use LSMW in loading euipment master using the Basic type EQUIPMENT_CREATE01 and assign the source legacy file.You can use the message type EQUIPMENT_CHANGE01 to change it.See in WE02 BD87  the stus whether it has been posted or not.
               Since your data would be going to non sap that means you have to create partner profile for outbound processing and also activate the port(WE21) for outbound processing.
                     If your client is intilligent enoough and also big than if it has an ETL tool than extraction from spreadsheet in the form of idoc would be much easier and would cut short the time consumed in writing large programs .However the business needs to have an existing legacy system and you try to convert data .
          Please do revert back incase of any issues.
    Regards
    Somnath

  • Issues in WGSREQ idoc in SAP

    Hi All,
       i am working in retail scenario.In my store when an invoice is being punched ,if any article is marked home delivery in that , PI creates WGSREQ idoc with the necessary data for PO creation in SAP and posts the idoc.The PO number is automatically generated in SAP for the particular idoc.But in certain cases Idoc is successfully posted in SAP but PO is noy created.
    If there are 2 or 3 articles in the same invoice out of which 2 are home delivery then PO gets generated for 1 and not for the other 1 even if the idoc is successful in sap.
    Please advice me what has to done

    1.  I don't know.  How about creating a pivot after exporting data
    2. System->List->Save->local file->clipboard
    Then paste whole lot in Excel
    3. This is a problem with Excel, not SAP.  SAP exports with leading zeroes.
    You could export as flat file & import into Excel into a spreadsheet with an appropriate numbering format.

  • Idoc segment with 1000 char

    Hi
    I have a custom IDOC created with one of the segments being 1000 char. The data is populated through a custom program.
    In WE02 I am unable to see all the 1000 char. Even if I export the IDOC to a spreadsheet or word doc it does not show completely all the characters.
    I am able to use FM IDOC_Read_Completely to read the IDOC and view the complete segment but I am looking for a standard transaction.
    Any inputs on how the I can view all the data in the segment in a standard trx ?.

    hi,
    the data in the edid4-sdata is filled with according to Segement field lenght.
    you can directly read from table with Idoc number from table EDID4 in se16.
    or we05 or we02 or we19 or BD87 transactions.
    prabhudas

  • Idoc Structure onto Excel or Word formats

    Iam preparing mapping document and like to get the idoc structure onto Word document or excel spreadsheet. Please tell me how to do it. WE60 giving me Html format. But I need it in tabular format either in Word or Excel.Thanks for all help

    Hi,
    vety often IDOCs have many fields/segments
    but in real life you don't you all of them
    (very often just a a FEW of them)
    it's not use to put all of them in
    a mapping document so I just add new fileds/delete old
    to older mapping documents
    (of course via XML idoc from repository) it takes a few minutes...
    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>

  • How To download a idoc to a text file

    Hi Gurus,
    Can anyone let me know how to download  idoc to  a text  file (Local).
    Thanks  in advance
    B S B.

    Hi,
    Check the code below...
    Reads an existing Idoc and dispays the contents in a spreadsheet format
    REPORT Z_DISPLAY_IDOC_AND_DATA line-size 275.
    * This tool reads an existing Idoc and dispays the contents in a       *
    * spreadsheet format. The spreadsheet (MS-EXCEL) will be automatically *
    * created if D_EXCEL = 'X'.                                            *
    data: idoc_control like EDIDC,
          NUMBER_OF_DATA_RECORDS like sy-dbcnt,
          NUMBER_OF_STATUS_RECORDS like sy-dbcnt,
          INT_EDIDS like edids occurs 0 with header line,
          INT_EDIDD like edidd occurs 0 with header line.
    TYPE-POOLS :  LEDID.
    data: STRUCT_TYPE TYPE  LEDID_STRUCT_TYPE ,
          IDOC_STRUCT TYPE  LEDID_T_IDOC_STRUCT,
          SEGMENTS TYPE  LEDID_T_SEGMENT,
          SEGMENT_STRUCT TYPE  LEDID_T_SEGMENT_STRUCT,
          excel_tab(2000) occurs 0 with header line.
    parameter: DOCNUM like edidc-docnum obligatory, ""Idoc Number
               sap_rel like SY-SAPRL default SY-SAPRL obligatory,
               pi_ver like EDI_VERREC-VERSION default '3' obligatory,
               d_excel as checkbox default 'X'. ""Download ?
    start-of-selection.
      perform read_idoc.
      perform process_idoc.
      if d_excel = 'X'.
        perform download_to_excel.
      endif.
    end-of-selection.
    FORM read_idoc.
      CALL FUNCTION 'IDOC_READ_COMPLETELY'
           EXPORTING
                DOCUMENT_NUMBER          = docnum
           IMPORTING
                IDOC_CONTROL             = idoc_control
                NUMBER_OF_DATA_RECORDS   = NUMBER_OF_DATA_RECORDS
                NUMBER_OF_STATUS_RECORDS = NUMBER_OF_STATUS_RECORDS
           TABLES
                INT_EDIDS                = INT_EDIDS
                INT_EDIDD                = INT_EDIDD
           EXCEPTIONS
                DOCUMENT_NOT_EXIST       = 1
                DOCUMENT_NUMBER_INVALID  = 2
                OTHERS                   = 3.
      IF SY-SUBRC <> 0.
        MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
                WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
      ENDIF.
    ENDFORM.                    "" read_idoc
    FORM process_idoc.
      perform read_idoc_structure.
      perform display_data_records.
    ENDFORM.                    "" process_idoc
    FORM display_data_records.
      data: PE_seg_HEADER like EDI_SAPI01,
            segname like EDI_IAPI12-SEGMENTTYP,
            prev_segname like EDI_IAPI12-SEGMENTTYP value ' ',
            pt_fields2 like EDI_IAPI12 occurs 0 with header line,
            PT_FVALUES2 like EDI_IAPI14 occurs 0 with header line,
            byte_first type i,
            byte_last type i,
            field_val(50),
            tmp_str(15),
            tmp_str3(15),
            seg_repeats type i value 0,
            tmp_str2(15),
            tab_cr(1) type x value '09',
            tot_ctr type i value 0,
            ctr type i value 0,
            msg(40) type c.
      data: IDOC_STRUCT_wa TYPE  LEDID_IDOC_STRUCT.
      sort int_edidd by segnum.
      describe table int_edidd lines tot_ctr.
      loop at int_edidd.
        move int_edidd-segnam to segname.
        clear msg.
        concatenate 'Reading segment ' segname
                    into msg separated by space.
        if tot_ctr <> 0.
          ctr = ( 100 * sy-tabix ) / tot_ctr.
        endif.
        CALL FUNCTION 'SAPGUI_PROGRESS_INDICATOR'
             EXPORTING
                  PERCENTAGE = ctr
                  TEXT       = msg.
        add 1 to seg_repeats.
        clear tmp_str2.
        if int_edidd-segnam <> prev_segname.
          seg_repeats = 1.
          clear: pe_seg_header, pt_fields2, pt_fvalues2.
          refresh: pt_fields2, pt_fvalues2.
          CALL FUNCTION 'SEGMENT_READ_COMPLETE'
               EXPORTING
                    PI_SEGTYP                 = segname
                    PI_RELEASE                = sap_rel
                    PI_VERSION                = pi_ver
               IMPORTING
                    PE_HEADER                 = pe_seg_header
               TABLES
                    PT_FIELDS                 = pt_fields2
                    PT_FVALUES                = pt_fvalues2
               EXCEPTIONS
                    SEGMENT_UNKNOWN           = 1
                    SEGMENT_STRUCTURE_UNKNOWN = 2
                    OTHERS                    = 3.
          IF SY-SUBRC <> 0.
            MESSAGE ID SY-MSGID TYPE 'I' NUMBER SY-MSGNO
                    WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
          ENDIF.
          prev_segname = int_edidd-segnam.
        endif.
        read table idoc_struct into idoc_struct_wa with key
                               segment_type = int_edidd-segnam.
        if sy-subrc = 0.
          IF IDOC_STRUCT_WA-SYNTAX_ATTRIB-MUSTFL = 'X'.
            TMP_STR = 'Mandatory'.                  ""Mandatory
          ELSE.
            TMP_STR = 'Optional'.                  ""Optional
          ENDIF.
          if IDOC_STRUCT_wa-SEGMENT_TYPE_ATTRIB-QUALIFIER = 'X'.
            tmp_str3 = 'Qualified'.
          else.
            tmp_str3 = 'Non-Qualified'.
          endif.
          shift IDOC_STRUCT_wa-SYNTAX_ATTRIB-OCCMAX
                                     left deleting leading '0'.
          move seg_repeats to tmp_str2.
          condense: IDOC_STRUCT_wa-SYNTAX_ATTRIB-OCCMAX, tmp_str2.
          concatenate tmp_str2 'of'  IDOC_STRUCT_wa-SYNTAX_ATTRIB-OCCMAX
              into tmp_str2 separated by space.
          write :/ IDOC_STRUCT_wa-SEGMENT_TYPE,
               tmp_str,
               TMP_STR3,
               tmp_str2,
               IDOC_STRUCT_wa-SYNTAX_ATTRIB-HLEVEL,
               IDOC_STRUCT_wa-SEGMENT_TYPE_ATTRIB-plast,
               IDOC_STRUCT_wa-SEGMENT_TYPE_ATTRIB-DESCRP.
          if d_excel = 'X'.
            concatenate 'Segment Name' tab_cr
                        'Mand / Opt ' tab_cr
                        'Qual / non-Qual' tab_cr
                        'Seq of Max' tab_cr
                        'Level' tab_cr
                        'Owner' tab_cr
                        'Description'
                        into excel_tab.
            append excel_tab.
            concatenate IDOC_STRUCT_wa-SEGMENT_TYPE tab_cr
                  tmp_str tab_cr
                  TMP_STR3 tab_cr
                  tmp_str2 tab_cr
                  IDOC_STRUCT_wa-SYNTAX_ATTRIB-HLEVEL tab_cr
                  IDOC_STRUCT_wa-SEGMENT_TYPE_ATTRIB-plast tab_cr
                  IDOC_STRUCT_wa-SEGMENT_TYPE_ATTRIB-DESCRP
                  into excel_tab.
            append excel_tab.
            concatenate tab_cr
                        'Field Nma' tab_cr
                        'Type' tab_cr
                        'Length' tab_cr
                        'Byte From' tab_cr
                        'Byte To' tab_cr
                        'Description' tab_cr
                        'Value' tab_cr
                        'Qualifier Meaning'
                        into excel_tab.
            append excel_tab.
          endif.
        endif.
        sort pt_fields2 by field_pos.
        byte_first = 0.
        loop at pt_fields2.
          clear: field_val.
          byte_last = pt_fields2-EXTLEN.
          write int_edidd-sdata+byte_first(byte_last) to
                field_val left-justified.
          shift pt_fields2-EXTLEN left deleting leading '0'.
          shift pt_fields2-byte_first left deleting leading '0'.
          shift pt_fields2-byte_last left deleting leading '0'.
          write:/ '   ', pt_fields2-fieldname,
                  pt_fields2-datatype,
                  pt_fields2-EXTLEN,
                  pt_fields2-byte_first ,
                  pt_fields2-byte_last,
                  pt_fields2-descrp,
                  field_val.
          read table pt_fvalues2 with key fieldname = pt_fields2-fieldname
                        fldvalue_l = field_val.
          add byte_last to byte_first.
          if sy-subrc = 0.
            write : pt_fvalues2-descrp.
          else.
            clear pt_fvalues2-descrp.
          endif.
          if d_excel = 'X'.
            concatenate tab_cr pt_fields2-fieldname tab_cr
                    pt_fields2-datatype tab_cr
                    pt_fields2-EXTLEN tab_cr
                    pt_fields2-byte_first tab_cr
                    pt_fields2-byte_last tab_cr
                    pt_fields2-descrp tab_cr
                    field_val tab_cr
                    pt_fvalues2-descrp
                    into excel_tab.
            append excel_tab.
          endif.
        endloop.
      endloop.
    ENDFORM.                    "" display_data_records
    FORM read_idoc_structure.
      data: idoctype type LEDID_IDOCTYPE.
      if not idoc_control-cimtyp is initial.
        STRUCT_TYPE = 'E'. ""Extended
        idoctype = idoc_control-cimtyp.
      else.
        STRUCT_TYPE = 'B'. ""Basic
        idoctype = idoc_control-idoctp.
      endif.
      CALL FUNCTION 'IDOC_TYPE_COMPLETE_READ'
           EXPORTING
                RELEASE              = sap_rel
                STRUCT_TYPE          = STRUCT_TYPE
                IDOCTYPE             = idoctype
                VERSION              = pi_ver
    *       IMPORTING
    *            IDOC_TYPE            = idoctype
           TABLES
                IDOC_STRUCT          = idoc_struct
                SEGMENTS             = segments
                SEGMENT_STRUCT       = segment_struct
           EXCEPTIONS
                IDOCTYPE_UNKNOWN     = 1
                IDOCSTRUCT_UNKNOWN   = 2
                SEGMENT_DATA_MISSING = 3
                ILLEGAL_STRUCT_TYPE  = 4
                OTHERS               = 5.
      IF SY-SUBRC <> 0.
        MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
                WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
      ENDIF.
    ENDFORM.                    "" read_idoc_structure
    FORM download_to_excel.
      data: name like RLGRAP-FILENAME.
      shift docnum left deleting leading '0'.
      concatenate docnum '-' idoc_control-idoctp '.xls'
                  into name.
      CALL FUNCTION 'RH_START_EXCEL_WITH_DATA'
       EXPORTING
         DATA_NAME                 = name
         DATA_TYPE                 = 'ASC'
         WAIT                      = ' '
       TABLES
         DATA_TAB                  = excel_tab
       EXCEPTIONS
         NO_BATCH                  = 1
         EXCEL_NOT_INSTALLED       = 2
         WRONG_VERSION             = 3
         INTERNAL_ERROR            = 4
         INVALID_TYPE              = 5
         CANCELLED                 = 6
         DOWNLOAD_ERROR            = 7
         OTHERS                    = 8
      IF SY-SUBRC <> 0.
        MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
                WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
      ENDIF.
    ENDFORM.                    "" download_to_excel
    Cheers
    VJ

  • EDI - IDOC  mapping question

    Dear Experts,
    For transformations between EDI and basic IDOC types, are there any off-the shelf  (ready to use) options? If yes what are they? If not, what is the easiest way of mapping in between these structures?
    Our setup involves Seeburger's AS2 adapter.
    Thanks

    Hi Aamir,
    Thank you for your response.
    We are working in an environment where we do not have any control over the setup. So I have a few follow up questions, answers to which would help me immensely.
    1. I saw that there are a"few" mappings available for which both the EDI and IDOC versions differ from what we need. So, is there anyway to get an actual listing of all supplied mappings?
    2. In case you have worked for a similar scenario, is it possible for you to share a sample mapping spreadsheet ?
    Thank you,
    N

  • Data Migration-LSMW using IDoc Method

    Hi Friends,
    I have contract relevant information in the form of a excel spreadsheet/tab delimited flat file.
    This transactional data has information such as Header Data, Item Data and Sub Item data (BOM explosion).
    I need to migrate this data from the flat file to the CRM application using the IDoc Method of LSMW.
    /When I used the Batch Input Recording method, the item data was not captured during recording./
    Kindly send me relevant information to [email protected]
    Thanks in Anticipation
    rgards,
    Praveen

    Hello Sven,
    thanks for your comment. Unfortunatelly those both transactions do not exitst because I work on SAP CRM 7.0 instead of SAP ECC. I also looked for similar transactions in the table but didn't find anything.

  • Export IDoc documentation

    Hi everyone,
    I am aware of a Tcode WE60 which is used to export IDoc documentation based on the message/basic type in HTML format. Is there anyway to export the IDoc documentation in text format through this Tcode? Or is there another Tcode which allows us to export the IDoc documentation in text format?
    I have tried searching for it but failed. Any help will be greatly appreciated.
    Thanks,
    Alpana

    hi,
    The best way I found to do this was to run function module 'IDOC_TYPE_COMPLETE_READ
    ' in SE37 test mode. It lists all details concerning the IDOC type required in table output format. You can then click on the output table contents required, for example SEGMENT_STRUCT contains all segment fields, their types, descriptions, etc. Then click 'Object > Display entire list' then 'System >  List > Save as > Local file' and select 'Spreadsheet'.
    You then have a full list of all segments/fields of the IDoc in a spreadsheet to use for mapping/documentation, etc.
    Hope this helps whoever needs this.
    M

  • IDoc To Local File

    Is there a way to convert an already generated IDoc (viewable thru WE02) into a local file on my machine - i.e. text, spreadsheet, html, etc...?
    Thanks - points will be rewarded.

    When in WE02, go into the detail of an  IDOC. Then choose from menu IDOC > print
    It gives you first a kind of print preview, from there you can download.

  • How to Read an IDOC

    Hi Experts,
    Can any one explain me about IDOC, and how to read it once it is created.
    Regards
    Venu

    Hi,
    IDOCS:
    IDocs are SAP’s file format to exchange data with a foreign system.
    IDocs are an ASCII file format to exchange data between computers; the format is chosen arbitrarily .
    IDocs are similar to segmented files; they are not a description language like ANSI X.12, EDIFACT or XML.
    The IDoc contents are processed by function modules, which can be assigned in customizing.
    IDocs are structured ASCII files (or a virtual equivalent). They are the file format used by SAP R/3 to exchange data with foreign systems.
    IDocs are simple ASCII data streams. When they are stored to a disk file, the IDocs
    are simple flat files with lines of text, where the lines are structured into data fields.
    The typical structured file has records, each record starting with a leading string that identifies the record type. Their specification is stored in the data dictionary.
    IDocs is the acronym for Interchange Document. This indicates a set of (electronic)
    information which builds a logical entity. An IDoc is e.g. all the data of a single
    customer in your customer master data file, or the IDoc is all the data of a single
    invoice.
    IDoc data is usually exchanged between systems and partners that are completely
    independent. Therefore, the data should be transmitted in a format that can easily be
    corrected by the computer operators. It is therefore mandatory to post the data in a
    human readable form.
    Nowadays, this means that data is coded in ASCII format, including numbers which
    are sent as a string of figures 0 to 9. Such data can easily be read with any text editor on any computer, be it a PC, Macintosh, UNIX System, S/390 or any internet
    browser.
    The information which is exchanged by IDocs is called a message and the IDoc is
    the physical representation of such a message. The name “messages” for the
    information sent via IDocs is used in the same ways as other EDI standards. .
    Everybody who has ever dealt with interface programming, will find IDocs very
    much like the hierarchical data files used in traditional data exchange.
    International standards like the ODETTE or VDA formats are designed in the same
    way as IDocs are.
    Other EDI standards like XML, ANSI X.12 or EDIFACT/UN are based on a data
    description language. They differ principally from the IDocs concept, because they
    use a programming language syntax (e.g. like Postscript or HTML) to embed the DATA.
    The IDoc process is a straight forward communication scenario. A communication is
    requested, then data is retrieved, wrapped and sent to the destination in a predefined format and envelope.
    An R/3 application creates data and updates the database appropriately. An
    application can be a transaction, a stand-alone ABAP Report or any tool that can
    update a database within R/3.
    If the application thinks that data needs to be distributed to a foreign system, it
    triggers the IDoc mechanism, usually by leaving a descriptive message record in the
    message table NAST.
    The application then either directly calls the IDoc engine or a collector job
    eventually picks up all due IDoc messages and determines what to do with them.
    If the engine believes that data is ready to be sent to a partner system, then it
    determines the function module which can collect and wrap the required IDoc data
    into an IDoc.
    In IDoc customising, you specify the name of the function module to use. This can
    either be one which is predefined by R/3 standard or a user-written one.
    When the IDoc is created it is stored in an R/3 table and from there it is sent to the foreign system.
    If the foreign system requires a special conversion, e.g. to XML, EDIFACT or X.12
    then this job needs to be done by an external converter, like the Seeburger ELKE™
    system. These converters are not part of R/3.
    If you have to decide on a converter solution, we strongly recommend using a plain
    PC based solution. Conversion usually requires a lot of fine tuning which stands
    and falls with the quality of the provided tools.
    DIFFERENCE B/W IDOC AND BDC:
    IDOC's are intermediary documents into which the data will be transferred and then this idoc's gets transferred to sap or non-sap system.
    ALE is used to create link between 2 systems. So without the linking the data cannot be uploaded or downloaded.
    BAPI, LSMW and BDC are used to transfer data b/w systems.
    BDC is used to transfer data b/w only sap systems.
    LSMW is used to transfer data b/w sap and non-sap systems.
    ale Idoc: Idoc is a part of ALE. it is applicable only if the external system and the sending system have the same format. ALE uses Internationally Standardized formats. Also it is facilitating Asynchronous data communication and safest data communication. If you got errors also you can correct it and send it again.
    lsmw: It the legacy data transfer. which is used for bulk data transfers. It uses BAPI, IDoc, BDc internally....
    bapi: SAP Provided way of data transfer. if the BAPi suits for our business bettere to go for bapi. it too uses internationally standardized data format Business Objects concept.
    idocs
    1.We will see the status of the IDOC in We02 or We05.
    2.In that There are three records.
    a.Data record
    b.status record.
    c.Control record.
    3.If u click on data record you can see the data ,which is transfering it.
    Details about IDOC:
    Data Creation in Idoc
    IDocs are text encoded documents with a rigid structure that are used to exchange data between R/3 and a foreign system. Instead of calling a program in the destination system directly, the data is first packed into an IDoc and then sent to the receiving system, where it is analyzed and properly processed. Therefore an IDoc data exchange is always an
    asynchronous process. The significant difference between simple RFC-calls and IDoc data exchange is the fact, that every action performed on IDocs are protocolled by R/3 and IDocs can be reprocessed if an error occurred in one of the message steps.
    While IDocs have to be understood as a data exchange protocol, EDI and ALE are typical use cases for IDocs. R/3 uses IDocs for both EDI and ALE to deliver data to the receiving system. ALE is basically the scheduling mechanism that defines when and between which partners and what kind of data will be exchanged on a regular or event triggered basis. Such a set-up is called an ALE-scenario.
    IDoc is a intermediate document to exchange data between two SAP Systems.
    *IDocs are structured ASCII files (or a virtual equivalent).
    *Electronic Interchange Document
    *They are the file format used by SAP R/3 to exchange data with foreign systems.
    *Data Is transmitted in ASCII format, i.e. human readable form
    *IDocs exchange messages
    *IDocs are used like classical interface files
    IDOC types are templates for specific message types depending on what is the business document, you want to exchange.
    WE30 - you can create a IDOC type.
    An IDOC with data, will have to be triggered by the application that is trying to send out the data.
    FOr testing you can use WE19.
    How to create idoc?
    *WE30 - you can create a IDOC type
    For more information in details on the same along with the examples can be viewed on:
    http://www.netweaverguru.com/EDI/HTML/IDocBook.htm#_Toc8400404
    http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a6620507d11d18ee90000e8366fc2/frameset.htm
    http://www.sappoint.com/presentation.html
    http://www.allsaplinks.com/idoc_search.html
    http://www.sapgenie.com/sapedi/idoc_abap.htm
    http://www.erpgenie.com/sapedi/idoc_abap.htm
    To Create Idoc we need to follow these steps:
    Create Segment ( WE31)
    Create Idoc Type ( WE30 )
    Create Message Type ( WE81 )
    Assign Idoc Type to Message Type ( WE82 )
    Creating a Segment
    Go to transaction code WE31
    Enter the name for your segment type and click on the Create icon
    Type the short text
    Enter the variable names and data elements
    Save it and go back
    Go to Edit -> Set Release
    Follow steps to create more number of segments
    Create IDOC Type
    Go to transaction code WE30
    Enter the Object Name, select Basic type and click Create icon
    Select the create new option and enter a description for your basic IDOC type and press enter
    Select the IDOC Name and click Create icon
    The system prompts us to enter a segment type and its attributes
    Choose the appropriate values and press Enter
    The system transfers the name of the segment type to the IDOC editor.
    Follow these steps to add more number of segments to Parent or as Parent-child relation
    Save it and go back
    Go to Edit -> Set release
    Create Message Type
    Go to transaction code WE81
    Change the details from Display mode to Change mode
    After selection, the system will give this message “The table is cross-client (see Help for further info)”. Press Enter
    Click New Entries to create new Message Type
    Fill details
    Save it and go back
    Assign Message Type to IDoc Type
    Go to transaction code WE82
    Change the details from Display mode to Change mode
    After selection, the system will give this message “The table is cross-client (see Help for further info)”. Press Enter.
    Click New Entries to create new Message Type.
    Fill details
    Save it and go back
    Check these out..
    Re: How to create IDOC
    Check below link. It will give the step by step procedure for IDOC creation.
    http://www.supinfo-projects.com/cn/2005/idocs_en/2/
    ALE/ IDOC
    http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
    http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
    http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
    http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
    http://www.sapgenie.com/sapedi/index.htm
    http://www.sappoint.com/abap/ale.pdf
    http://www.sappoint.com/abap/ale2.pdf
    http://www.sapgenie.com/sapedi/idoc_abap.htm
    http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm
    http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm
    http://www.allsaplinks.com/idoc_sample.html
    http://www.sappoint.com/abap.html
    http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
    http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
    http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
    http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
    http://www.sapgenie.com/sapedi/index.htm
    http://www.allsaplinks.com/idoc_sample.html
    http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.docs
    go trough these links.
    http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
    http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
    http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
    http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
    http://www.sapgenie.com/sapedi/index.htm
    http://www.sappoint.com/abap/ale.pdf
    http://www.sappoint.com/abap/ale2.pdf
    http://www.sapgenie.com/sapedi/idoc_abap.htm
    http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm
    http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm
    http://www.allsaplinks.com/idoc_sample.html
    http://www.sappoint.com/abap.html
    http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
    http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
    http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
    http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
    http://www.sapgenie.com/sapedi/index.htm
    http://www.allsaplinks.com/idoc_sample.html
    http://http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
    An IDoc is simply a data container that is used to exchange information between any two processes that can understand the syntax and semantics of the data...
    1.IDOCs are stored in the database. In the SAP system, IDOCs are stored in database tables.
    2.IDOCs are independent of the sending and receiving systems.
    3.IDOCs are independent of the direction of data exchange.
    The two available process for IDOCs are
    Outbound Process
    Inbound Process
    AND There are basically two types of IDOCs.
    Basic IDOCs
    Basic IDOC type defines the structure and format of the business document that is to be exchanged between two systems.
    Extended IDOCs
    Extending the functionality by adding more segments to existing Basic IDOCs.
    To Create Idoc we need to follow these steps:
    Create Segment ( WE31)
    Create Idoc Type ( WE30)
    Create Message Type ( WE81)
    Assign Idoc Type to Message Type ( WE82)
    imp links
    http://www.allsaplinks.com/idoc_sample.html
    http://www.sapgenie.com/sapedi/idoc_abap.htm
    www.sappoint.com
    --here u can find the ppts and basic seetings for ALE
    http://sappoint.com/presentation.html
    www.sapgenie.com
    http://www.sapgenie.com/ale/index.htm
    WE30 - you can create a IDOC type.
    An IDOC with data, will have to be triggered by the application that is trying to send out the data.
    Try this..Hope this will help.
    SAP ALE & IDOC<<<<
    Steps to configuration(Basis) >>
    1. Create Logical System (LS) for each applicable ALE-enabled client
    2. Link client to Logical System on the respective servers
    3. Create background user, to be used by ALE(with authorizaton for ALE postings)
    4. Create RFC Destinations(SM59)
    5. Ports in Idoc processing(WE21)
    6. Generate partner profiles for sending system
    The functional configuration(Tcode: SALE)
    • Create a Customer Distribution Model (CDM);
    • Add appropriate message types and filters to the CDM;
    • Generate outbound partner profiles;
    • Distribute the CDM to the receiving systems; and
    • Generate inbound partner profiles on each of the clients.
    Steps to customize a new IDoc >>>
    1. Define IDoc Segment (WE31)
    2. Convert Segments into an IDoc type (WE30)
    3. Create a Message Type (WE81)
    4. Create valid Combination of Message & IDoc type(WE82)
    5. Define Processing Code(WE41 for OUT / WE42 for IN)
    6. Define Partner Profile(WE20)
    Important Transaction Codes:
    SALE - IMG ALE Configuration root
    WE20 - Manually maintain partner profiles
    BD64 - Maintain customer distribution model
    BD71 - Distribute customer distribution model
    SM59 - Create RFC Destinations
    BDM5 - Consistency check (Transaction scenarios)
    BD82 - Generate Partner Profiles
    BD61 - Activate Change Pointers - Globally
    BD50 - Activate Change Pointer for Msg Type
    BD52 - Activate change pointer per change.doc object
    BD59 - Allocation object type -> IDOC type
    BD56 - Maintain IDOC Segment Filters
    BD53 - Reduction of Message Types
    BD21 - Select Change Pointer
    BD87 - Status Monitor for ALE Messages
    BDM5 - Consistency check (Transaction scenarios)
    BD62 - Define rules
    BD79 - Maintain rules
    BD55 - Defining settings for IDoc conversion
    WEDI - ALE IDoc Administration
    WE21 - Ports in Idoc processing
    WE60 - IDoc documentation
    SARA - IDoc archiving (Object type IDOC)
    WE47 - IDoc status maintenance
    WE07 - IDoc statistics
    BALE - ALE Distribution Administration
    WE05 - IDoc overview
    BD87 - Inbound IDoc reprocessing
    BD88 - Outbound IDoc reprocessing
    BDM2 - IDoc Trace
    BDM7 - IDoc Audit Analysis
    BD21 - Create IDocs from change pointers
    SM58 - Schedule RFC Failures
    Basic config for Distributed data:
    BD64: Maintain a Distributed Model
    BD82: Generate Partner Profile
    BD64: Distribute the distribution Model
    Programs
    RBDMIDOC – Creating IDoc Type from Change Pointers
    RSEOUT00 – Process all selected IDocs (EDI)
    RBDAPP01 - Inbound Processing of IDocs Ready for Transfer
    RSARFCEX - Execute Calls Not Yet Executed
    RBDMOIND - Status Conversion with Successful tRFC Execution
    RBDMANIN - Start error handling for non-posted IDocs
    RBDSTATE - Send Audit Confirmations
    FOr testing you can use WE19.
    http://sap-img.com/abap/reads-an-existing-idoc-and-dispays-the-contents-in-a-spreadsheet-format.htm
    ALE/ IDOC/ XML
    http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
    http://www.thespot4sap.com/Articles/SAP_XML_Business_Integration.asp
    http://help.sap.com/saphelp_srm30/helpdata/en/72/0fe1385bed2815e10000000a114084/content.htm
    IDOC Convertion
    /people/kevin.wilson2/blog/2005/12/07/changing-fields-in-an-idoc-segment
    ALE/ IDOC
    http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
    http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
    http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
    http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
    http://www.sapgenie.com/sapedi/index.htm
    http://www.sappoint.com/abap/ale.pdf
    http://www.sappoint.com/abap/ale2.pdf
    http://www.sapgenie.com/sapedi/idoc_abap.htm
    http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm
    http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm
    http://www.allsaplinks.com/idoc_sample.html
    http://www.sappoint.com/abap.html
    http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
    http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
    http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
    http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
    http://www.sapgenie.com/sapedi/index.htm
    http://www.allsaplinks.com/idoc_sample.html
    IDOC Creation....
    http://www.erpgenie.com/sap/sapedi/idoc_abap.htm
    You can view the definition of any IDoc data structure directly with transaction WE30.
    u cn use function module 'FIELD_POSITION_IN_SEGMENT_GET' to extract data from idocs.
    You can view the idoc through we02 or we05. In that there are three types
    status records gives the status of that idoc in differenttimes
    data records gives the data in that idoc
    control records gives the date, time and creater of that idoc.
    I think its helps you.
    Thanks and Regards,
    D.Revathi.

  • Uploading IDOC

    Hi All,
    I have a requirement in which i need to upload the data from the excel spreadsheet into the wbs structure using IDOC.
    A standard basic type PROJECT01 is available for this.
    Every record on the Excel Spreadsheets will be interfaced for loading. The assumption is that the file has the correct data.
    Can anybody provide an insight into the steps to be followed in this case

    Hi Bhuvan,
    Basicall this problem arises when  user Id being used in the SM59 to trigger the IDoc's from the R3 system , i,e , the XI user id being used in SM59 of R3 does not have the authorizations to post the Idoc.
    Note : 837595 describes the authorizations needed to post and Idoc. Make sure that the user id has the authorizations in this note.
    Activate the authorization check in transaction ST01.
    And also it may be due to insufficient roles for the user which ur using in RFC connection to SAP system.
    Check with the  port in IDX1 whether u have configured corectly.
    Check this link
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/d19fe210-0d01-0010-4094-a6fba344e098
    PAGE - 11
    Regards,
    Vinod.

  • Create a change request for multiple customers from spreadsheet

    Hello Experts,
    1.We have a spreadsheet with 100's of Customer data maintained in it , can we create a change request by downloading data from spreadsheet directly instead of manually entering the data in the CR. Also can we create a single change request for multiple Create customers.
    2.Can we create CR's automatically , lets say we have 100's of customer data loaded into MDG hub by Data Services using DEBMAS Idoc , can this create automatic CR's , is this possible.
    Thanks.

    Dear Collins,
    1.We have a spreadsheet with 100's of Customer data maintained in it , can we create a change request by downloading data from spreadsheet directly instead of manually entering the data in the CR. Also can we create a single change request for multiple Create customers.
    Answer:there are various options are available in MDG to process multiple material as shown below
    you can down load the customers using file down load funcationality and same change,upload the customers using the file Upload process.
    you can create a single CR for muntiple customers options are shown below.
    2..Can we create CR's automatically , lets say we have 100's of customer data loaded into MDG hub by Data Services using DEBMAS Idoc , can this create automatic CR's , is this possible.
    Answer:Yes you can create CR automatically using DTIMPORT tcode and some configuration needs to be done further reading go to the link SAP Master Data Governance - SAP Library
    regards
    shankar

Maybe you are looking for

  • Office 2007 Document Attaching in Solution Manager

    Dear Gurus, When document attaching in Solution Manager 7.01, the system does not support Microsoft Office 2007 formats. (docx, xlsx) Are there any customizing for this topic? Thank you,

  • Can my mini provide ethernet for blu ray player?

    i know you can share internet when connected to internet with ethernet, but i want to share my wireless network my mini connects to with my blu ray player. has anyone done this and had it work? is there a trick? thanks for any info....

  • FM  to check the date

    Dear All, Please advice the right function module to check whether the date entered is a valid one. Thanks Ravindra Suvarna

  • P2P Software for Mac

    Hey everyone, On my old PC i used Ares for P2P, mostly because it didn't seem to drag any spyware with it. On my new Mac, I've got BitTorrent, but it's difficult to find any MP3's. If you got any good torrent search sites, or alternative programs, le

  • Why is the option to choose to edit with lightroom adjustment or edit original missing

    I am currently using Lightroom 3 and Photoshop Cs4. Usually when I open file in photoshop from lightroom, I will be asked to choose to edit with lightroom adjustment or to edit original file. However, today, the options were missing, and the file dir