REJECT

Variants:

1. REJECT.

2. REJECT dbtab.

This statement is not allowed in an ABAP Objects context. See REJECT not allowed.

Variant 1

REJECT.

Effect

This statement exits a GET event block when processing logical databases in executable programs.
Stops processing the current database table line provided by the logical database and resumes with the next line of the table on the same hierarchy level. Unlike the CHECK statement, REJECT is not context-sensitive but always leaves the current GET event block.

Variant 2

REJECT dbtab.

Effect

Similar to variant 1. In this case, however, dbtab is a table from the database hierarchy on a level no deeper than the current database table. Processing continues by reading the next record of the table dbtab.

Example

Logical database F1S
Hierarchy: SPFLI → SFLIGHT → SBOOK

NODES: SFLIGHT,
        SBOOK.

GET SFLIGHT.
    ...
GET SBOOK.
    ...
    REJECT 'SFLIGHT'.
    ...

REJECT cancels processing of the event 'GET SBOOK' and resumes with the processing of the event 'GET SFLIGHT'.

Note

The name of the subroutine containing the "PUT dbtab" statement must begin with PUT_dbtab.

Exceptions

Non-Catchable Exceptions

Cause: The table whose name is in the field dbtab is not active, that is, it is not in the current table in the database hierarchy. You can therefore not continue processing the next record in this table.
Runtime Error: REJECT_TABLE_NOT_FOUND

Related

CHECK, EXIT, STOP, RETURN

Additional help

Leaving Event Blocks