Basic form
MODULE modl.
Additions
1. ... OUTPUT
2. ... INPUT
Effect
The processing block between the " MODULE modl. " and " ENDMODULE. " statements is snown as a module . We call the module modl in the screen flow logic with the statement " MODULE modl. ". This screen must belong to the same program (module pool) as the module.
Example
DATA: INPUT, GOOD_INPUT.
MODULE CONTROL.
...
IF INPUT NE GOOD_INPUT.
MESSAGE E123.
ENDIF.
ENDMODULE.
The ABAP/4 statement MODULE , which is always terminated by ENDMODULE , must not be confused with the flow logic statement MODULE ( screen ).
Addition 1
... OUTPUT
Addition 2
... INPUT
Effect
The module called before screen output (in the PROCESS BEFORE OUTPUT section of the flow logic) should be qualified by the addition OUTPUT . Since the addition INPUT is the default value, it can be omitted. This means that the module called user input (in the PROCESS AFTER INPUT section of the flow logic), is either followed by no addition or qualified by the addition INPUT . A module modl can thus exist twice - as an input and as an output module.
Here we cannot combine the additions OUTPUT and INPUT .
· An error message (MESSAGE Emnr ) cancels processing of the module.
· A warning message (MESSAGE Wmnr ) repeats the current module (or the module chain [CHAIN ]) if you enter different data.
If when we just press ENTER after the warning (or even after I and S messages), processing continues after the MESSAGE statement.(99.5)
Recent posts at team blogs are
Syntax for change list line
Syntax for modify data in internal table
How EDI Message Control works ?
Spiral model software testing
Heat and temperature concept
MODULE modl.
Additions
1. ... OUTPUT
2. ... INPUT
Effect
The processing block between the " MODULE modl. " and " ENDMODULE. " statements is snown as a module . We call the module modl in the screen flow logic with the statement " MODULE modl. ". This screen must belong to the same program (module pool) as the module.
Example
DATA: INPUT, GOOD_INPUT.
MODULE CONTROL.
...
IF INPUT NE GOOD_INPUT.
MESSAGE E123.
ENDIF.
ENDMODULE.
The ABAP/4 statement MODULE , which is always terminated by ENDMODULE , must not be confused with the flow logic statement MODULE ( screen ).
Addition 1
... OUTPUT
Addition 2
... INPUT
Effect
The module called before screen output (in the PROCESS BEFORE OUTPUT section of the flow logic) should be qualified by the addition OUTPUT . Since the addition INPUT is the default value, it can be omitted. This means that the module called user input (in the PROCESS AFTER INPUT section of the flow logic), is either followed by no addition or qualified by the addition INPUT . A module modl can thus exist twice - as an input and as an output module.
Here we cannot combine the additions OUTPUT and INPUT .
· An error message (MESSAGE Emnr ) cancels processing of the module.
· A warning message (MESSAGE Wmnr ) repeats the current module (or the module chain [CHAIN ]) if you enter different data.
If when we just press ENTER after the warning (or even after I and S messages), processing continues after the MESSAGE statement.(99.5)
Recent posts at team blogs are
Syntax for change list line
Syntax for modify data in internal table
How EDI Message Control works ?
Spiral model software testing
Heat and temperature concept
ABAP TOPIC WISE COMPLETE COURSE
BDC OOPS ABAP ALE IDOC'S BADI BAPI Syntax Check
Interview Questions ALV Reports with sample code ABAP complete course
ABAP Dictionary SAP Scripts Script Controls Smart Forms
Work Flow Work Flow MM Work Flow SD Communication Interface
/p>
No comments:
Post a Comment