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

Similar Messages

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

    HI all,
    Error Message - EDI: Syntax error in IDoc (mandatory segment missing)
    Status ID - E0
    Message No - 072
    Status of the IDoc - 26
    Please help me how to solve this issue?
    Thanks,
    Srini

    Hi,
    This error normally comes up when the sequence of segments has been disturbed.
    For successfully posting an IDOC you need to maintain the sequence of the segments as in WE30.
    You can also check which segments are mandatory in WE30 by clicking on the segment name and the pop up that comes.
    Thanks,
    Manish

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

  • 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

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

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

  • 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

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

    Hi,
    My requirement is that I was adding two diffrent field values under two diffrent segments as "E1EDKA1" and "E1EDK02" in outbound invoice IDOCS, INVOIC02 (process code: SD09 - IDOC_OUTPUT_INVOIC).
    I am getting the IDOC number through Tcode "VF02". Can any body give me idea how to check that syntax error in debug mode.
    Please find the following error details using TCODE "WE02".
    *EDI: Syntax error in IDoc (segment cannot be identified)*
    *Message no. E0 078*
    *Diagnosis*
    *The segment E1EDKA1 does not occur at the current level of the basic type INVOIC02 (extension ).*
    *This error can have several reasons:*
    *The segment E1EDKA1 is assigned to a group whose header segment does not occur.*
    *The segment E1EDKA1 does not exist in the syntax description of the basic type INVOIC02 (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.*
    Please help me to resolve this problem. <REMOVED BY MODERATOR>
    Regards,
    Skumar.
    Edited by: Alvaro Tejada Galindo on Apr 28, 2008 1:09 PM

    It seems that you added segment E1EDKA1 at a place where it is not supposed to be. That's where this error is coming from. The structure of every IDOC is definded by SAP standard and you cannot change the sequence or the level of standard segments. If you require a certain field at a certain level you have to add that field to a Z-segment and then add that Z-segment where appropriate in your extension.
    Hope that helps,
    Michael

  • Error CL_TAO_GUI_SESSION_SM- Create: Mandatory Attribute missing for Technical RFC destination

    hai
    We have installed solution manager and CBTA for test automation. For SUT , We have created Technical RFC for development client and quality client
    as TST_BID_CLNT220 and TST_BID_CLNT_909 respectively.  Similarly SMBID_CLNT_220 and SMBIQ_CLNT_909 are the business RFC destination to connect SUT.
    Now I have created test System data container which have both target system (Quality and development) . I have also created Test profile
    for both . In the Test Profile I have mentioned Techinical RFC name , Test profile name, business user and password.
    I have record va01 tcode in development client. The same script is used for quality also .
    I am able to execute the script in development . But when I execute for quality it is giving following error
    Error CL_TAO_GUI_SESSION_SM->Create: Mandatory Attribute missing for Technical RFC destination TST_BIQ_CLNT909
    Can any one help me . Pls tell me whether I followed the steps correctly
    Regards
    Jaya

    Hi,
    It will be very difficult to solve without being on the customer site and having all information.
    Right now, the error code is network error...
    Kind regards,
    Yann

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

    Hi Idoc Experts !
    The error pasted in subject is what i'm getting when i'm calling function module MASTER_IDOC_DISTRIBUTE.
    THE IDOC IS GETTING GENERATED BUT HAS SYNTAX ERRORS WITH STATUS/ERROR CODE :26.
    I'm tryin to generate an IDOC with following details:
    Direction         1     Outbox
    Current status    26
    Basic type        WMMBID02
    Extension
    Message type      WMMBXY
    Partner no.       XEROX
    Partn.Type        LS
    Port              170_INVRPT
    Can anyone be of some help?
    Points guaranteed for authentic answers !
    Thanks,
    Sachin Soni

    Hi,
    While passing the idoc data, you are not passing the mandatory segment and passing the child segment. Try to add the data for the mandatory segment.
    Check and find the mandatory segments on the IDoc through WE30 .And check if all this segments are populated in the IDoc which failed ( WE02).
    Regards,
    Soumya.

  • How to isolate error with a record/segment in IDOC with multiple records

    I have an IDOC with multiple records/segments (typically 1000 records/segments). Sometime XI can not process the IDOC because of some control characters in data.
    1. How can I pre-processed the IDOC to remove those control characters?
    Can I use XPATH expression/Java class to do it? How can I configure the XPATH expression/Java class in XI to pre-process the file?
    2. Until I have answer to 1st question. I would like to find out the error is exactly for which record? What configuration can I do in XI to isolate the error is with which record/segment in IDOC?
    Thanks in advance.

    Split the IDoc.
    with in the UDF, after the validations if every thing fine, pass as successful records to success_MT and pass it to target system using Branching in BPM.
    if errors found in the record, then store the error records in Hash table with in UDF, get the IDoc number, frame as a string and raise alert.
    U have to do this in the context of IDoc.
    If U wanna get the IDoc Number, Segment Name and field name for every failure, U can pass the expected error field name as constant to UDF, frame the sentence in the UDF like -> <b>IDoc 1234321 segment – SEG001 – field – FLD03 has a special character ‘*’</b>.
    If U wanna pass this string to source/target, U can do in error messages branch in BPM.
    U must use BPM for splitting the IDoc, since it is multi-mapping.
    reg.,
    Yallabandi.

  • Issues with itunes error -50, determining gapless playback, missing speaker options, home sharing not working

    In the last few weeks I have been experiencing multiple issues with my iTunes.
    I believe it began when my itunes library corrupted and I had to start again.
    By starting again I mean I went to previous itunes libraries and used the most recent backup.
    After I noticed a large number of unknown error (-50) messages I thought I better copy the backup I was using from the previous libraries folder over to the itunes folder (in case the error related to failed attempts to back up the library).
    This problem in itself wasn't too bad as I am able to close and relaunch iTunes and carry on however I have noticed some less desirable side effects - the loss of home sharing. I am unable to pick speakers to broadcast to (I have 2 airport express units plugged in and working and an Apple TV2) and I am unable to access the iTunes library on Apple TV.
    I've done some basic troubleshooting: creating rules to allow the home sharing ports, temporarily disabling antivirus/firewall, uninstalling antivirus/firewall, setting up rules on the router for homesharing ports, uninstalling iTunes, rebooting, reinstalling iTunes and retrying, disabling home sharing and reenabling, disabling peerblock, deauthorising itunes and reauthorising and rebooting both the pc and Apple TV, checking sharing settings under preferences and verifying both the entire library is shared and that the status of home sharing is on but no devices connected, created a new library and reimporting my media and the problem still exists.
    I noticed that occasionally when I switch between libraries, deauthorise and reauthorise I do get access to home sharing and Apple Tv gets full access to the library BUT iTunes quickly becomes unresponsive and when I close and relaunch Apple TV can no longer see my library or iTunes.
    I have checked the network I am running on is marked as a home network, I have tried connecting the Apple TV via LAN instead of WiFi but this makes no difference. What I do find interesting is that I have iTunes running on another pc and on a virtual machine and as soon as I run either their libraries appear on Apple TV so there must be something about the installation on my pc and nothing wrong with the Apple TV, airport express, router etc.
    With that in mind I retried an uninstall and this time deleted as many tmp files as I could see in the iTunes library folder, rebooted and reinstalled. I also checked the permission levels on the iTunes application folder and the iTunes library folder (located on an additional internal drive), I then tried running iTunes as an administrator (which my user account is already set as) but all the problems are still evident.
    The determining gapless playback has no effect on how I use iTunes but it clearly does not need to run for every single recently added track any time I make a minute change to other library entries. I tried looking up one of the files it was determining gapless playback for but it wasn't corrupt or read only so I don't see why it needs to retry continually.
    I'm running Windows 7 64bit with all latest updates installed and iTunes 64bit 10.6.3.25, all apple devices are running the latest version of firmware and I'm running out of ideas. I did try running CCleaner to clear up and registry issues if there were any and I ran Appcleaner to remove any iTunes cache that may have been left between installs. I'm running out of ideas - what am I missing here?

    I have found the problem was in part caused by Windows firewall.
    Exactly how Windows firewall can cause the problem when I wasn't even using it I don't know.
    What I do know is that when I checked 'allow a program through the firewall' I found 4 rules set for iTunes, one of which was public network access.
    I deleted the superfluous rules and the Home Sharing problems are solved.
    All that needs sorting now is the 'determining gapless playback'.

  • IDOC Syntax Error E0072 with status 26 after upgrade to ECC6.0

    Hi
    We have upgraded SAP R/3 from 4.6C to ECC6.0. After upgrade, when we create PO and output EDI, we are seeing this IDOC syntax error E0072 for Mandatory Segment E1EDK01. In 4.6C it was working fine with no issues, only after upgrade this problem started. It says E1EDK01 is missing which is mandatory. We are using basic type ORDERS01 with no extensions. When we see WE30 it looks fine, WE20 settings looks fine.
    Order of the segments got scrambled in upgraded version. First segment is E1EDP19001, this is supposed to be under E1EDP01 segment. There are two E1EDP19001 segments created but there were no sub segments to E1EDP01.
    Any help in this regard is highly appreciated.
    Thanks
    Pandiri

    User Exit activation and fixing the issue in user exit fixed this issue.

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

    Hi all,
    Im developing a interface for purchase/sales orders. i populated the fields into segments and am running the function module. it is creating an idoc with status 60
    EDI: Syntax error in IDoc (segment cannot be identified).
    I dont know which segment its not identifying..
    mesage type ZXXXXXX
    process code used orde
    fm idoc_input_orders.
    can somebody help me with this in trouble shooting
    thanks,
    Kiran

    Hi Vijay,
    this is the structure of edidc when i c it in we19..dont know how to clear this error.
    EDIDC   2000000000000404101620 60        2SAPSD1    LSSD1CLNT200                                                                               
    E1EDK01                                                           
           E1EDK14                     0081800                               
           E1EDK14                     00710                                 
           E1EDK14                     00610                                 
           E1EDK14                     012ZOR                                
           E1EDK14                     019OMY                                
           E1EDK03                     00220040809                           
           E1EDK03                     02200000000                           
           E1EDK03                     02300000000                           
           E1EDKA1                     AG 0002200253                         
           E1EDKA1                     VE 00000096                           
           E1EDK02                     001CUSTPONOTEST1                      
           E1EDK02                     044J0000000143                        
        4  E1EDKT1                     Z004I    VBBK                         
        4  E1EDKT1                     Z002I    VBBK                         
        4  E1EDP01                     000001     0000000010     PCE         
           E1EDL44                     1                                     
    this is the erro message im getting..
    The segment E1EDL44 does not occur at the current level of the basic type ORDERS05 (extension ).
    This error can have several reasons:
    The segment E1EDL44 is assigned to a group whose header segment does not occur.
    The segment E1EDL44 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 ).
    thanks..

Maybe you are looking for