Not generating a spool output in the background job

Hi Team,
I have an alv report and If I schedule the program using SM36 transaction it is not generating the spool ouput.
If I run the same program in background mode when we use se38 and select execute in background in program menu and it works successfully and generates alv grid list in the spool output.
But, user wants to schedule the job in sm36 and check the same output in spool. Please advise why it is not generating.
Note:I am using the cl_salv_table=>factory method to generate the output.
Thanks in advance,
Sunil Kumar.

This is not really an ABAP question and you might want to ask your Basis admin for assistance. But I believe that spool will not be generated if you don't specify print parameters for a step. When you define the step in SM36, make sure to specify the print parameters.

Similar Messages

How to check the ALV output for the background job

Hi Guru,
We are having a cutomized report which will display the result like a ALV report.
We configured it as an background job, after the completion of the background job, it will send the result to the SPOOL, and we can use SP02 to check the output,
But it is not easy for user to directly check the result easily, is there an method we can save it as an spreadsheet and send the output to a specific location or mailbox and then user can check it easily
thanks,

In SM37 ,select the Job > Spool > Select Spool No > Display Contents > Here it will show you the Output of the Report.Now select Ctrl +Shift + F12 , it will ask you to save the Spread sheet in specified location.
Best Regards,
Ankur

Output after the background job finished successfully

Hi All,
We executed a Dunning job in the background (sm37) and the job finished succesfully. How to check whether the job has created an output ? Where to look for the output ?
Regards
Shiva

You can check the spool request of your job via SM37 or SMX. Go to SM37 select your job and check the spool request.
Regards
Subhash

Problem in getting spool number of a background job.

Hi all,
In a Z program I am calling a standard program to run as background job. I need to get the report o/p of the standard program. For this I need the spool no of the background job. Now I am querying on table tbtcp by giving jobname. Program name and run date and getting the spool no. but the cache is that the table is not getting updated with the spool no as soon as the job finishes. It is taking some time to update the table ( The time depends on the no of background jobs scheduled. ). So of we query on the table immediately after the background job finishes we are getting spool no as 0. so I am unable to read the spool into Internal tables. Even the table tsp01 is also behaving in the same way. ( it is taking time to update ) .
Any pointers to this will be appreciated .
Regards,
Shiva....

This is some prototype that I put together from separate pieces, so it looks funky, but might be helpful. The first step is to SUBMIT the program with EXPORTING LIST TO MEMORY. The next FM reads the list from memory and the next one (optional) converts it to a text format. You might want to search for other FMs in SE37 by 'LIST*'.
DATA list_tab TYPE TABLE OF abaplist.
SUBMIT RPR_TRIP_HEADER_DATA
USING SELECTION-SET 'OLD_LIST'
EXPORTING LIST TO MEMORY
              AND RETURN.
CALL FUNCTION 'LIST_FROM_MEMORY'
TABLES
    listobject = list_tab
EXCEPTIONS
    not_found = 1
    OTHERS     = 2.
types : t_txt(1000) type c.
DATA: i_txt2 type table of t_txt,
i_txt type list_string_table.
call function 'LIST_TO_ASCI'
EXPORTING
*   LIST_INDEX               = -1
   WITH_LINE_BREAK          = 'X'
IMPORTING
   LIST_STRING_ASCII        = i_txt
*   LIST_DYN_ASCII           =
TABLES
   LISTASCI                 = i_txt2
   LISTOBJECT               = list_tab
EXCEPTIONS
   EMPTY_LIST               = 1
   LIST_INDEX_INVALID       = 2
   OTHERS                   = 3
if sy-subrc <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
         WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
endif.
Also check this links:
http://sap.ittoolbox.com/groups/technical-functional/sap-dev/spool-number-of-previously-printed-abap-list-635173#

Urgent : Want to know table stores spools created by a background job

Actually background job executed by me creates 2 spool requests
table - tbtcpv holds only the 1 spool
Can any one tell me the table which stores all the spool created by the background job ?
Need urgent help.....

Guru,
Try with below tables
TBTCO
TBTCO
TBTCP
TBTCR
TBTCS
TBTCJSTEP
TBTCO
TBTCP
Pls. reward if useful..

SPOOL not generated while smartform is executed in Background

Hi
I have issue while creating spool for smartform in background.Its works fine in foreground and i m able to view the outpt.
But in background it should generate a spool but it is not generating?
I have given the ouput options to supress the dialog but it still it is not generating the spool.
     control-preview = 'X'.
      control-no_dialog = 'X'.
      control-device = 'PRINTER'.
      control-no_dialog = 'X'.
      control-GETOTF = 'X'.
      OUTPUT_OPTIONS-TDDEST = 'LP01'.
      OUTPUT_OPTIONS-TDNOPRINT = 'X'.
Any suggestions??
Thanks & Regards
Jyo

Hi Jyotheswar,
When the smartform is generated in background create a new spool by using following code
      output_options-no_dialog = 'X'.
      output_options-tdarmod = 1.
      output_options-tdcopies = 001.
      output_options-tddest = 'LP01'.
      output_options-tdprinter = 'SWIN'.
      output_options-tdlifetime = 1.
      output_options-tdnewid = 'X'.
tdnewid is the field used to create a new spool request. You can get the new spool request number in job_output_info-spoolids.
Regards,
Birendra

Certain Maintenance Plan not getting scheduled in the background job

Hi Gurus,
I am facing an issue here.
A weekly background job (RISTRA20) runs every weekend and schedules the maintenance plans.
But we have noticed that some maintenance plans are not getting scheduled. i.e no orders or schedule is getting generated.
When I run IP30 manually for these plans then the schedule gets generated and orders get called.
I have checked up the background job and it is running fine.
Also, i have noticed a similarity in all these plans which are not getting scheduled. There schedule has been restarted (through IP10) at somepoint or the other.
But i don't see any direct impact of this?
Can any of you provide some help on this?? Points will be rewarded.
Thanks and regards,
Nitin Saini

Hi Narender,
Thanks for replying.
The message number for 'Groups don't match' is ME303.
I think this does not have anything to do with the restart as i have done further investigation.
Whenever I run IP30 with sortfield input as AS02*, i get the error as mentioned above for a certain number of maintenance plans while the remaining plans get scheduled.
If i run IP30 for any other sort fields, it runs fine and i don't encounter the error
mentioned above.
If you send me ur email address, i could forward you screen-shots of the issue.

Smartform output in the background

Hello all,
Now I met a problem about smartform output in the background:
The default printer is LP01. When I execute the program which calls this smartform in background, I change the printer to LP03.
Then I use the t-code:SP02 and find the printer is LP01 not LP03.
(But if I use the hardcode 'LP03', the printer is changed to LP03)
What can i do change the printer to LP03?
---part of my code:
DATA: ls_pri_params         TYPE pri_params,
      ls_control_parameters TYPE ssfctrlop,
      lv_print              TYPE sypdest,
      lv_valid              TYPE bool,
      ls_output             TYPE ssfcompop,
      lv_repid              TYPE syrepid.
CALL FUNCTION 'GET_PRINT_PARAMETERS'
    EXPORTING
      mode                   = 'BATCH'
      report                 = lv_repid
    IMPORTING
      out_parameters         = ls_pri_params
      valid                  = lv_valid.
lv_print = ls_pri_params-pdest.
ls_output-tddest = lv_print.
ls_output-tddest = 'LP03'.
CALL FUNCTION '/1BCDWB/SF00000004'
    EXPORTING
      output_options     = ls_output
      user_settings      = space.
Thanks in advance!

Hi Nina,
You can use sy-batch. See the following codes:
IF SY-BATCH = 'X'. "means program is executed in the background.
   ls_output-tddest = 'LP03'.
ELSE.
   ls_output-tddest = lv_print.
ENDIF.
Regards,
Hendy

Send/export the background job spool in Excel (in MHTML format) in ECC 6.0.

Hello All,
I have a requirement to send/export the background job spool in Excel (in MHTML format) in ECC 6.0. Please help.
Thank you.
Nalini

Hi Jigar,
Thanks for your response.
Anything is like download to desktop or email is fine. But in MHTML format.
We can download the ALV report in MHTML spreadsheet format when we run the program online. But the program is running for long time and going to dump.
So i scheduled it as background job and downloading the output in .HTML format. But user wants the spool/report output in .MHTML spreadsheet format.
I can write the code. Instead of changing the existing program I would like to know is there any way (from standard SAP) that I can get the background spool in MHTML spreadsheet format.
Thanks,
Nalini

How to send the spool output to the specific user during ALE distribution

Hi All
In ALE internal order Configuration done by BAPI Method SAVEREPLICA Business object BUS2075whenever user changed the internal order which is moved to the destination system because of change data setting in data element fields.
I want to know how to send the spool output of the changed internal order to the specific user during ALE distribution.
Please help me to reslove the above issue
Thanks & Regards
KRISHGUNA

Solved by myself

In IDoc to file example if IDoc has not generated?what might be the problem

In IDoc to file example if IDoc has not generated? what might be the problem? where we can find it?

Hi Sudhakar,
We need to check in sm58 of R/3 system for any errors..and according to the error message we have to fix the problem.
It can fail with many reasons for example error in RFC destination connection etc.
Regards,
Prasanthi.

How to schedule the background job daily twice?

Hi,
How to schedule the background job daily twice? any conditions?
Regards,
Srihitha

see the step by step procedure.
Scheduling Background Jobs:
1. Background jobs are scheduled by Basis administrators using transaction SM36.
2. To run a report in a background, a job needs to be created with a step using the report name
and a variant for selection parameters. It is recommended to create a separate variant for each
scheduled job to produce results for specific dates (e.g. previous month) or organizational units (e.g.
company codes).
3. While defining the step, the spool parameters needs to be specified
(Step-> Print Specifications->Properties) to secure the output of the report and help authorized users
to find the spool request. The following parameters needs to be maintained:
a. Time of printing: set to Send to SAP spooler Only for now
b. Name abbreviated name to identify the job output
c. Title free form description for the report output
d. Authorization a value defined by Security in user profiles to allow those users to access
this spool request (authorization object S_SPO_ACT, value SPOAUTH). Only users with matching
authorization value in their profiles will be able to see the output.
e. Department set to appropriate department/functional area name. This field can be used in
a search later.
f. Retention period set to Do not delete if the report output needs to be retained for more
than 8 days. Once the archiving/document repository solution is in place the spool requests could
be automatically moved to the archive/repository. Storage Mode parameter on the same screen
could be used to immediately send the output to archive instead of creating a spool request.
Configuring user access:
1. To access a report output created by a background job, a user must have at
least access to SP01 (Spool requests) transaction without restriction on the user
name (however by itself it will not let the user to see all spool requests). To have
that access the user must have S_ADMI_FCD authorization object in the profile with
SPOR (or SP01) value of S_ADMI_FCD parameter (maintained by Security).
2. To access a particular jobs output in the spool, the user must have
S_SPO_ACT object in the profile with SPOAUTH parameter matching the value used
in the Print Specifications of the job (see p. 3.d above).
3. Levels of access to the spool (display, print once, reprint, download, etc) are
controlled by SPOACTION parameter of S_SPO_ACT. The user must have at least
BASE access (display).
On-line reports:
1. Exactly the same configuration can be maintained for any output produced
from R/3. If a user clicks Parameters button on a SAP Printer selection dialog, it
allows to specify all the parameters as described in p. 3 of
Scheduling background jobs section. Thus any output created by an online report
can be saved and accessed by any user authorized to access that spool request
(access restriction provided by the Authorization field of the spool request
attributes, see p. 3.d of Scheduling background jobs section).
Access to reports output:
1. A user that had proper access (see Configuring user access above) can
retrieve a job/report output through transaction SP01.
2. The selection screen can be configured by clicking Further selection
criteria button (e.g. to bring Spool request name (suffix 2) field or hide other
fields).
3. The following fields can be used to search for a specific output (Note that
Created By must be blank when searching for scheduled jobs outputs)
a. Spool request name (suffix 2) corresponds to a spool name in p. 3.b in
Scheduling background jobs section above).
b. Date created to find an output of a job that ran within a certain date range.
c. Title corresponds to spool Title in p. 3.c in Scheduling background jobs
section above).
d. Department - corresponds to spool Department in p. 3.e in Scheduling
background jobs section above).
4. Upon entering selection criteria, the user clicks the Execute button to
retrieve the list of matching spool requests.
5. From the spool list the user can use several function such as view the
content of a spool request, print the spool request, view attributed of the spool
request, etc. (some functions may need special authorization, see p.3 in
Configuring user access)
a. Click the Print button to print the spool request with the default attributes
(usually defined with the job definition). It will print it on a printer that was
specified when a job was created.
b. Click the Print with changed attributed button to print the spool request
with the different attributes (e.g. changing the printer name).
c. Click the Display contents button to preview the spool request contents. A
Print and Download functions are available from the preview mode.

Actual Varaint Name used in the Background Job

Hi,
When a program is executed in Background made the selection screen variant selected is not the one that is shown in the Background Job Step information. There we see variant as &0000000000044.
I want to find the actual variant that was selected at the time of running the program in background mode.
Thanks.

Hi,
I also faced the same issue and after my R&D i found a workaround for this. Check this out.
Create a selection screen parameter and hide it.
PARAMETERS: po_varnt TYPE sy-slset NO-DISPLAY.
Now place below code in AT SELECTIO-SCREEN OUTPUT event.
AT SELECTION-SCREEN OUTPUT.
    CHECK sy-batch IS INITIAL.
    CLEAR po_varnt.
    MOVE sy-slset TO po_varnt.
If you are running in background by pressing F9 from selection screen, Use your hided parameter po_varnt for the variant name instead of sy-slset.
If you are running the report in foreground or through SM36 then you can use sy-slset to know the variant name.
Thanks,
Vinod.

Read Error logs after running the background jobs

Hi,
How to read the error logs after running the background jobs. In our scenarion we are running the COHV transaction to release the production orders in background. But we are not finding the error logs after background job. We would like to read the error logs and correct for further processing.
Kindly suggest.
Thanks & Regards,
N. Laxman

Hi
you can check the back ground jobs defined by any user in SM37 and where you can see the spool and job logs as well.
plz check in your case and revert back
Regards
Anupam Sharma

The background job "SM:EXEC SERVICES" is ending Green in Just 0 seconds

Solution Manager 4.0
In our customer system the background job "SM:EXEC SERVICES" is ending Green in Just 0 seconds or just 1 second.
Here is the log:
Job log overview for job:    SM:EXEC SERVICES 000000046740000 / 12193100
Date       Time     Message text                                                                               Message class Message no. Message type
28.04.2009 12:19:31 Job started                                                                                00           516          S
28.04.2009 12:19:31 Step 001 started (program RDSMOPBACK_AUTOSESSIONS, variant &0000000001054, user ID BJ8099)      00           550          S
28.04.2009 12:19:32 RDSMOPBACK_AUTOSESSIONS : MemSize Begin = 1374064                                              DSWP          000          I
28.04.2009 12:19:32 Solution Enterprice Portal(GGP) is being edited (Operations)                                   DSWP          438          I
28.04.2009 12:19:32 RDSMOPBACK_AUTOSESSIONS : MemSize End = 20902480                                               DSWP          000          I
28.04.2009 12:19:32 Job finished                                                                                00           517          S
Due to this EWA reports are not being generated.
What could be the reason that the Job ends immediately with no significant warnings or error in the log?
Many thanks in advance,
Manoj

Hi Manoj
Following Notes will be helpful to you to analyze the problem
Note 894279 - Background processing in SAP Solution Manager
Note 1246329 - RDSMOPBACK_AUTOSESSIONS: Additional displays
Note 1163920 - SM:Scheduler: Improved display in job log
Note 946607 - Automatic diagnosis in SAP Solution Manager
SAP Note 727998 "Complete Replacement of Service Definitions for SDCC/SDCCN"
Note 986973 - How to analyze problems with EarlyWatch Alerts in SolMan
however, is this problem occurring for sessions of ALL the systems today, if yes, then something wrong only in solman, last note of the above shows you to manually run the job interactively, may be will help in analyzing and i hope SDCCN settings in Solman are already fine..
thanks
Bhudev

Not generating a spool output in the background job

Similar Messages

Maybe you are looking for