Show TOC

User Trace: Background InformationLocate this document in the navigation structure

Use

The user trace is used to look for errors that occur with certain users and not with others. Trace information, located in the Developer Trace for each work process, is written to the user trace from the user view, provided this option is activated.

Activate the user trace only as long as you need it to reproduce error situations, and then deactivate it. This prevents system performance from being affected and unnecessarily large trace files from being produced.

Prerequisites

You are in the logon list (SM04) and have selected the user(s) you want to trace.

Security Settings

Some security settings impair the validity of the user trace because the trace level is not passed on to (inherited by) processes . In particular, if you want to create traces with RFC or HTTP calls, certain prerequisites must be met on the client and server sides.

RFC Requests

On the sending system (RFC client) the settings in the gateway and in the destination are important.

  • If in the destination (transaction SM59) the setting Gateway Standard Value is active in Start of the navigation path Special Options Next navigation step Send Trace End of the navigation path, parameter gw/export_trace_level must =1 (trace level is inherited).

  • If Send Trace is set in the destination, the required user trace is created.

    The setting Do Not Send Trace stops a user trace being created.

For the receiving system the following applies:

  • For the receiving gateway to accept the trace (that is, write the trace for the processing step and all subsequent processing steps), parameter gw/accept_remote_trace_level must be =1.

  • For the receiving work process to accept the trace (that is, write the trace for the processing step and all subsequent processing steps for this session), parameter rdisp/accept_remote_trace_level must be =1.

HTTP Requests

For the receiving system the following applies:

  • For the receiving ICM to accept the trace (that is, write the trace for the processing step and all subsequent processing steps), parameter icm/accept_remote_trace_level must be =1.

  • For the receiving work process to accept the trace (that is, write the trace for the processing step and all subsequent processing steps for this session), parameter rdisp/accept_remote_trace_level must be =1.

Internal Requests

The trace level is always inherited in internal communication if another work process in the system is requested to do so (for example, update tasks, generation of ABAP processes, number range server requests, and so on).

For the processing work process to activate the trace, parameter rdisp/accept_remote_trace_level must be =1.

Features

Functions of the Trace Display

In the trace display (screen User Trace for <BENUTZER> on <server> ), additional menu functions and buttons are available.

Function

Menu/Button

Expand/collapse single steps in user trace

Double-click the line (for example, step by MEYER, mode 1, step 6 or choose Expand or Collapse.

Expand or collapse all steps at once

Expand all or Collapse all

Output trace information unformatted

Start of the navigation path Trace Next navigation step Unformatted End of the navigation path

Define load and display components

Start of the navigation path Trace Next navigation step Component Selection End of the navigation path

Reset (delete) trace file

Start of the navigation path Edit  Next navigation step Reset Trace End of the navigation path

Execute function trace

Start of the navigation path Edit  Next navigation step  Function Trace End of the navigation path

Go to next C stack

Start of the navigation path Edit  Next navigation step  Next C Stack End of the navigation path

Go to other system functions

Goto

More Information