/
Creating a GUI trace for analysis of SAPUI tree / control errors (mode / session trace)

Creating a GUI trace for analysis of SAPUI tree / control errors (mode / session trace)

If there is a dump with runtime error MESSAGE_TYPE_X from the program SAPLOLEA, especially in connection with the function AC_SYSTEM_FLUSH, then the error cannot be narrowed down on the basis of this dump. The reason is that the data which were sent triggered an error in the SAPGUI. To isolate these errors a GUI trace is necessary. The following steps are necessary:

  • Start the corresponding application in SAPGUI and navigate / execute actions immediately BEFORE the step that triggers the error.

  • Go to the SAPGUI options

  • Then "Traces" > "Mode Trace" ("Session Trace" for English installation)

  • In this subscreen, select the following options:

    • Advanced Tree Control

    • Automation

    • Control Manager

    • General

    • Office Integration

  • To delete old trace data select the "Delete all trace files" function

  • Then "Activate" and save

  • Now all actions on the SAPGUI for the selected options are written to a trace file

  • Now perform the necessary step to create the dump

  • Then go back to the trace settings in the SAPGUI and first deactivate the trace

  • With "Show trace" the recorded data is displayed

  • Save this result to a file and, depending on the request, attach it to your support message or send it by e-mail