ABAP_to_the_Future

Designing a Report Interface 10.2
The following information describes the steps in a bit more detail:
1. Create Container (Optional)
For some reports, the program has to create an object to represent a container
and pass it on to the UI framework; this container defines where the report
lives on an SAP screen. In some cases, the container and screen are created by
the programmer. (However, it’s also possible to automate the creation of both
the screen and container.)
2. Initialize (Generic)
The program executes an initialization routine, filling variables with a mixture
of hard-coded values and user input from the selection screen. These variables
are filled in based on a routine created by the programmer (the nature of the
routine varies wildly depending on the UI framework in use).
3. Application-Specific Changes (Specific)
The program executes application-specific routines (column definitions, sorting,
etc.) that were written by the programmer.
4. Display (Generic)
The program displays the report, which, again, is done based on code written
by the programmer.
As you can see, you’ve got your work cut out for you! Each step will need one or
more method definitions in order to get the job done (these method definitions
are listed in Figure 10.3). But don’t worry—the rest of this section will walk you
through the process of defining these methods.
Figure 10.3 View Interface: Methods
415