ABAP Keyword Documentation → ABAP − Reference → Obsolete Language Elements → Obsolete User Dialogs → Obsolete statements of the screen flow logic → FIELD - VALUES, SELECT
Dynpros, Obsolete Input Help Using SELECT
The example illustrates how obsolete dynpro input help works.
Other versions: 7.31 | 7.40 | 7.54
Source Code
REPORT demo_dynpro_f4_help_dynpro.
DATA: carrier(3) TYPE c,
connection(4) TYPE c.
CALL SCREEN 100.
MODULE cancel INPUT.
LEAVE PROGRAM.
ENDMODULE.
Description
The static next dynpro number of dynpro 100 is 100. The input fields are taken from the program fields
carrier
and connection
. The function code of the
pushbutton is CANCEL with the function type E.The dynpro field carrier
is assigned the search help DEMO_F4_DE with the search help parameter CARRID, which accesses the database table SCARR. The screen flow logic is as follows:
PROCESS AFTER INPUT.
MODULE cancel AT EXIT-COMMAND.
FIELD carrier VALUES ('AA', 'LH').
FIELD connection SELECT *
FROM spfli
WHERE carrid = carrier
AND connid = connection.
When selecting the F4 help for the individual fields, the user is shown the following types of input help:
- For the airline carrier, the search help displays the list of airline names and copies the airline
ID for the selected row into the input field. If the airline code is not one of those listed in the
VALUES
list of the flow logic, the input check triggers an error message in the PAI event. The search help, therefore, overrides theVALUES
addition for the input help, but not for the input checks. For this reason, do not use aVALUES
addition here.
- For the connection, the flow logic displays the list of selected entries from the database table SPFLI and copies the connection number of the selected row into the input field.