ABAP's Dialog

Tomorrow system online, data is a mess, no one to mention bugs, boring ing ....

Today talk about SAP Development Common Dialog Bar

General Individual dialog program can be directly built function Group, function group, general report program.

Basic is a unified style, the main program includes a series of subroutines, generally include: top (data definition), PBO (processing before screen output), PAI (screen event and logical management), FRM (Form package)

Output style is generally: TC table, common structure fields ...

General field logic in Pai, moudle xxx on input/request.

1, INPUT: The value will be executed. REQUEST: Value change is not performed. There is a big difference between the two, the former is time-consuming and the latter very rigorous.

2, LOOP at TC: This can be easily understood as an electronic picture tube, from top to bottom, from left to right, output table content in turn. Screen control must be before or during the PBO loop, and data processing can be effective in loops or later (modify)

3, screen event receiving ok_code must be emptied in time, a series of other events such as rolling pulley will continue to trigger the previous Ok_code event. Especially generate documents, with new data!

4, TC add line, update line number 1) Any position, this situation is generally in the PBO loop before the cycle of updating the serial number, the efficiency slightly affected.

                                      2) append blank line, modify auto-generated Insert_row l_line = l_selline  - <tc>-top_line + 1                                                ,         &NB Sp                   Insert initial line into <table> INDEX l_selline< Span class= "L0S55". (can be calculated directly at this time as the line number base)

5, screen control: can generally be in the status, or later. Button control alone with excluding, normal field can be edited, visible, etc., Screen-input,invisible&length

ABAP's Dialog