ABAP Keyword Documentation → ABAP - Reference → User Dialogs → Classic Lists → Creating Lists
Other versions: 7.31 | 7.40 | 7.54
This statement stores the content of a variable
dobj together with the current list line whose line number is contained in
sy-linno in the
hide area of the current list level. The data type of the variable
dobj must be
flat and no field symbols or components of
Boxed Components can
be specified that point to rows of internal tables, and no class attributes can be specified. The saved values can be read as followed:
Any user action on a displayed screen list that causes a list event assigns all values saved using
HIDEto the relevant variables.
If a list row of a list level is read or modified using the statements
READ LINE or
MODIFY LINE, all the values of this row saved using
HIDEare assigned to the relevant variables.
HIDEstatement works independently of whether the list cursor was set. In particular, variables for empty list rows can be stored (that is, rows in which the list cursor was positioned using statements like
HIDEstatement should be executed directly in the statement that has set the list cursor in the row.
HIDEstatement on a field symbol can cause runtime errors. The syntax check displays a warning.
Saving square numbers and cubic numbers for a list of numbers. The example shows that any variable can
be stored independently of the row content. In the real world, one would more likely save only the number
and execute the calculation, when required, in the the event block for
REPORT ... DATA: square TYPE i, cube TYPE i. START-OF-SELECTION. FORMAT HOTSPOT. DO 10 TIMES. square = sy-index ** 2. cube = sy-index ** 3. WRITE / sy-index. HIDE: square, cube. ENDDO. AT LINE-SELECTION. WRITE: square, cube.
Cause: The field is too long for
HIDEin a table row or a component in a table row is not possible.
HIDEin a local field is not possible.
HIDEis not possible on an empty page.
Cause: Illegal field
Cause: Permitted number of
HIDEstatements per list row exceeded