... If you’re familiar with REUSE_ALV_GRID_DISPLAY, then this mechanism of callback is know for you, if not, then in simply words it’s an kind of event handler. When RRI finish to fill the internal tables ...
... to hide it from us.
CL_GUI_ALV_GRID class cannot be used to display data without some effort, that’s why many of the beginners starts with the REUSE_ALV_GRID_DISPLAY function module or CL_SALV_TABLE ...
... table in two, three lines when you goes to the code you'll see it's nothing more than call of REUSE_ALV_GRID_DISPLAY... really old FM, which at the end use CL_GUI_ALV_GRID.
Direct reasons
&n ...
... more than alpha release. Basically what I try to get from this class: Fast CL_GUI_ALV_GRID creation Replacement of REUSE_ALV_GRID_DISPLAY and REUSE_ALV_GRID_DISPLAY_LVC for a simple ...
... to use OO ALV grid but REUSE_ALV_GRID_DISPLAY. Once you start with classes, switch to cl_gui_alv_grid. If you teach selection-screens don't mix it with SE51 screens, and so on. Give them time to learn ...
Many people still asks how to create field catalog for CL_GUI_ALV_GRID or REUSE_ALV_GRID_DISPLAY on a base of internal table. This is very easy since we have SALV classes, you could see it in ...
... but when you'd like to reuse them then third one (FM to call dynamic selection-screen in separate task) seems the best. First of all the question is why do we need separate task to call ...
... Selection-options which are the same as in MB51 should be coded with the same names so we can pass them to RM07DOCS by method call_mb51_static. I used REUSE_ALV here just to be able to do it faster, but ...
I've decided which way should I go, so now time to do it. I need to do following things to get what I desired: Create a function group or class to be able to reuse the solution in other programs also ...
... F4 call so we can directly restrict searched range with some data. Finally DISPFIELD if set makes the parameter on SHLP display only . So now lets go to the code. To be able to reuse it ...
... your customization table and it's name then you could store it as a FM or method in a class so you could reuse it without any rework. But to make it more understandable I keep it that way. report zab_select_configuration. ...