04-24-2009 3:37 PM
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
04-24-2009 3: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
05-08-2009 7: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
KR Jaideep,
08-23-2011 9:50 AM
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
11-19-2013 5: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
12-02-2013 9: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-