Entering content frame

Object documentation Developer Traces Locate the document in its SAP Library structure


Developer traces contain technical information for use in the event of problems with your system. Using the entries in the developer traces requires a sophisticated knowledge of the host systems in which your SAP system is running and of the SAP system itself.


The traces can be useful in diagnosing host system and SAP-internal problems that are affecting your SAP system.

Developer traces are written in files in the work directory of the SAP application server that generated the trace.

You can use trace logging to track down sporadic errors.


File Names of Developer Traces

The names of the trace files are as follows:

File Names for Developer Traces


File Name



Work process /task handler

dev_w<n>, whereby n is the number of the work process



Message server


Internet Communication Manager (ICM)


SAP Web Dispatcher


RFC (Remote Function Call) facility

dev_rfc, dev_rfc<n>

dev_rfc traces RFC calls to external functions (written in C or Visual Basic).

dev_rfc<n> traces RFC calls that are executed in SAP work processes. <n> is the number of the work process in the server (as shown above). A work process uses the same log file across RFC calls.



Enqueue (lock)


Standalone enqueue server: dev_enqrepl, dev_enqsig, dev_enqsrv, dev_enqwork, dev_enqio_<n>

Startup (sapstart)


R3trans and tp transport programs


Monitoring infrastructure (test mode only)


In normal operation, you will not see this file. It is used only by test tools of the monitoring infrastructure. It therefore appears only if the test tools must be activated during a support session.


The information traced is determined by the trace level - this applies to all trace files (see below).

Error and System Log Entries in Trace Files

Each line in the trace files starts with the component abbreviation. This is the letter that identifies the trace component. The assignment can be found under Trace Components:

In accordance to these letters lines that contain error information begin with *** ERROR =>. Lines for which system log entries are written start with *** LOG <message ID>.

An "error line" contains the name of the calling function, the operation that failed, the error number from the host system (if a system call is involved), and the name of and line in the C module that failed.


The following sections explain how to use developer traces.

Turning Developer Traces On and Off

To find out how to activate and deactivate developer traces see Activating and Deactivating Developer Traces.

Displaying Developer Traces

To find out how to display developer traces see Displaying Trace Files.

Downloading Developer Traces

To find out how you can easily and quickly downlad trace files on to your computer see Downloading Trace Files.

Additional Information

Further trace functions include:

Trace logging

System Trace



Leaving content frame