SAP NetWeaver AS ABAP Release 740, ©Copyright 2014 SAP AG. All rights reserved.
ABAP Keyword Documentation → ABAP − Reference → User Dialogs → Screens → Statements in the Screen Flow Logic → MODULE → Module Call - Examples →Screens, Conditional Module Call
The example shows how to call modules on a condition-related basis.
Source Code
PROGRAM demo_dynpro_on_condition .
DATA: ok_code TYPE sy-ucomm,
input1(20) TYPE c, input2(20) TYPE c, input3(20) TYPE c,
fld(20) TYPE c.
CALL SCREEN 100.
MODULE init_screen_100 OUTPUT.
SET PF-STATUS 'STATUS_100'.
ENDMODULE.
MODULE cancel INPUT.
LEAVE PROGRAM.
ENDMODULE.
MODULE cursor INPUT.
GET CURSOR FIELD fld.
MESSAGE i888(sabapdemos) WITH text-001 fld.
ENDMODULE.
MODULE module_1 INPUT.
MESSAGE i888(sabapdemos) WITH text-002.
ENDMODULE.
MODULE module_2 INPUT.
MESSAGE i888(sabapdemos) WITH text-003.
ENDMODULE.
MODULE module_* INPUT.
MESSAGE i888(sabapdemos) WITH text-004 input3.
ENDMODULE.
MODULE c1 INPUT.
MESSAGE i888(sabapdemos) WITH text-005 '1'.
ENDMODULE.
MODULE c2 INPUT.
MESSAGE i888(sabapdemos) WITH text-005 '2' text-006 '3'.
ENDMODULE.
Description
The static next screen number of screen 100 is 100. The input fields have been assigned the screen fields input1, input2, and input3. The function code of the pubshbutton is EXECUTE. In GUI status STATUS_100, the icon Cancel (F12) has been activated using the function code CANCEL with the function type E. Also, the F2 function key has been assigned the CS function code with the function type S, and the F8 function key has been assigned the EXECUTE function code without any specific function type. The screen flow logic is as follows:
Issuing information messages, the program shows which modules are called after which user actions and which data is transported: