Get Example source ABAP code based on a different SAP table
• GET node ABAP Statement
GET node Short Reference
ABAP_SYNTAX_OBS GET node $[LATE$] $[FIELDS f1 f2 ...$].
ABAP_ALTERNATIVES: 1 GET node $[FIELDS f1 f2 ...$]. 2 GET node LATE $[FIELDS f1 f2 ...$].
ABAP Addition ... FIELDS f1 f2 ...
What does it do? The statement GET is only intended for use in executable programs that are linked with a logical database. GET can be used to handle two types of events while executable program of this type are processing:
Read events of the logical database
Closing a hierarchy level in the logical database If a list is written during a GET event, an automatic line break is created beforehand.
Latest notes:
The event blocks after GET are implemented internally as procedures. Declarative statements in GET event blocks create local data.
If logical databases are no longer used, it is no longer necessary to use the statement GET node either. ABAP_HINT_END
ABAP Alternative 1 GET node $[FIELDS f1 f2 ...$].
What does it do? This statement defines an event block whose event is raised by the ABAP runtime framework after an executable program is submitted, if the logical database with which the program is linked provides data in the work area node. The node work area must be declared using the NODES statement (or TABLES). The data can be processed in the event block. GET node also controls the behavior of the logical database.
The logical database reads all data from all nodes that are not defined for field selection using SELECTION-SCREEN FIELD SELECTION in the logical database and are located on the access path of the logical database superior to node. This is independent of whether GET event blocks have been defined for these nodes or not. However, only the data of those nodes can be accessed for which a work area was declared using the NODES (or TABLES) statement.
