SAP NetWeaver AS ABAP Release 740, ©Copyright 2014 SAP AG. All rights reserved.
ABAP Keyword Documentation → ABAP − Reference → Obsolete Language Elements → Obsolete Processing of External Data → Logical Databases (Obsolete) → Logical Databases - Statements → Statements for Logical Databases →Obsolete Syntax
CHECK SELECT-OPTIONS.
Effect
This form of the statement CHECK for exiting processing blocks is only intended for use in executable programs that are associated using a logical database, and then only in the event blocks for the reporting events GET. It must not be used in methods.
The statement checks whether the content of the interface work area that was filled for the current GET event by the logical database fulfills the conditions in all selection tables that are associated with the current node of the logical database. The name of the node is copied statically from the next highest GET statement in the program. The following restrictions apply:
If the conditions in one of the selection tables are not met, and the statement is not listed within a loop, then the GET event block is exited and the runtime environment behaves as with the other variant of CHECK used for exiting processing blocks. If the statement is listed within a loop, then only the current loop pass is exited.
Notes
Example
Exiting a GET event block if the content of the components seatsmax and seatsocc of the interface work area sflight do not fulfill the conditions in the selection tables s_max or s_occ. Before the program can run, it must be associated with the logical database F1S.
NODES sflight.
SELECT-OPTIONS: s_max FOR sflight-seatsmax,
s_occ FOR sflight-seatsocc.
GET sflight.
cl_demo_output=>write( |{ sflight-carrid } {
sflight-connid }| ).
CHECK SELECT-OPTIONS.
cl_demo_output=>write( |{ sflight-seatsmax } {
sflight-seatsocc }| ).
END-OF-SELECTION.
cl_demo_output=>display( ).
Non-Catchable Exceptions