JOB is created but SPOOL is not created - using SUBMIT stmt in WD

Question

Hi,
I am submitting report from WD. PFB the code i used. This is cuccessfully creating the JOB in SM37 and the status is 'Finished'. But when I click for the SPOOL, it is giving me an error 'No list available'.
I used the following code for submitting the program.
* call the FM 'JOB_OPEN' and create the job.
  SUBMIT ztest TO SAP-SPOOL
    WITH pnppernr-low EQ pernr
    WITH pnpbukrs-low EQ bukrs
    SPOOL PARAMETERS lv_print_parameters
    WITHOUT SPOOL DYNPRO
    VIA JOB lv_name NUMBER lv_number " job name and number created from JOB_OPEN
    AND RETURN.
* call the FM 'JOB_CLOSE' and close the job.
The submit stmt is working perfectly fine when executed directly..from R/3. The spool is also being created.
I tried debugging the same. This goes to the INITIALIZITION part of the program but no goin to START-OF-SELECTION.
Pls suggest if I am missing something in the code.
Thanks,
Teja.

Answer 1

>
teja wrote:
> Hi,
>
> I am submitting report from WD. PFB the code i used. This is cuccessfully creating the JOB in SM37 and the status is 'Finished'. But when I click for the SPOOL, it is giving me an error 'No list available'.
>
> I used the following code for submitting the program.
>
>
> * call the FM 'JOB_OPEN' and create the job.
>
>   SUBMIT ztest TO SAP-SPOOL
>     WITH pnppernr-low EQ pernr
>     WITH pnpbukrs-low EQ bukrs
>     SPOOL PARAMETERS lv_print_parameters
>     WITHOUT SPOOL DYNPRO
>     VIA JOB lv_name NUMBER lv_number " job name and number created from JOB_OPEN
>     AND RETURN.
>
> * call the FM 'JOB_CLOSE' and close the job.
>
>
> The submit stmt is working perfectly fine when executed directly..from R/3. The spool is also being created.
>
> I tried debugging the same. This goes to the INITIALIZITION part of the program but no goin to START-OF-SELECTION.
>
> Pls suggest if I am missing something in the code.
>
> Thanks,
> Teja.
Hi,
I guess this wont work. Didnt you get any dump ?
FM's with dialog screens,conversion exits would cause the webdynpro session to disconnect.