Show TOC Start of Content Area

Function documentation Tracing Locate the document in its SAP Library structure

Use

Using tracing assumes that the problem was noticed elsewhere, for example, by a log message, by complaining users or obviously non-functioning components or applications. That is why tracing is always an exceptional procedure triggered by other information. This implies that traces are switched off during normal operation. It is therefore recommended to set the default severity for locations to ERROR. This ensures that stack traces of exceptions are visible even in normal operation mode. If it is really necessary to turn on traces permanently for understanding whether a system is working correctly or not, those trace messages must better be log messages.

The following topics will help you to start using traces more efficiently:

Addressees of Trace Messages

How to Use Locations

Typical Types of Trace Messages

Content of Trace Messages

Severities Usable for Trace Messages

End of Content Area