Skip to Content
0
Jun 09, 2020 at 07:51 AM

cl_salv_table - container handling for single click event

264 Views

Hi all,

maybe this a really old feshion topic and discussed many times before. But I did not find a good matching thread so far.

I am using SALV for showing some data in a regaulr report.

Now I would like to enhance the functionality and add a refreshing functionality. This refresh should be also executed in some specific cases (i.e. reprocessing data).

Right now I did not use a container for viusualization of the SALV.

As customer specific functions can be justed added by using a container I set "cl_gui_container=>default_screen" to factory class of SALV. This works fine in a first moment.

As the SALV contains also some events (i.e. showing application log by using function module BAL_DSP_LOG_DISPLAY) I recognized that the default screen was blocked with SALV export. Further screen will be loaded.

My question is now:

Do I have to create a screen with customer container which will be assigend to facotry class of SALV (not using cl_gui_container=>default_screen) to handle also "call transaction" and other funcion which seems to use also the default screen? Or do I have any other option to avoid this?