In ABAP Objects, the following statements cause an error message:
STOP.
Reason:
The STOP statement should only be used
during the events INITIALIZATION,
AT SELECTION-SCREEN, START-OF-SELECTION, and
GET. During execution of type 1 programs, it ends processing of the corresponding event blocks and triggers the sending of the
selection screen during the event
INITIALIZATION and in all other cases the event END-OF-SELECTION of the runtime environment. The old event concept of the
ABAP runtime environment is not supported by ABAP Objects.
In ABAP Objects, the following statement causes an error message:
REJECT [dbtab].
Reason:
The REJECT statement should only be used during the GET event while type 1 programs are being executed with
logical databases. Editing of the
current line of the node of the logical database is terminated with REJECT
and the next line of the same or of a lower lying node dbtab is read. The old event concept of the
ABAP runtime environment and the previous way of processing logical databases is not supported by ABAP Objects.
In ABAP Objects, the following syntax causes an error message:
CHECK SELECT-OPTIONS.
Correct syntax:
CHECK f IN seltab.
Reason:
This form of the statement CHECK is intended only for use during the event GET during execution of type-1 programs with
logical databases. The statement
checks whether the content of the work area, which was filled by the logical database for the current GET event, meets the conditions in all the
selection tables that are connected
with the current node in the logical database. The name of the node is taken statically from the next
highest GET statement in the ABAP program. Thus the statement
does not make sense outside of an GET event block. However, the previous event concept of the
ABAP runtime environment, that is, the previous way of processing logical databases, is not supported by ABAP Objects.