Installation The best way to install the UI Log component is to proceed as follows:
  1. Install GuiXT as of version 2020 Q3 2



  2. Install Script Editor Pro as of version 2020 Q3 2



    You need the Script Editor pro to generate GuiXT scripts based on the recordings. If you do not have a license for it, please request the free 30-day trial license.
  3. Import the SAP transport request sap.trans.uilog.zip into your SAP development system using transaction STMS. The transport request contains all function modules and transactions required for UI log recording and for executing the generated scripts.

     


  4. Request the license key for the UI Log component from Synactive (email to office@synactive.com). If you have a valid maintenance contract for InputAssistant, the license key is free of charge. Otherwise you can request a 30-day trial key and then decide if you want to buy the UI Log tool.

    For example, the license key looks like this:
    MyCompany20200831.uilog.mwemirrismky 
  5. To write the UI log entries in the system, the RFC user needs the following authorization

    S_RFC
    RFC_TYPE=FUGR, RFC_NAME=/GUIXT/LOGG
    ACTVT=16

Now the first test can begin.  
 
A first test Start transaction /GUIXT/UILOG, enter a freely chosen project name and click on "Configuration":


 Note: When calling transaction /GUIXT/UILOG in the SAP Easy Access Menu, please enter /n/GUIXT/UILOG, otherwise it will not work because of  the leading / character.

In the next screen confirm that you want to create a new project:



It is now sufficient to enter a project title and then save the project configuration:



Briefly on some further details: Later, the generated scripts will be stored in the suggested script directory C:\guixt\uilog; you can replace it with any other directory. In the example above, the languages installed in your SAP System are proposed as languages. For testing purposes, you can also just enter "en" and later use the languages for which you want to generate scripts.


Next, add the following statement to the GuiXT session script "esession.txt" (or session.txt if you have set script names without language keys in the GuiXT configuration)

ProcessingOption uiLog="On" uiLogProject="TEST01" _
     uiLogTransactions="VA01,VA02,MM02,XD02" _
     uiLogLicense="MyCompany20200831.uilog.mwemirrismky" uiLogInterval="1"
This enables the recording for the specified transactions. You can find the individual parameters in the documentation for ProcessingOption.
If you omit the parameter uiLogTransactions=, all transactions are recorded.

Now open a new session and perform some transactions. Then call /GUIXT/UILOG again and start the first evaluation "Transactions" of your project "TEST01" with F8:



Various times are displayed, which you can break down in detail for each call (pushbutton Transaction calls, then F2 on the process under consideration):




Now the UI Log component is tested as basically functional and you can try out the further possibilities for UI analysis and script generation.