ABAP Keyword Documentation → ABAP − Reference → Text Repositories → Messages
Behavior of Messages
When a message
is sent using the statement MESSAGE
, it must be classified with a one-character
message type. For the
basic form of the statement MESSAGE
, the message type defines how the message
is displayed and determines the subsequent program flow. Valid message types are "A", "E", "I", "S",
"W", and "X". These stand for termination (abort) message, error message, information message, status message, warning, and exit message.
The system behavior after a message of a particular type with the basic form of the statement
MESSAGE
, i.e. without the additions
RAISING
or INTO
, is context-dependent:
Other versions: 7.31 | 7.40 | 7.54
Notes
- Messages that are sent with the basic form of the statement
MESSAGE are mainly intended for use in dialog processing for the PAI event. Here, messages
of type "E" and "W" permit an error dialog to be used in connection with the statement
FIELD
of the dynpro structure logic. Therefore messages of type "E" or "W", in particular, should never be used in other contexts.
- In list processing, warnings are always turned into error messages before being processed further, regardless of any other context.
- An alternative to creating runtime errors with messages of type “X” are
assertions and the language
elements
RAISE SHORTDUMP
andTHROW SHORTDUMP
.
Continue
Messages in Control Processing
Messages in Background Processing