Get Example source ABAP code based on a different SAP table
ABAP_MSG - Behavior When a message is sent using the statement MESSAGE, it must be classified with a single-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. The abbreviations stand for termination (abort) message, error message, information message, status message, warning, and exit message. The system behavior after sending a message of a particular type with the basic form of the statement MESSAGE, that is, without the additions RAISING or INTO, is context-dependent:
Messages in list processing
Messages in Dialog Processing
Messages in Control Processing
Messages in Batch Input
Messages in Background Processing
Messages in Updates
Messages in Conversion Routines
Messages in Procedures
Messages in RFC Processing
Messages in ICF Processing
Messages in APC Processing
Messages in ABAP daemon Processing
Latest 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. Therefore, messages of type E and W allow 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 and THROW SHORTDUMP. ABAP_HINT_END
