Entering content frame

Messages Without Screens Locate the document in its SAP Library structure

This context applies to all situations that do not belong to any screen processing. In ABAP programs, this includes the following processing blocks:

         The program constructor LOAD-OF-PROGRAM

         PBO modules (PBO of screens)

         The selection screen event AT SELECTION-SCREEN OUTPUT (PBO of a selection screen)

         The reporting events INITIALIZATION, START-OF-SELECTION, GET, and END-OF-SELECTION

         The list events TOP-OF-PAGE and END-OF-PAGE

All other processing blocks are associated with screen processing (reacting to user input).

 

In order to make the following table more concise, the above mentioned processing blocks are structured into two groups.

Group 1:  LOAD-OF-PROGRAM,  PBO module of screens, AT SELECTION-SCREEN OUTPUT

Group 2: Reporting- and list events (INITIALIZATION, START-OF-SELECTION, GET,  END-OF-SELECTION, TOP-OF-PAGE and END-OF-PAGE)

 

Message Processing

Type

Display

Processing

A

Dialog box

Program terminates, and control returns to last area menu

E

Group 1: Dialog box
Group 2: Status line of
                 current window

Group 1: as type A.
Group 2: Program termination and display of an empty screen with empty GUI status. After the user action: Return to the calling position of the program.

I

Group 1: Status line of the
..............next screen
Group 2: Dialog box

Program continues processing after the MESSAGE statement

S

Status line of next screen

Program continues processing after the MESSAGE statement

W

Group 1: Status line of the
..............next screen
Group 2: Status line of the
...............current window

Group 1: as type S.
Group 2: Program termination and display of an empty screen with empty GUI status. After the user action: Return to the calling position of the program.

X

None

Triggers a runtime error with short dump

 

 

Leaving content frame