Start of Content Area

Function documentation Log User Actions  Locate the document in its SAP Library structure

Use

Logging traces allows you to save user actions within the respective application areas in the system long-term.

Example

In the application area Reporting, Planning and OLAP Technology, you can log selected executions of queries and the subsequent query navigations, as well as particular actions, in the planning modeler.

You can trace the following:

...

      The execution of the query in the query monitor (see Query Monitor)

      The execution of the query on the Web or in the SAP Enterprise Portal

      The execution of the query in the BEx Analyzer

      The data request of the planning modeler

      The data store of the planning modeler

Integration

You can rerun and control traces, as well as use them to define automatically executable regression tests. For more information, see Trace Tool Environment.

In the application area Reporting, Planning and OLAP Technology, you can jump directly to the query monitor using the trace tool.

Prerequisites

     The user has sufficient authorization for logging traces (see Trace Tool Environment Authorizations).

     The user executes actions that can be logged by the trace tool.

Features

A successful trace logging comprises the following steps:

     Activating the trace logging

     Executing the actions to be logged

     Deactivating the trace logging

It is irrelevant if the activation or deactivation and the execution of the actions takes place in the same mode, or in two different modes.

During activating and deactivating a trace logging, the following cases are supported:

     Users want to activate or deactivate themselves.

     An administrator wants to activate or deactivate a particular user.

You can determine for each user, if, in addition to logging user actions, they are to be activated or deactivated for generating tests.

Activities

Activating the Trace Logging

...

       1.      In the navigation window from the Trace Tool functional area, choose the This graphic is explained in the accompanying text User Activation area.

       2.      The Trace User field is initialized with the current user name.

If, as an administrator, you want to activate another user, enter this name in the Trace User field.

       3.      If the user intends to convert a trace into an automatic test, set the indicator for the Activation for Test Generation option.

       4.      To activate yourself as a user, choose This graphic is explained in the accompanying text Activate USERNAME.

If, as an administrator, you want to activate a user whose name you have entered in the Trace User field, choose This graphic is explained in the accompanying text Activate.

As a result of your activation, the system displays the activated user as well as the time of activation and the selection for the test generation in the user table.

User Interaction

...

       1.      To log a trace in the application area Reporting, Planning and OLAP Technology, call the required environment for executing the query or modeling a planning application:

     Query monitor

     BEx Analyzer

     Web browser for executing the query on the Web

     Planning modeler

       2.      Perform all the actions (query navigations or actions in the planning modeler) that the system is to log.

Deactivating the Trace Logging

...

       1.      To end the trace logging, go back to the This graphic is explained in the accompanying text User Activation area of the trace tool.

       2.      If, as a user, you want to deactivate yourself, choose This graphic is explained in the accompanying text USERNAME Deactivate.

If you want to deactivate yourself, or as an administrator, you want to deactivate another user, select the corresponding entry in the user table and choose This graphic is explained in the accompanying text Deactivate.

Note

If the current session ends during the logging of user actions, the system automatically shuts the trace logging. Therefore, for example, executing the query monitor again, or refreshing the Web browser window interrupts logging. If further interactions take place, a new trace occurs.

If, on the contrary, in a second session, the user for the trace logging is deactivated and then reactivated, and this then executes further interactions in the first session, a new trace occurs.

 

End of Content Area