This is a test message to test the length of the message box.
ABAP Quick Classes and Dynpros
Created by Software-Heroes

ABAP Quick - Classes and Dynpros


How do you best use local classes and screens with each other? And does the whole thing actually make sense?

How exactly do classes and screens work together? And can you actually link them meaningfully? Today we show you a solution how it can work.


Local class

We define the local class according to our requirements. We take the PBO and PAI of screen 2000 into scope and create a public attribute for the screen data. In this case, it is important that the visibility of the attributes on the screen is public, otherwise they cannot be accessed from our main program.


Here is the example class, how the implementation looks for our example:

      BEGIN OF ts_screen,
        bukrs TYPE t001-bukrs,
        text  TYPE text50,
      END OF ts_screen.

      ms_screen TYPE ts_screen.





  METHOD start.
    ms_screen-bukrs = '0815'.
    ms_screen-text = 'A random text'.

    CALL SCREEN 2000.

  METHOD pbo_2000.
    SET PF-STATUS '2000'.
    SET TITLEBAR '2000'.

  METHOD pai_2000.
    CASE sy-ucomm.



When defining the screen, we can then directly access the attributes via the global instance, read and store data in it. When storing the fields, it is only important to ensure that only public attributes of the instance can be used.


The disadvantage of this method is that the field properties cannot be used from the context of the variable, as with a global variable that was defined using TABLES. Another advantage is the decoupling from the main program and the global data. In the end, you will probably choose a hybrid approach for your solution.



The class is connected via the classic modules for PBO and PAI, but here you only need to call the methods and can implement the rest of the logic in the class, as in the example class above.


  go_app->pbo_2000( ).

MODULE pai_2000 INPUT.
  go_app->pai_2000( ).



After starting the report you will get the following result. The fields were filled before the screen was opened and are displayed correctly and can also be changed. The display of the menu and the processing of the user-command also work as desired.



Working with screens is now not a problem for you in the world of classes. You just have to make it clear to yourself at what time which methods are called and where your data is used. A hybrid approach with the definition of global structures via TABLES and the transfer of data to the class is recommended for the implementation of complex applications.

Included topics:
QuickDynproLocal class
Comments (0)

And further ...

Are you satisfied with the content of the article? We post new content in the ABAP area every Friday and irregularly in all other areas. Take a look at our tools and apps, we provide them free of charge.

ABAP Tools - Quick Actions und Highlighting (ABAP Unit)

Category - ABAP

With the last release of the ABAP Development Tools, Quick Actions were added for ABAP development in the ABAP Unit area. Here we take a closer look at them.


ABAP Quick - RFC Error handling

Category - ABAP

How do you actually handle errors when communicating via a destination in the function module? More about this in our tip.


ABAP Quick - CLEAR right

Category - ABAP

Delete correctly? In this article we want to take a look at when it makes sense to delete and how you can do it effectively.


ABAP Quick - Performance chained statements

Category - ABAP

Let's take a look at the performance when creating chained statements with DATA and FIELD-SYMBOL. Which variant will be ahead in terms of performance?


ABAP - ALV still relevant in 2022?

Category - ABAP

Today the joking question, do we still need reports that generate ALV outputs in 2022? In this article, we want to look into this question.