I have detected massive performance problems when using transaction WLF_IDOC or SE03. Especially when double-clicking on a segment in WLF_IDOC in the navigation tree or when selecting a function in the object catalog in SE03.
We would like to look into this. Could you please create an incident on component BC-FES-JAV? You can help us by providing a performance trace: open the trace dialog [1], press the "profiling" button, enter a filename and press the apply button (in this case without checking the "Start Trace" before). Then go through the steps which are too slow. Please attach the resulting trace file to the incident. Also please describe the steps you are taking, so we can try to do the same.
We might need to logon to your system in case we do not see such performance delays in our internal systems.
our first step would be to look into this profiling trace, but in case the trace indicates that the performance issue indeed comes from SAP GUI for Java and not the backend or network, it is required to log on to your system where you are having this problem. And for this we definitely need to have this incident.
I do not see a benefit of having the trace posted here as it only helps for the very first step, but not for the required follow up activities. To really work on the issue we require an incident created.
The incident should contain
- the profiling traces you created
- the steps performed described in a way so we can recreate it
- the required backend be prepared for remote logon
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.