Application Development and Automation Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

Regarding dialodue programming and table control

Former Member
0 Likes
352

Hi to all,

My query is :

1.) In dialogue module pool what is the sequence of events.

2.)When i use table control, why it is required to press display button twice to get the result in table control.

3.)What are the different attributes of a table control(like current_line etc) to process table control and give me a good example code to understand table control.

Thanks .

Bye...

1 REPLY 1
Read only

Former Member
0 Likes
328

Hi ,

In dialogue module pool sequence of events is

first PBO (process before output)

next PAI (process after input)

PBO will trigger before the screen displayed and

PAI will triger after entering input values.

<b>

different attributes of a table control</b>

FIXED_COLS

I

Number of lead columns. Transferred from Screen Painter. Can be changed in the ABAP program.

Fixed columns

LINES

I

Controls the scroll bar of the table control. At LOOP without internal table, LINES has the initial value zero and must be set in the program so that the scroll bar can be used. At LOOP AT <itab> the system sets this component to the number of rows of the internal table, whenever the table control is processed for the first time. The initialization event of a table control is not determined uniquely. If the corresponding internal table is not fully created at this event, then the LINES variable receives an incorrect value. If LINES in the LOOP loop is smaller as the number of rows of the internal table, then the table control contains blank rows at the end.

Therefore you should always set the LINES component explicitly in the ABAP program, including at LOOP AT <itab>. In this way you have full control over the dimensions of the vertical scroll bar and so can control the number of rows that are ready for input. Initialization should usually occur at PBO directly before the LOOP statement for the table control.

TOP_LINE

I

Top row at next PBO. Set at PAI by position of the vertical slider box. Can be changed in the ABAP program.

CURRENT_LINE

I

Current line in the loop. Set automatically in the LOOP loop to the value SY-STEPL +(TOP_LINE-1). No changes allowed in the ABAP program.

LEFT_COL

I

First displayed horizontal scrollable column after the lead column. Set at PAI by position of the horizontal slider box. LEFT_COL contains the absolute number of the column independent of any column shift by the user. Can be changed in the ABAP program.

LINE_SEL_MODE

I

Row selection mode: 0, 1, 2 for none, one or multiple rows can be selected. Transferred from Screen Painter. Can be changed in the ABAP program.

Row selection

COL_SEL_MODE

I

Column selection mode: 0, 1, 2 for none, one or multiple rows can be selected. Transferred from Screen Painter. Can be changed in the ABAP program.

Column selection

LINE_SELECTOR

C(1)

Flag (X or blank) for selection column. Transferred from Screen Painter. Can be changed in the ABAP program.

Selection column

H_GRID

C(1)

Flag (X or blank) for horizontal separators. Transferred from Screen Painter. Can be changed in the ABAP program.

Separators

V_GRID

C(1)

Flag (X or blank) for vertical separators. Transferred from Screen Painter. Can be changed in the ABAP program.

Separators

COLS

CXTAB_COLUMN

Control table for single columns (see below).

INVISIBLE

C(1)

Flag (X or blank) for visibility of entire table control

Please look in to the transaction DWDM. You have lots of examples for all type of controls with source code.

Regards.

Francis Reddy.