Total column not changed between header & detailed screen

Question

I have a report with header data contains contracts information and detailed data contains orders, debit credit memo related to the contracts.  I write the report using CL_SALV_TABLE to display  contract value, usage  in full ALV_GRID. When I double click on a contract line, it will go to the second screen to show all orders related to that contract.  The second screen with orders information will be in a screen on a container with all standard function ( Export list to Excel, Word format etc..), sort, total and sub total) and a push button to go back to first screen.
  The report works fine but when I am on the second screen, I total and sub total the amount on that screen in order to check with total value in header record and it total up correctly by currency.
But when I go back to the first screen, select a different contract record,  double click on the line to get to the order info screen,  all order data display correctly except that the total column still show amount from the previous detailed screen.  If I select the column again and click the total, it will total correctly.   I did refresh the data in the screen before go back to first screen but it does not solve the problem.
DOES ANYONE HAVE A SIMILAR SYMPTON LIKE THIS? 
Thanks for your advice.
On the order detailed screen, I create a container with screen 100 and write PAI, PBO like this:
Screen 100:
process before output.
  module status_0100.
  module load_data_to_control.   "Load usage data to screen
process after input.
module user_command_0100.
module status_0100 output.
  set pf-status 'PF100'.
  set titlebar 'T100'.
endmodule.  
module load_data_to_control output.
  if gr_cont is not bound.
    create object gr_cont
      exporting
        container_name = 'CONTAINER_100'
      exceptions
        others         = 1.
    if  sy-subrc <> 0.
      message a052(zvn) with
      ' No container object found'.
    endif.
    try.
        cl_salv_table=>factory(
        exporting
     list_display   = list_display
          r_container = gr_cont
      container_name =
        importing
          r_salv_table = gr_alv_2
        changing
          t_table = gt_orders
      catch cx_salv_msg into gr_error.
    endtry.
    perform set_functions.        " Set all standard function in screen 100
    perform set_column_order using gr_alv_2.       "Set column format, display
    perform handle_events.                       "Register events for selection mode & user commands
     Display order screen 0100
    gr_alv_2->display( ).
  else.
    gr_alv_2->refresh( ).
endif.
module user_command_0100 input.
  data: wa_d type gt_dtab,
        ls_contract type vbeln,
        ls_order    type vbeln,
        ls_invoice  type vbeln,
        ls_belnr type belnr_d,
        ls_row   type char10.
  data: l_text type char128.
    case  sy-ucomm.
    when 'RETURN' or 'BACK' or 'EXIT' or 'CANCEL'.
*... refresh the table in order to see the new data
      gr_alv_2->refresh( ).
      leave to screen 0.
    when others.
  endcase.
endmodule.                 " USER_COMMAND_0100  INPUT

Answer 1

Hi ,
When you are using the CL_SALV_TABLE, what is the use of screen 100. Better populate the evnts table in CL_SALV_TABLE
Cheers
Pavan