ABAP Keyword Documentation → ABAP - Reference → Obsolete Language Elements → Obsolete User Dialogs → Obsolete statements of the screen flow logic
FIELD - VALUES, SELECT
Other versions: 7.31 | 7.40 | 7.54
Obsolete Syntax
Variants
1. FIELD f VALUES ([[NOT] val1], [[NOT] val2], ...
[[NOT] BETWEEN vali AND valj], ...).
2. FIELD f SELECT *
FROM dbtab
WHERE col1 = f1 AND col2 = f2 ...
[INTO wa]
WHENEVER [NOT] FOUND
SEND {ERRORMESSAGE|WARNING} [num [WITH p1 ... p4]].
Effect
These variants of the statement FIELD
can be used in the event block at PAI in the dynpro flow logic. They compare the content of the dynpro field f either with entries from a value list or with the results of a database access.
These types of input checks in the dynpro flow logic are executed after the automatic input checks and
before the self-defined input checks in the ABAP program. The specified value list or the results set
from the database accesses overrule the automatic input helps from ABAP Dictionary. They are themselves
overruled by the events POH and POV. The additions VALUES and SELECT
have no influence on the effect of the statement FIELDS on the data transport from the dynpro to the ABAP program.
Note
These variants are supported only for reasons of compatibility. Replace them by checks within the ABAP program.
Variant 1
FIELD f VALUES ([[NOT] val1], [[NOT] val2], ...
[[NOT] BETWEEN vali AND valj], ...).
Effect
A value list is specified by entries (in parentheses and separated by commas) after the addition VALUES.
The content of the dynpro field f can be compared with single values
val1,val2 ... and with value ranges [vali,valj]. The result of each
of the comparisons can be negated using the NOT operator. The comparison
fields val must be placed in inverted commas and specified in uppercase letters. The content must be part of the value ranges of the data types CHAR or NUMC from ABAP Dictionary.
If a comparison is not true, an error message appears in the status bar of the current GUI window and the associated input field is made ready for input again.
Example
Checks the input field for an airline.
PROCESS AFTER INPUT.
FIELD carrier
VALUES ('AA', NOT 'BA', BETWEEN 'QF' AND 'UA').
Variant 2
FIELD f SELECT * FROM dbtab
WHERE col1 = f1 AND col2 = f2 ...
[INTO wa]
WHENEVER [NOT] FOUND
SEND {ERRORMESSAGE|WARNING} [num [WITH p1 ... p4]].
Effect
When the statement FIELD is executed, the addition SELECT
searches for a row of the database table dbtab whose primary key fields
col1 col2 ... match the contents of the dynpro fields f1 f2 .... The
database table dbtab must be defined in ABAP Dictionary. In the WHERE
condition, all primary key fields of the database table that are specified in AND comparisons must be specified with an equal sign (=).
Depending on whether the addition NOT is specified or not, an error or warning
message is sent if no entries or only one entry was found in the database table. In both cases, the
input field for dynpro field f is made ready for input again. The message
class of the message to be sent must be two characters long and is taken from the first two places of
the value specified after the addition MESSAGE-ID of the introductory statement
of the associated ABAP program. If a message class is not specified there, a standard message is sent.
The message number can be specified as a numeric literal num. If the message
contains placeholders, they can be filled with up to four values p1 to
p4 as in the ABAP statement MESSAGE with the addition WITH. The placeholders can be specified either as text literals or as dynpro fields.
If a row is found, its content can be assigned to a table work area wa whose
structure must match the row type of dbtab. A table area like this is declared in the dynpro by adopting dynpro fields from ABAP Dictionary.
Note
Without the addition INTO, the addition SELECT
is similar to a subquery in Open SQL. If the addition INTO is used, the
SELECT syntax above can be used as a standalone statement in the dynpro flow logic, that is,
without the FIELD statement. However, the use of a dynpro statement SELECT is also obsolete. Replace it with the respective Open SQL statement in the ABAP program.
Example
Checks whether a row with the same primary key exists in the database table spfli
for the dynpro fields carrier and connect . The
associated ABAP program must contain an appropriate MESSAGE-ID addition in the introductory statement.
PROCESS AFTER INPUT.
FIELD connect
SELECT *
FROM spfli
WHERE carrid = carrier AND connid = connect
WHENEVER NOT FOUND SEND ERRORMESSAGE 107
WITH carrier connect.