Get Example source ABAP code based on a different SAP table
ARTICLE
Behavior of messages When you send a message using statement MESSAGE, it must be classified with a one-character message type. 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 message, error message, information message, status message, warning, and exit message. The system behavior after a message of a particular type is sent is context-dependent:
Messages during list processing
Messages in dialog processing
Messages in control processing
Messages in batch input
Messages in background processing
Messages in updating
Messages in conversion routines
Messages in procedures
Messages in RFC processing
Messages in HTTP servers
Notes
Messages are mainly intended for use during dialog processing, and there for the event PAI. 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.
During list processing, warnings are always turned into error messages before being processed further, regardless of any other context.
As of release 6.20, you can use assertions as an alternative to generating runtime errors with messages of type 'X'.
