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.
If a field selection is defined in the logical database for nodes on the access path of the logical database superior to node and for which no GET event blocks are defined, all data is read only for the nodes with a NODES (or TABLES) statement exists. For nodes without a NODES (or TABLES) statement, only the key fields are read, since the logical database needs the key fields to build the access path. After the event block GET is ended regularly, the nodes that are inferior in the hierarchical structure of the logical database are processed (see PUT). At the end of a hierarchy level of the logical database, all fields of the work area node are set to hexadecimal zero. • LATE GET
ABAP Alternative 2 GET node LATE $[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 has read all records of node node. The same applies to node and FIELDS as to the previous variant. This event block can be used for final processing actions for the hierarchy level of the node. • FIELDS GET
ABAP Addition
What does it do? The addition FIELDS specifies that the logical database reads only the specified fields f1 f2 ... and the key fields for node node. To do this, the node must be defined for field selection in the logical database using SELECTION-SCREEN FIELD SELECTION . The content of the remaining fields of the work area is set to hexadecimal zero.
