Get Example source ABAP code based on a different SAP table
ID MODULE • MODULE ABAP Statement
MODULE> Short Reference >
ABAP_SYNTAX MODULE mod ${OUTPUT$|$[INPUT$]$}.> ...> ENDMODULE.>
ABAP Addition ... OUTPUT$|$[INPUT$]>
What does it do? The statement MODULE> defines a dialog module> mod>. The naming conventions> apply to the name mod>. The functions of a dialog module mod> are implemented between the statements MODULE> ad ENDMODULE>. A dialog module is called using the identically named statement MODULE>> of the dynpro flow logic> of any dynpro> in the ABAP program. • OUTPUT MODULE • INPUT MODULE
ABAP Addition
What does it do? The additions OUTPUT> and INPUT> determine whether the dialog module can be called at the PBO>> or PAI> event. The addition INPUT> is the default and could therefore also be omitted, although this is not recommended for reasons of program readability. Two dialog modules with the same name can be defined in a program, if one of them has the addition OUTPUT> and the other has the addition INPUT>. However, this is also not recommended for reasons of readability.
Latest notes: For reasons of data encapsulation, it is recommended that very few functions are implemented in dialog modules and that procedures> are called instead. ABAP_HINT_END
Example ABAP Coding
PAI module for a dynpro with the dynpro number 100. In the PAI module, no functionality is implemented and an instance method of an object is called instead. MODULE user_command_0100 INPUT. screen_handler->user_command( ). ENDMODULE.> ABAP_EXAMPLE_END