Error in Idoc with status 26

Hi,
IDOC  showing an error messge when syntex check.
EDI: Syntax error in IDoc (segment cannot be identified)
Diagnosis:
The segment E1EDP19 does not occur at the current level of the basic type ORDERS01 (extension ).
This error can have several reasons:
The segment E1EDP19 is assigned to a group whose header segment does not occur.
The segment E1EDP19 does not exist in the syntax description of the basic type ORDERS01 (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....
Regards,
Sudha

Hi,
I have pasted a portion of my code:
DATA: BEGIN OF GT_EDIDC OCCURS 0.
        INCLUDE STRUCTURE EDIDC.
DATA :END OF GT_EDIDC.
DATA: BEGIN OF GT_EDIDC1 OCCURS 0.
        INCLUDE STRUCTURE EDIDC.
DATA :END OF GT_EDIDC1.
DATA: BEGIN OF GT_EDIDD OCCURS 0.
        INCLUDE STRUCTURE EDIDD.
DATA :END OF GT_EDIDD.
DATA : BEGIN OF GT_Z1ZPSOBJLOC OCCURS 0.
        INCLUDE STRUCTURE Z1ZPSOBJLOC. ' segment name
DATA : END OF GT_Z1ZPSOBJLOC.
* Control Record
FORM BUILD_CONTROL_RECORD .
  GT_EDIDC-MESTYP = C_MESTYP.
  GT_EDIDC-IDOCTP = C_IDOCTP.
  GT_EDIDC-DIRECT = C_1.
  APPEND GT_EDIDC.
ENDFORM.                    " built_control_record
*&      Form  built_data_record
* Data record
FORM BUILD_DATA_RECORD .
  LOOP AT GT_Z1ZPSOBJLOC INTO WA_Z1ZPSOBJLOC.
    GT_EDIDD-MANDT = SY-MANDT.
    GT_EDIDD-SEGNAM = C_SEG.
    GT_EDIDD-SDATA = WA_Z1ZPSOBJLOC.
    APPEND GT_EDIDD .
  PERFORM DISTRIBUTE_DATA.
  ENDLOOP.
ENDFORM.                    " built_data_record
*&      Form  distribute_data
* Distribute Data
FORM DISTRIBUTE_DATA .
  CALL FUNCTION 'MASTER_IDOC_DISTRIBUTE'
    EXPORTING
      MASTER_IDOC_CONTROL            = GT_EDIDC
    TABLES
      COMMUNICATION_IDOC_CONTROL     = GT_EDIDC1
      MASTER_IDOC_DATA               = GT_EDIDD
    EXCEPTIONS
      ERROR_IN_IDOC_CONTROL          = 1
      ERROR_WRITING_IDOC_STATUS      = 2
      ERROR_IN_IDOC_DATA             = 3
      SENDING_LOGICAL_SYSTEM_UNKNOWN = 4
      OTHERS                         = 5.
  CASE SY-SUBRC.
      WHEN 1.
      MESSAGE E004.
    WHEN 2.
      MESSAGE E005.
    WHEN 3.
      MESSAGE E006.
    WHEN 4.
      MESSAGE E007.
    WHEN 5.
      MESSAGE E008.
    WHEN OTHERS.
* Do Nothing
  ENDCASE.
  COMMIT WORK.
* Clear IDOC data internal table after use
  CLEAR GT_EDIDD.
  REFRESH GT_EDIDD.
ENDFORM.                    " distribute_data
Hope it proves useful.
Regards,
Gayathri

Similar Messages

  • Error in idoc with status 20 "Error triggering EDI Subsystem"

    Dear All,
    I have query related to IDOC Status 20.
    I am tirggering IDOC with standard t-code from IS-Retail system. I have created two ports a) TRFC port and b)File port .
    <b>We are having sending and receiveing application on two different OS i.e one XI on Windows and IS Retail on AIX(Unix). I am not able to send idoc to another system. I am getting these IDOC status in WE05 (STATUS 01 , 30 , 03 , 20 )</b>
    Keeping the above fatcs in mind could you please tell me how to remove the <b>error with status 20 "Error triggering EDI Subsystem".</b>

    Hi prabhat,
    You should have checked the automatic triggering possible at the file port level and the partner profile setting could be 'start subsytem'.
    Go to WE21 and do the access test for the file port.
    Once you done and find no issues then go to SM59 and test the connection for the RFC destination assigned to the ports.Possibly it has to do with the RFC destination.
    Other reasons could be yours is a test client and got refreshed recently.so the production client settings might be causing this error.Check with your basis to get it working.
    other reason could be the logical system assigned to the client should be having production client's name.
    Check these.
    I am sure you should be able to solve this issue.
    Thank you.
    regards,
    karun.M

  • ERROR IN IDOC WITH STATUS 51

    Hello Experts,
    I am facing a connectivity issue B/w Dev server
    i am getting data into BI dev from ECC dev.
    but when i am running the infopack the IDOC error status appearing in ECC dev with status 51  with error message text Incomplete control parameter for commmunication with the BW system appearing
    please suggest where to maintain the parameter and how to transfer  data

    earlier it was working fine than after that our basis guy did client copy activity on ECC Dev client and after that its not working.
    if i run infopack it shows 0 records and request turns red with below error
    Error when updating Idocs in Source System
    Diagnosis
    Errors have been reported in Source System during IDoc update:
    System Response
    Some IDocs have error status.
    Procedure
    Check the IDocs in Source System . You do this using the extraction monitor.
    when i am checking in WE02 the idocs are showing STATUS 51
    now i have activated Source system and i am authorised for all transactions
    but still facing the problemm

  • 5 IDOC with status 29 Error in ALE service

    hi there,
    im looking at this similar problem with less information on me the only info i got is this can anyone help me out pls
    IDOC Status Outbox:
    IDOC failure between 13/07/2008 to 14/07/2009
    1 IDOC with status 02 Error passing data to port
    5 IDOC with status 29 Error in ALE service
    IDOC Status InBox:
    88 IDOC with status 51 Application document not posted
    regards
    raju

    Hi,
    Check this thread.
    DB13-DBCHECK by saving log-throwing DUMP:TSV_TNEW_BLOCKS_NO_ROLL_MEMORY
    Regards.

  • "Error during application input" while processing IDOC with status 51

    Hi ,
    I tried to post an error IDOC with status "51" of message type FIDCC2 using program RBDINPUT, it just creates a message "Error during application input" . It is not calling the application dialog . Does anyone have answer for this?
    Thanks,
    Hemant.

    HI,
    Kindly check the RFC entries in t-code SM58.
    If any entries are their please release them manually selecting each one and press "F6".
    Regards,
    Anil.

  • Inbound Processing of Idocs with status other than success

    Hi,
           I am new to ALE/Idocs. Can anyone  please let me know how can I process the Idocs which have the status other than 53.
    Thanks &  Regards,
    Indira

    Hi,
    In addition to the previous posts few more programs to process failed inbound IDocs are as mentioned below.
    - Use program RBDAGAIE to process edited IDocs (IDocs with status 69)
    - Use program RBDAPP01 to process IDocs failing with serialization issue (IDocs with status 66)
    - Use program RBDAGAI2 to process IDocs after ALE inbound error (IDocs with status 56, 61, 63, 65)
    ~ Bineah

  • Idoc with status 32

    Hi
    In we05 transaction  i see one idoc with status 32.
    Status text was: idoc was edited
    T100 text was: change data record was saved..
    how to overcome this staus to post the idoc in target system??

    Hi,
        RBDAGAIE - Reprocessing of Edited IDocs .
        The above Standard program is for  Reprocessing Idoc's.Go through this program.So that u will rectify that error.
    Note: -  
          Description: This report reprocesses an edited IDoc in inbound or outbound processing. The edited IDoc has one of the following statuses:
    32: IDoc edited (outbound)
    69: IDoc edited (inbound).

  • Reprocessing IDOCS with status 52

    Hi all,
    I facing a problem with IDOC status 52.
    After correcting the error it had given, I want to reprocess it again.
    Kindly tell me any report or transaction name for reprocessing IDOC with status 52.
    Regards,
    Rahul

    Hi Rahul,
    You can use the below Programs for IDocs Reprocessing:
    RBDMANI2 : Reprocess Idocs manually
    RBDMANIN : Posting of IDocs with Status 51
    RBDMOIND : Outbound Idocs status 03->12
    RSEOUT00 : For Processing 30 Status IDocs
    RBDAPP01 : For Processing 64 Status IDocs
    RBDAGAIN : Reprocess Incorrect Outbound IDocs
    RBDAGAI2 : Reprocessing of IDocs after ALE Input Error
    Regards
    Aneesh.

  • Reprocess Idocs with status 3

    Hi ,
    I want to reprocess successful IDOCs with status 3 again,how can I do that?
    I think logically we can change the status other than 3 and use BD 87 to reprocess them?is this correct way?Idoc numbers would change or they would create new IDOCs?
    thank you,
    Babu

    Hi,
    You can use transaction BD87 to monitor the IDoc statuses.
    and use the following programs to reprocess outbound and inbound error IDoc(s).
    RBDAGAI2 - Re-processing of IDocs after ALE Input Error
    RBDAGAIE - Reprocessing of Edited IDocs
    RBDAGAIN - Process Outbound IDocs with Errors Again
    RBDAGAIP - New Posting of Partially Posted IDocs
    RBDMANI2 - Manual Processing of IDocs: Post IDocs Not Yet Posted
    RBDINPUT
    <b>Reward points</b>
    Regards

  • Performance issues in using RBDAPP01 for reprocessing iDocs with Status 64

    Hi All,
    I am using the Standard ABAP Program 'RBDAPP01' for reprocessing Inbound iDocs with Status 64 (Ready to be posted).
    When this is scheduled as a job in background, I find that it opens multiple sessions and occupies all available dialog sessions.
    This in turn slows down the entire system.
    Also, I find the addition 'Packet Size' on the selection screen for the program.
    Is it related in any way to the number of sessions the program creates?
    Any pointers in resolving this issue will be extremely helpful.
    Thanks in advance.
    Regards,
    Keerthi

    Hi,
    When you mention Parallel Processing, it becomes active only if I choose that particular option on the selection screen right?
    In my case, I haven't chosen parallel processing, but still the overall system performance seems to have fallen very badly.
    Now please correct me if my understanding is wrong.
    If I increase my Packet Size, it should improve the system performance, but will increase my runtime for the selected iDocs.
    But as I have not selected parallel processing in this current situatuon, it should not have any impact here.
    Have I summarized it rightly?
    Thanks in advance.
    Regards,
    Keerthi

  • Generate IDOC with status lanced (03)

    Hello,
    I need to generate IDOC with status lanced. I don't need program like RSEOUT00 but a module function.
    Thnx.

    Hello,
    In partner profile (WE20) Outbound options tab, select radiobutton 'Transfer IDOC Immediately'  in output mode. So IDOC created in status '30' will be passed onto port (03) immediately without you having to run the program RSEOUT00.
    Thanks,
    Venu

  • Splitter program for processing the IDOCS with status 64.

    Hello folks,
    I have a requirement explained below. I am looking for a sample code which could help me to jump start with initial development.
    Requirement:
    Develop a splitter program which retrieves all the IDCOS with status 64, create and schedule batch jobs with 200 IDOCS each. The splitter program with be scheduled every 15 min.
    Restrictions
    Only 150 batch jobs can be created at a time.
    Estimation
    There may be around 36000 IDOCS with status 64 every hour.

    Srinivas,
    Here is the explaination why we require a splitter program.
    Using RBDAPP01 parellel processing
    Let us assume there are 4 servers A, B, C and D in a server group. If we select RBDAPP01 parellel processing there will be too many RFC calls to the servergroup.
    (there are some more RFC calls later on for Order creation for example). As there is a restriction with number of RFC calls, we need to clear other RFC's before making new one. This is making complex and messy.
    Using RDBAPP01 serial processing
    For the volume of orders getting created each day, it takes a week to process those Idoca created in one day. Hence it is not a good solution.
    Splitter program
    We spawn 150 batch jobs with 200 records each. This way if we think it takes 20 min for each job to complete...by the end of 20th min we must had processed 30000 idocs.
    Hence it is the solution offered.
    Srinivas...still this confuses me..but if I am wrong anywhere please correct me.
    But your initial response has helped me a lot. Everything was blank to me, ur reply made it clear over the requirement.
    Thanks a lot,
    Naren

  • Mark as deteled idoc with status 40

    Hello,
    I have to mark as deleted an idoc with status 40.  If  idoc has other status (for example 51), I can do it from transaction BD87. But is not possible with status 40.
    For your information, we're using realease 4.6 .
    Thanks,
    Sené

    Hi,
    Yes, we can't reprocess the IDOC with status 40. I have to mark as deleted this idoc. And with other idocs we are using BD87 to mark as deleted.
    How can i mark as deleted this idoc?
    Thanks,
    Sené

  • Reprocessing IDOC with status 52

    Hi,
    I got status 52 for one of the IDOCs, I want to reprocess it . When I use BD87 & BD73, those are not working.
    Please tell me any other way to process it.
    Thanks & Regards
    Vijay

    Hi..Vijay,
    There are already many threads with the same question.
    pls search for your query before posting.
    Eg:
    Re: Idoc status 52 -> How to make it green i.e. 53
    Reprocessing IDOCS with status 52
    regards,
    Padma

  • Processing idocs with status 8

    hi friends,
    how to process idocs with status 8

    Hi,
    Chek this thread which contains step by step procedure to process Idocs
    mannualy process idoc
    Also try these steps
    1. Goto Infopackage
    2. Click on the "Details" Tab of the Infopackage
    3. Goto Datapackage which is currently process
    4. Under the detail tab you can see
    Date, Time, Record... in that you can also see IDOC#
    5. Take the IDOC# and goto BD87 of the Sourcesystem
    6. Paste the IDOC# against IDOC
    7. Give IDOC Status = 64
    8. Give Partner system = "Your Source System"
    9. Execute BD87.
    10. You will navigate to next screen
    11. Maximize all by using "Expand Subtree" button on Menu
    12. You can see "IDOC stauts " column with 64
    13. Click on the row against to 64
    14. Click button "Execute" on Menu.
    15. Your IDoc will start processing
    16. If it success IDoc status will be turned to 53 else to 51.

Maybe you are looking for

  • Fixed Asset Importation Issue (Capitalisation Date)

    Hello experts, I have an issue regarding fixed asset importation. I've import the fixed asset master data correctly in the system, with it's correct capitalisation date, APC, depreciation cumulative value and everything else correctly in the master d

  • Asset with Investment Measure; Depreciation reversal

    Hi, An asset is created with investment measure(through settlement of WBS) in 11/2008. In the same month it was depreciated fully. Now the users want the depreciation to be reversed. The fiscal year 2008 is already closed. Is there any way, the asset

  • Problem with audio from speaker at bottom

    I have looked around the net and found several other people have had this issue, but want to know more about possible fixes. My iPhone 4 has an issue where the audio from the speaker on the bottom of the phone disappears. Randomly. It could be during

  • Desktop RTMP video works fine - but Android gives me NetStream.Seek.Failed

    I have an app built using Adobe AIR. The app uses StageVideo and plays a live RTMP H264 encoded stream using NetStream.play. The app works as expected in ADL, and when installed as an app on the desktop. But if use the exact same code and install the

  • BAPI to extend material to multiple sales organisation

    Hi Experts, I need to know a BAPI for extending a material to multiple sales org. at one go. My requirement is detailed below: Suppose an user is providing the details as below: Material: 90000038 Sales Org: 0011, 0022, 0033. I need a BAPI where I wi