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

interactive reporting

Former Member
0 Likes
445

i designed an alv report which when you click a primary key item transfer is controlled to transaction iw52 to make some changes to the notification. when i click back to go back to my report i want the report to dispplay the changes which i would have done. below is the code i used to call transaction iw52

SET PARAMETER ID 'IQM' FIELD gt_notif-gv_qmnum.

CALL TRANSACTION 'Iw52' AND SKIP FIRST SCREEN.

1 ACCEPTED SOLUTION
Read only

uwe_schieferstein
Active Contributor
0 Likes
415

Hello Timothy

You have to encapsulate data selection in your ALV report. For example, you have a routine that selects the data based on the selection criteria (routine SELECT_DATA).

I assume that you call transaction IW52 either in an event handler method or at PAI of the dynpro displaying the ALV list.

The easy case is when the transaction is called at PAI. Simply add the following coding:

  perform SELECT_DATA.  " refreshes output itab and selects data again

At PBO of your dynpro you probably have the following coding:

" Container for displaying ALV grid has not been created yet -> create
  IF ( go_container IS NOT BOUND ).
    CREATE OBJECT go_container ...

  ELSE.
    go_grid->refresh_table_display( ).  " refresh ALV list display
  ENDIF.

If you call the transaction within an event handler method then add the following coding in the event handler:

  CALL METHOD cl_gui_cfw=>set_new_ok_code( 'REFRESH' ).  " triggers PAI

And at PAI at the following lines:

  CASE gd_okcde.
    ...

   WHEN 'REFRESH'.
     perform SELECT_DATA.

   WHEN others.
   ENDCASE.

Regards

Uwe

2 REPLIES 2
Read only

Former Member
0 Likes
415

hi

set refresh field in catalog as 'X'

regards

ravish

<b>reward if useful</b>

Read only

uwe_schieferstein
Active Contributor
0 Likes
416

Hello Timothy

You have to encapsulate data selection in your ALV report. For example, you have a routine that selects the data based on the selection criteria (routine SELECT_DATA).

I assume that you call transaction IW52 either in an event handler method or at PAI of the dynpro displaying the ALV list.

The easy case is when the transaction is called at PAI. Simply add the following coding:

  perform SELECT_DATA.  " refreshes output itab and selects data again

At PBO of your dynpro you probably have the following coding:

" Container for displaying ALV grid has not been created yet -> create
  IF ( go_container IS NOT BOUND ).
    CREATE OBJECT go_container ...

  ELSE.
    go_grid->refresh_table_display( ).  " refresh ALV list display
  ENDIF.

If you call the transaction within an event handler method then add the following coding in the event handler:

  CALL METHOD cl_gui_cfw=>set_new_ok_code( 'REFRESH' ).  " triggers PAI

And at PAI at the following lines:

  CASE gd_okcde.
    ...

   WHEN 'REFRESH'.
     perform SELECT_DATA.

   WHEN others.
   ENDCASE.

Regards

Uwe