If you want to perform calculations or other operations which are not associated with certain additional fields, you can formulate ABAP code for the GET and GET LATE events of a logical database table when creating an InfoSet. The code for GET events is particularly important if you have defined parameters or selection criteria for the InfoSet. It is here that you must define the code to check whether a table line is to be evaluated or not.
As far as linking to logical database tables is concerned, ABAP code for the GET and GET LATE events is treated in each case like an additional field. The code becomes part of every query report generated for an InfoSet. Since that code is not assigned to any InfoSet, it is transparent to the end-user.
To create or maintain GET/GET LATE code for a logical database table from the InfoSet maintenance screen, choose the symbol Code, and GET, or GETLATE, with the F4 help.
If you chose one of these functions then first enter in an entry field, at the top right of the screen, a number for the sequence.
The sequence is only relevant for the code for the GET event. This code appears together with the code for additional fields and SELECT statements for linked additional tables in the GET event for the logical database table concerned.
Usually, the GET event code is used for initialization and precedes additional fields and additional tables in the sequence.
To ensure that query reports can be generated without problems, it is important that it is clear which fields are accessed in every piece of code. If some code contains ABAP statements that access certain fields implicitly, then an ABAP FIELDS statement must also be used in the code to ensure that all fields used are explicitly named. You can find an example of this and further information in Access Optimization in Queries.
If you want to assign the code to a different logical database table, you must delete the code and then redefine it.