internal table with few records (Progress indicator)

[Former Member]

I have a it_tab internal table with 10 records.

loop at it_tab into wa_tab.

perform progress_indicator.

perform Process_data1.

perform process_data2.

perform process_data3.

endloop

the performs process_data1, data2 ,data3  has so many internal statements

and takes long runtime.

Now I have to show the user a progress indicator on the

screen.

form progress_indicator.

lv_percentage = ( sy-tabix / l_lines ) * 100.

  if lv_percentage gt lv_percent or lv_tabix eq 1.

    CALL FUNCTION 'SAPGUI_PROGRESS_INDICATOR'

        EXPORTING

           percentage = lv_percentage

           text       = lv_text.

   lv_percent = lv_percentage.

  endif.

endform,

I am facing problem that the progress indicator

does not show until the loop ends, it just appears

once , I want to show the indicator continuously

on the screen as long as the loop runs.

[Former Member]

I have a it_tab internal table with 10 records.

loop at it_tab into wa_tab.

perform progress_indicator.

perform Process_data1.

perform process_data2.

perform process_data3.

endloop

the performs process_data1, data2 ,data3  has so many internal statements

and takes long runtime.

Now I have to show the user a progress indicator on the

screen.

form progress_indicator.

lv_percentage = ( sy-tabix / l_lines ) * 100.

  if lv_percentage gt lv_percent or lv_tabix eq 1.

    CALL FUNCTION 'SAPGUI_PROGRESS_INDICATOR'

        EXPORTING

           percentage = lv_percentage

           text       = lv_text.

   lv_percent = lv_percentage.

  endif.

endform,

I am facing problem that the progress indicator

does not show until the loop ends, it just appears

once , I want to show the indicator continuously

on the screen as long as the loop runs.

[RaymondGiuseppi]

try

lv_percentage = ( sy-tabix * 100 ) / l_lines.

(Clock is displayed if percentage is at least 1, here each field is an integer so dividing gives only 0 until the last record where it gives 100)

Regards,

Raymond

PS: Read theRules of Engagement

[amy_king]

Hi Kiran,

This seems to be a re-phrasing of your other discussion created yesterday, I would try to keep all the information in a single discussion so that folks replying have all the information.

Cheers,

Amy

[ThomasZloch]

Yes, please stick to one discussion per issue, follow up on older ones, also try solving problems yourself before posting, if you succeed, your learning curve will be steeper.

Locked.

Thomas