Show TOC Start of Content Area

Function documentation Severity Evaluation  Locate the document in its SAP Library structure

Use

The message logging depends on its severity level, compared with the severity threshold assigned to the source object. In some cases it is not advisable to call the output API (logT, fatalT, errorT, and so on), due to potential performance issues (for example – resolving the parameter list of the call). An additional severity check before making the output calls is required. There are APIs that enable you to do this; you can find them in the LogController class:

This graphic is explained in the accompanying text

beLogged(Severity level)

beFatal(), beError(), beWarning(), beInfo(), bePath(), beDebug()

This returns a Boolean “true“ if the message passes the respective severity level check; otherwise it returns “false”.

 

More information:

Relative Severities

 

End of Content Area