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: 

No spool created

Former Member
0 Kudos

Hi all.

I have a report (B) which calls another report (A) using SUBMIT.

When executing the report (B) in background no spool is created, but when I run report A in background a spool is created.

I tried adding LINE-SIZE and LINE-COUNT to the SUBMIT but it did not change anything.

Any Ideas?

Thanks,

Hagit

5 REPLIES 5

Former Member
0 Kudos

Hi

If you use Submit & return, the spool will be generated.

0 Kudos

Hi

Thanks for the quick reply.

I am using 'AND RETURN' - this is how I wrote it:

SUBMIT ZMM_INV_OLD LINE-SIZE 170 LINE-COUNT 58

WITH SELECTION-TABLE SELECTION_TABLE AND RETURN.

Former Member
0 Kudos

Hi,

Try submit the report A using the below syntax..

SUBMIT (v_prog) WITH p_fpath EQ text-004 "parameters if needed

WITH p_fname EQ v_fname "parameters if needed

TO SAP-SPOOL

SPOOL PARAMETERS v_params

WITHOUT SPOOL DYNPRO

USER sy-uname VIA JOB v_jobname NUMBER v_jobcount

AND RETURN.

Please close the thread, if solved

Regards,

Aditya

Former Member
0 Kudos

Execute report A with same values as when you execute report B.

For this you need to put a bbreakpoint on the submit of report A , and then check the values (SELECTION-TABLE SELECTION_TABLE) that are input to report A,

Now , execute A with these values and check.


SUBMIT ZMM_INV_OLD LINE-SIZE 170 LINE-COUNT 58
WITH SELECTION-TABLE SELECTION_TABLE AND RETURN. "Check values at this point and then pass to report A

If you issue is not resolved , please give your code in thread.

Edited by: Harsh Bhalla on Nov 30, 2009 2:32 PM

Edited by: Harsh Bhalla on Nov 30, 2009 2:33 PM

0 Kudos

Hi,

I'm using function RS_REFRESH_FROM_SELECTOPTIONS to get the selections from report B, and the selection screen of both reports are identical.

The problem only happens when I run the report in background.

Thanks,

Hagit