Ansicht
Dokumentation
ABENABAP_MESSAGES_TYPES - ABAP MESSAGES TYPES
SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up ABAP Short ReferenceThis documentation is copyright by SAP AG.
- 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:
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.
ROGBILLS - Synchronize billing plans Addresses (Business Address Services)
This documentation is copyright by SAP AG.
Length: 4689 Date: 20240419 Time: 140644 sap01-206 ( 49 ms )
