Enter Debug Mode

The logging API will not throw exceptions (see: Central Concepts -> Exceptions). Instead it offers assertions that can be used to analyze problems (see: Central Concepts -> Assertions). Since they are inactive by default, they will do nothing when violated. Instead the code behind a assertion will be executed like the assertion did not exist.

You can change this behaviour in transaction SAAB as you like. If you proceed as described, the change will only affect your own user.

The assertions are assigned to the checkpoint group /USI/BAL_LOG_WRITER.

As the API does not use Breakpoints or logpoints so far - only the block assertions is relevant. Change the setting as you like and save. The behavior 'Break' is recommended to search for issues. It will start the debugger whenever an assertion is violated.

Choose the activation period and confirm.