|
EDITOR-CALL
Loads an ABAP program or
internal table into a text editor.
A D V E R T I S E M E N T
Syntax
EDITOR-CALL FOR <itab>…
EDITOR-CALL FOR REPORT <prog>…
Loads the internal table <itab>
or the program <prog> into a text editor, where you can edit it using standard
editor functions.
ELSE
Introduces a statement
block in an IF control structure.
Syntax
ELSE.
If the logical expression
in an IF statement is false, ELSE introduces the statement block to be executed
instead.
ELSEIF
Introduces a statement
block in an IF control structure.
Syntax
ELSEIF <logexp>.
If the logical expression
in an IF statement is false and <logexp> is true, ELSE introduces the statement
block to be executed instead.
END-OF-DEFINITION
Closes a macro definition.
Syntax
END-OF-DEFINITION.
This statement concludes a
macro definition introduced with DEFINITION.
END-OF-PAGE
Event keywords for
defining event blocks for list events.
Syntax
END-OF-PAGE.
Whenever the page footer
is reached while a list is being created, the runtime environment triggers the
END-OF-PAGE event, and the corresponding event block is executed.
END-OF-SELECTION
Event keywords for
defining event blocks for reporting events.
Syntax
END-OF-SELECTION.
Once a logical database
has read all of the required lines and passed them to the executable program,
the runtime environment triggers the END-OF-SELECTION event, and the
corresponding event block is executed.
ENDAT
Closes a statement block
in control level processing.
Syntax
ENDAT.
This statement concludes a
control level processing block introduced with AT.
ENDCASE
Closes a CASE control
structure.
Syntax
ENDCASE.
This statement concludes a
control structure introduced with CASE.
ENDCATCH
Closes a CATCH area.
Syntax
ENDCATCH.
This statement concludes
an exception handling block introduced with CATCH SYSTEM-EXCEPTIONS.
ENDCLASS
Closes a class definition.
Syntax
ENDCLASS.
This statement concludes a
class declaration or implementation introduced with CLASS.
ENDDO
Closes a DO loop.
Syntax
ENDDO.
This statement concludes a
loop introduced with DO.
ENDEXEC
Closes a Native SQL
statement.
Syntax
ENDEXEC.
This statement ends a
Native SQL statement introduced with EXEC SQL.
ENDFORM
Closes a subroutine.
Syntax
ENDFORM.
This statement concludes a
subroutine definition introduced with FORM.
ENDFUNCTION
Closes a function module.
Syntax
ENDFUNCTION.
This statement concludes a
function module introduced with FUNCTION.
ENDIF
Closes an IF control
structure.
Syntax
ENDIF.
This statement concludes a
control structure introduced with IF.
FETCH
Uses a cursor to read
entries from a database table.
Syntax
FETCH NEXT CURSOR <c> INTO <target>.
If the cursor <c> is
linked with a selection in a database table, FETCH writes the next line of the
selection into the flat target area <target>.
FIELD-GROUPS
Declares a field group for
an extract dataset.
Syntax
FIELD-GROUPS <fg>.
This statement defines a
field group <fg>. Field groups define the line structure of an extract dataset.
You can also define a special field group called HEADER: When filling the
extract dataset, the system automatically prefixes any other field groups with
this field group.
FIELD-SYMBOLS
Declares field symbols.
Syntax
FIELD-SYMBOLS <FS>
[<type>|STRUCTURE <s> DEFAULT <wa>].
Field symbols are
placeholders or symbolic names for other fields. Pointed brackets are part of
the syntax for field symbol names. The <type> addition allows you to specify the
type of a field symbol. The STRUCTURE addition forces a structured view
of the data objects that you assign to the field symbol.
FIND
Searches for patterns.
Syntax
FIND <p> IN [SECTION
OFFSET <off> LENGTH <len> OF] <text>
[IGNORING CASE|RESPECTING CASE]
[IN BYTE MODE|IN CHARACTER MODE]
[MATCH OFFSET <o>] [MATCH LENGTH <l>].
The system searches the
field <text> for the pattern <p>. The SECTION OFFSET <off> LENGTH <len> OF
addition tells the system to search only from the <off> position in the length <len>.
IGNORING CASE or RESPECTING CASE (default) specifies whether the search is to be
case-sensitive. In Unicode programs, you must specify whether the statement is a
character or byte operation, using the IN BYTE MODE or IN CHARACTER MODE
(default) additions. The MATCH OFFSET and MATCH LENGTH additions set the offset
of the first occurrence and length of the search string in the fields <p> and
<l>.
FORM
Defines a subroutine.
Syntax
FORM <subr> [USING …
[VALUE(]<pi>[)] [TYPE <t>|LIKE <f>]… ]
[CHANGING… [VALUE(]<pi>[)] [TYPE <t>|LIKE <f>]… ].
Introduces a subroutine
<form>. The USING and CHANGING additions define the subroutine’s
parameter interface. The subroutine end with ENDFORM.
FORMAT
Sets formatting options
for list output.
Syntax
FORMAT… <optioni>
[ON|OFF]…
The formatting options
<option i
> (such as color) set in the
FORMAT statement, apply to all subsequent output until they are turned off using
the OFF option.
FREE
Release space in memory.
Syntax
FREE <itab>.
FREE MEMORY ID(<key>).
FREE OBJECT <obj>.
This statement deletes an
internal table, a data cluster in ABAP memory, or an external object in OLE2
Automation, depending on the variant of the statement used.
FUNCTION
Defines a function module.
Syntax
FUNCTION <func>.
Introduces the function
module <func>. This statement is not entered in the ABAP Editor, but is
automatically generated by the Function Builder in the ABAP Workbench. The
function module definition ends with the ENDFUNCTION statement
FUNCTION-POOL
Introduces a function
group.
Syntax
FUNCTION-POOL.
The first statement in a
function group. This statement is not entered in the ABAP Editor, but is
automatically generated by the Function Builder in the ABAP Workbench. A
function group is an ABAP program that contains function modules.
GET
Event keyword for defining
event blocks for reporting events.
Syntax
GET <node> [FIELDS <f1>
<f 2>…].
Only occurs in executable
programs. When the logical database has passed a line of the node <node> to the
program, the runtime environment triggers the GET event, and the corresponding
event block is executed. You can use the FIELDS option to specify explicitly the
columns of a node that the logical database should read.
GET BIT
Reads an individual bit.
Syntax
GET BIT <n> OF <f> INTO
<g>.
Reads the bit at position
<n> of the hexadecimal field <f> into the field <b>.
GET CURSOR
Gets the cursor position
on a screen or in an interactive list event.
Syntax
GET CURSOR FIELD <f>
[OFFSET <off>] [LINE <lin>]
[VALUE <val>] [LENGTH <len>].
GET CURSOR LINE <lin>
[OFFSET <off>] [VALUE <val>] [LENGTH <len>].
At a user action on a list
or screen, the statement writes the position, value, and displayed length of a
field or line into the corresponding variables.
GET DATASET
Syntax
GET DATASET <dsn>
[POSITIONS <pos>]
[ATTRIBUTE <attr>].
Gets the attributes of a
file opened using OPEN DATASET. The POSITIONS additions writes the current
read/write position to the field <pos>. The ATTRIBUTE addition writes the
attributes to a structure, <attr>, of the type DSET_ATTRIBUTES.
GET LOCALE LANGUAGE
Gets the current text
environment.
Syntax
GET LOCALE LANGUAGE <lg>
COUNTY <c> MODIFIER <m>.
Returns the current
language, country ID and any modifier into the corresponding variables
GET PARAMETER
Gets an SPA/GPA parameters
Syntax
GET PARAMETER ID <pid>
FIELD <f>.
Writes the value of the
SPA/GPA parameter <pid> from the user-specific SAP memory into the variable <f>.
GET PF-STATUS
Gets the current GUI
status.
Syntax
GET PF-STATUS <f> [PROGRAM
<prog>] [EXCLUDING <itab>].
Returns the name of the
current GUI status (the same as SY-PFKEY) into the variable <f>. The PROGRAM
addition writes the name of the ABAP program to which the status belongs into
the variable <prog>. The EXCLUDING addition returns a list of all currently
inactive function codes into the internal table <itab>.
GET PROPERTY
Gets a property of an OLE2
Automation object.
Syntax
GET PROPERTY OF <obj> <p>
= <f>.
Writes the property <p> of
an external OLE2 Automation object to the variable <f>.
GET REFERENCE
Gets a data reference.
Syntax
GET REFERENCE OF <obj>
INTO <dref>.
Writes a data reference to
an existing data object <obj> to the data reference variable <dref>.
GET RUN TIME FIELD
Measures the runtime in
microseconds.
Syntax
GET RUN TIME FIELD <f>.
The first time the
statement is executed, the variable <f> is set to zero. In each subsequent call,
the runtime since the first call is written to <f>.
GET TIME
Synchronizes the time.
Syntax
GET TIME [FIELD <f>].
Refreshes the system
fields SY-UZEIT, SY-DATUM, SY-TIMLO, SY-DATLO, and SY-ZONLO. The FIELD addition
fills the variable <f> with the current time.
GET TIME STAMP FIELD
Returns a time stamp.
Syntax
GET TIME STAMP FIELD <f>.
Returns the short or long
form of the current date and time, depending on whether the variable <f> has the
type P(8) or P(11). The long form returns the time correct to seven decimal
places.
HIDE
Stores information about
list lines.
Syntax
HIDE <f>.
While the list is being
created, this statement stores the contents of the field <f> and the current
line number in the internal HIDE area When the cursor is positioned on a line in
an interactive list event, the stored value is returned to the field <f>.
|
