Error generating IDOC (Transaction F110) - Segment E1IDIBA is blank

Hi experts,
I'm facing a problem here when trying to generate an IDOC through F110.
I'm using PEXR2003 that needs to be sent to a German Bank.
On this IDOC Type (which was never used before on this company) I need the new fields (updated from PEX2002) to be filled up.
The segment that I need the informations to be filled up is E1IDIBA (IBAN and SWIFT-Code).
Does anybody know how I can get this segment filled?
I've been stuck on this point for 2 days!
Thank you very much!

EXIT_SAPLIEDP_902 is the user exit to add/modify segments in PEXR2003 IDoc, if the contents differs for each payment document number processed in the IDoc. This user exit is called at the end of processing for each payment document. We use it in our company for manipulating the PAYEXT IDoc before it is sent to the banks for clearing the payment to our vendors.
To debug this user exit, you need to set and save the parameters and/or payment proposal in F110 but should not actually run it, if you want your breakpoints to be hit.
Put your breakpoint and run the program RFFOEDI1 with the payment run date and identification saved in F110 through SE38.
If the above exit is not what you are looking for there are two other user exits  EXIT_SAPLIEDP_901 and EXIT_SAPLIEDP_903, which are called at the beginning and end of processing for each bank (i.e., EDI partner)
Regards,
Vishnu Tallapragada

Similar Messages

  • EDI: Syntax error in IDoc (mandatory group/segment missing)

    hi EDI/IDoc experts,
    Need you help urgently. According to the requirement, i need populate a segement  E1IDT01 of basic type PEXR2002 . I added the code , then run and generate an idoc , the new segment
    E1IDT01  was populated,  but Syntax error 26 happend. Error message as below.   It also strange that i can see E1IDKU5 populate out as usual, but some others segment disappeared , i am sure that in my code ,i didn't changed any variable related to other segement . how can i fix this problem?
    EDI: Syntax error in IDoc (mandatory group missing)
    Message no. E0079
    Diagnosis
    The segment group E1IDKU5 has the attribute 'Mandatory' in the syntax description of the basic type PEXR2002 (customer enhancement ). However, the segment group is missing in the IDoc. The segment number logged in the status record identifies the item before which the segment group is missing.
    Procedure
    Please check the IDoc or the syntax description of the basic type PEXR2002 (customer enhancement ).

    Hi all,
    Thanks so much for your concern!
    Finally ,this problem has been figured out  .
    Requirement is user want to use segment E1IDT01 in idoc to populate the long text they maintained in accounting document vendor item line (use FB01 to create accounting doc).
    Why I made out " EDI: Syntax error in IDoc (mandatory group/segment missing)" this message out ,because  I didn't fill data correctly. I missed to keep SY-TABIX in momory .
    when we use Function module ,or do..enddo...or read table it_table. we should be careful that SY-TABIX  is changed .So we can't just use MODIFY EDIDD_TABLE INDEX  SY-TABIX  in the last . we should define a local variable to keep  SY-TABIX  in memory and then use it to modify EDIDD_TABLE. 
    Follow is the final code.
    IF SEGMENT_NAME = 'E1IDT01'.
    TABLES :STXL.
    * Define for long text getting
      DATA: LIT_TLINE  LIKE TLINE   OCCURS 0 WITH HEADER LINE.
      DATA: LV_STRING(2000)  TYPE C.                          
      DATA: LV_TDNAME TYPE THEAD-TDNAME,
            LV_ID     TYPE THEAD-TDID     VALUE '0001',
            LV_LANG   TYPE THEAD-TDSPRAS  VALUE 'E' ,
            LV_OBJ    TYPE THEAD-TDOBJECT VALUE 'DOC_ITEM'.
    data:   LV_LINE   TYPE I,                " long Text lines
            LV_LEN    TYPE I,                " long Text length   
            LV_TABIX  LIKE SY-TABIX.                              
    * Clear memory
      CLEAR:LV_TDNAME,
            LV_STRING,                                        
            LV_LINE,                                           
            LIT_TLINE, LIT_TLINE[],                          
            LV_LEN,                                            
            LV_TABIX.                                        
    * Keep sy-tabix memory using a variable--This is the key point
      LV_TABIX = SY-TABIX.
    * Combine TDNAME with company code + accounting doc + fiscal year + item number.
        CONCATENATE  REGUP_DATA-BUKRS REGUP_DATA-BELNR
                     REGUP_DATA-GJAHR REGUP_DATA-BUZEI INTO  LV_TDNAME.
    * When vendor item has long text , read long text into lv_string
        SELECT SINGLE *
          FROM STXL
          WHERE TDOBJECT = LV_OBJ
            AND TDNAME   = LV_TDNAME
            AND TDID     = LV_ID
            AND TDSPRAS  = 'E'.
        IF SY-SUBRC = 0.
          CALL FUNCTION 'READ_TEXT'
            EXPORTING
              CLIENT   = SY-MANDT
              ID       = LV_ID
              LANGUAGE = LV_LANG
              NAME     = LV_TDNAME
              OBJECT   = LV_OBJ
            TABLES
              LINES    = LIT_TLINE.
          IF NOT LIT_TLINE[] IS INITIAL.
            DESCRIBE  TABLE LIT_TLINE LINES LV_LINE.
            DO LV_LINE TIMES.
              READ TABLE LIT_TLINE INDEX SY-INDEX.
              CONCATENATE LV_STRING LIT_TLINE-TDLINE INTO LV_STRING.
            ENDDO.
            LV_LEN = STRLEN( LV_STRING ).
    * Make sure we only need  less than 840 charicters
            IF LV_LEN > 840.
              LV_STRING = LV_STRING+0(840).
              LV_LEN    = 840.
            ENDIF.
    * Populate Vendor item long text with segment E1IDT01 start from
    * Fields TXT03 to TXT14.
             EDIDD_TABLE-SDATA+147(LV_LEN) = LV_STRING.
            MODIFY EDIDD_TABLE INDEX LV_TABIX.
          ENDIF.
        ENDIF.
      ENDIF.

  • Update termination error SAPSQL_ARRAY_INSERT_DUPREC with transaction f110

    Hi ,
      When we executed the transaction F110 for payment runs it gave an update termination error "Express document 'update was terminated' ".
    Update was terminated
    Error Info  00671: ABAP/4 Processor : SAPSQL_ARRAY_INSERT_DUPREC
    Could you please anyone suggest me how to overcome this express document error.
    Thanks,
    Saran

    Hi,
    I think u r getting this exception as ur trying to INSERt a record which ia already existing, so try to change the data and Run the tcode.
    Revert back if any issues,
    Reward with points if helpful ,
    Regards,
    Naveen

  • Error in generating IDoc from F110

    Hi All,
    Please help me in solving this error, I am strucked in generating I-Doc. from Payment Program (F110).  After running the APP program successfully, I am getting the following message:
    Payment by EDI /  IDoc generation----
    "IDocs were generated for the followings entries.
    Company Code: XXXX, House BankXXXX, Payment Method X.
    IDoc type could not be determined for the IDoc...."
    Though message says IDoc is generated, but not seen anywhere. I have checked in WE02 (I Doc List)
    Here apart from the basic settings for running the APP like, House Banks, bank determinations etc.,
    1. I have maintained----
    EDI Partner Profiles in FI12 and WE20 with partner Type-B.
    2. In OBVCU, Payment Methods/Country: I have done the followings settings to the payment methods---C & T ; Under "C"----Under Payment medium: I have selected Classic Payment Medium Programs: RFFOEDI1  and the same settings in "T" also.
    3. In OBVU, Payment Method in Company code: Under "C": under Form Data: For Form for the Payment Medium: SAP Script and F110_EDI_01 and same for Next form. and the same settings for Payment Method "T".
    4. Maintained the required settings in the Vendor/Customer Master Data.
    5. Also maintained Variant in Printout/Data medium tab in F110
    Pls. let me know what are all the other settings which need to be done apart from the above,  Do we need to do the RFC settings also?
    Can somebody helpme in solving this issue?
    Regards,
    Aman

    Hi,
    The following details i have already maintained in the I Doc type under;
    Outbound parameters of WE20,
    1)Message Type: DRDEB, Receiver port: A000000043, Basic type under IDOC type: PEXR2002
    2)Message Type: EUPEXR, Receiver port: EUPEXPORT,Basic type under IDOC type: IDCREF01
    3)Message Type: PAYEXT, Receiver port: SUBSYSTEM, Basic type under IDOC type: PEXR2001
    4)Message Type: DRDEB, MESSAGE CODE: IHC, MESSAGE FUNCTION: IHC, Receiver port: A000000043, Basic type under IDOC type: PEXR2002
    Inbound parameters:
    Message Type: FINSTA,  PROCESS CODE: FINS
    Plz. let me know if i missed out anything.
    regards,
    Aman

  • IDOC Status 26: EDI: Syntax error in IDoc (segment cannot be identified).

    Hi All,
    I have created IDOC extension for IDOC Basic type "PROACT01" and have followed all required necessary steps but getting IDOC
    Status 26. EDI: Syntax error in IDoc (segment cannot be identified). The exact error is:
    Please check Error Details and the details of the steps I followed for Setting up IDOC Extension:
    Error Detail :
    EDI: Syntax error in IDoc (segment cannot be identified)
    Message no. E0078
    Diagnosis
    The segment ZPROSEG does not occur at the current level of the basic type PROACT01 (extension PROACTEX).
    This error can have several reasons:
    The segment ZPROSEG is assigned to a group whose header segment does not occur.
    The segment ZPROSEG does not exist in the syntax description of the basic type PROACT01 (extension PROACTEX).
    The sequence of segments in the group in which the segment appears is incorrect.
    Previous errors ('mandatory' segment or group missing) may be due to this error.
    Procedure
    Please check the IDoc or the syntax description of the basic type PROACT01 (extension PROACTEX).
    Can you please look at this problem and suggest what is wrong with IDOC Extension/Custome Segment?
    Below is the Details of the Steps which I have followed:
    1. Tcode WE31 - Created new custom Segment ZPROSEG with 4 fields. Released segment.
    2. TCode WE30 - Created IDOC Extension PROACTEX for Basic Type PROACT01. Released IDOC extension.
         Here when I run syntax check warning appears "No predecessors exist".  I am not sure if its okay!!
    3. TCode WE82 - Added Extension PROACTEX in the Message Type PROACT with BASIC Type PROACT01.
    4. TCode WE20 - Added IDOC Extension PROACTEX in the predefined partner profile in WE20 transaction.
    5. Added the following code in the Customer Exit EXIT_SAPLWVMI_001 include ZXWVMIU01 .
    DATA segnam(27).
    READ TABLE dedidd WITH KEY segnam = 'ZPROSEG'.
    IF sy-subrc NE 0.
    LOOP AT dedidd WHERE segnam = 'E1EDP31'.
    CLEAR dedidd.
    dedidd-segnam = 'ZPROSEG'.
    zproseg-matnr = 'Mat1'.
    zproseg-lgort = '001'.
    zproseg-gernr = 'SNo1'.
    zproseg-labst = 2.
    dedidd-sdata = zproseg.
    APPEND dedidd.
    ENDLOOP.
    ENDIF.
    Finally ran  transaction WVM2 (Transfer of Stock & Sales Data) to generate IDOC, its creating IDOC but when checked IDOC in WE05 its getting Status Error "26".
    Looking forward for your reply.
    Many thanks in advance.

    Hello,
    Actually you are appending the Z segment instead of inserting into the correct position. So the segment is added at the last, so hierarchy of segments is collapsed.
    So get the index of the previous segment E1EDP31 and increase the index by 1 and INSERT the Z segment with that new index as below.
    LOOP AT dedidd WHERE segnam = 'E1EDP31'.
    lv_index = sy-tabix. " <<--
    ADD 1 TO lv_index. " <<--
    CLEAR dedidd.
    dedidd-segnam = 'ZPROSEG'.
    zproseg-matnr = 'Mat1'.
    zproseg-lgort = '001'.
    zproseg-gernr = 'SNo1'.
    zproseg-labst = 2.
    dedidd-sdata = zproseg.
    *APPEND dedidd.
    INSERT dedidd INDEX lv_index. " <<---
    ENDLOOP.
    Here actually we are insering the record inside the LOOP and it regenerates the index again. It is not actually a good practice.
    So the best practice is get the index and generate the segment inside the loop, store them into another internal table, come out the loop and insert the Z segments into DEDIDD by looping the new internal table.

  • Error in BDC of F110 transaction?

    Hi,
    I am getting an error during the execution of the BDC in foreground Mode which is  "Field F110O-XPOS1(7) doesnot exist in the screen SAPF110O1003".
    This appears when i am trying to edit a payment proposal using BDC .
    Codes used in the main program are :
    PERFORM F4312_BDC_FIELD  USING 'BDC_CURSOR' 'F110O-XPOS1(07)'.
    PERFORM F4312_BDC_FIELD       USING 'BDC_OKCODE'     '=PI'.
    PERFORM F4312_BDC_FIELD       USING 'F110O-ABPOS'     '1'.
    PERFORM F4312_BDC_FIELD       USING 'F110O-XPOS1(01)'     ''.
    PERFORM F4312_BDC_FIELD       USING 'F110O-XPOS1(07)'     'X'.
    Is it possible that the screen feild name has changed from server to server because these codes are copied from old server to new one?

    Hi,
    This is my sample code for F110 BDC: This is a automated process for which we have written code.
    REPORT YF110_SAMPLE .
    tables: lfa1,
            t001,
            t042z,
            varid.
    DATA: i_bdcdata LIKE bdcdata OCCURS 0 WITH HEADER LINE.
    DATA: messtab TYPE TABLE OF bdcmsgcoll WITH HEADER LINE.
    DATA: po_date LIKE sy-datum.
    DATA: p_next LIKE sy-datum.
    DATA: p_run1(10),po_date1(10), p_next1(10).
    DATA: ws_laufd LIKE reguh-laufd,
          ws_laufi LIKE reguh-laufi.
    data: p_dele value space.
    data: ws_lines.
    SELECTION-SCREEN: BEGIN OF BLOCK blk1 WITH FRAME.
    PARAMETERS: p_run LIKE sy-datum obligatory.
    SELECTION-SCREEN: END OF BLOCK blk1.
    selection-screen: begin of block blk2 with frame .
    parameters: p_runid like reguh-laufi obligatory,
                p_land1 like t005-land1 obligatory.
    *select-options: p_bukrs for t001-bukrs no intervals obligatory.
    parameters: p_bukrs like t001-bukrs obligatory.
    parameters:  p_hbkid like t012-hbkid ,
                p_hktid like t012k-hktid ,
                p_waers like tcurc-waers .
    *select-options: p_rzawe for t042z-zlsch no intervals obligatory,
                   p_fvari for varid-variant no intervals obligatory.
    parameters:  p_rzawe like t042z-zlsch obligatory,
                p_FVARI like varid-variant obligatory.
                        matchcode object zfvari1.
    selection-screen: end of block blk2.
    *SELECTION-SCREEN: BEGIN OF BLOCK blk3.
    *PARAMETERS: p_dele AS CHECKBOX ."modif id DE.
    *SELECTION-SCREEN: END OF BLOCK blk3.
    *at selection-screen output.
    loop at screen.
       if screen-group1 = 'A1'.
         screen-input = '1'.
         modify screen.
       endif.
       if screen-group1 = 'DE'.
         screen-active = '0'.
         modify screen.
       endif.
    endloop.
    start-of-selection.
      ws_laufd = p_run.
      po_date = sy-datum. "p_run .
      perform get_next_date using po_date
                            changing p_next.
    p_next = p_run + 30.
      CONCATENATE p_run4(2) p_run6(2) p_run+0(4) INTO p_run1
          SEPARATED BY '/'.
      CONCATENATE po_date4(2) po_date6(2) po_date+0(4) INTO po_date1
          SEPARATED BY '/'.
      CONCATENATE p_next4(2) p_next6(2) p_next+0(4) INTO p_next1
          SEPARATED BY '/'.
      REFRESH messtab.
      CLEAR messtab.
      IF p_dele <> 'X'.
       PERFORM bdc_data USING:
                            'X' 'SAPF110V' '0200',
                            ' ' 'BDC_CURSOR' 'F110V-LAUFI',
                            ' ' 'BDC_OKCODE' '=PAR',
                            ' ' 'F110V-LAUFD' p_run1,
                            ' ' 'F110V-LAUFI' p_runid,
                            'X' 'SAPF110V' '0200',
                            ' ' 'BDC_OKCODE' '=LOG',
                            ' ' 'BDC_CURSOR' 'F110V-VONKK',
                            ' ' 'F110C-BUDAT' po_date1,
                            ' ' 'F110C-GRDAT' po_date1,
                           ' ' 'F110V-VONKK' s_vendor-low,
                           ' ' 'F110V-BISKK' s_vendor-high,
                            ' ' 'F110V-BUKLS(01)' p_bukrs,
                            ' ' 'F110V-ZWELS(01)' p_rzawe,
                            ' ' 'F110V-NEDAT(01)' p_next1,
                            'X' 'SAPF110V' '0200',
                            ' ' 'BDC_OKCODE' '=PRI',
                            ' ' 'BDC_CURSOR' 'F110V-VONKK(01)',
                            ' ' 'F110V-XTRFA' 'X',
                            ' ' 'F110V-XTRZW' 'X',
                            ' ' 'F110V-XTRBL' 'X',
                           ' ' 'F110V-VONKK(01)' s_vendor-low,
                           ' ' 'F110V-BISKK(01)' s_vendor-high,
                            'X' 'SAPF110V' '0200',
                            ' ' 'BDC_OKCODE'  '=STA',
                            ' ' 'BDC_CURSOR' 'F110V-VARI1(03)',
                            ' ' 'F110V-VARI1(03)' p_fvari,
    "'ZFID0060RWA218',
                            'X' 'SAPLSPO1' '0100',
                            ' ' 'BDC_OKCODE' '=YES',
                            'X' 'SAPF110V' '0200',
                            ' ' 'BDC_OKCODE' '/EBCK'.
                           'X' 'SAPF110V' '0200',
                           ' ' 'BDC_OKCODE'  '=SICH',
                           'X' 'SAPF110V' '0200',
                           ' ' 'BDC_OKCODE' '/EBCK',
                           'X' 'SAPF110V' '0200',
                           ' ' 'BDC_OKCODE' '/EBCK'.
                           'X' 'SAPLSPO1' '0100',
                           ' ' 'BDC_OKCODE' '=YES'.
                           'X' 'SAPF110V' '0200',
                           ' ' 'BDC_CURSOR' 'F110V-LAUFD',
                           ' ' 'BDC_OKCODE' '=VOEX',
                           ' ' 'F110V-LAUFD' p_run1,
                           ' ' 'F110V-LAUFI' p_runid,
                           'X' 'SAPF110V' '1106',
                           ' ' 'BDC_CURSOR' 'F110V-STRDT',
                           ' ' 'BDC_OKCODE' '=EP',
                           ' ' 'F110V-STRDT' p_run1,
                           ' ' 'F110V-XSTRF' 'X',
                           ' ' 'F110V-STRZT' '00:00:00'.
        FREE MEMORY.
        CALL TRANSACTION 'F110' USING i_bdcdata MODE 'A'
                                                UPDATE 'S'
             MESSAGES INTO messtab.
    break-point.
        if sy-subrc = 0.
       CALL FUNCTION 'SCHEDULE_PAYMENT_PROPOSAL'
         EXPORTING
           i_laufd                 = p_run
           i_laufi                 = p_runid
          I_STRDT                 = sy-datum
          I_STRZT                 =
          I_XSTRF                 = 'X'
          I_BHOST                 =
          I_INKEY                 =
          I_PTYPE                 = 1
          I_CALLREP               =
          I_CALLVAR               =
        EXCEPTIONS
          STARTDATE_WRONG         = 1
          PARAMETERS_MISSED       = 2
          LOCK_FAILED             = 3
          JOB_OPEN_FAILED         = 4
          JOB_CLOSE_FAILED        = 5
          OTHERS                  = 6 .
       IF sy-subrc <> 0.
            MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
                    WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
       ENDIF.
          write:/ 'Proposal Successfully Generated..'.
           refresh i_bdcdata. clear i_bdcdata.
            perform bdc_data      using: 'X' 'SAPF110V' '0200',
                              ' ' 'BDC_CURSOR' 'F110V-LAUFD',
                              ' ' 'BDC_OKCODE' '=ZAEX',
                              ' ' 'F110V-LAUFD' p_run1,
                              ' ' 'F110V-LAUFI' p_runid,
                              'X' 'SAPLSPO1'   '0100',
                              ' ' 'BDC_OKCODE' '=YES',
                              'X' 'SAPF110V' '1106',
                              ' ' 'BDC_CURSOR' 'F110V-XSTRF',
                              ' ' 'BDC_OKCODE' '=EP',
                              ' ' 'F110V-STRDT' p_run1,
                              ' ' 'F110V-XSTRF' 'X',
                              ' ' 'F110V-STRZT' '00:00:00',
                              ' ' 'F110V-XMITD' 'X'.
    break-point.
          CALL TRANSACTION 'F110' USING i_bdcdata MODE 'A'
                                                UPDATE 'S'
             MESSAGES INTO messtab.
          if sy-subrc = 0.
              write:/ 'Payment Run Scheduled'.
          endif.
        endif.
       endloop.
        SELECT single laufd laufi INTO (ws_laufd,ws_laufi) FROM reguh
          WHERE laufd = p_run
            AND laufi = p_runid
            AND xvorl = 'X'.
          IF sy-subrc <> 0.
            WRITE:/ 'Error in Proposal Run',p_runid,' dated ',p_run.
          ENDIF.
        ELSE.
            CALL FUNCTION 'DELETE_PAYMENT_PROPOSAL'
              EXPORTING
                date                      = p_run
                identification            = p_runid
              I_DATUM                   =
             EXCEPTIONS
               ABNORMAL_END              = 1
               NO_DELETE_AUTHORITY       = 2
               OTHERS                    = 3
            if sy-subrc = 0.
              write:/ 'Proposal ',p_runid, ' Successfully deleted.'.
            endif.
        ENDIF.
    Form
    FORM bdc_data USING    a
                           b
                           c.
      CLEAR: i_bdcdata.
      IF a = 'X'.
        i_bdcdata-program = b.
        i_bdcdata-dynpro =  c.
        i_bdcdata-dynbegin = 'X'.
      ELSE.
        i_bdcdata-fnam = b.
        i_bdcdata-fval = c.
      ENDIF.
      APPEND: i_bdcdata.
    ENDFORM.
    *&      Form  get_next_date
    FORM get_next_date USING    PO_DATE
                       CHANGING P_NEXT.
        data: i type i,
              p_date like sy-datum.
        i = 0.
        p_date = po_date.
        while i <= 4.
          p_date = p_date + 1.
          CALL FUNCTION 'DATE_CHECK_WORKINGDAY'
            EXPORTING
              DATE                             = p_date
              FACTORY_CALENDAR_ID              = 'WY'
              MESSAGE_TYPE                     = 'E'
           EXCEPTIONS
             DATE_AFTER_RANGE                 = 1
             DATE_BEFORE_RANGE                = 2
             DATE_INVALID                     = 3
             DATE_NO_WORKINGDAY               = 4
             FACTORY_CALENDAR_NOT_FOUND       = 5
             MESSAGE_TYPE_INVALID             = 6
             OTHERS                           = 7  .
          IF SY-SUBRC <> 0.
            continue.
          else.
            i = i + 1.
          ENDIF.
        endwhile.
        p_next = p_date.
    ENDFORM.                    " get_next_date
    Regards
    Subramanian

  • EDI: Syntax error in IDoc (too many repetitions of a segment)

    Hi All -
       We are getting an "EDI: Syntax error in IDoc (too many repetitions of a segment)" error message while processing the REMADV message in the payment run program.
    Basic Type : PEXR2002
    Message Type : REMADV
    Segment Name : E1EDP02
    This issue is due to BELNR length in above segment, since payment run program assigning the 45 chars but BELNR length is 35 char, is there any way or OSS notes we can implement to rectify the same.
    Thanks in Advance.
    Rds,
    K

    Hi,
    This error is the segment definition violation. Open your BASIC IDOC type in WE30, double click on the segment TESTIDOC.
    In the popup you can see properties like mandatory segment, Minimum number and Max number. Your IDOC is crossing the max number of repetitions it can have. If any of the segment definition perperties like this one, or improper position of the segment etc occurs IDOC is generated with syntax error.
    Thanks,
    Vinod.

  • User exit , transaction F110, an outbound Idoc

    Hi,
    During the payment process in transaction F110, an IDOC is generated.  I need to identify the user exit within the IDOC build process to do some special processing.
    The special process is to ‘substitute’ the POSTING DATE on the IDOC with the “NEXT PAYMENT DATE” from the proposal.
    Regards,
    Jyoti Shankar

    Hi Joyti,
    I have requirement to trigger outbound IDOC after generating payment document....as your reply i think you already did this requirenment.
    Kindly help how to configure outbound IDOC for this............
    Plse reply me soon....
    Thanks.

  • Payment program F110 not generating IDoc

    Hi All
    while running payment program F110 I get a sucess message IDocs generated for company code and payment method, In the payment log i see this infomation.
    when i check these IDoc's in WE02 I can't find any of these IDoc's. It looks to me the program RFFOEDI1 with the variant I created is not getting executed in spite of the check box "Generate IDoc" being checked.
    can any one suggest what would be wrong?
    Thanks
    Pranav

    Hi All,
    Thanks for the quick response. Following are the config made with forms;
    In Paying company code setup:
        Form for payment adivce: F110_US_AVIS
        EDI accompanying sheet form: F110_EDI_01
    In Payment method in company code:
        Form for payment medium : F110_EDI_01
        Next form : F110_US_DTA
    I have checked with all other configuration and seems to be in place. Please let me know if these config regarding forms are correct.
    When I run the program REFFOEDI1 with the variant I created these IDocs are getting generated. These are not getting generated when I run the payment program F110. I am missing some thing which is not triggering this program from payment program. Please let me know if you have any suggestion.
    Thanks
    Pranav

  • Syntax error in IDoc (too many repetitions of a segment)

    Hi,
    I tried to load master data from R/3 into BW system. The load is not ending and the IDoc error message is displaying,
    The error message is " EDI: Syntax error in IDoc (too many repetitions of a segment) with status 26"  .
    I tried to analise the issue and checked in the Idoc List Outbox of BW system. I found Red status message with number 26 stating " Error during Syntax check of IDoc (Outbound) and the message type is RSRQST.
    Could any one help me out in solving this problem. Reply to the message if any more information needed.
    Thanks in Advance.
    Regards
    Koushik

    I'm getting the same error. I think it is because I have a InfoPackage selection routine, that selects more than 1000 select conditions. I guess it is a parameter that needs to be changed somewhere. Any help on this one?
    BR
    Øyvind

  • Idoc Error - EDI: Syntax error in IDoc (segment cannot be identified)

    Hi All,
    have created a new reduced message type for our new vendor A/C group through BD53. Also done reqd config for sending the vendor master through this message type. .
    I have created couple of vendors for testing with X01 with withholding tax functionality and when try to send these vendors , Idocs are getting failed .
    When I create vendor without withholding tax functionality , idoc is getting posted succesfully . If create vendor with entries in the feild whih are related to withholding tax  . Idocs are getting failed .
    If I see the status in WE05 ,Idocs which are posted succefully are showing the basic type as CREMAS03 . For idocs which are getting failed have the basic type as CREMAS04 and also the extension  as Z1CREMAS . I don`t understand why the system is defaulting CREMA04 & Z1CREMAS when I send the vendor master with withholding tax feild entries.
    I am not much familiar with ALE /Idoc set up. Please can any body help me to resolve the issue.
    The error message in we05 as below
    EDI: Syntax error in IDoc (segment cannot be identified)
    Message no. E0078
    Diagnosis
    The segment Z1LFA1M does not occur at the current level of the basic type CREMAS04 (extension Z1CREMAS).
    This error can have several reasons:
    The segment Z1LFA1M is assigned to a group whose header segment does not occur.
    The segment Z1LFA1M does not exist in the syntax description of the basic type CREMAS04 (extension Z1CREMAS).
    The sequence of segments in the group in which the segment appears is incorrect.
    Previous errors ('mandatory' segment or group missing) may be due to this error.
    Procedure
    Please check the IDoc or the syntax description of the basic type CREMAS04 (extension Z1CREMAS).
    Thanks

    Hi,
    I don`t understand what do you mean release after adding segment.
    Message type works i.e. Idoc get posted if I send with the  vendor w/o withholding tax field entries. Idoc fails when send vendor with withholding tax field entry.
    Regards

  • Issue:EDI: Syntax error in IDoc (mandatory segment missing):Idoc extention

    Hi all,
    I have extended the the standard IDOC MATMAS05  classification view with structure as below-
    E1MARAM                        Master material general data (MARA)--->Mandatory segment
         Z1KLART                        KLART --->Extended chaild to E1MARAM
             Z1CLASS                        segment for class --->Extended chaild to Z1KLART
             Z1CHARACTERISTIC               CHARACTERISTIC --->Extended chaild to Z1KLART
         E1MARA1                        Additional Fields for E1MARAM
         E1MAKTM                        Master material short texts (MAKT) --->Mandatory segment(Child   to                                                                               
    E1MARAM )
    I am getting an error in IDOC fro material master as:EDI: Syntax error in IDoc (mandatory segment missing ).
    Diagnosys By system is :*The segment E1MAKTM has the attribute 'Mandatory' in the syntax description of the basic type MATMAS05 (customer enhancement ZMATMAS05). However, the segment is missing in the IDoc. The segment number logged in the status record identifies the item before which the segment is missing.
    This error may have been triggered by an unidentifiable segment before the expected mandatory segment.*
    Please help to resolve the issue.
    Thank you.
    Edited by: sanu debu on Apr 30, 2009 11:25 AM
    Edited by: sanu debu on Apr 30, 2009 11:31 AM

    Hi,
       You cannot add an segment in the middle of other segments.
    YOu have to add any segment at the last.
    If you want to add a segment as the child of another segment, it should be added after the last child of the parent segment.
    In you case, you have to add your segment after the E1CUCFG segment.(NOt under that segement)
    Regards,
    Ravi Kanth Talagana

  • Error in IDOC: XML IDoc conversion: No known segments identified

    Hi Team
    i am facing error in my scenario.  When we are testing my  interface, another  Interface is picking up the Messages and resulting into an error.
    There is no mapping involved in my scenario.
      <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    - <!--  Call Adapter
      -->
    - <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
      <SAP:Category>XIAdapter</SAP:Category>
      <SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_IDOC_RUNTIME</SAP:Code>
      <SAP:P1>XML IDoc conversion: No known segments identified</SAP:P1>
      <SAP:P2 />
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText />
      <SAP:Stack>Error: XML IDoc conversion: No known segments identified</SAP:Stack>
      <SAP:Retry>M</SAP:Retry>
      </SAP:Error>
    please help me out
    thanx in advance

    Hi,
      Do The following:
    1) Delete the IDX2 entry and try to reimport once again....and in the IR also do the same.
    2) Have a look into this SAP Note- 742093
    3) Check the IDX1 entry , RFC destination entry... may be not pointing correctly.
    4) If any field which is mandatory in the idoc must not be disabled...take care about it.
    Hope this will help you...
    Regds,
    Pinangshuk.

  • Error importing Idoc - Unable to read segments

    Hi experts,
    I have some problems importing a custom built IDoc in IR.
    The error I got was:
    ZPATINFO_IDTY.ZPATINFO: Error
    +Error: IDoc type ZPATINFO contains error (unable to read segments)
    Import failed with 1 error.
    I've tried to import standard IDocs and they were successful.
    I tried to import the metadata in IDX2, and was successful. A popup saying "unable to read segment versions" but i could still see the structure in IDX2.
    I've added roles to my user:
    SAP_BC_MID_ALE_DEVELOPER
    SAP_BC_MID_ALE_IDOC_ADMIN
    SAP_BC_MID_ALE_IDOC_DEVELOPER
    Please help.
    Thanks!
    Ron

    First of all check if you have the proper authorizations;
    From Note: 837595
    Authorization object S_RFC
    Field name RFC_TYPE value FUGR
    Field name RFC_NAME value EDIMEXT, SDTX
    Field name ACTVT    value 16
    Authorization object S_IDOCDEFT
    Field name ACTVT   value 03
    Field name EDI_CIM value ' '
    Field name EDI_DOC value TXTRAW01
    Field name EDI_TCD value WE30
    Authorization object S_CTS_ADMI
    Field name CTS_ADMFCT  value TABL
    Authorization object S_TABU_DIS
    Field name ACTVT      value 03
    Field name DICBERCLS  value
    Then check if the idoc and its segments have been released in R3.

  • EDI: Syntax error in IDoc (segment cannot be identified)

    Hi All,
    Im facing the below error EDI: Syntax error in IDoc (segment cannot be identified).
    And this error is coming only for few idocs rest are getting processed successfully.
    Message no. E0078
    Diagnosis
    The segment E1EDP03 does not occur at the current level of the basic type ORDERS05 (extension ).
    This error can have several reasons:
    The segment E1EDP03 is assigned to a group whose header segment does not occur.
    The segment E1EDP03 does not exist in the syntax description of the basic type ORDERS05 (extension ).
    The sequence of segments in the group in which the segment appears is incorrect.
    Previous errors ('mandatory' segment or group missing) may be due to this error.
    Procedure
    Please check the IDoc or the syntax description of the basic type ORDERS05 (extension ).
    Please suugest.
    Thanks,
    Spandana

    Hi,
    Is this standard program or custom program?
    you might be appending the Z segment instead of inserting it. Always best practice is get the index of the segment and instert it.
    If all the data is not populated then segment position will change incase of appending. Please check your code and revert back.
    Refer the below link for detailed information.
    IDOC Status 26: EDI: Syntax error in IDoc (segment cannot be identified).
    Thank you

Maybe you are looking for