As we got a short description of ESDUS and ESRUO and connected FMs in previous parts, then now it's time for examples. Let's start with scenarios which I described in first part 1. When you open ...
... 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 ALV OO can be used ...
I can already call MB51 from previously created method but still I need to add an implicit enhancement into RM07DOCS so I'll be able to export results from MB51 and leave the program without displaying ...
I've got method to get selection screen parameters to table so I can call MB51 by submitting program RM07DOCS. Of course if I do that without any changes of parameters then I would get not this list ...
As I have needed types I can start to create methods which I need. Firstly fast method the read select-option data from any program which will call our class. I will use here FM RS_REFRESH_FROM_SELECTOPTIONS . ...
... which contains most of the fields which are available in MB51 (structure list in RM07DOCS). Just after t_list you'll find type tt_list which is just table type for t_list. *--------------------------------------------------------------------* ...
... both needs - additional fields and direct display of ALV grid. So I started to dig and debug to see what is possible to do and these possibilities I found: Copy program RM07DOCS (MB51) to Z-one and to ...