Spool not getting created in batch job

Question

Hello experts,
We have a requirement of printing BA00, BA01 and LD00 from different application.
We have done same code for all BA00, BA01, and LD00.
Normally the code is working fine except in few cases, when batch job is created but spool is not created.
DATA: job_name TYPE tbtcjob-jobname,
              number   TYPE tbtcjob-jobcount,
              print_parameters TYPE pri_params,
              wv_pripar    TYPE pri_params,
              wv_arcpar    TYPE arc_params,
              wv_val       TYPE c VALUE 'X',
              wv_false     TYPE c VALUE 'X',
              gv_mandt     TYPE tsp01-rqclient,
              gv_user      TYPE tsp01-rqowner.
          CLEAR: gv_mandt, gv_user, number.
          gv_mandt = sy-mandt.
          gv_user  = sy-uname.
          job_name = 'DELIVERY_PRINTING'.
          CLEAR: range1.
          range1-sign = 'I'.
          range1-option = 'EQ'.
          range1-low = 'LD00'.
          CLEAR: range1-high.
          APPEND range1 TO range.
          CALL FUNCTION 'JOB_OPEN'
            EXPORTING
              jobname          = job_name
            IMPORTING
              jobcount         = number
            EXCEPTIONS
              cant_create_job  = 1
              invalid_job_data = 2
              jobname_missing  = 3
              OTHERS           = 4.
          IF sy-subrc = 0.
            SUBMIT sd70av2a WITH  rg_kschl IN range
                            WITH  rg_vbeln IN deli_tab
                            TO SAP-SPOOL
                          SPOOL PARAMETERS print_parameters
                          WITHOUT SPOOL DYNPRO
                          VIA JOB job_name NUMBER number
                          AND RETURN.
            IF sy-subrc = 0.
              CALL FUNCTION 'JOB_CLOSE'
                EXPORTING
                  jobcount             = number
                  jobname              = job_name
                  strtimmed            = 'X'
                EXCEPTIONS
                  cant_start_immediate = 1
                  invalid_startdate    = 2
                  jobname_missing      = 3
                  job_close_failed     = 4
                  job_nosteps          = 5
                  job_notex            = 6
                  lock_failed          = 7
                  OTHERS               = 8.
              IF sy-subrc <> 0.
              ENDIF.
            ENDIF.
            WAIT UP TO 10 SECONDS.
** to give the data to the printer***
*            CLEAR gv_rqident.
            SELECT SINGLE listident INTO gv_listident FROM tbtcp
                          WHERE jobname = job_name
                           AND  jobcount = number.
          IF sy-subrc = 0.
            MOVE gv_listident to gv_rqident.
            CALL FUNCTION 'RSPO_OUTPUT_SPOOL_REQUEST'
              EXPORTING
                spool_request_id = gv_rqident.
          ENDIF.
The same code is for all the output BA00, BA01 and LD00.
The issue is that for few batch jobs (which is created in the above code) , spool is not getting created.
Thanks and Regards,
Paritosh Pandey

Answer 1

Hi,
The code starting from WAIT UP TO 10 SECONDS. - not only does it look attrocious, is error prone (if no free process for executing batch job is available for 10 seconds, or if the job runs for more than 10 seconds, what will happen...?), but seems utterly unnecessary... Is there any reason immediate spool output can not be handled by simply setting PRINT_PARAMETERS-PRIMM = 'X'?
cheers,
Janis
Edit in:
Ok, i just read Document in spool but not printed... Do not use an output device relying on frontend access methods to do printing from background processing. Frontend is not available during background processing, period. To my knowledge there is no easy, clean solution to this problem other than defining and assigning, per user, output devices not relying on frontend printing. What if the dialog user has logged off by the time batch job finishes..? May the spool remain unprinted?
Has the SAP Basis refused to define output devices (I have hard time believing this...)? Well, tell them one time to stop being silly and if they do not cooperate, tell the owner of the requirement that it can not be implemented due to uncooperative Basis then... and that the users will have to keep going to SP01 and manualy start the output!
Message was edited by: Jānis B