Does any one know the consequences of creating a dialog transaction and assigning a report (executable) program to it? This particular report program has several screens (but no selection screen and no START-OF-SELECTION code). Several dialog transactions were created for this report program for different screens.
Hi Ramki,
Why dont you use a transaction code for Report programs, instead of dialog program transaction code.
Because if you are trying to use a module pool transaction code, then its expecting only the blocks in PBO and PAI to be executed.
So incase all your screens are dialog it appears to be fine. But even here i would suggest call the normal report transaction and in start of selection have, call screen 100 or so on. That should be best.
Another point is INITIALIZATION event will also not be executed.
Pavan
Add a comment