Application Development Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 

SUBMIT report via job and don't show selection-screen

Former Member
0 Kudos

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,

1 ACCEPTED SOLUTION

Former Member
0 Kudos

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.

14 REPLIES 14

Sandra_Rossi
Active Contributor
0 Kudos

I don't understand, you submit the program in a background job. What happens exactly?

0 Kudos

The job is blocked when it reaches the statement

CALL SELECTION-SCREEN 100.

sachin_yadav3
Active Participant
0 Kudos

Instead by submitting with selection-table can you try with option submit <Prog> with <p_par> = <p_par>.

0 Kudos

Same as before, the job is blocked when it reaches

CALL SELECTION-SCREEN 100.

horst_keller
Product and Topic Expert
Product and Topic Expert
0 Kudos

For a start, try to add the addition USING SELECTION-SCREEN 100 to your SUBMIT statement.

0 Kudos

Tried it, didn't work 😕

horst_keller
Product and Topic Expert
Product and Topic Expert
0 Kudos

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 ...

Sandra_Rossi
Active Contributor
0 Kudos

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.

0 Kudos

Problem is that I am only consuming the report, I can't change it.

Is there no way around this?

horst_keller
Product and Topic Expert
Product and Topic Expert
0 Kudos

Unfortunately no.

A CALL SELECTION-SCREEN in the submitted program is like a CALL SCREEN. You cannot handle it using SUBMIT.

Former Member
0 Kudos

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.

0 Kudos

How do I use batch input?

horst_keller
Product and Topic Expert
Product and Topic Expert
0 Kudos

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.

0 Kudos

Thanks, I will have to see an alternative then.

Regards,

Oussama