No result when I submit in background job a Z transaction

Question

Hi,
I design a screen with the screen painters for my Z report instead of using SELECTION-SCREEN command to build my screen of selection. In the PAI process, I launch the same report in backgound with JOB_OPEN,SUBMIT, JOB_CLOSE and nothing happens. I go to SM50 and no job is found and SM37 confirm me thatt the job has been launch and terminate without error.
My report, when the background checkbox is checked, launch it-self in background to insert rows in 2 Z tables. Theses 2 tasks take time and are not possible to process in foreground and the user can't wait after the result. That is why I Submit my report in background.
I made it in another program with a selection screen built with SELECTION-SCREEN command and I never had this problem.
It is possible to do a selection screen with the screenpainters and launchable in background or it is only possible with SELECTION-SCREEN command.

Answer 1

JOB_OPEN,SUBMIT, JOB_CLOSE and nothing happens. I go
to SM50 and no job is found and SM37 confirm me thatt
the job has been launch and terminate without error.
In SM50 you can see the jobs only while they are running. Since there is an entry in SM37, it means that the job has been initiated, so something did happen. Check the job log for the details (I strongly advise to add some messages in your program to track the progress).
You might also want to take a look at the FM SUBST_START_REPORT_IN_BATCH. Here is a code example that I've just written recently to force the report execution in the background (a message is displayed to the user but the report runs in a backrgound job):
PARAMETERS: p_vkorg TYPE tvko-vkorg OBLIGATORY MEMORY ID vko.
DATA: rspar TYPE TABLE OF rsparams,
      wa_rspar LIKE LINE OF rspar.
START-OF-SELECTION.
IF sy-batch IS INITIAL.
  wa_rspar-selname = 'P_VKORG'.
  wa_rspar-kind = 'P'.
  wa_rspar-low  = p_vkorg.
  APPEND wa_rspar TO rspar.
  CALL FUNCTION 'SUBST_START_REPORT_IN_BATCH'
    EXPORTING
      iv_repname                          = sy-repid
    TABLES
      tt_reportparam                      = rspar
   EXCEPTIONS
     variant_exist_check_failed          = 1
     variant_update_failed               = 2
     variant_update_not_authorized       = 3
     variant_update_no_report            = 4
     variant_update_no_variant           = 5
     variant_update_variant_locked       = 6
     variant_insert_failed               = 7
     variant_insert_not_authorized       = 8
     variant_insert_no_report            = 9
     variant_insert_variant_exists       = 10
     variant_insert_variant_locked       = 11
     variant_write_failed                = 12
     no_batch_service                    = 13
     no_server_list                      = 14
     batch_scheduling_failed             = 15
     OTHERS                              = 16
  IF sy-subrc = 0.
    MESSAGE ‘Report started in background’ TYPE ‘I’.
  ELSE.
    MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
            WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
  ENDIF.
ELSE.
<do stuff here>
ENDIF.
SUBST_START_REPORT_IN_BATCH actually calls JOB_OPEN, JOB_CLOSE but I just find it easier to use one FM instead of 2-3.