Get Example source ABAP code based on a different SAP table
ID MESSAGE-text • TYPE MESSAGE text
MESSAGE>, text> Short Reference >
ABAP_SYNTAX ... text TYPE mtype ...>
What does it do? This variant sends a character string in text> as a message> of the message type> specified in mtype>. text> is a character-like expression position> whose value is used as the short text of the message. Only the first 300 characters are used. No long text can be defined for a message of this type. mtype> expects a character-like data object containing the message type in uppercase letters. Invalid message types raise an uncatchable exception. In this variant, the addition WITH>> and the variant with INTO>> are not allowed.
Latest notes:
If field symbols or formal parameters of the type any> or data > are specified for text>, these must be character-like when the statement is executed. The variant MESSAGE oref >>, which has identical syntax, cannot be executed using generically typed field symbols or formal parameters.
The system fields sy-msgid> and sy-msgno> are filled in a non-specific way when a character string is specified, which means that this variant should only be used on rare occasions if the content of the system fields is not required for identifying the message. Otherwise, in all cases in which messages are passed using these system fields, for example, from function modules>, or logged, language-independent access to the message text would be lost. ABAP_HINT_END
Example ABAP Coding
Output of an exception text as an information message>. ABEXA 00411 ABAP_EXAMPLE_END