System Messages 

Exceptions

Exceptions are used for all errors and are always listed at the end of an API, so that different errors can be found and logged.

The API checks all entries. It produces a log of any errors that occur, and sets an ERROR exception for each error.

Under certain circumstances, an exception may be set before the API has checked all entries.

Usually, the only exceptions set are ERROR exceptions. This means that processing was terminated – because essential data was missing, for example.
Some function modules also use a WARNING exception or return code. In this case, a warning message is written to the log.

For each error found, an entry is also written to the log.

Log

The messages that would normally appear in dialog mode are written to a database log. All types of message (error, warning, and success messages) are saved. This explains all process flows, even in case of complex errors.

API for Reading the Message Log

There is an API module especially for reading the log before it is saved to the database. The messages and some message attributes are transferred to an internal table. After each API that is called externally, the collected messages (in mixed form) are available to this API. You can evaluate the message identifiers internally in your program, and present the messages in your user interface.

See also General APIs.