This statement concludes
an interface definition introduced with INTERFACE.
ENDLOOP
Closes a LOOP.
Syntax
ENDLOOP.
This statement concludes a
loop introduced with LOOP.
ENDMETHOD
Closes a method.
Syntax
ENDMETHOD.
This statement concludes a
method implementation introduced with METHOD.
ENDMODULE
Closes a dialog module.
Syntax
ENDMODULE.
This statement concludes a
dialog module introduced with MODULE.
ENDON
Closes a conditional
statement block.
Syntax
ENDON.
This statement ends a
conditional statement block introduced with ON CHANGE.
ENDPROVIDE
Closes a PROVIDE loop.
Syntax
ENDPROVIDE.
This statement concludes a
loop introduced with PROVIDE.
ENDSELECT
Closes a SELECT loop.
Syntax
ENDSELECT.
This statement concludes a
loop introduced with SELECT.
ENDTRY
Closes a TRY area.
Syntax
ENDTRY.
This statement concludes a
control structure introduced with TRY.
ENDWHILE
Closes a WHILE loop.
Syntax
ENDWHILE.
This statement concludes a
loop introduced with WHILE.
EVENTS
Defines events in classes
or interfaces.
Syntax
EVENTS <evt> EXPORTING..
VALUE(<ei>) TYPE type [OPTIONAL]�
The event <evt> can be
declared in the declaration part of a class or within an interface definition,
and may have EXPORTING parameters that are passed to the event handler. The
parameters are always passed by value.
EXEC SQL
Introduces a Native SQL
statement.
Syntax
EXEC SQL [PERFORMING
<form>].
Between EXEC SQL and the
ENDEXEC statement, you can include a database-specific Native SQL statement. The
PERFORMING addition allows you to pass a multiple-line selection line by line to
a subroutine.
EXIT
Leaves a loop or
processing block.
Syntax
EXIT.
Within a loop: The entire
loop is terminated, and processing continues with the first statement following
the loop. Outside a loop: Terminates the current processing block. In a
reporting event: Jumps directly to the output list.
EXIT FROM STEP-LOOP
Ends a step loop.
Syntax
EXIT FROM STEP-LOOP.
Terminates step loop
processing. A step loop is ais a way of displaying a table on a screen.
EXIT FROM SQL
Ends Native SQL
processing.
Syntax
EXIT FROM SQL.
This statement may occur
within a subroutine called using the PERFORMING addition in the EXEC SQL
statement. The entire subroutine is processed, but no more subsequent lines of
the selection are processed.
The data objects <fi>
or <g i>, or the data objects in the internal table <itab> are stored
as a data cluster in the cross-program ABAP memory of the current internal
session, in a cluster database table <dbtab>, or in the cross-transaction
application buffer of the table <dbtab>.
EXTRACT
Creates an extract dataset
and adds lines to it.
Syntax
EXTRACT <fg>.
With the first EXTRACT
statement of a program, the system creates the extract dataset and adds the
first extract record. In each subsequent EXTRACT statement, the new extract
record is added to the dataset. Each extract record contains exactly those
fields that are contained in the field group <fg>, plus the fields of the field
group HEADER (if one exists).
