IDOC DATA in F110

Hi All,
We are trying to send the data of F110 from R/3 to PI system by using 2 IDOC types EUPEXR and PAYTEXT.
We are receiving the IDOC's in the PI system but, we would like to have the data of the IDOC type EUPEXR and PAYTEXT, where as we are getting the PAYTEXT idoc first and EUPEXR next.
We tried to implement the serialization of Idoc Message type technique, but we are receiving the both the IDOcs in the PI system with same type stamp.
Can anyone suggest us how do we avoid this such that we always receive the EUPEXR idoc first and PAYTEXT idoc second in the PI system...
Thanks,
Rajesh.G

Hi
Why are you picking the Idocs based on TimeStamp?
We are also using simliar process with PI as middleware but we are not facing any issues?
Let me know what is the requirement and where does these idoc finally go and get updated?
Regards
Jyo

Similar Messages

  • Idoc data in flat file structure

    Dear Experts,
             We have  idoc data in flat file structure. We need to fetch it using ftp and map it to an idoc.
    please tell me how to proceed .
    Thanks,
    Aju

    Hi,
    For flat file you need to use the File content conversion parameters.
    Refer the blog,
    SAP Network Blog: How to process flat files with multiple documents like POs, SOs etc. in a File to IDoc scenario
    How to process flat files with multiple documents like POs, SOs etc. in a File to IDoc scenario
    Thanks
    Swarup

  • XML IDOC data (hosted on a web server)   &  handling multiple WSDLs

    Hi ALL,
    1)how to design an Interface for picking up an XML IDOC data (hosted on a web server) which will be uploaded to SAP or converted to a file
    this is what the customer has given me ..can any one explain me this and help me how to more forward
    2).This Interface must use UDDI concept because we are going to use multiple BAPIs /RFCs as WSDLs
    what is this mean can any send me some document on this
    3).Use web-service navigator concept as we will be handling multiple WSDLs
    i worked on 1. to define a place holder in WebAS for holding the
    wsdls.
    2. publish the wsdls in WebAS UDDI Repostory
    but i have never used web-service navigator concept as we will be handling multiple WSDLs what is the difference ..send me some step by step docs ..
    thanks very much
    RK..

    1.I am not clear with the requirement too. THere is no big deal in sending XML to IDOC or File. Based on your requirement you have to import IDOC structure or ify ou are using file, create a structure for the file.
    If u are asking about sendin the XML directly without mapping, even you can do that without MM and even IM.
    Please be more elaborate and if you are not clear with what client said, paraphrase them or ask again. Its not good to start work unless we are very clear with the requirement.
    you can say to my understanding i feel this, now pI will send data like this. Is it correct?
    2. More information on UDDI
    http://en.wikipedia.org/wiki/UDDI
    I dont think you need to worry much about this now with many features provided in ESR especially
    3. http://<Host>:<port>/wsnavigator/
    The webservices going out of PI are published here.
    provide host and port are host and port details of ext system.
    Once you enter link in your browser, it shows the available webservices hosted there.
    All you need is to click on the required wsdl and test it.
    It is as good as sending your data from PI to other system.
    It is similar to Altova XML spy but the difference here is you enter the values directly here but in XML spy we send XML .

  • Read MULTIPLE idocs data with all sgmn to my internal table in a single

    Dear SAP Folks!
    I have a question, I know to read SINGLE idoc data with all segments, we have FM IDOC_READ_COMPLETELY but my requirement is to Read MULTIPLE idocs data with all segments to my internal table in a single shot without keeping this FM in loop! since it is performance issue, at a time i may want to read 1000 idocs data!
    Could anyone please let me know is there any way to get this, keeping mind of performance and any other FM?
    Best Regards,
    Srini

    Hi,
    I know idoc numbers and i can write a select Query to DB table EDID4 to get all segments data to my internal table. But i am looking for FM to do this. because i have too many number of idocs and each idoc is having many segments(I am thinking in performance point of view!) The FM IDOC_READ_COMPLETELY can accept only ONE IDOC number as import parameters at a time to get segment data. in similar way do we have any other FM? or other way? except select query to EDID4 table?
    Best Regards,
    Srini

  • IDOC data to excel file

    Hi
    I have downloaded the IDOC Data in my Excel file.
    But the problem is that I am getting all the details in a single column.
    I want the systematic data should appear on my Excel.
    Thanks

    hi,
        Sorry for the delay, just now i have seen your issue, here just i am trying to help you in case till now you have not got it....
    Thanks
    Satyasuresh
    Here the code....
    *& Report  YSAT_IDOC_TO_EXCEL                     *
    REPORT  YSAT_IDOC_TO_EXCEL line-size 275.
    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.
    data: begin of i_split1 occurs 0,
              segment(20),
              fieldname(20),
              field1(20),
              field2(20),
              field3(20),
              field4(20),
              field5(60),
              field6(20),
              field7(20),
              field8(20),
          end of i_split1.
    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 no-display ,
    pi_ver like EDI_VERREC-VERSION default '3' no-display,
    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
    text
    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
    text
    FORM process_idoc.
      perform read_idoc_structure.
      perform display_data_records.
    ENDFORM. " process_idoc
    *& Form display_data_records
    text
    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(2) type c value '@@',
      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.
    SAPGUI_PROGRESS_INDICATOR
        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.
    SEGMENT_READ_COMPLETE
          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
    text
    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
        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 and sy-subrc <> 3.
        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
    text
    FORM download_to_excel.
    data: name like RLGRAP-FILENAME.
      data: name TYPE STRING.
      shift docnum left deleting leading '0'.
      concatenate docnum '-' idoc_control-idoctp '.xls'
      into name.
      perform to_split.
    CALL FUNCTION 'RH_START_EXCEL_WITH_DATA'
       EXPORTING
         DATA_filename       = name
         WAIT                = 'X'
         DATA_TABLE          = 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.
      break donepus.
      CALL FUNCTION 'WS_DOWNLOAD'
        EXPORTING
          FILENAME                = 'C:\Documents and Settings\donepus\Desktop\test2.xls'
          FILETYPE                = 'DAT'
        TABLES
          DATA_TAB                = i_split1
        EXCEPTIONS
          CONVERSION_ERROR        = 1
          INVALID_TABLE_WIDTH     = 2
          INVALID_TYPE            = 3
          NO_BATCH                = 4
          UNKNOWN_ERROR           = 5
          GUI_REFUSE_FILETRANSFER = 6
          OTHERS                  = 7.
      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
    *&      Form  to_split
          text
    -->  p1        text
    <--  p2        text
    FORM to_split .
       break donepus.
    loop at excel_tab.
        split excel_tab at '@@' into i_split1-segment
                                     i_split1-fieldname
                                     i_split1-field1
                                     i_split1-field2
                                     i_split1-field3
                                     i_split1-field4
                                     i_split1-field5
                                     i_split1-field6
                                     i_split1-field7
                                     i_split1-field8.
            append i_split1.
            clear i_split1.
    endloop.
    ENDFORM.                    " to_split

  • Idoc data in transparent tables

    Hi,
    There is a existing program which picks up data from Idoc and creates the output files for further processing.
    My requirement is I need to pick up data with using Idoc tables, is there any SAP transparent tables which stores the data? Is it possible or is there any method available to select the data?
    Regards,
    Kumar.

    Hi,
    Use the table EDID4 to read the IDOC data.
    You can also use the FM IDOC_READ_COMPLETELY
    Thanks,
    Naren

  • Idoc data  comparison between different R/3 clients.

    Hi ppl ,
    Is there a way idoc comparison can be done between different clients without going
    by Segment by Segment comparison ?
    I have a requirement wherein i have thousands of idocs in QA system and i need to
    compare those with the ones in PROD system. The segments in the idocs may vary
    depending on the data that flows from the third party system which will post idocs in R/3.
    So, the segment wise comparison of data is also ruled out .
    Do we have any standard reports which will help in achieving this purpose ?
    Please let me know how the idoc data comparison can be carried out .
    Regards,
    Nick.

    Hi Nick,
    There is no standared tools available for comparing the data of two idocs.
    By using beyond compare s/w you can check the data, but the thing is you have to download the idoc data to file format.
    By using Idoc_xml_transform function module you can download idoc data to xml format, after you can compare.
    Check this
    http://download.cnet.com/Beyond-Compare/3000-2242_4-10015731.html
    Regards
    Ramesh

  • Idoc data definitions- TPSDL01,SHPMNT03,TPSSHT01

    My translator allows me to import idoc standards.
    My customer is not sure how to export the data definitions from SAP. Are the above IDOC data type definitions available on the web? 
    Sample definition:
    BEGIN_RECORD_SECTION
      BEGIN_CONTROL_RECORD
        BEGIN_FIELDS
          NAME                 TABNAM
          TEXT                 Name of table structure
          TYPE                 CHARACTER
          LENGTH               000010
          FIELD_POS            0001
          BYTE_FIRST           000001
          BYTE_LAST            000010
          NAME                 MANDT
          TEXT                 Client
          TYPE                 CHARACTER
          LENGTH               000003
          FIELD_POS            0002
          BYTE_FIRST           000011
          BYTE_LAST            000013
          VALUE_TABLE          T000

  • IDOC Data transfer

    Hi Experts,
                      I have few questions related to IDOC Data transfer. I have two different SAP Systems S1 and S2,  S1 Creates sales order and send the data through  IDOC Type ORDERS05 to S2,  To create sales order in S1.
    As i know, Program IDOC_INPUT_ORDERS is used for I/B IDocs in S2. Will be there be any programs to push the data from S1 System.
    Thank you
    Kris

    hi,
    idoc is not meant for sending files to another system, they are basically data containers which are sent to other systems like to send the data related to sales orders you can send idoc ORDERS.
    you need to first be clear with the requirement for which business object you want to transfer the data, then need to look out if the Idoc is available for the same then only u can sent it.
    for more info on idocs you can easily search on forums.
    Reg,
    NJ

  • SM58 - IDoc adapter inbound: IDoc data record table contains no entries

    Trying to send Idocs from SAP ECC6.0 via PI 7.0 up until 2 days ago there was no problem.
    Since yesterday, only one specific type of Idoc does not make it into XI (PI). In the Idoc monitor (WE02) the idocs that were created gives status 3 which is good. But all Idocs of that specific type (ZRESCR01) does not go to XI. I can only find them bakc in SM58 where it gives the following message:
    IDoc adapter inbound: IDoc data record table contains no entries
    I have checked SAP notes 1157385 and also 940313, none of them gives me any more insight into this error. I have also checked all the configuration in WE20, SM59, and in XI (repository and directory) and in XI IDX1, IDX2 but could not find anything that would cause this. I can also not think of anything that changed since 2 days ago.
    Please point me in the right direction.

    hi,
    i think in sm 58 u can find entries only when there is some failure in login credential .
    if there is change in IDoc structure than you have to reimport the idoc metadata defination at IDX2.otherwise not requird.
    please check the logical system name pointing to the your requird target system....
    please also verify thet your port should not be blocked.
    pls find the link it may help
    Monitoring the IDOC Adapter in XI/PI using IDX5
    regards,
    navneet

  • Idoc data - Need to see the full SDATA field value

    My SAP system is 4.6C. I need to see and extract the field data of the SDATA field in the EDID4 table. The field size in se11 is showing as of 1000 characters, but the field data when displaying is getting truncated. The message that comes below is Field SDATA is too wide to display (field will be truncated) --> Message no. MO 441 --> The field SDATA is more than 200 characters long. --> the system response comes as The field is output in a format restricted to 200 characters. So, it seems that the data after 200th character is getting truncated.
    How can i increase the display field of the SDATA field???

    It is not possible to view the IDoc data directly in the database. You need to use either WE05 transaction for an existing IDoc or WE60 to view the documentation and layout for each type.
    In a nutshell, there are different segments, each with their own layout, but it's not efficient to create database tables with separate fields for each segment. So all the data is stored in "raw" format and then, knowing the segment code, it may be correctly parsed into a readable format.

  • IDOC Data Records

    I have the IDOC Number with me. How to fetch the Data Records from that ?

    If you want to read the idoc records in your program:
    use the folloing fms:
    Sample code:
      CALL FUNCTION 'EDI_DOCUMENT_OPEN_FOR_READ'
        EXPORTING
          document_number = p_docnum
        IMPORTING
          idoc_control    = f_idoc_control
        EXCEPTIONS
          OTHERS          = 01.
      IF sy-subrc <> 0.
        MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
                WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4
                RAISING error_opening_idoc.
      ENDIF.
    * Read IDOC data segments
      CALL FUNCTION 'EDI_SEGMENTS_GET_ALL'
        EXPORTING
          document_number = p_docnum
        TABLES
          idoc_containers = t_idoc_data
        EXCEPTIONS
          OTHERS          = 01.
      IF sy-subrc <> 0.
        MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
                WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4
                RAISING error_reading_idoc.
      ENDIF.
    * Close IDOC
      CALL FUNCTION 'EDI_DOCUMENT_CLOSE_READ'
        EXPORTING
          document_number = p_docnum
        IMPORTING
          idoc_control    = f_idoc_control
        EXCEPTIONS
          OTHERS          = 01.
      IF sy-subrc <> 0.
        MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
                WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4
                RAISING error_closing_idoc.
      ENDIF.

  • Cound not find any entry in table EDP12 for a partner provided in IDOC data

    Hi All,
    I have an inbound IDOC for a purchase order.
    If a put a query to the table EDP12 for the partner  or message type (ORDERS) provided in the IDOC data, I do not get any entry for this.
    Could you please enlighten me on this...
    Thanks,
    Sanjeet

    Hi Gautham,
    Even if I go to T-Code SE11 or SE12 in production or quality system and try to see the contents of this view, one message pops up saying "You do not have authorization for T-code SM30".
    And in DEV system, I get a message saying "No database view exists for view VEDI_TDP21".
    Anyway my current question is : In T-code WE42, there are two process codes for message type ORDERS:
    1. ORDE                                            (ORDERS           Create sales order)
    2. ORDE_BY_WORKFLOW                (ORDERS           Sales Order withtext in workflow)
    How can I confirm one process code out of the above two for the message type ORDERS?
    Regards,
    Sanjeet

  • How does IDOC data transfer happensbetween two system?

    Hi,
    If there are data in system A and I need to transfer to system B using IDoc.
    What are the key things which will enable data transfer from system A to system.
    It would be great if someone can explain how does IDOC data gets transferred from system A to sytemB.
    Regards,
    Rachel
    Moderator Message : Search for available information or Read SAP documentation. Thread locked
    Edited by: Vinod Kumar on Apr 26, 2011 12:37 PM

    thanks for all your replies...
    let me write down what i have understood ..plz correct me if i have not followed properly..
    1) Once IDocs successfully reach R3 , a function module specific to the Idoc type is called "<b>automatically</b>" and updates database...
    2) this function module we specify in the process code while creating partner profiles
    basically all we need to do is to specify correct function module, right?
    the rest of the process ie . updation in the tables(database) is done automatically..
    Once database is updated, where can i see the added/updated records in database?
    also how do we find this function module?
    I am using MATMAS05...
    Regards,
    Roshani

  • ABAP Report for IDOC data of perticular IDOC basic type

    Hi,
    I have requirment to create report to display the IDOC Data of the perticular IDOC type.
    However I believe in IDOC the data comes in raw format.
    Is there any standard TCODE wherein we can have IDOC data of perticular IDOC type.
    or Could you please let me know how is it possible to retrieve data from IDOC using SAP ABAP .
    Thanks
    Vinay
    Moderator message: (almost) duplicate post locked.
    Edited by: Thomas Zloch on May 2, 2011 12:39 PM

    Hi,
    Please find a sample code
    * Build Control records
    CONTROL_RECORD_OUT-MESTYP = MESTYP.
    CONTROL_RECORD_OUT-IDOCTP =  IDOC_TYPE.
    CONTROL_RECORD_OUT-RCVPRT = 'LS'.   " << Fill the receiver port type US/LS
    CONTROL_RECORD_OUT-RCVPRN = LOGSYS.
    * Build Data records
    *--- EDIDD40 data Here if you have multiple items then make a loop
    loop at i_itab.                   " i_itab contains the details about EDIDD40 fields
      IT_EDIDD-SEGNAM = SEGMENT.   " Will be EDIDD40
      IT_EDIDD-SDATA = i_itab.
    *--- Append the data
    APPEND IT_EDIDD.
    endloop.
    aRs

Maybe you are looking for