Show TOC Start of Content Area

Background documentation Severities for Trace Messages  Locate the document in its SAP Library structure

The following table outlines the specific severity you must use in each situation and the information you have to provide with the trace message.

Severity

Description

DEBUG

Information only valuable for developers to analyze the internal status of a program.

PATH

Information for developers and support engineers to understand the execution flow of a program. The method calls that supply information on this severity level are entering(), exiting(), throwing() and catching().

INFO

Information, valuable for support engineers and developers to understand and trace the business logic.

ERROR

Information describing uncorrectable error conditions in program execution, which terminate the current application without fulfilling the desired task. The application remains usable afterwards. The method call assertion() is used to test a Boolean expression and stop with an error if it is not fulfilled.

Also, technical context information in exception must use severity ERROR.

 

 

 

End of Content Area