07-28-2016 10:14 AM
Hi,
I am trying to submit a report via job, but the problem is that the report has a selection screen which I can't skip.
SELECTION-SCREEN BEGIN OF SCREEN 100.
PARAMETERS:
<p_par> TYPE <type>.
SELECTION-SCREEN END OF SCREEN 100.
I can't change this report.
I am able to pass the parameter via an rsparams table, but the selection screen is blocking the job.
This is how I submit the job:
SUBMIT <prog> AND RETURN
WITH SELECTION-TABLE lt_job_parameters
VIA JOB lv_job_name
NUMBER lv_jobcount.
Any help will be appreciated.
Thanks,
07-28-2016 12:34 PM
As far as I know, calling a selection-screen manually (CALL SELECTION-SCREEN) acts exactly like a standard screen.
It sounds like only batch input will help you in such case.
07-28-2016 10:36 AM
I don't understand, you submit the program in a background job. What happens exactly?
07-28-2016 10:46 AM
The job is blocked when it reaches the statement
CALL SELECTION-SCREEN 100.
07-28-2016 10:38 AM
Instead by submitting with selection-table can you try with option submit <Prog> with <p_par> = <p_par>.
07-28-2016 10:49 AM
Same as before, the job is blocked when it reaches
CALL SELECTION-SCREEN 100.
07-28-2016 10:55 AM
For a start, try to add the addition USING SELECTION-SCREEN 100 to your SUBMIT statement.
07-28-2016 10:59 AM
07-28-2016 11:23 AM
Yep, the problem is, that there is a CALL SELECTION-SCREEN 100 in the called program.
While the "start" selection screen is closed automatically after been filled in batch processing, a selection screen called with CALL SELECTION-SCREEN must be closed explicitly.
I'll check if I can find how to do that ...
07-28-2016 11:22 AM
Why do you have a CALL SELECTION-SCREEN in the submitted program? I's no sense in a background job. You must re-design your program.
07-28-2016 11:24 AM
Problem is that I am only consuming the report, I can't change it.
Is there no way around this?
07-28-2016 12:31 PM
Unfortunately no.
A CALL SELECTION-SCREEN in the submitted program is like a CALL SCREEN. You cannot handle it using SUBMIT.
07-28-2016 12:34 PM
As far as I know, calling a selection-screen manually (CALL SELECTION-SCREEN) acts exactly like a standard screen.
It sounds like only batch input will help you in such case.
07-28-2016 12:44 PM
07-28-2016 12:49 PM
CALL TRANSACTION USING
You must connect a transaction code to the program. Call the transaction with a BDC table in a report and submit that via job.
07-28-2016 12:57 PM