Spool is not generated

[Former Member]

Dear All,

I am facing one problem. We run a program after the program completes now the spool request is not generated.

When i saw in sm37 the status showing cancelled instead of finished

Anyone can please answer what may be the problem and solution

Regards

Divya

[Former Member]

Dear All,

I am facing one problem. We run a program after the program completes now the spool request is not generated.

When i saw in sm37 the status showing cancelled instead of finished

Anyone can please answer what may be the problem and solution

Regards

Divya

[Former Member]

Hi,

Could you please debug the function mdoule which is using for generating the Spool request. Then it is possible to help you.

[former_member404244]

Hi,

Debug the job in SM37..put a break point in ur program...

and then IN SM37 , check ur job and in the command box type 'JDBG' and enter

and now press F8 u wuiil be in the program ...

Regards,

Nagaraj

[Former Member]

Dear Nagaraj,

Thanks .But i went to sm37 InJob Name typed JDBG and entered nothing is working...anything i have to do...can you please explain step by step if you dont mind...thanks divya

[Former Member]

Hi,

Debgugging the cancelled or finished jobs is not possible. So schedule a job in the future time, and start debugging by entering the command JDBG.

But definitely it could have written some error log before the job cancelled.

I mean definitely some error message got triggerred.

If you can not find any thing in the job log, then in the debugging, directly put the break point at statement MESSAGE, so that it will take you directly to the messages if any.

Probably because of no data, or no authorization etc.. they might have raised an error message.

Regards,

Santhosh.

[Former Member]

Hi!

Obviously the program terminates abnormally before the spool request is written and committed.

An abnomral termination normally performs an implicit rollback as well as an implicit commit work is performed when a report ends normally.

So what is the reason for the abnormal termination of your job?

Regards,

Volker

[Former Member]

in SM37 itself, Select the job which is having cancelled status and then click the Display Job Log Button.

Then you will be able to see the reasons

[Former Member]

Hello In joblog it is not given the reason...Message text showing only job started.

[Former Member]

what job you are running...??

[Former Member]

some sale is runnign z*

zsale_production_qty

zccd_pgi

[Former Member]

if it is a program generates OO ALV then it will fail in background( if you don't take certain precautions)

[Former Member]

What precaution i have to take?

[Former Member]

Precaution will be:

Need to code extra in addition to what is there now. you need to call the offline method of class cl_gui_alv_grid and then avoid calling the custom controls.

For more details search in All the forums with key word cl_gui_alv_grid=>offline

For quick info

[Former Member]

When you execute the program in the background and if the program is not succuessful then try to populate a message and check the same at Job Log(in the Toll bar) in the transaction "SM37", it might be helpful to you.

Thanks,

Naveen.

[Former Member]

<<read the question carefully and post>>

Edited by: Vijay Babu Dudla on Apr 24, 2009 9:23 AM

[Former Member]

Hi,

There are a couple of things I might check if I get this error.

1. Check the job log in SM37 for the job. Does it give any explanation of why the job failed? - as someone had posted earlier, the job might have abended even before it starting creating a spool. If this is the case, then check the program in debug for runtime errors.

2. Check the system log - SM21 on the application server that the job was run. - In some cases you would see TemSe errors related to the spool space on the server. - Check the SAP BASIS admin follk and they would be able to fix it for you.

Hope these helps for your analysis.

~DB