BackGround Job's Spool Request is having "Waiting" "Frontend unavailable"

Hello Friends,
I am facing one problem related to Spool Request, which is generated through Scheduled Background Jobs (scheduled by funcional people).
The Background Job is having status "completed" when analyzing it. But, its associated Spool Request is showing "waiting" Status, with "Frontend unavailable" as Status Text.
Here is the brief status of that Spool Request.
28448     1      300 USER1 00:00 LP01 X_65_80      Frontend unavailable
in Detail:
Description          Value
Status:              Frontend unavailable
Last event:
Message:             Request on hold
Date:                01.07.2009
Time:                00:00:27
Job status:          On hold
Error class:         Delayed
Area:                Data transfer
Printout:            Not printed
The Setting of LP01 O/Device is as followed:
Output Device        LP01
Device Type        SWIN SWIN : Windows printing via SAPlpd
Device Class      Standard Printer
Host Spool Access Method       F F: Printing on Front End Computer
Host printer                     __DEFAULT
Moreover, the SAP User USER1 is allocated LP01 as Output Device with "Output Immediately" & "Delete After Output" checked status.
Some Background Jobs are showing the same status for this LP01.
I have a doubt on allocated O/P Device LP01.
Any Clue for this issue ?
Regards,
Bhavik G. Shroff

Hello Markus,
Here , in our Landscape , there is not Print Server. All are taking prints through, Networked Printer and their local connected Printers.
Can i configure "send to SAP Spooler for now" instead of "Print Immediately "in the Print Specification of those Background Jobs ?
Moreover, Some Background jobs are sending E-Mails with the processed Reports as an Attachments. They are showing sometime unexpected behavior, in sending emails, although there is no relation is with this Printing related issue.
When i am looking into "Overview of Send Orders" of SCOT, some Background Jobs are showing success for sending emails, and some are not showing success, even though All the recipients are same for the scheduled Background Jobs which are running on same time.
Regards,
Bhavik G. Shroff

Similar Messages

Afer background job finished, spool was not generated

hi all
Afer background job finished, spool was not generated but all background jobs is not
soem background jobs was created spool.
even if same user and same backgorund job, sometime generated spool or not.
how can I solve??
thanks

Hi,
Spool will be generated only spool specification wil be defined for that job.
Select the job go to steps spool specification you can see the device assigned to it.
Regards
Ashok

Script to find Jobs in a Request Set having incompatibilities

All,
Could anyone please share - Script to find Jobs in a Request Set having incompatibilities.
Working on R12.1.1
DB:11.1.0.7
Thanks for your time and help!
Regards,

Could anyone please share - Script to find Jobs in a Request Set having incompatibilities.Please see this thread -- Re: incompatibilities table
Thanks,
Hussein

Job in background and multiple spool requests

Hi everybody,
I'm executing a program in a background job. The program outputs 2 spool requests. When I get to SM37 t-code to see job's result, I can see at "Job Log" option that 2 spool requests were generated. But... when I press "Spool" option from SM37 t-code I only see the last one. In spite of this, when I get at the spool controller through SP01 t-code I can see both of them. Can you help me with this issue? Why from one place I get 1 request and from the other the 2 ones?
Thanks in advance and kind regards,
MMP.

Hi,
Check out [this thread|https://forums.sdn.sap.com/click.jspa?searchID=16405444&messageID=1181695] which has a discussion on this topic and points out [Note 519059|https://service.sap.com/sap/support/notes/519059]:
8] Question: How are the spool requests assigned?
Answer: The step information is stored in table TBTCP. This has space for exactly one spool request (field LISTIDENT). If a step generates several spool requests during the processing, only one can be stored. In this case the application is responsible for a "spool overview".
Regards,
Jamie

Background Job Processing Spool Retention period

Hi ,
In my program i am calling another ABAP program and sumitting the same as a background job(using Job_Submit,Close etc.)
In this case i can view the Spool generated by the called program(using sm37).
But this spool exists for a very less period in the system.Is it possible to specify a retention period,as 90 days in my case.?
Pls Help !!!
Answers will be rewarded.
Regards,
Rohan

hi Roahn,
You must set print parameters before the printing process starts.
When printing lists after creating them, the system uses the print format specified in the print parameters to split the completed list and fit it onto the print pages, truncating it if necessary.
When printing lists while creating them, the system uses the print format to actually format the list in the program.
Print parameters are set either interactively by the user or from within the program.
For each print process, the spool system needs a complete and consistent set of print parameters. In ABAP, the structure PRI_PARAMS (ABAP Dictionary) represent a set of print parameters.
When passing the print parameters interactively, the system displays a dialog box after starting the report, on which the user has to enter the most important print parameters.
It's shown below which input field of the Print List Output dialog window conform to which PRI_PARAMS component.
Input field----
Retention period
Component-------PEXPI
Meaning----
Number of days for which the system holds the spool request before deleting it. (Default value: 8).

Background Job Processing/Spool List Recipient

When setting up a report to run as a background job and setting it up to e-mail the results via the Spool List Recipient button, it always sends the results in htm format. Is there a way it can be e-mailed in Excel?

hi swapna.
in scot it is not configured as excel how to do it.to get an attachment in excel format
thanks in advance

Regarding the output of background job in spool

Hi Friends:
I have a report.When I run it in foreground, it displays an alv output.
I want to see the output when I run it in background. When I select the job & press on spool, it shows a message that no list available. Please help with the settings to see the output in spool.
Suitable points will be rewarded.
Regards:
Gaurav

Hi,
have a look at this thread:
Re: OO ALV in background job
Best regards.

Background Job and spool numbers

hi All
I have a requirement to schedule a job in background programmatically. Depending upon the end result of the job, two different spools should be generated. The job name and spool names should be given programmatically. these spools should be emailed to a email ID. What will be the best option of executing the above scenario.
Shakir.

Hi,
you can use Workflows to execute the above scenario.
Regards
Mudit

Not able to print to locl printer, spool request status is in wait

Hi All,
When user print to locl printer, the spool request is created and we get a error message saying "connection closed after (protocol) error (RC=1)". And we found the status of spool request is in wait state and if double clicked on it, it is showing "Internal error printing".
Below is the log of Spool work process for your reference
Found unqueued job 21701/1 (LOCL)
ERROR => Printer LOCL: Lookup failed ?!?!? -> Status DELAY http://rspopcc. 0813
Just to update you user is able to print all other documents except the documents from SAP application. And user is connecting to SAP application server through Citrix.
We are on HP-UX, Oracle database and SAP R/3 3.1i version.
Thanks in advance.
Regards,
Chandrika

sundaresh suryanarayan wrote:
Hello Chandrika,
>
> Is this printer is a network printer ?. Use Device Type : SWIN and Access Method : G Front End Printing .
>
> Thanks
>
> Sundaresh Suryanarayan
Hi Sundaresh,
Thanks for your reply.
Yes it is a network printer. User is printing to his default printer(LOCL, with host printer __DEFAULT) and we are using device type SAPWIN and access method F(printing on front end computer).
Regards,
Chandrika

Email multiple spools from background job - SM36 using Spool List recipient

I create a background job using Spool List Recipient to email me the reports. The program that I scheduled to run creates 2 spools. When the spools are sent via email, only the last spool is sent.
Please advise on how I can get the 2 spools sent via email.

i would not use the Spool List recipient from Job and use the function RSPO_SPOOLJOB_TO_OFFICE in your Program instead.
tell me if it helps.
Regards,
Laurent

File path problem in background job spool

Hello ,
i have probelm in file path of the background job in spool.
i have selection screen
Radiobutton : p_local
parameter: path1.
Radibutton: p_applicatioserver
parameter: path2.
if i keep program in background job, it will alwas take second option.
Now user selected first option and executed job in abckground. File stored in the spplication server with corect file path name. (path2)
But when i go to sm37 entered job name and checked the spool, it gives me the file path name path1. but i need the file path1 in the background spool. my question whether i need to change the file path name in program or whether i have to change the setting
Regards,
zub

First of all, local is not an option in background job; you can only save to the apps server, and your program should take that into consideration by checking for sy-batch = 'X', for example. You should be checking in your at selection-screen to be sure the user has not chosen local path and file and background job.

Background Job Scheduling

Hi,
I am scheduling a report to run in background.
In this report it is creating background jobs automatically for different company codes.
It submits the 1st background job and waits until it finishes.
Then 2nd job starts in background and continues with other jobs.
At end it finishes all the jobs and closes.
Now my problem is.
1.       Whether is it possible for us to submit all the jobs at 1 time. And execute at same time. Ie., 1st, 2nd job will start at same time.
2.       If possible how can we do that.
What I have written is
loop at companycode.
Create job name.
call fun 'Job_Open'.
submit xxxx user sy-uname via job job_name numer job_count
to sap-spool
spool parameters l_spool_parameter
without spool dynpro
with companycode
with ......
and return.
endloop.
Please help ASAP, urgent.

hi praveen,
Job Scheduling Explained
Definition
Before any background processing can actually begin, background jobs must be defined and scheduled. The scheduled time for when a job runs is one part of the jobs definition. There are several ways to schedule jobs:
From Transaction SM36 (Define Background Job)
With the "start program in the background" option of either Transaction SA38 (ABAP: Execute Program) or Transaction SE38 (the ABAP editor)
Through the background processing systems own programming interface. (Many SAP applications use the internal programming interface to schedule long-running reports for background processing.)
Through an external interface.
Scheduling Background Jobs
Use
You can define and schedule background jobs in two ways from the Job Overview:
·         Directly from Transaction SM36. This is best for users already familiar with background job scheduling.
·         The Job Scheduling Wizard. This is best for users unfamiliar with SAP background job scheduling. To use the Job Wizard, start from Transaction SM36, and either select Goto ® Wizard version or simply use the Job Wizard button.
Procedure
       1.      Call Transaction SM36 or choose CCMS ® Jobs ® Definition.
       2.      Assign a job name. Decide on a name for the job you are defining and enter it in the Job Name field.
       3.      Set the jobs priority, or Job Class:
·         High priority:      Class A
·         Medium priority: Class B
·         Low priority: Class C
       4.      In the Target server field, indicate whether to use system load balancing.
·         For the system to use system load balancing to automatically select the most efficient application server to use at the moment, leave this field empty.
·         To use a particular application server to run the job, enter a specific target server.
       5.      If spool requests generated by this job are to be sent to someone as email, specify the email address. Choose the Spool list recipient button.
       6.      Define when the job is to start by choosing Start Condition and completing the appropriate selections. If the job is to repeat, or be periodic, check the box at the bottom of this screen.
       7.      Define the jobs steps by choosing Step, then specify the ABAP program, external command, or external program to be used for each step.
       8.      Save the fully defined job to submit it to the background processing system.
       9.      When you need to modify, reschedule, or otherwise manipulate a job after you've scheduled it the first time, you'll manage jobs from the Job Overview.
Note: Release the job so that it can run. No job, even those scheduled for immediate processing, can run without first being released.
Specifying Job Start Conditions
Use
When scheduling a background job (either from Transaction SM36, Define Background Job or CCMS ® Jobs ® Definition), you must specify conditions that will trigger the job to start.
Procedure
Choose the Start condition button at the top of the Define Background Job screen.
Choose the button at the top of the Start Time screen for the type of start condition you want to use (Immediate, Date/Time, After job, After event, or At operation mode) and complete the start time definition in the screen that appears.
For the job to repeat, check the Periodic job box at the bottom of the Start Time screen and choose the Period values button below it to define the frequency of repetition (hourly, daily, weekly, monthly, or another specific time-related period). Then choose the Save button in the Period values screen to accept the periodicity and return to the Start Time screen.
Once youve completed specifying the job start conditions, choose the Save button at the bottom of the Start Time screen to return to the Define Background Job screen.
No job can be started until it is released, including jobs scheduled to start immediately. Since releasing jobs can be done only by a system administrator from the job management screen (Transaction SM37) or by other users who have been granted the appropriate Authorizations for Background Processing, no unauthorized user can start a job without explicit permission
Managing Jobs from the Job Overview
Use
The Job Overview, or Job Maintenance, screen is the single, central area for completing a wide range of tasks related to monitoring and managing jobs, including defining jobs; scheduling, rescheduling, and copying existing jobs; rescheduling and editing jobs and job steps; repeating a job; debugging an active job; reviewing information about a job; canceling a job's release status; canceling and deleting jobs; comparing the specifications of several jobs; checking the status of jobs; reviewing job logs; and releasing a job so it can run.
Procedures
To display the Job Overview screen, choose CCMS ® Jobs ® Maintenance or call Transaction SM37. Before entering the Job Overview screen, the system first displays the Select Background Jobs screen. You'll need to complete this Job Selection screen to define the criteria for the jobs you want to manage. Once you've selected jobs to manage, you can choose from a wide range of management tasks:
To copy a single existing job, choose Job ® Copy.
To reschedule or edit job steps or attributes of a single job, choose Job ® Change. A job step is an independent unit of work within a background job. Each job step can execute an ABAP or external program. Other variants or authorizations may be used for each job step. The system allows you to display ABAP programs and variants. You can scan a program for syntax errors. You can also display the authorizations for an authorized user of an ABAP job step.
To repeat a single job, choose Job ® Repeat scheduling.
To debug an active job, choose Job ® Capture: active job. Only a single selection is allowed. If an active job seems to be running incorrectly (e.g., running for an excessively long time), you can interrupt and analyze it in debugging mode in a background process, and then either release it again or stop it altogether.
You will be able to capture a background job only if you are logged on to the SAP server on which the job is running. To find server information in the Job Overview, select and mark the job, then choose Job ® Job details.
To review information about a job, choose Job ® Job details. Details displayed can include:
current job status
periodicity, or the repetition interval
other jobs linked to the current job, either as previous or subsequent jobs
defined job steps
spool requests generated by the current job
To cancel a job's "Released" status, select the job or jobs from the Job Overview list and choose Job ® Release -> Scheduled.
To cancel a job from running but keep the job definition available, select the job or jobs from the Job Overview list and choose Job ® Cancel active job.
To delete a job entirely, select the job or jobs from the Job Overview list and choose Job ® Delete. Jobs with the status of Ready or Running cannot be deleted.
To compare the specifications of more than one job, select the jobs from the Job Overview list and choose Job ® Compare jobs.
To check the status of jobs, select the job or jobs from the Overview Job list and choose Job ® Check status. This allows you to either change the job status back to Planned or cancel the job altogether. This is especially useful when a job has malfunctioned.
To review job logs, select a job or jobs with the status Completed or Canceled from the Job Overview list and
regards
karthik
reward me points if helpfull

Background Job not Printing TOs immediately

Hello experts,
I am having an issue with printing Transfer Orders created by background job, the output requests are sent to the output controller with status '-' . It works when I manually create the TOs or if I run the RLAUTA10 program with my userID in SE38 .
I have set the background job user default print parameters in SU3 to print immediately.
Also in the Job step, I have set up the print parameters to 'print immediately'
I have assigned printer for sorce storage type & set the indicator to use the source sto type in OMLV, The printer seems to be determined correctly, I've checked the Spool request name & printer in the spool controller, only issue seems to be the print not being triggered immediately.
Not sure, if there is some other setting that I have to make to be able to print the TOs created by the background job immediately.
Any help would be appreciated.
Thanks
Kris T

whether the printer which you assigned is configured in SAP (network printer)? or LOCL?
printing may not happen if LOCL(background job)
Thanks

How to create the multiple spool requests for a single report.

Hi gurus,
I have one requirement to be completed , i need to send the out put of the report via mail in pdf format. for that what i did was, iam executing report in background and creating spool request and converting it to pdf and sending the file.
now the problem is, its a customer ledger report, for each customer i need to create a new spool request and send mail to that particular customer, now my dought is how to create multiple spool requests for a single pro and how i need to go about it.
And one more question is can we create a spool request for a report which is running in online.
waiting for inputs frm gurus.

Hello,
As per my knowledge for creating new spool id you will have to set
output_options-tdnewid = 'X'.
and then using
job_output_info-spoolids
create a pdf using
call function 'CONVERT_OTFSPOOLJOB_2_PDF'
Rachana.

F.27, Duplicate Spool Request

Hi All,
While running the program - Periodic Account Statement (t-code F.27) u2013 in background(Program > Execute in background) 2 spool requests are generated.
Why 2 spool requests are generated ? Only 1 spool request should get generated.
Correspondence Type used is a customized Correspondence Type(Z).
Unwanted Spool generated is of type u2018ABAP Listu2019 and title generated is u2018F140 LOCL 20100927KORKu2019.
Because of the 2 spools 2 hard prints are printed.
Please suggest as to what could be the cause of 2 spools ?
Thanks
Dev

Hi,
As info says:
Output
    If correspondences are printed, a log with the spool requests created by
    the print programs is output for each program run. If you do not specify
    in the program on which printer the log is to be printed, the program
    may take the printer specified in the user master of the user who
    started the program or the printer specified when the job is scheduled.
    If the program is carried out online, the log is displayed on the
    screen. If the program is planned as a job, the spool request name of
    the log is made up of the identifier F140, the printer destination, the
    date of creation and the program ID KORK.
    The correspondences are printed by means of the corresponding print
    programs. If printing is possible on the basis of the data and the
    configuration, a spool request is created for each correspondence type
    and company code. Regardless of whether printing actually takes place,
    the processed correspondence requests are marked as completed by means
    of a print date, so that reorganization can be carried out.
ie: you have a SPOOL with the log, and you have other SPOOL with the printable document that you must send to customers.
I hope this helps you
Regards,
Eduardo

BackGround Job's Spool Request is having "Waiting" "Frontend unavailable"

Similar Messages

Maybe you are looking for