![]() ![]() The only way to programmatically call your report or transaction, say, from a different screen or function module, would would be the SUBMIT … AND RETURN or CALL TRANSACTION statements.īut these two come with serious drawbacks: Both SUBMIT … AND RETURN and CALL TRANSACTION Problems with SUBMIT … AND RETURN and CALL TRANSACTION ![]() However, you cannot easily integrate it into a seamless dialog sequence.Your report can be started as a standard report or you can create a transaction code to embed it into a user role or an area menu. ![]() Once your report is fully functional and neatly polished, you still have serious limitations left: Gt_mydata TYPE STANDARD TABLE OF mytable.ĭepending on how cleanly you like to program, you might eliminate the obsolete TABLES statement, pass the select-options and table as parameters (to avoid accessing global data in form routines), and use a local application class with (mostly private) methods instead of form routines. It will probably look something like this: REPORT zalv. Suppose you have a simple report that consist of a selection screen and an ALV grid (hopefully programmed with the new SALV service classes). If you strive for sophistication and flexible reuse, you should consider some of the advanced programming techniques I discuss in this weblog. It’s quick and simple, but it comes with some limitations. ABAP report programming has its advantages. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |