Syntax for the at first and at last Statements
The following is the syntax for the at first and at last statements.
loop at it.
---
at first.
---
endat.
---
at last.
---
endat.
---
endloop.
where:
it is an internal table and --- represents any number of lines of code (even zero).
Syntax for the at new and at end ff Statements
The following is the syntax for the at new and at end of statements.
sort by c.
loop at it.
---
at new c.
---
endat.
---
at end of c.
---
endat.
---
endloop.
where:
it is an internal table.
c is a component of it and --- represents any number of lines of code (even zero).
Syntax for the on change of Statement
The following is the syntax for the on change of statement.
on change of v1 or v2 . . .
---
[else.
---]
endon.
where:
v1 and v2 are variable or field string names.
. . . indicates that any number of or conditions might follow and --- represents any number of lines of code.
Syntax for FOR ALL ENTRIES
SELECT ... FOR ALL ENTRIES IN <itab> WHERE <cond> ...
<cond> may be formulated as described above. If you specify a field of the internal table <itab> as an operand in a condition, you address all lines of the internal table. The comparison is then performed for each line of the internal table. For each line, the system selects the lines from the database table that satisfy the condition. The result set of the SELECT statement is the union of the individual selections for each line of the internal table. Duplicate lines are automatically eliminated from the result set. If <itab> is empty, the addition FOR ALL ENTRIES is disregarded, and all entries are read.
The internal table <itab> must have a structured line type, and each field that occurs in the condition <cond> must be compatible with the column of the database with which it is compared. Do not use the operators LIKE, BETWEEN, and IN in comparisons using internal table fields. You may not use the ORDER BY clause in the same SELECT statement.
You can use the option FOR ALL ENTRIES to replace nested select loops by operations on internal tables. This can significantly improve the performance for large sets of selected data.
I hope it helps.
Thanks,
Vibha
<REMOVED BY MODERATOR>
Edited by: Alvaro Tejada Galindo on Apr 22, 2008 5:52 PM
Bluesky
