Skip to content

ABAP Keyword Documentation →  ABAP - Reference →  User Dialogs →  Dynpros →  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 statement FIELD in the dynpro flow logic, the dialog module mod can be specified at PAI time using the statement MODULE. If the conditions ON or AT are not specified, the module is called immediately after the data transport specified in FIELD.

As well as two conditions in the regular module call, special conditions for the call of the dialog module, related to the dynpro field dynp_field, can be specified after FIELD.


Note

The addition SWITCH of the standalone statement MODULE cannot be used with the statement FIELD. Instead, the switch associated with the dynpro field in Screen Painter is used.

Addition 1

... ON INPUT

Effect

This condition dictates that the module mod is called only if the dynp_field is not empty for a dynpro field that is ready for input. All dynpro fields except fields of type STRING or SSTRING are considered empty if they contain nothing but blanks in the screen display. Dynpro 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 the first character in the input field of the dynpro field dynp_field, the condition ON INPUT is not met. Instead, the condition ON *-INPUT is met (see below).


Note

In the screen display, an empty field of type STRING or SSTRING can be detected clearly by the fact that the cursor can be positioned only at the beginning of the field.

Addition 2

... ON REQUEST

Effect

This condition dictates that the module mod is called only if the value of the dynpro field dynp_field was modified by input after the event PBO. This applies even when 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 input values also produce a call of mod:

  • Applying a default value set using System → User Profile → Hold Data. This requires the dynpro property Hold Data to be active.
  • Applying a default value from the User Memory. This requires that an SPA/GPA parameter is specified in the PARAMETER-ID property of a screen element.
  • Applying data passed when calling a dialog transaction using the addition USING of the statement CALL TRANSACTION.
  • Applying a default value predefined in the system or in ABAP Dictionary for input/output fields of certain types.

Addition 3

... ON *-INPUT

Effect

This condition dictates that the module mod is called only if the user entered an asterisk ("") as the first character in the input field of the dynpro 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 they were used after a standalone MODULE statement.

Addition 5

... AT CURSOR-SELECTION

Effect

The condition AT CURSOR-SELECTION has the same meaning as if it were used after a standalone MODULE statement.