IDoC Creation : type ISU_VDEW_UTILMD_V30

Hi Experts,
I need to create an IDoc, Type ISU_VDEW_UTILMD_V30  and Message Type  = ISU_UTILMD.This IDoc Type Consist of 35 segments ,in
this 3 segments are mandatory .The hierarchy level of segments differs from 1-5.i am using the function module
'MASTER_IDOC_DISTRIBUTE ', to create the IDoc.i am populating the segment data from module pool program,
DATA :it_edidc TYPE TABLE OF edidc,
wa_edidc LIKE LINE OF it_edidc,
DATA  it_idoc_data TYPE TABLE OF  edidd .
CALL FUNCTION 'MASTER_IDOC_DISTRIBUTE'
  EXPORTING
    master_idoc_control                  = wa_edidc
*   OBJ_TYPE                             = ''
*   CHNUM                                = ''
  TABLES
    communication_idoc_control           = it_edidc
    master_idoc_data                     = it_idoc_data
EXCEPTIONS
   error_in_idoc_control                = 1
   error_writing_idoc_status            = 2
   error_in_idoc_data                   = 3
   sending_logical_system_unknown       = 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.
  LOOP AT it_edidc INTO wa_edidc.
    MESSAGE s006(zmsg_cls) WITH wa_edidc-docnum.
  ENDLOOP.
After Executing this code Idoc created with error.status code is 26.in details it is showing syntax error.
eg: <b>The segment E1VDEWDTM does not occur at the current level of the basic type ISU_VDEW_UTILMD_V30 (extension ).</b>
i am populating the it_edidd internal table with the segments order  IDoc type.Is there any particular way  to populate the
Data records.?
.plz help me to solve the proble.Points rewarded for solution.

Hi,
The possible reason for this error is that a segemnt is not getting appended at its correct position in the hierarchy level of the idoc.
What you need to make sure is that the edidd internal table contains the segment name field(segnam) in the correct order.
Only if the internal table having data has all the segment names in the records in correct order will the idoc be successfully posted without errors.
Thanks,
Sandeep.

Similar Messages

  • Output type for movement type for IDOC creation

    Dear Experts,
    Can anybody tell how to create "Output type for different movement types for IDOC creation"
    Specially for Movement type used for Inbound & outbound.

    Hi,
    pls find below link's
    https://www.sdn.sap.com/irj/sdn/wiki?path=/display/abap/idoc%2bsteps
    BAPI & IDOC material
    IDOC Scenario Steps
    http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm
    http://sap.niraj.tripod.com/id51.html
    http://www.thespot4sap.com/Articles/SAP_ALE_IDOCS.asp
    Changing fields in an Idoc segment
    Regards
    Raj.

  • Output type for IDOC creation

    Hi Sapgurus,
    Can anybody help as per below.
    Client has third party interface system from which they access stock data from SAP system to front end system.They required stock quantity.As per below transaction I have to create output type for IDOC creation for below t codes.Pls guide for creating output type.
    Note: Consider as per MM point of view.Output type is not for printout,It is for IDOC to display stock at front end system.
    MB1C u2013  Inward + Outward (As per movement types)
    MB1B u2013  Inward + Outward (As per movement types)
    VL02N - Inward + Outward (As per Delivery types (Inbound & Outbound))
    VL06G - Outward
    VL09 -   Inward + Outward (As per Delivery types (Inbound & Outbound)
    MB0A u2013 Inward
    MB01 u2013 Inward
    MBST u2013 Reversal of Inward stock

    Hi,,
    Check the below  idoc WMIVID01
    "IDoc for Inventory"" in help.sap.com
    regards,
    Lalita

  • Contract creation in Backend with Idoc message type BLAORD

    Hello,
    We are creating Backend contracts from the Bidding engine functionality. We only want to create backend contracts and did the necesary configuration.
    We activated BADI: BBP_DETERMINE_LOGSYS
    Method CONTRACT_LOGSYS_DETERMINE.
    We did not yet implement BADI:
    BBP_CTR_BE_CREATE in SRM 5.0
    In SAP R/3 Backend system (Version 46C) we see SAP is trying to create a contract via Idoc message Type: BLAORD.
    In the trx BD87 in the backend we get status 51 :
    Mesage number: 00 055
    "Make an entry in all required fields"
    In the segments of the Idoc however we do not see which field is missing!
    How can we best analise this problem. Or maybe anyone can give us a a hint what is missing.
    Thanks for any reply.
    Aart

    Hello RRK,
    In ref. to your mentioning to change the backend configuration from WKK to MKK might not be as easy to do for organizations.  As those configurations effect the overall creation of purchasing document types in R/3. 
    The Key issue is why the "Target Value" in the Header of the SRM GOA does not get transferred to the R/3 contract.  That's why the issue is still there. 
    Were you guys able to figure out why that was missing? In the BLAORD IDoc the Target Value seems to not get transferred from SRM - its 0.00 if the IDoc is reviewed in WE19.  This seems to be the problem.
    Just wanted to know if you see the same issue in ur system.
    Thanks.
    Sunny.

  • What is the IDOC Basic Type for sales order creation

    Hi Experts,
    Can anyone tell me Idoc Basic type for sales order creation.
    Thanks
    Prashant

    Hi,
    The basic types for creating the order are:
    1.Orders01
    2.Orders02
    3.Orders03
    4.Orders04
    5.Orders05.
    The basic type for SIS order is:
    SISCSO01.
    Regards,
    Krishna.

  • Problem with creation of IDOC Segment Type

    Hi,
    I tried to create IDOC Segment Type Z1LFA1 but error
    prompted "Structure Z1LFA1 already exist.".
    I tried deleting it at se11  but prompted
    "You cannot edit object R3TR TABL Z1LFA1 with the
    standard editor"                          
    and at sm30-TADIR, but prompted
    with "Cannot delete object directory entry, object exists."
    How will go about this??
    Please help!
    Thanks!

    hi,
    yup, tried doing that on we31 but the segment does not exist yet.
    we're currently upgrading from 4.6 to ecc, I think the structure
    was tranferred to our ecc client but the idoc segment and idoc type were not. I'll just have to transport it then.
    Thanks!

  • Output type for MB1B & MB1C-IDOC creation

    Dear Expert,
    I have to make output type for MB1B & MB1C transaction to create IDOC.Can anybody guide path to create Output type for same.

    Hi anupmore124,
    You can create a new condition type, named as "ZWA1" and you can copied this from WA01.
    Once this is copied, change the following data:
    1. In partner functions, include:
    Medium: 6 - EDI
    Funciton: (blank)
    You can delete the other partner function(s), if you want that this new output message type can be handled only by EDI (for IDOCs).
    2. In the "General data" tab, you need to have selected only:
    Access sequence: i.e. 0003 - Trans.Type/Print Vers./Indic.
    Check box active "Access to conditions"
    The rest of the check box needs to be inactive.
    3. In the "Default" tab, define:
    Dispatch time: 1 - Send with periodically scheduled job
    Transmission medium: 6 - EDI
    Then, save the data and now, the IDOC can be created.
    Obviously, I presume that you made your customising before in WE20 with the correct IDOC message type, etc.
    I hope this help.
    Kind regards,
    Sandra

  • IDOC creation after the creation of a purchase order

    Hi everybody,
                I want some configuration details regardign IDOC creation. The requirement is, once i create a purchase order in one system, the details should automatciaclly transfer to other system through IDOC. could any one suggest any document or detailed procedure to accomplish the task. Thanks in advance,
             Santosh.

    hi santosh kumar,
    Creating an IDoc Segment WE31:
    The segment defines the structure of the records in an IDoc. They are defined with transaction WE31.
    We will define a structure to send a text from the text database.
    Transaction WE31 calls the IDoc segment editor. The editor defines the fields of a
    single segment structure. The thus defined IDoc segment is then created as a data
    dictionary structure. You can view the created structure with SE11 and use it in an
    ABAP as any TABLES declaration.
    To demonstrate the use of the IDoc segment editor we will set up an example, which
    allows you to send a single text from the text pool (tables STXH and STXL) as an
    IDoc. These are the texts that you can see with SO10 or edit from within many
    applications.
    We will show the steps to define an IDoc segment YAXX_THEAD with the DDic
    structure of THEAD.
    To facilitate our work, we will use the "copy-from-template-tool", which reads the
    definition of a DDIC structure and inserts the field and the matching definitions as
    rows in the IDoc editor. You could, of course, define the structure completely
    manually, but using the template makes it easier.
    The tool in release 4.0b lets you use both DDIC structures or another IDoc segment
    definition as a template.
    The thus created structure can be edited any time. When saving, it will create a data
    dictionary structure based on the definition in WE31. The DDIC structure will retain
    the same name. You can view the structure as a table definition with SE11 and use it
    in an ABAP the same way.
    Defining the Message Type (EDMSG)
    The message type defines the context under which an IDoc is transferred to its destination. It allows for using the same IDoc file format for several different applications.
    Imagine the situation of sending a purchase order to a supplier. When the IDoc with
    the purchase order reaches the supplier, it will be interpreted as a sales order
    received from a customer, namely you.
    Simultaneously you want to send the IDoc data to the supplier's warehouse to inform
    it that a purchase order has been issued and is on the way.
    Both IDoc receivers will receive the same IDoc format; however, the IDoc will be
    tagged with a different message type. While the IDoc to the supplier will be flagged
    as a purchase order (in SAP R/3 standard: message type = ORDERS), the same IDoc
    sent to the warehouse should be flagged differently, so that the warehouse can
    recognize the order as a mere informational copy and process it differently than a
    true purchase order.
    The message type together with the IDoc type determine the processing function.
    The message types are stored in table EDMSG.
    Defining the message type can be done from the transaction WEDI
    EDMSG: Defining the message type (1)
    The entry is only a base entry which tells the system that the message type is
    allowed. Other transactions will use that table as a check table to validate the entry.
    IT is as shown .
    EDMSG: Defining the message type (1):
    The entry is only a base entry which tells the system that the message type is
    allowed. Other transactions will use that table as a check table to validate the entry.
    Sales Orders are being created through inbound IDocs using FM 'EDI_DATA_INCOMING'. Now a Report is required to check the status of these Inbound IDocs along with Sales Orders generated against customer Purchase Orders.
    Requirement:
    Sales Orders are being created through inbound IDocs using FM 'EDI_DATA_INCOMING'. Now a Report is required to check the status of these Inbound IDocs along with Sales Orders generated against customer Purchase Orders.
    Processing:
    The report selects, 'ORDERS' IDoc numbers & status, generated between given time range, from table EDIDC. Further, it calls Function Module 'IDOC_READ_COMPLETELY' to get the IDoc details. Then required information is extracted by reading relevant field data of IDoc segments.
    sampl code:
    REPORT  Z_EDI_FILE_LOAD_STATUS_REPORT           .
    Staus Report for Inbound IDOCs ( Sales Orders )
    Program        : Z_EDI_FILE_LOAD_STATUS_REPORT
    Presented By   : www.rmtiwari.com
    TABLES : EDIDC.
    ALV stuff
    TYPE-POOLS: SLIS.
    DATA: GT_FIELDCAT TYPE SLIS_T_FIELDCAT_ALV,
          GS_LAYOUT   TYPE SLIS_LAYOUT_ALV,
          GT_SORT     TYPE SLIS_T_SORTINFO_ALV,
          GT_LIST_TOP_OF_PAGE TYPE SLIS_T_LISTHEADER.
    DATA : BEGIN OF T_REPORT OCCURS 0,
             IDOC_NO       TYPE EDI_DOCNUM,
             IDOC_DATE     TYPE SY-DATUM,
             IDOC_TIME     TYPE SY-UZEIT,
             SORDER_NO     TYPE VBELN,
             STP_NO        TYPE KNA1-KUNNR,
             STP_NAME(35)  TYPE C,
             STP_PHONE(12) TYPE C,
             PO_NO(15)     TYPE C,
             STATUS        TYPE C,
             S_TEXT(70)    TYPE C,
             ERROR(70)     TYPE C,
           END OF T_REPORT.
    --PARAMETER--
    selection-screen begin of block date with frame title TEXT-S01.
    select-options: UDATE for  EDIDC-UPDDAT
                          default SY-datum obligatory,    "Changed On
                    UTIME for  EDIDC-UPDTIM .             "Changed Time
    selection-screen end   of block date.
    INITIALIZATION.
    START-OF-SELECTION.
    PERFORM SHOW_STATUS_REPORT.
    *&      Form  alv_grid
          text
    -->   p1        text
    < --  p2        text
    FORM ALV_GRID.
      IF GT_FIELDCAT[] IS INITIAL.
        PERFORM FIELDCAT_INIT.
        PERFORM LAYOUT_INIT.
        PERFORM SORT_INIT.
      ENDIF.
      PERFORM GRID_DISPLAY.
    ENDFORM.                    "alv_grid
    *&      Form  layout_init
    FORM LAYOUT_INIT.
      GS_LAYOUT-ZEBRA             = 'X'.
      GS_LAYOUT-CELL_MERGE        = 'X'.
      GS_LAYOUT-COLWIDTH_OPTIMIZE = 'X'.
      GS_LAYOUT-NO_VLINE          = ' '.
      GS_LAYOUT-TOTALS_BEFORE_ITEMS = ' '.
    ENDFORM.                    " layout_init
    *&      Form  fieldcat_init
    FORM FIELDCAT_INIT.
      DATA: LS_FIELDCAT TYPE SLIS_FIELDCAT_ALV.
       CLEAR LS_FIELDCAT.
      LS_FIELDCAT-FIELDNAME    = 'IDOC_NO'.
      LS_FIELDCAT-KEY          = 'X'.
      LS_FIELDCAT-REPTEXT_DDIC = 'IDOC'.
      LS_FIELDCAT-OUTPUTLEN    = 10.
    Fix for ALV print bug, which puts 'N/A' over last digit
    Set inttype to 'N' to stop corruption of printed ALV cell.
      LS_FIELDCAT-INTTYPE = 'N'.
      APPEND LS_FIELDCAT TO GT_FIELDCAT.
      CLEAR LS_FIELDCAT.
      LS_FIELDCAT-FIELDNAME    = 'IDOC_DATE'.
      LS_FIELDCAT-REPTEXT_DDIC = 'Creation Date'.
      LS_FIELDCAT-OUTPUTLEN    = 10.
      APPEND LS_FIELDCAT TO GT_FIELDCAT.
      CLEAR LS_FIELDCAT.
      LS_FIELDCAT-FIELDNAME    = 'IDOC_TIME'.
      LS_FIELDCAT-REPTEXT_DDIC = 'Creation Time'.
      LS_FIELDCAT-OUTPUTLEN    = 8.
      APPEND LS_FIELDCAT TO GT_FIELDCAT.
      CLEAR LS_FIELDCAT.
      LS_FIELDCAT-FIELDNAME    = 'STATUS'.
      LS_FIELDCAT-REPTEXT_DDIC = 'St'.
      LS_FIELDCAT-OUTPUTLEN    = 2.
      APPEND LS_FIELDCAT TO GT_FIELDCAT.
      CLEAR LS_FIELDCAT.
      LS_FIELDCAT-FIELDNAME    = 'ERROR'.
      LS_FIELDCAT-REPTEXT_DDIC = 'Message'.
      LS_FIELDCAT-OUTPUTLEN    = 70.
      APPEND LS_FIELDCAT TO GT_FIELDCAT.
      CLEAR LS_FIELDCAT.
      LS_FIELDCAT-FIELDNAME    = 'STP_NO'.
      LS_FIELDCAT-REPTEXT_DDIC = 'S.T.Party No'.
      LS_FIELDCAT-OUTPUTLEN    = 10.
      APPEND LS_FIELDCAT TO GT_FIELDCAT.
      CLEAR LS_FIELDCAT.
      LS_FIELDCAT-FIELDNAME    = 'STP_NAME'.
      LS_FIELDCAT-REPTEXT_DDIC = 'Sold to Party Name'.
      LS_FIELDCAT-OUTPUTLEN    = 35.
      APPEND LS_FIELDCAT TO GT_FIELDCAT.
      CLEAR LS_FIELDCAT.
      LS_FIELDCAT-FIELDNAME    = 'PO_NO'.
      LS_FIELDCAT-REPTEXT_DDIC = 'Purch Order'.
      LS_FIELDCAT-OUTPUTLEN    = 15.
      APPEND LS_FIELDCAT TO GT_FIELDCAT.
      CLEAR LS_FIELDCAT.
      LS_FIELDCAT-FIELDNAME    = 'STP_PHONE'.
      LS_FIELDCAT-REPTEXT_DDIC = 'S.T.Party Phone'.
      LS_FIELDCAT-OUTPUTLEN    = 15.
      APPEND LS_FIELDCAT TO GT_FIELDCAT.
    ENDFORM.                    "fieldcat_init
    *&      Form  sort_init
    FORM SORT_INIT.
      DATA: LS_SORT TYPE SLIS_SORTINFO_ALV.
      CLEAR LS_SORT.
      LS_SORT-FIELDNAME = 'IDOC_DATE'.
      LS_SORT-SPOS      = 1.
      LS_SORT-UP        = 'X'.
      APPEND LS_SORT TO GT_SORT.
      CLEAR LS_SORT.
      LS_SORT-FIELDNAME = 'IDOC_TIME'.
      LS_SORT-SPOS      = 2.
      LS_SORT-UP        = 'X'.
      APPEND LS_SORT TO GT_SORT.
      CLEAR LS_SORT.
      LS_SORT-FIELDNAME = 'STATUS'.
      LS_SORT-SPOS      = 3.
      LS_SORT-UP        = 'X'.
      APPEND LS_SORT TO GT_SORT.
      CLEAR LS_SORT.
      LS_SORT-FIELDNAME = 'IDOC_NO'.
      LS_SORT-SPOS      = 4.
      LS_SORT-UP        = 'X'.
      APPEND LS_SORT TO GT_SORT.
    ENDFORM.                    "sort_init
    *&      Form  grid_display
    FORM GRID_DISPLAY.
      CALL FUNCTION 'REUSE_ALV_GRID_DISPLAY'
        EXPORTING
          IS_LAYOUT     = GS_LAYOUT
          IT_FIELDCAT   = GT_FIELDCAT
          IT_SORT       = GT_SORT
          i_callback_program      = SY-REPID
          I_CALLBACK_TOP_OF_PAGE = 'TOP_OF_PAGE'
          I_DEFAULT     = ' '
          I_SAVE        = 'X'
        TABLES
          T_OUTTAB      = T_REPORT
        EXCEPTIONS
          PROGRAM_ERROR = 1
          OTHERS        = 2.
    ENDFORM.                    "grid_display
    *&      Form  COMMENT_BUILD
          Processing of listheader
    FORM COMMENT_BUILD USING P_FK_LIST_TOP_OF_PAGE TYPE SLIS_T_LISTHEADER.
      DATA: LS_LINE TYPE SLIS_LISTHEADER.
      REFRESH P_FK_LIST_TOP_OF_PAGE.
    List Heading : Typ H
      CLEAR LS_LINE.
      LS_LINE-TYP  = 'H'.
      LS_LINE-INFO  = 'Sales Order Interface: Z_EDI_FILE_LOAD'.
      APPEND LS_LINE TO P_FK_LIST_TOP_OF_PAGE.
    List : Typ S
      clear LS_LINE.
      LS_LINE-typ  = 'S'.
      LS_LINE-key  = 'Date Range:'.
      LS_LINE-info  = UDATE-low.
      if not UDATE-high is initial.
        write ' To ' to  LS_LINE-info+30.
        LS_LINE-info+36 = UDATE-high.
      endif.
      APPEND LS_LINE TO P_FK_LIST_TOP_OF_PAGE.
    ENDFORM.                               " COMMENT_BUILD
          FORM TOP_OF_PAGE                                              *
          Ereigniss TOP_OF_PAGE                                       *
          event     TOP_OF_PAGE
    FORM TOP_OF_PAGE.
      PERFORM COMMENT_BUILD  USING gt_LIST_TOP_OF_PAGE[].
      CALL FUNCTION 'REUSE_ALV_COMMENTARY_WRITE'
        EXPORTING
          IT_LIST_COMMENTARY = GT_LIST_TOP_OF_PAGE.
    ENDFORM.                    "TOP_OF_PAGE
    *&      Form  show_status_report
    FORM SHOW_STATUS_REPORT .
    Report to show status.
      DATA: BEGIN OF T_TEDS2 OCCURS 0.
              INCLUDE STRUCTURE TEDS2.
      DATA: END OF T_TEDS2.
      DATA: BEGIN OF T_IDOC_CONTROL_TMP OCCURS 0.
              INCLUDE STRUCTURE EDIDC.
      DATA: END OF T_IDOC_CONTROL_TMP.
      CONSTANTS: C_STATUS_IN_IDOC_POSTED       LIKE EDIDC-STATUS VALUE '53'.
      DATA : T_EDIDS TYPE STANDARD TABLE OF EDIDS WITH HEADER LINE.
      DATA : T_EDIDD TYPE STANDARD TABLE OF EDIDD WITH HEADER LINE.
      DATA : GV_PARTNER_SEG TYPE E1EDKA1,
             GV_PO_REF_SEG  TYPE E2EDK02.
    Get text for status values
      SELECT * FROM TEDS2 INTO TABLE T_TEDS2 WHERE LANGUA = SY-LANGU.
    Read the IDoc's status after processing
      SELECT * FROM EDIDC
        INTO TABLE T_IDOC_CONTROL_TMP
       WHERE UPDDAT IN UDATE
         AND UPDTIM IN UTIME
         AND MESTYP = 'ORDERS'.
      LOOP AT T_IDOC_CONTROL_TMP.
      IDoc has been processed, since control record changed.
        READ TABLE T_TEDS2 WITH KEY STATUS = T_IDOC_CONTROL_TMP-STATUS.
        T_REPORT-IDOC_NO = T_IDOC_CONTROL_TMP-DOCNUM.
        T_REPORT-IDOC_DATE = T_IDOC_CONTROL_TMP-CREDAT.
        T_REPORT-IDOC_TIME = T_IDOC_CONTROL_TMP-CRETIM.
        T_REPORT-S_TEXT = T_TEDS2-DESCRP.
        IF T_IDOC_CONTROL_TMP-STATUS = C_STATUS_IN_IDOC_POSTED.
        ok status
          T_REPORT-STATUS = 'S'.
        ELSE.
        error status
          T_REPORT-STATUS = 'E'.
        ENDIF.
        Get IDoc details.
        CALL FUNCTION 'IDOC_READ_COMPLETELY'
          EXPORTING
            DOCUMENT_NUMBER         = T_REPORT-IDOC_NO
          TABLES
            INT_EDIDS               = T_EDIDS
            INT_EDIDD               = T_EDIDD
          EXCEPTIONS
            DOCUMENT_NOT_EXIST      = 1
            DOCUMENT_NUMBER_INVALID = 2
            OTHERS                  = 3.
      Get Error status
        READ TABLE T_EDIDS WITH KEY STATUS = T_IDOC_CONTROL_TMP-STATUS.
        IF SY-SUBRC EQ 0.
          REPLACE FIRST OCCURRENCE OF '&1' IN T_EDIDS-STATXT
                                WITH T_EDIDS-STAPA1.
          REPLACE FIRST OCCURRENCE OF '&2' IN T_EDIDS-STATXT
                                WITH T_EDIDS-STAPA2.
          REPLACE FIRST OCCURRENCE OF '&3' IN T_EDIDS-STATXT
                                WITH T_EDIDS-STAPA3.
          REPLACE FIRST OCCURRENCE OF '&4' IN T_EDIDS-STATXT
                                WITH T_EDIDS-STAPA4.
          REPLACE FIRST OCCURRENCE OF '&' IN T_EDIDS-STATXT
                                WITH T_EDIDS-STAPA1.
          REPLACE FIRST OCCURRENCE OF '&' IN T_EDIDS-STATXT
                                WITH T_EDIDS-STAPA2.
          REPLACE FIRST OCCURRENCE OF '&' IN T_EDIDS-STATXT
                                WITH T_EDIDS-STAPA3.
          REPLACE FIRST OCCURRENCE OF '&' IN T_EDIDS-STATXT
                                WITH T_EDIDS-STAPA4.
          T_REPORT-ERROR = T_EDIDS-STATXT.
        ENDIF.
        LOOP AT T_EDIDD.
          CASE T_EDIDD-SEGNAM.
            WHEN 'E1EDKA1'.
              GV_PARTNER_SEG = T_EDIDD-SDATA.
              CLEAR : T_REPORT-STP_NAME.
              CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'
                EXPORTING
                  INPUT  = GV_PARTNER_SEG-PARTN
                IMPORTING
                  OUTPUT = T_REPORT-STP_NO.
              SELECT SINGLE NAME1 TELF1
                INTO (T_REPORT-STP_NAME,T_REPORT-STP_PHONE)
                FROM KNA1
               WHERE KUNNR = T_REPORT-STP_NO.
            WHEN 'E1EDK02'.
              GV_PO_REF_SEG = T_EDIDD-SDATA.
              T_REPORT-PO_NO = GV_PO_REF_SEG-BELNR.
          ENDCASE.
        ENDLOOP.
        APPEND T_REPORT.
      ENDLOOP .
      SORT T_REPORT BY STATUS IDOC_NO.
    Show Report
      PERFORM ALV_GRID.
    ENDFORM.                    " show_status_report
    thanks
    karthik
    reward me points if usefull.

  • Problem in Idoc creation in ME22N

    Hi All,
    We are facing a problem in Idoc creation in transaction ME22N.Our requirement is to trigger an output type and create a idoc everytime a change is made to a particular Purchase Order.
    Presently however,for some vendors,when we change the plant at the item level,an Idoc is not created(with a message that the changes are not relevant to create an Idoc).Any other change to the Purchase Order like changes in quantity or price,results in successful Idoc creation.
    We have also noticed that this happens only in the case of certain vendors.The Customer Info records and vendor data are all believed to be fine.
    Are any other config settings required to be maintained for this?
    Thanks in advance!
    Regards,
    Nejuma Iqbal

    Hi Nejuma,
    I don't think there is any problem with cofiguration settings.u r getting the idocs for some vendors .
    if iam not wrong u r giving LS in the tcode(we20).The method which u r using is change pointers.As u r using standard idoc all the settings will be done.
    Only settings u have to do is
    1>generate partner profiles(WE20)
    2>Distribute model view(BD64).
    REGARDS,
    Nagaraj

  • Value mapping in the ERP system during IDOC creation

    We have a PI File-IDOC scenario.
    We can translate simple mappings such as currency or unit of measure in PI(7.1) using the Value Mapping function. For complicated mappings involving business logic (e.g. Tax code which is derived from multiple fields) we want to perform these mapping in the ERP (ECC6) system. Is there an approved generic SAP standard process where these value mappings can be done in the IDOC creation which is still valid when re-processing?
    e.g. a specific BADI or enhancement point recommended for these mapping?
    There might also be a requirement to add segments based on value mapping logic for example when a tax record segment is only required for a non-zero tax code which is mapped via business logic.
    Can someone please direct me in the right direction.

    Thanks for your answers but I assumed that using a user exit / Enhancement point was obvious. What I'd like to know is a generic entry point that I can estabolish a IDOC enhancement framework. Somewhere I can call a class containing methods linked to IDOC message types
    e.g. Call similar to my prototype (this will be where dependant on mappings certain segments will need to be inserted such as tax segments.
      ASSIGN control-mestyp TO <mestyp>.
        CALL METHOD (<mestyp>)
          EXPORTING
            control        = control
            data           = data
          IMPORTING
            have_to_change = have_to_change
            protocol       = protocol
            new_entries    = new_entries.
    The "entry point" must be processed both at creation and reprocess. We are also dealing with Inbound IDOCs not outbound

  • Debugging EDI output (IDOC creation) for purchase order...

    Hi,
    We have a EDI output type defined for Purchase order. When I go to Messages tab in ME22N transaction and repeat the EDI output and save it, it creates a IDOC which I can see using transaction WE02.
    Now the problem is there is a user exit which I know gets triggered, when the IDOC is created for this PO. When we do some changes in this user exit, I see those changes are reflected when new IDOC is created. But if I put breakpoint, and do repeat output -> save, the debugger does not stop there.
    Is there is some technique I can see the breakpoint stoppage in user exit for IDOC creation during EDI output for Purchase order ?
    Regards,
    Rajesh

    Hi
    Youc can set the output Peridoically (After Giving the output type, set the furthere data as periodic).
    Save.
    Set the break point in your user exit.
    Go to se 38 -> Run RSNAST00,
    Give the object id (Your PO #)
    Give the output type  and execute, the control will stop at break point.
    Regards,
    Baburaj

  • PO Collaboration : Invoice Creation Type field

    Hello,
    The Invoice Creation Type field in the SNC Web UI is always "Invoice Creation not allowed" irrespective of the settings to the Master Data / Transaction Data.
    Given below are the settings I ve maintained
    ECC System:
    PO -> Item Details -> Invoice Tab:
    Inv. Receipt Indicator - Checked
    GR-Bsd IV - Checked / Unchecked
    SNC System:
    Vaildation Checks - Tried both these settings:
    1. PO_INVOICE_CREATION - Active
        PO_INVOICE_DATA_ASSIGN - Active
        PO_INVOICE_RELATED_TO_PO_OR_ASN - Inactive
    2. PO_INVOICE_CREATION - Inactive
        PO_INVOICE_DATA_ASSIGN - Active
        PO_INVOICE_RELATED_TO_PO_OR_ASN - Active
    Infact, I am not able to see the Invoice tab itself in the PO details screen in SNC Web UI.
    Note : I am using the Orders.Orders05 Idoc for sending the PO from ECC to SNC system.

    Hi Bharath
    Your settings are fine
    Please do the following checks
    If you use IDocs of type ORDERS.ORDER05, SAP SNC can instead read the data for these fields from a reference document, such as a contract, that has previously been transferred via the Core Interface (CIF).
    In your PO you would have referenced a contract/agreement, Please check whether it is CIFed or not
    Also before CIFING do implement these notes
    1053121 & 828912
    Now when you send the ORDERS idoc, The RON xml reads this data and puts in structure
    <FollowUpInvoice>
      <RequirementCode>01</RequirementCode>
      <GoodsReceiptBasedInvoiceIndicator>TRUE</GoodsReceiptBasedInvoiceIndicator>
      <CustomerSelfBillingIndicator>FALSE</CustomerSelfBillingIndicator>
      <ProductTaxationCharacteristicsCode>V1</ProductTaxationCharacteristicsCode>
      </FollowUpInvoice>
    Irrespective, whether you create invoice for ASN or PO, the tab should be visible as Nikhil rightly mentioned
    In SAP SNC , Controlling Invoice Creation for POs is done by FollowUpRequirementCode as mentioned above
    Now since you are using ORDERS, you need to check you SA or Contract in Item Details Tab
    the following fields need to be checked "IR" in both cases and In Header Details Field "Invoicing Party"
    Also during creation of PO, make sure you dont check Unlimited Overdelivery in item delivery tab and even in your reference document.
    Now after implementing above two notes reCIF and try creating PO, It will work
    Please do mention whether you are able to see the above structure in your RON xml in SCM side and what details???
    Best Regards
    Vinod

  • IDOCs creation - Transfer Orders(TOs)  for Deliveries - Basic doubts, thanq

    Hi Experts,
    Am new to IDOCs.  I hv a requirement, so, request u that, Can I get some Wht to do tips from u?
    My doubts:
    1- I hv been asked to create IDOC, Wht does it mean?
    2 - How the created IDOC will be get posted?
    My requirement is:
    Original inbound idoc sent from Gentran will update the delivery with all serial numbers per material for all serialized product.  The message code will be the indicator that a Transfer Order-TO, idoc must be created for TO confirmation.
    I need to do===>   Should be executed only when the message code on the delivery idoc is u201CTOCu201D.  Look up the warehouse code on the delivery header using the delivery nbr in the delivery idoc.  Create a new TO confirm idoc per delivery idoc being processed.  Create a line item on this idoc for every line on the delivery idoc.  Each TO line includes the delivery number and delivery item number so the TO number and line number can be looked up in table LTAP by using the delivery number and line item number found on the delivery idoc.  There will be at 2 transfer orders for each delivery item b/c of the 2 step pick process, so select the TO nbr that has 916 as the destination storage type (LTAP-NLTYP).  There may be more than 1 pair of TOs per delivery item so this must be completed for each TO found relevant to each delivery item.
    The inbound delvry03 idoc will update the delivery with the serial numbers as part of the standard functionality.  Since the transfer order must also be confirmed with the quantities on the inbound idoc, an additional idoc must be created from within the delivery update process.  The transfer order can be updated and confirmed using the standard idoc and function module which should be created and initiated from the delivery update function module customer exit.
    Source = DELVRY03     Destination = WMTCID01
    Record Name-Field Name-Record Name-Field Name-Description---Comments
    E1EDL20     VBELN-E1LTCOH-LGNUM-Warehouse Number-Look w/ idoc delivery nbr
    E1EDL20     VBELN-E1LTCOH-TANUM-Transfer Order Number- Look w/ idoc delivery nbr
    E1EDL24     POSNR-E1LTCOI-TAPOS-Transfer Order Line Item- Look  w/ idoc delivery line nbr
    EVERY THING IS DATA TRIGGERED!!!
    thanq
    Edited by: Srinivas on Jun 27, 2008 4:41 PM

    IDOC Programming
    There are two processes in IDOC processing one is INBOUND PROCESS( IDOC coming to the system and its handling at various stages) and the other is OUTBOUND PROCESS( IDOC is send to other system . Separate ABAP programs are written for these 2 processes and different configuration settings are required for each one .Depending upon the trigeering mechanism different programming approaches are used.OUTBOUND PROGRAMS handle the IDOC creation and INBOUND PROGRAMS handle the inbound IDOC and the data trasfer from the IDOC to the database tables.
    NEED FOR ABAP PROGRAMMING arises if
    1)New IDOC was created
    Depending upon the triggering mechanism i.e change pointer,message control
    etc the programming technique changes and the type of process.
    2)Existing IDOC was extended
    User Exits are used to populate data in new segments added and to read them
    back.
    3)To enhance an exsiting process.
    User Exits are used .
    Basic structure of an OUTBOUND PROGRAM
    The basic structure of all outbound programs is same. The CONTROL
    record which is of TYPE EDIDC has to be filled. It contains important fields like
    IDOCTP IDOC type
    MESTYP Message Type
    RCVPRN Recieving Partner (Destination)
    RCVPRT Partner Type (it is LS i.e Logical System)
    The DATA RECORD internal table which is of TYPE EDIDD has to be filled
    in the same order as there are segments in the IDOC definition.
    It has 2 important fields which are to be filled ,these are
    SEGNAM Name of the segment
    SEGDATA Data in the segment and can be upto 1000 bytes.This field
    is corresponds to each data segment in the IDOC.
    e.g.
    DATA INT_EDIDD LIKE EDIDD OCCURS 0 WITH HEADER LINE.
    DATA W_SEGDATA LIKE zsegment "custom segment zsegment
    INT_EDIDD-SEGNAM = 'ZSEGMENT'
    W_SEGDATA-field1 = value "taken from some table
    W_SEGDATA-field2 = value "taken from some table
    INT_EDIDD-SEGDATA = W_SEGDATA
    APPEND INT_EDIDD
    This will fill the data record corresponding to the segment ZSEGMENT . For all
    segments the sam steps will be repeated until all the data corresponding to all the
    segments in the idoc is filled in the internal table of type EDIDD.
    There is only one control record and can be multile data records in the idoc
    structure.
    Which data is to be extracted from the tables to be filled in EDIDD type internal table is determined in standalone programs from the objects which are specified in the selection screen and from the object key passed to the function module in case of message control and is taken from BDCP table in case of change pointers using function modules "CHANGE_POINTERS_READ"
    In case of stand alone programs and function modules based on change pointers method the function module "MASTER_IDOC_DISTRIBUTE" is used to send the IDOC to ALE layer for distribution ,in case of message control it is handled automatically by the RSNASTED program invoked by the message control.
    OUTBOUND PROCESS AND OUTBOUND PROGRAM.
    Outbound programs are used in outbound process to genearte IDOCs . There
    purpose is to extract the data from the tables and to fill the IDOC data records
    and the control record in the IDOC and pass ito the ALE layer for distribution to the recieving system .
    Depending upon the triggering mechanism (how and when the outbound program will be started different techniques and interface is used for outbound program.
    1)Message control
    Application like PO(purchase order) creation use this technique , where the output type is linked to the application(Message control is a configurable cross application component which can be set in IMG .Such programs are created in the form of function modules and linked to the output type which is linked to the apllication.These have predefined interfaces.
    In outbound programs(function module) that use message control the key of the
    application document is passed to the function module whcig will read the data from the table depending upon the key passed(NAST structure) and fill the IDOC segemnts with the application data.The control record is also passed to the function module but is not fully filled, the rmaining fields are filled and the control is passed back to the calling program which is RSNASTED and is invoked by the
    message control to process ALE and EDI output types and this program on recieving the IDOC data will create the physical IDOC in the system.
    The parameteers passed to the function module are
    IMPORTING PARAMETERS
    OBJECT LIKE NAST
    It contains documents key.
    CONTROL_RECORD_IN LIKE EDIDC
    It contains the partailly filled control record
    EXPORETING PARAMETER
    OBJECT_TYPE
    CONTROL_RECORD_OUT LIKE EDIDC
    TABLES
    INT_EDID LIKE EDIDD
    The internal table used to fill the data records in the same order as they exists in the IDOC.
    The important parameters that should be filled in the custom function module are
    CONTROL_RECORD_OUT and INT_EDIDD .The OBJK field of the structue NAST contains the key of the apllication document.
    2)Stand alone programs
    Generally used for Master Data transfer and as such depending upon the requirement can have different interfaces.The programs have a selection screen which has select options to select the objects, and parameters for specifying the recipient Logical System and the Message Type.
    Data is selected based on the specified objects from the tables . and control record of type EDIDC is created and filled with important values like DIRECTION ,IDOCTP,RCVPRT,RCVPRN and MESTYP .
    Data is filled in an internal table of TYPE EDIDD according to segment definitions
    and in same order and the function module MASTER_IDOC_DISTRIBUTE is called passing the control record and the internal table containg IDOC data and importing an internal table consisting of control records for each communication IDOCS created.
    3)Change pointer
    Change Pointer table is read and checked if changes were made to important fields , if so the outbound program will be triggered automatically , these have predefined interfaces
    ALE/IDOC Transaction
    SALE Area Menu for ALE configurations.It includes transactions for
    Logical System definition and linking it to a client, Transactions for
    RFC Destination and Port Definition Etc.
    SM59 RFC Destination
    Here we specify the login settings for the destination including
    the I.P address or Application Server name and the User name and
    password.The information entered here is used to run Remote Function
    Calls(RFC ) on the destination server .We can create number of types
    of RFC Destinations but 3 types are important .
    R/3 (R/3 to R/3), LS(logical system) and TCP/IP.
    The name of the RFC destination should be same as that of Logical
    System as it helps in creation of automatic partner profiles.
    WE21 Port Definition.
    There are 6 types of ports but only 2 types File and Transactional RFC
    types of ports are important.
    We have to specify the RFC Destination before a port can be created.
    WE57 This is used to assign the Inbound function module to the Message Type
    and to the IDOC Type.
    WE42 This is used to define the process Code for Inbound Processing.
    BD95 Define Filter object type .We can specify the field and the table it belongs
    to as a filter object .
    BD59 Assignment of Filter object type to the Message Type .Here we create the
    link between Filter object and the segment and the message type and the
    segment Field.
    BD50 Set message Type to reducible.
    BD65 Define Mandatory Fields.
    BD64 Distribution Model . Also known as Customer Distribution Model Used to
    define all the messages that will be exchanged between remote systems
    and the name of thes logical systems. Any filters can also be specified.
    The model once created has to be distributed on every system which will
    be communicating ,It can be maintained on only One system.
    BD21 Creating IDOcs from change pointers.
    This can be used to create IDOCs from change pointers for a particular
    message LIKE MATMAS.
    BD22 This can be used to delete change pointers.
    BD87 Status Monitor. Idocs can be selected base on number of criteria and there
    processing status can be seen in detail.
    BD10 Material Master Data Distribution .
    Based on Message MATMAS.
    BD12 Customer Master Data Distribution .
    Based on Message CREMAS.
    BD14 Vendor Master Data Distribution
    Based on Message DEBMAS .
    BDFG Generate ALE Interface for BAPI.
    Here we specify the Business Object and the BAPI Function module for
    which the interface has to be created.
    WE31 Segment Editor.
    This is used to create segments. We create the segment type and
    segment definition is automatically created by editor e.g. Z1DUMMY is
    segment type and Z2DUMMY is the segment definition .We specify the
    fields and the data elements these cp\orresponds to create segments.
    WE30 IDOC Editor
    It is used to create a new IDOC Type or IDOC Extension .We specify the
    segments that will be addd to the IDOC type.
    WE02/05 IDOC List.
    Various selct options and parameters are provided to select IDOCs
    depending on the date, direction , mesage type etc.
    WE20 Partner Profile
    Here we create partner profile for each and every partner from / to which
    the messages will be exchanged.There are 6 types of PF generally only
    profiles of type LS(Logical System) ,KU(Customer) ,LI(Vendor) is used.
    We specify the partner number and partner type and the agent and
    the agent type responsible for handling of errors .
    For every message send to the partner we have a outbound record and for
    evry message coming from the partner we have the inbound record .
    We specify the message in the otbound/inbound records ,double
    clicking will take us to the detailed screen where the IDOC Type ,Port
    and whether the IDCO will be immediatelt processed or collected are
    mentioned.

  • IHC errors valid clearing partner not found and no header details found while idoc creation after f110

    IHC errors :valid clearing partner not found and no header details found while idoc creation after f110
    Please let me know where the config is missing for ihc automatic payment program.in we02 status is not 53.
    Please help

    Hi
    Please share the error message in the IDOC.
    If the error message is IHC204 "No valid clearing partner was found", it may be due to the missing correct configuration in Set Up Creation of Payment Requests for Inbound IDoc in FI, which links the clearing partner, ALE logical system partner type and IHC account number.
    Cheers
    taro

  • Change pointers and Idoc creation

    Hello,
    I would like to create change pointers for any changes regarding one of our customer infotypes: 9002 (hrp9002)
    I was able to do that, however, I'm struggeling with the details.
    The problem is that I do not want to send any data related to infotype 9002. I just need this change pointer to trigger idoc creation for the related objects.
    Example: Let's assume that infotype 9002 gets created for position S 40001234. Once a night a customer report is executed via a job which reads all unprocessed change pointers (including the one mentioned above) and sends the corresponding object. In this case, an Idoc for the holder of position 40001234 should be created WITHOUT data for infotype 9002.
    The message type is HRMD_A.
    What do I need to do?
    Thank you for your input.

    Hi,
    For Info type 9002 we need to implement Badi HRALE00CHANGE_PTRS using below code.
       LOOP AT  t_changed_objects  INTO   wa_changed_objects .
        CASE  wa_changed_objects-infty.
          WHEN '9002'.
            wa_cp_data-tabname = 'HROBJINFTY'.
            wa_changed_objects-plvar = '01' .
            wa_cp_data-tabkey  = wa_changed_objects .
            wa_cp_data-cdchgid = 'U'.
    *  wa_cp_data-CDOBJCL = 'HRMD_A'.
            APPEND wa_cp_data TO t_cp_data1 .
        ENDCASE.
      ENDLOOP.
      IF t_cp_data1 IS NOT INITIAL .
        CALL FUNCTION 'CHANGE_POINTERS_CREATE_DIRECT'
          EXPORTING
            message_type          = 'HRMD_A'
          TABLES
            t_cp_data             = t_cp_data1
          EXCEPTIONS
            number_range_problems = 1
            OTHERS                = 2.
        IF sy-subrc <> 0.
    * Implement suitable error handling here
        ENDIF.
      ENDIF.
    This code will create entry in BDCP2 table.
    After thsi populating segemnet you need to code for below exit as .
    EXIT_SAPLRHAL_003
       IF PNNNN_NAME = 'P9002' .
    *FIELD-SYMBOLS: <FS_plog> TYPE ANY.   "Field Symbol for dynamic filling of data based on the structure
    *Clearing the SUBRC
    CLEAR SUBRC.
    * fill workarea for infotype with infotype-data
    ASSIGN pnnnn_data TO <FS_plog> CASTING TYPE P9002.
    LS_9002 = <FS_plog>.
    * move fields
    MOVE-CORRESPONDING LS_9002 TO LS_p9002.
    * fill IDoc-data with workarea for segmenttype
    ASSIGN sdata_data TO <FS_plog> CASTING TYPE Z1P9002.
    <FS_plog> = LS_P9002.
    CONVERTED = ZCDP_IF_CONSTANTS_DTIRIS=>GC_CROSS .
    ENDIF.
    It will work fine.
    Thanks
    Anju

Maybe you are looking for

  • No signal using DVI cable from mac mini

    I have the dell 2007wfp monitor and I can't use the DVI cable I get the message No signal coming from your computer. then the display goes to sleep. It works OK with the DVI to VGA but everything is stretched and peoples faces look weird. I have a ma

  • COST CENTER AND PC BALANCES

    Hi all In which table balances(total) of the cost center and profit center's stored? Regards Hari

  • PDF layer structure in Illustrator

    I have saved a mapinfo drawing with geographic info to a pdf. The layer structure in the PDF is what I expected and reflects the layer structure in mapinfo.  When I open the pdf file in Illustrator howver I only get one layer. Is there any way of kee

  • Database Check Inconsistency

    Hi All, I have added a field to the standard table NAST. I have activated it. But When i go to the Utilities -> Database Object -> check I am getting the following error The database object is not consistent:    (Fields, Primary index) folowed by the

  • Since I upgraded my IPad to iOS 5, I lost all my ebooks and all the music I had in the IPod. How can I recover them? I need urgent help.

    After my upgrade to iOS 5, all downloaded ebooks disappeared from my IPad. All the music in the IPod are also lost. I cannot turn on location services. What can I do to restore these items? Amechy