Skip to Content
author's profile photo Former Member
Former Member

IDoc Delays: 64 to 62 status

Hello - We have been seeing some intermittent delays on some of our ORDERS idocs. They are configured to process immeadiately, but we have been seeing some delays when they are going from status 64 (Ready to be Transferred) to status 62 (IDoc passed to application). These delays are sporatic and ranging from 2 minutes to 20 minutes.

Any thoughts?

Thanks - Kyle Winters

Add a comment
10|10000 characters needed characters exceeded

Related questions

4 Answers

  • author's profile photo Former Member
    Former Member
    Posted on Apr 24, 2009 at 02:43 PM

    Hi,,

    see the below notes how to process 64 and 62 idoc status and what might be the reason.

    << Cut and paste without attribution from http://www.abapprogramming.net/2009/01/edi-inbound-process-via-function-module.html removed >>

    regards,

    Prabhudas

    Edited by: Rob Burbank on Apr 24, 2009 11:02 AM

    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on May 08, 2009 at 06:08 PM

    Hi,

    Are these idocs processed using workflows or ??

    Please have a look at following SAP notes.

    » Idocs remain in inbound with status 62

    » ALE: Link to application log in status 62

    » IDocs-Status 62 cannot be processed

    » IDoc: Problems with inbound processing using workflow

    » IDoc: Workflow is not started in RSEINB00

    » ALE: IDocs remain in status 64 / 3.X inbound

    » IDocs remain in status 64

    KR Jaideep,

    Add a comment
    10|10000 characters needed characters exceeded

    • Hi,

      my answer is now quite late regarding the issue, but if you still encounter this issue you can apply OSS Note 1557798 to change the timestamp at the status 62 level.

      After applying the OSS note you can analyze if the delay is before or after passing the IDOC to application. (status 62)

      Regards,

      Luc

  • Posted on Nov 19, 2013 at 05:20 AM

    If the settings in WE20 is "Trigger through background".

    Idocs are received with status 64 and the program RBDAPP01 processes the Idocs to change the status to 62 and then to 53.

    Might be there is a long run of the job which you scheduled with the above program or the job might have started late from the scheduled start.

    Regards,

    Thanga Prakash T

    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Dec 02, 2013 at 09:54 PM

    Hello Kyle,

    just as a thought. Who creates the idoc, e.g. an own written programm? May there be a locking problem (the realease of the idoc lock)?

    -Regards

    -Jürgen-

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.