other_dobj
is output, this output is overwritten. If the list cursor is
positioned above the output of other_dobj , then the output also
appears above.
The data object other_dobj should be defined globally in the
current program. Using local data objects in procedures may produce
unwanted results, for example if the components of the same structures
are used in different procedures.
The data object other_dobj can also be specified as a field
symbol or as a dereferenced data reference. In this case, the field
symbol or data reference must not point to a row of an internal table.
Example ABAP Coding Table-like output of flight connections.
DATA: carrid TYPE spfli-carrid,
connid TYPE spfli-connid.
WRITE: 10 'Carrier', 40 'Connection'.
ULINE.
SELECT carrid connid
FROM spfli
INTO (carrid,connid).
WRITE: / carrid UNDER 'Carrier',
connid UNDER 'Connection'.
ENDSELECT.
ABAP_ADDITION_3 ... NO-GAP
What does it do? The list cursor is
positioned directly after the output (and not at the position after the
next position in the list buffer).
Example ABAP Coding The output of the two WRITE statements is
"NoGap".
WRITE: 'No' NO-GAP, 'Gap'.
ABAP_ADDITION_4 ... QUICKINFO info
What does it do? A tooltip is associated
with the output. If the mouse cursor is placed on the output area of
dobj , the content of info appears in a colored rectangle.
info expects a character-like data object with length 40.
The addition QUICKINFO has no effect on input-ready fields and
line elements . If a list output is
overwritten by another output, then no tooltip for the overwritten field
appears at or after the position where overwriting starts.
Example ABAP Coding Additional information on the output of date and time.
WRITE: (10) sy-datum QUICKINFO 'Date of list creation',
(8) sy-uzeit QUICKINFO 'Time of list creation'.
Runtime Exceptions See WRITE - TO
Documentation extract taken from SAP system, � Copyright SAP AG. All rights reserved