How to refresh an ALV (CL_SALV_TABLE) after a parallel process

Question

Hello all,
I have created a list using CL_SALV_TABLE. When you click on a line, a new mode must be opened. There, the user will fill in some data that must be retrieved and shown in the main list when the user closes the new mode. To do so Iu2019ve used u201CCALL FUNCTION func STARTING NEW TASK task CALLING meth ON END OF TASKu201D statement.
Iu2019ve tried to refresh the list within meth (called on end of task) but it doesn't work. I've also tried to get all the data again, but it prompts a short dump, set a new ok code using method cl_gui_cfw=>set_new_ok_code, even a WAIT until process is finished (not valid because I need process 1 active all the timeu2026)
SAP help says u201CThe SET USER-COMMAND u2018OKCDu2019 statement replaces the REFRESH SCREEN commandu201D
CALL FUNCTION 'function'
    STARTING NEW TASK w_taskname
    PERFORMING end_of_creation ON END OF TASK
    EXPORTING
       i_zzta         = ztztl_zzta
       i_manual_order = space
    EXCEPTIONS
       communication_failure = 1 MESSAGE w_msg
       system_failure        = 2 MESSAGE w_msg.
[u2026]
FORM end_of_creation USING p_taskname.
  RECEIVE RESULTS FROM FUNCTION 'function'
     IMPORTING
        e_zzta         = ztztl_zzta
     EXCEPTIONS
        communication_failure = 1 MESSAGE w_msg
        system_failure        = 2 MESSAGE w_msg.
  [Modify list]
  SET USER-COMMAND 'OKCD'. 
[u2026]
AT USER-COMMAND.
 CASE sy-ucomm.
    WHEN 'OKCD'.  
     Perform get_data.  
How can I have the same behaviour when using CL_SALV_TABLE??
Thanks in advance!

Answer 1

Hello Matt,<br><br>
does not work means that if I write the following within method ON END OF TASK, the report is not refreshed.
<br><br>
<pre>
o_alv->refresh( ).
</pre><br><br>
I've also tried:
<br><br>
<pre>
o_alv->refresh( ).
o_alv->display( ).
data: o_alv TYPE REF TO cl_salv_table</pre><br><br>
<pre>Short dump: RPERF_ILLEGAL_STATEMENT
Error analysis                                                                               
There is probably an error in the program                                                    
    "SAPLSLVC_FULLSCREEN".                                                                       
    The program was probably called in a conversion exit                                         
    or in a field exit. These are implemented by                                                 
    function modules called CONVERSION_EXIT_xxxxx_INPUT/OUTPUT or                                
    USER_EXIT_xxxxx_INPUT.                                                                       
    Conversion exits are triggered during screen field transports or                             
    WRITE statements, field exits during field transports from the                               
    screen to the ABAP/4 program.                                                                
    In this connection, the following ABAP/4 statements are not allowed:                                                                               
-  CALL SCREEN                                                                               
-  CALL DIALOG                                                                               
-  CALL TRANSACTION                                                                               
-  SUBMIT                                                                               
-  MESSAGE W... and MESSAGE I...                                                             
    -  COMMIT WORK, ROLLBACK WORK                                                                
    -  COMMUNICATION RECEIVE                                                                     
    -  STOP                                                                               
-  REJECT                                                                               
-  EXIT FROM STEP-LOOP                                                                               
Moreover, conversion exits for output conversion                                             
    (implemented by function modules called                                                      
    CONVERSION_EXIT_xxxxx_OUTPUT) do not allow                                                                               
-  MESSAGE E...                                                                               
to be used.
Trigger Location of Runtime Error                                                                
    Program                                 SAPLSLVC_FULLSCREEN                                  
    Include                                 LSLVC_FULLSCREENU01                                  
    Row                                     187                                                  
    Module type                             (FUNCTION)                                           
    Module Name                             REUSE_ALV_GRID_DISPLAY</pre><br><br>
But this short dump is expected since CALL FUNCTION - STARTING NEW TASK help says u201CIn the callback routine, you are not allowed to execute statements that interrupt the program execution or terminate a SAP LUW. Statements for list output are not executed.u201D<br><br>
Thanks Matt, I'll take a look at that forum, but I also tried a self list refresh using a timer and that prompted another short dump: LIST_TOO_MANY_LPROS -> "Error analysis: At present, the maximum permitted number of nested screen levels is restricted to 50." <br><br>
If I find a solution I'll let you know.<br><br>
<br><br>
Thank you!!
Edited by: Matt on Aug 26, 2009 1:16 PM