‎2016 May 25 2:34 PM
Hi Guys,
Can anyone have any idea why the waiting for RFC is taking 95% time to execute one report.
Please check the above print screen and let me know what I have to do.
Thanks,
Satya
‎2016 May 25 2:59 PM
Looks like the RFC is taking 12, 13 seconds to execute.
Is the RFC in the same system or different system? Also, the logic in the RFC might be complicated and it makes sense to execute a complex program that long.
-Chandra
‎2016 May 25 3:09 PM
Function group OLEA contains OLE_FLUSH_CALL and other function modules that are called for interaction between ABAP backend and frontend UI (i.e. your PC).
What is this program doing? Is somebody downloading an ALV result list to a local Excel file? It's not unusual (Tom Jones) that this takes time when large files are involved and/or the network connection is slow and/or the PC is overloaded or "underspecced".
Thomas
‎2016 May 25 3:14 PM
Check with basis - looks like basis problem.
BTW that's normal: Processing is much faster than RFC waiting times.
Regards Clemens
‎2016 May 26 7:55 AM
Thanks to all for your replay.
Thomas, you are correct OLE_FLUSH_CALL is taking more time because I am downloading one file to my local system by using this program. Can we optimize the performance, Is there any other way is there to solve this problem.
Thanks,
Satya
‎2016 May 26 1:10 PM
Write excel to server file. Download later on Request .
Regards Clemens
‎2016 May 27 6:11 AM
Hi Clemens,
I am not clear with your words, Can you please elaborate.
Thanks,
Satya
‎2016 May 27 9:53 AM
Hi Satya,
if you know than the download to the local frontend PC is a performance issue, then you could better write it to a server file (open dataset, Tranbsfer...). Transfering data to server files happend at the speed of light.
Then, and only if needed for local processing, you can download the files from the server to the local desktop and then open with excel.
Still not clear?
Best regards
Clemens