Message Behaviour

MESSAGE

Variants:

1. MESSAGE xnnn.

2. MESSAGE ID id TYPE mtype NUMBER n.

3. MESSAGE xnnn(mid).

4. MESSAGE msg TYPE mtype.

Effect

Sends a message. Messages are stored in the table T100, are processed using transaction SE91 and can be created by forward navigation.

The ABAP runtime environment handles messages according to the type declared in the MESSAGE statement and the context in which the message was sent. The following message types exist:

A - Abend

: Transaction terminated

E - Error

: Error message

I - Info

: Information

S - Status

: Status message

W - Warning

: Correction possible

X - Exit

: Transaction terminated with short dump

Messages are mainly used to handle user input on screens. The following table shows the behavior of each message type in each context. An explanation of the numbers used is included at the end of the table:

                            A     E     I     S     W     X
--------------------------------------------------------------
PAI Module                   1     2     3     4     5     6
PAI Module for POH            1     7     3     4     7

    6
PAI Module for POV            1     7     3     4     7

    6
--------------------------------------------------------------
AT SELECTION-SCREEN ...     1     8     3     4     9     6
AT SELECTION-SCREEN for  POH  1     7     3     4     7     6
AT SELECTION-SCREEN for  POV  1     7     3     4     7     6
AT SELECTION-SCREEN ON EXIT 1     7     3     4     7     6
--------------------------------------------------------------
AT LINE-SELECTION           1    10     3     4    10     6
AT PFn                      1    10     3     4    10     6
AT USER-COMMAND             1    10     3     4    10     6
--------------------------------------------------------------
INITIALIZATION              1    11     3     4    11     6
START-OF-SELECTION          1    11     3     4    11     6
GET                         1    11     3     4    11     6
END-OF-SELECTION            1    11     3     4    11     6
--------------------------------------------------------------
TOP-OF-PAGE                 1    11     3     4    11     6
END-OF-PAGE                 1    11     3     4    11     6
TOP-OF-PAGE DURING ...      1    10     3     4    10     6
--------------------------------------------------------------
LOAD-OF-PROGRAM             1     1     4     4     4     6
--------------------------------------------------------------
PBO Module                   1     1     4     4     4     6
AT SELECTION-SCREEN OUTPUT  1     1     4     4     4     6
--------------------------------------------------------------
Procedure:                    see

Messages
--------------------------------------------------------------

1. The message appears in a dialog box and the program terminates. When the user has confirmed the message, control returns to the next- highest area. All the internal sessions are deleted from the stack.
   
   
2. The message appears in the status line. Then PAI terminates and the system returns to the current screen. All the screen fields combined using FIELD or CHAIN are now ready for input. The user must enter new values. The system triggers the PAI event again, with the new values.
   
   
3. The message appears in a dialog box. Once the user has confirmed the message, the program continues immediately after the MESSAGE statement.
   
   
4. The message appears in the status line of the next screen. The program continues immediately after the message statement.
   
   
5. The message appears in the status line. Then the system continues as in 2, except that the user can quit the message using ENTER without having to enter new values. The system continues handling the PAI event from immediately after the message statement.
   
   
6. No message is displayed and a runtime error, MESSAGE_TYPE_X, is triggered. The short dump text contains the message identification.
   
   
7. The program terminates with a runtime error DYNPRO_MSG_IN_HELP. While F1 and F4 are processed, the system cannot send error messages or warnings.
   
   
8. The message appears in the status line. Then the system stops selection screen processing and returns to the selection screen itself. The screen fields specified in the additions to the AT SELECTION-SCREEN statement are now ready for input. The user must enter new values. The system then starts processing the selection screen again with the new values.
   
   
9. The message appears in the status line. Then the system continues as in 8, except the the user can quit the message using ENTER, without having to enter new values. The system continues handling the PAI event from immediately after the message statement.
   
   
10. The message appears in the status line and the processing block terminates. The list level is displayed as before.
    
    
11. The message appears in the status line and the processing block terminates. The system then returns to the program call.
    
    
12. For a demonstration of messages in different contexts, see Example Programs for Messages.