Previous sections described how to use additional tables, additional structures and additional fields to extend the scope of a query for evaluating data from a data source when you create an InfoSet. Additional tables, additional structures and additional fields have two common features:
The point (event) at which SAP Query reads an additional table or performs a calculation on an additional field depends on the logical database table, since the associated ABAP code becomes part of the GET event processing that table.
Any query for the InfoSet can address both additional fields and additional table fields, provided they are assigned to a field group of that InfoSet.
The previous sections also discussed parameters and selection criteria which you use to create selection options.
This topic discusses additional options which make additional tables, additional structures, additional fields, parameters and selection criteria more flexible and give you more room to move, but cannot be addressed in queries for the InfoSet. These options generate ABAP code for all queries of an InfoSet, but this is invisible to the end-user.
This code declares data to be used in a report (for example, variables for calculations).
This code appears under the event START-OF-SELECTION which precedes the first database access.
This code appears under the event GET for a logical database table, but does not depend on a particular additional field.
This code appears under the event GET LATE for a logical database table.
This code appears under the event END-OF-SELECTION either before or after output of the list.
This code is copied into every generated report and appears at TOP-OF-PAGE just before the instructions for output of the page header.
The diagram below shows how the structure of sections of code you can amend in a query report for the InfoSet FLBX (using the logical database F1S).
To request a list of defined codes of the InfoSet, select.
The following sections describe the different sections of code in more detail.