MESSAGE

MESSAGE

Variants:

1. MESSAGE xnnn.
2. MESSAGE ID mid TYPE mtype NUMBER nr.
3. MESSAGE ynnn(mid).

Additions:

1. ... WITH f1 ... f4
2. ... RAISING exception

Effect

Outputs the message nnn for the MESSAGE-ID specified in the REPORT statement with the message type x. Dialog control recognizes the following message types:

I - Info : Press ENTER to continue

W - Warning : Correction possible

E - Error : Correction required

A - Abend : Transaction terminated

X - Exit : Transaction terminated with short dump
MESSAGE_TYPE_X

S - Success : Message on next screen
See also MODULE.

Notes

In list processing (see LEAVE TO LIST-PROCESSING), the effect of the message types differs in some respects:

Example

MESSAGE I001.

You edit messages by selecting Tools -> ABAP Workbench -> Development -> Programming environ. -> Messages.

Effect

Inserts the contents of a field fi in the message instead of in the placeholder &i . If unnumbered variables (&) are used in a message text, these are replaced consecutively by the fields f1 to f4.
To aid compilation, only numbered variables (&1 to &4) are to be used in future if several fields are involved.
If a "&" is supposed to appear in the message at runtime, you must enter &&.
In the long text of a message, the symbol &Vi& is replaced by the field contents of fi.
After WITH , you can specify 1 to 4 fields.

Note

You can output up to 50 characters per field. If the field contains more characters, these are ignored.

Example

MESSAGE E0004 WITH 'Hugo'. 

Note

When executing the statement, the contents of the fields f1 to f4 are assigned to the system fields SY-MSGV1, SY-MSGV2, SY-MSGV3 and SY-MSGV4.

Effect

Only possible within a function module or a method (see FUNCTION, METHOD):

Triggers the exception exception.

If the program calling the function module or method handles the exception itself, control returns immediately to that program (see CALL FUNCTION and CALL METHOD ). In this case, the export parameters of the function module are ignored. However, the calling program can refer to the system field values (see above).

If the calling program does not handle the exception itself, the message is output (see RAISE).

Note

If an error occurs in the target system during a Remote Function Call, details from the error message are returned to the calling system (SY-MSGNO, SY-MSGID, SY-MSGTY, SY-MSGV1, SY-MSGV2, SY-MSGV3, and SY-MSGV4). These fields are initialized at the start of every RFC call.

Example
MESSAGE E001 RAISING NOT_FOUND.

Effect

As for variant 1, where you can set the following message components dnyamically:

ID Message class

TYPE Message type

NUMBER Message number

You can also use all the other additions as with the basic form.

Example

MESSAGE ID 'SU' TYPE 'E' NUMBER '004' WITH 'Hugo'. 

Outputs the message with the number 004 and MESSAGE-ID SU (see above) as an E (Error) message and replaces the first variable (&) with 'Hugo'.

Example

MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO 
		WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4. 

Constructs the message dynamically from the contents of the system fields SY-MSGID, SY-MSGTY, SY-MSGNR, SY-MSGV1,SY-MSGV2,SY-MSGV3,and SY-MSGV4. These may, for example, be set by an exception after CALL FUNCTION or CALL TRANSACTION ... USING.

Example

MESSAGE X004(SU) WITH 'Hugo'.