Skip to content

ABAP Keyword Documentation →  ABAP - Reference →  User Dialogs →  Screens →  Statements in the Screen Flow Logic →  FIELD 

FIELD - MODULE

Other versions: 7.31 | 7.40 | 7.54

Syntax


FIELD dynp_field MODULE mod [ {ON INPUT} 
  
                         | {ON REQUEST} 

              
             | {ON *-INPUT} 

              
             | {ON {CHAIN-INPUT|CHAIN-REQUEST}} 

              
             | {AT CURSOR-SELECTION}.

Extras

1. ... ON INPUT

2. ... ON REQUEST
3. ... ON *-INPUT

4. ... ON {CHAIN-INPUT}|{CHAIN-REQUEST}

5. ... AT CURSOR-SELECTION

Effect

After the FIELD statement of the dynpro flow logic, at the event PAI you can call the dialog module mod using the MODULE statement. If no condition ON or AT is specified, the module is called immediately after the data transport specified in FIELD.

Besides two conditions of the normal module call, after FIELD you can specify special conditions for the call of the dialog module, which concern the screen field dynp_field.


Note

Addition SWITCH of the stand-alone statement MODULE is not possible in connection with the FIELD statement. Instead, the switch assigned to the screen field in the Screen Painter takes effect.

Addition 1

... ON INPUT

Effect

With this condition, module mod is called only if the dynp_field is not empty for a

screen field that is ready for input. All screen fields except fields of type STRING or SSTRING are considered empty if they contain nothing but blanks in the screen display. Screen fields of type STRING and SSTRING are considered empty if they do not contain any characters.

If the input field has the special attribute *-Input and the user has entered an asterisk as first character in the input field of screen field dynp_field , the condition ON INPUT is not met. Instead, the condition ON *-INPUT is fulfilled (see below).


Note

In the screen display, you can recognize an empty field of type STRING or SSTRING by the fact that the cursor can be positioned only on the beginning of the field.

Addition 2

... ON REQUEST

Effect

With this condition, module mod is called only if the value of the screen field dynp_field has been changed by input after the event PBO. It is considered as input if the existing input is overwritten with the same value or if the initial value of the field is entered explicitly. Besides user input, the following value input results in a call of mod:

  • Transfer of a default value set via System → User Profile → Hold Data. However, this requires the dynpro property Hold Data to be active.
  • Tansfer of a default value from the SAP Memory. This requires that in the PARAMETER-ID property of a screen element an SPA/GPA parameter is specified.
  • Transfer of data that is passed in the call of a dialog transaction using the addition USING of the DS:ABAP.CALL_TRANSACTION>CALL TRANSACTION statement.
  • Transfer of a default value predefined in the system or in the ABAP Dictionary for input/output fields of certain types.

Addition 3

... ON *-INPUT

Effect

With this condition, module mod is called only if the user endered an asterisk ("") as first character in the input field of screen field dynp_field and if the input field has the special attribute -Input. The content of dynp_field is passed to the ABAP program without the leading asterisk.

Addition 4

... ON {CHAIN-INPUT|CHAIN-REQUEST}

Effect

The conditions ON CHAIN-INPUT and ON CHAIN-REQUEST have the same meaning as if used after a stand-alone MODULE statement.

Addition 5

... AT CURSOR-SELECTION

Effect

The condition AT CURSOR-SELECTION has the same meaning as if used after a stand-alone MODULE statement.