Standard job scheduling problem

hi,
i am using ERP 6 ,windows 2003 , MS SQL 2005.
i am scheduling the standard job like (SAP_COLLECTOR_FOR_JOBSTATISTIC ).
in start time when i am selecting IMMEDIATE it is ok and working.
but in start time when i select particular date/time it gives error (Error saving job SAP_COLLECTOR_FOR_JOBSTATISTIC to
database)
can any one tell me why is this happing.

hi,
i am using ERP 6 ,windows 2003 , MS SQL 2005.
i am scheduling the standard job like (SAP_COLLECTOR_FOR_JOBSTATISTIC ) in sm36.
in start time when i am selecting IMMEDIATE it is ok and working.
but in start time when i select particular date/time it gives error :-
"Error saving job SAP_COLLECTOR_FOR_JOBSTATISTIC to
database"
can any one tell me why is this happing.

Similar Messages

Error saving job to database for standard jobs scheduling

Hi,
In IDES server when iam goto Tr.code -- SM36 -- Standard Jobs -- Default Scheduling iam getting below error.
Error saving job to database
Message no. BT117
Diagnosis
The SAP system was unable to save the current job in the database. This failure suggests that there is a problem with the database system or with the network connections between the SAP application servers and the database system.
System Response
Job not saved and not scheduled.
Procedure
To analyze this problem, start by checking the system log for messages about network or database problems. You can also use the computing center management system to check your system for problems.
Guide me for the same.
Thanku

HI,
Sometimes this error will come.
Try to schedule jobs manually using SM36 instead of using standard job button.
Also you can check this thread
Re: Error saving job SAP_REORG_JOBS to database
Which seems to report same problem.
Its nothing to take with database conenctivity as SAP is up and running .
Try this and revert.
Regards,

Background job scheduling problem in APO

Hi fellow SDNers,
i am going through this peculiar problem of background job scheduling:
scenario is like , i have an CSV (excel file) in aplication server which would load data into the infosource, which i have scheduled to run in backhround (in infopackage) ,after event is triggered (option in scheduling tab of infopackage...THE SCHEDULING OPTIONS)
now everything seems to be fine.. but the data is not getting loaded...?? could u lease help me out..how to load data from excel file (in background), after an event gets triggered.
thanks in advance,
Rohan

hi Alexander,
i am triggering the event from BP_EVENT_RAISE FM in APO by passing the event id... this would automaitically raise the event...just like sm64
Thanks
Rohan

Reporting Agent Job Scheduling problem

hi All,
I am trying to schedule reporting agent job. I have few pre calculated webtemplates in one reporting agent scheduling package. when i try to schedule it and go to "start condition" - I want to put "After Event". I am selecting Event and giving the parameter name. But when i save and go out the job is already scheduled (checked in sm37). so I tried to chk the job condition again and the event i selected is not there !!!!
I want to create after even condition and schedule that parameter via mainframe as our all job schedule through main frame only !!! can some one tell me why its not working with reporting agent ??
I will definately assign the points.

dinesh and SB,
thank you for your reply. understood your point. but what i m asking is when i put "after event" criteria in the start selection... wouldnt it show that always when ever i go to Reporting Agent scheduling Package --> right click --> schedule --> start condition (i meant the event name and parameter should be saved there)
but once i save it and get out from the scheduling package i can see the job has been scheduled but its not showing that its even controlled job !!!
is it possible to use "after event" option in Reproting agent's job ?
I have few queries under one Reporting Agent scheduling package which is added in one process chain - the PC is running once a month - i added RA at the end of the process chain and the variant will be schedule by mainframe once the process chain has completed successfully. now 2nd thing is: i need to run Reporting Agent job every single day. so need to schedule it twice. we schedule everything by main frame. so if i can save "after event" criteria then i can schedule that parameter by mainframe. the problem is the start condition is not saving my after event condition entries or parameter names.
I hope i m clear. pl. guide its kind a urgent.

Background job scheduling problem

Hai..Can anyone check the below program and correct it.
I am unable to see the output in SP01 (SPOOL REQUEST)
MY PROGRAM:-
REPORT zh_test4.
TABLES : mara, TBTCO.
DATA : BEGIN OF itab OCCURS 0,
      matnr LIKE mara-matnr,
      END OF itab.
****background data declarations
data : job_name like TBTCO-JOBNAME.
data : job_num like TBTCO-JOBCOUNT,
       rep like sy-repid.
***selection screen
PARAMETERS : p_matnr LIKE mara-matnr default '1500-610'.
SELECT matnr FROM mara INTO TABLE itab WHERE matnr EQ p_matnr.
job_name = 'HARI'.
CALL FUNCTION 'JOB_OPEN'
EXPORTING
DELANFREP              = ' '
JOBGROUP               = ' '
    jobname                = job_name
SDLSTRTDT              = NO_DATE
SDLSTRTTM              = NO_TIME
IMPORTING
   jobcount               = job_num
EXCEPTIONS
   CANT_CREATE_JOB        = 1
   INVALID_JOB_DATA       = 2
   JOBNAME_MISSING        = 3
   OTHERS                 = 4
IF sy-subrc <> 0.
write :/ ' Job opening problem'.
else.
write :/ 'Job succesfully opened', sy-subrc.
ENDIF.
MOVE SY-UNAME TO TBTCO-AUTHCKNAM.
rep = sy-repid.
job_name = 'HARI'.
CALL FUNCTION 'JOB_SUBMIT'
EXPORTING
ARCPARAMS                         =
    authcknam                         = SY-UNAME
    jobcount                          = job_num
    jobname                           = job_name
LANGUAGE                          = SY-LANGU
PRIPARAMS                         = ' '
   REPORT                            = 'ZH_TEST4'
VARIANT                           = 'VAR'
IMPORTING
STEP_NUMBER                       =
EXCEPTIONS
   BAD_PRIPARAMS                     = 1
   BAD_XPGFLAGS                      = 2
   INVALID_JOBDATA                   = 3
   JOBNAME_MISSING                   = 4
   JOB_NOTEX                         = 5
   JOB_SUBMIT_FAILED                 = 6
   LOCK_FAILED                       = 7
   PROGRAM_MISSING                   = 8
   PROG_ABAP_AND_EXTPG_SET           = 9
   OTHERS                            = 10
IF sy-subrc <> 0.
WRITE :/ 'JOB SUBMIT PROBLEM',
          job_name,
          job_num,
          rep,
          sy-subrc.
else.
write :/ 'Job succesfully submitted in background', sy-subrc.
ENDIF.
CALL FUNCTION 'JOB_CLOSE'
EXPORTING
    jobcount                          = job_num
    jobname                           = job_name
LASTSTRTDT                        = NO_DATE
LASTSTRTTM                        = NO_TIME
PRDDAYS                           = 0
PRDHOURS                          = 0
PRDMINS                           = 0
PRDMONTHS                         = 0
PRDWEEKS                          = 0
PREDJOB_CHECKSTAT                 = ' '
PRED_JOBCOUNT                     = ' '
PRED_JOBNAME                      = ' '
SDLSTRTDT                         = datum
SDLSTRTTM                         = uzeit
STARTDATE_RESTRICTION             = BTC_PROCESS_ALWAYS
   STRTIMMED                         = 'X'
TARGETSYSTEM                      = ' '
START_ON_WORKDAY_NOT_BEFORE       = SY-DATUM
START_ON_WORKDAY_NR               = 0
WORKDAY_COUNT_DIRECTION           = 0
RECIPIENT_OBJ                     =
TARGETSERVER                      = ' '
DONT_RELEASE                      = ' '
TARGETGROUP                       = ' '
IMPORTING
JOB_WAS_RELEASED                  = 'X'.
EXCEPTIONS
   CANT_START_IMMEDIATE              = 1
   INVALID_STARTDATE                 = 2
   JOBNAME_MISSING                   = 3
   JOB_CLOSE_FAILED                  = 4
   JOB_NOSTEPS                       = 5
   JOB_NOTEX                         = 6
   LOCK_FAILED                       = 7
   INVALID_TARGET                    = 8
   OTHERS                            = 9
IF sy-subrc <> 0.
write :/ 'Unable to close the Job', rep, sy-subrc.
else.
write :/ 'Succesfully closed the job', sy-subrc.
ENDIF.

Here is an example, slightly different from your version.
REPORT ztest.
PARAMETERS: p_vbeln LIKE vbak-vbeln,
            p_bkrun NO-DISPLAY.
DATA: ls_vbak LIKE vbak.
DATA: v_answer,
      v_jobcount LIKE tbtcjob-jobcount.
IF p_bkrun IS INITIAL.
*-- not background processing
    CALL FUNCTION 'POPUP_TO_CONFIRM_STEP'
         EXPORTING
              textline1      = 'This may time out.'
              textline2      = 'Do you want to run in background?'
              titel          = 'Warning!!!'
              cancel_display = space
         IMPORTING
              answer         = v_answer.
    IF v_answer = 'J'.
*-- run in the background
      CALL FUNCTION 'JOB_OPEN'
           EXPORTING
                jobname          = 'ZTEST'
           IMPORTING
                jobcount         = v_jobcount
           EXCEPTIONS
                cant_create_job = 1
                invalid_job_data = 2
                jobname_missing = 3
                OTHERS           = 4.
      IF sy-subrc <> 0.
        MESSAGE ID sy-msgid TYPE 'E' NUMBER sy-msgno
                WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
        EXIT.
      ENDIF.
*-- submit the program in the background
      SUBMIT ztest
        WITH p_bkrun = 'X'
        WITH p_vbeln = p_vbeln
        USER sy-uname
        VIA JOB 'ZTEST' NUMBER v_jobcount AND RETURN.
*-- close the job
      CALL FUNCTION 'JOB_CLOSE'
           EXPORTING
                jobcount             = v_jobcount
                jobname              = 'ZTEST'
                strtimmed            = 'X'
           EXCEPTIONS
                cant_start_immediate = 1
                invalid_startdate    = 2
                jobname_missing      = 3
                job_close_failed     = 4
                job_nosteps          = 5
                job_notex            = 6
                lock_failed          = 7
                OTHERS               = 8.
      IF sy-subrc <> 0.
        MESSAGE ID sy-msgid TYPE 'W' NUMBER sy-msgno
                WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
      ENDIF.
      EXIT.
    ELSE.
      CLEAR v_answer.
    ENDIF.
ENDIF.
CHECK v_answer IS INITIAL.
SELECT SINGLE * FROM vbak
                  INTO ls_vbak
                 WHERE vbeln = p_vbeln.
IF sy-subrc <> 0.
    WRITE:/ 'Invalid Order Id.'.
ENDIF.
END-OF-SELECTION.
CHECK v_answer IS INITIAL.
IF p_bkrun IS INITIAL.
    WRITE:/ 'Here is the result running the program in foreground.'.
ELSE.
    WRITE:/ 'Here is the result running the program in background.'.
ENDIF.
WRITE:/ ls_vbak-vbeln,
          ls_vbak-vkorg.

JOB Scheduling problem

Hi All,
My problem is the next:
I would like to call two functions, in one function module, but I cannot schedule the second job after the first. I wrote the code, use the parameter PREDJOB_CHECKSTAT of JOB_CLOSE, but when the mother function called two jobs started immediately and paralell. What is worng in the following code?
Thanks /and points :)/ for your help!
Tamas
      L_JOBNAME = 'REQUEST_COPY'.
      CALL FUNCTION 'JOB_OPEN'
        EXPORTING
          JOBNAME = L_JOBNAME
        IMPORTING
          JOBCOUNT = L_JOBCOUNT.
      SUBMIT RSSEM_REQUEST_COPY
                   WITH RNR = I_RNR
                   WITH S_CUBE = LS_CUBES-SOURCE_CUBE
                   WITH T_CUBE = LS_CUBES-TARGET_CUBE
                   USER SY-UNAME VIA JOB L_JOBNAME NUMBER L_JOBCOUNT
                   AND RETURN.
      CALL FUNCTION 'JOB_CLOSE'
        EXPORTING
          JOBCOUNT = L_JOBCOUNT
          JOBNAME   = L_JOBNAME
          STRTIMMED = 'X'.
      L_JOBNAME2 = 'REQUEST_CLOSE'.
      CALL FUNCTION 'JOB_OPEN'
        EXPORTING
          JOBNAME = L_JOBNAME2
        IMPORTING
          JOBCOUNT = L_JOBCOUNT2.
     SUBMIT Z_REQUEST_CLOSE_ZSD_P25
               USER SY-UNAME VIA JOB L_JOBNAME2 NUMBER L_JOBCOUNT2
               AND RETURN.
      CALL FUNCTION 'JOB_CLOSE'
        EXPORTING
          JOBCOUNT = L_JOBCOUNT2
          JOBNAME   = L_JOBNAME2
          STRTIMMED = 'X'
          PREDJOB_CHECKSTAT = 'X'
          PRED_JOBCOUNT = L_JOBCOUNT
          PRED_JOBNAME = L_JOBNAME.

Hi Thomas,
Thanks for all helps, I found the solution!
Inserted a select from the Job Status Table into th second job definition.
Thanks for the ideas!
Tamás
The finally code is the the following:
      L_JOBNAME = 'REQUEST_COPY'.
      CALL FUNCTION 'JOB_OPEN'
        EXPORTING
          JOBNAME = L_JOBNAME
        IMPORTING
          JOBCOUNT = L_JOBCOUNT.
      SUBMIT RSSEM_REQUEST_COPY
                   WITH RNR = I_RNR
                   WITH S_CUBE = LS_CUBES-SOURCE_CUBE
                   WITH T_CUBE = LS_CUBES-TARGET_CUBE
                   USER SY-UNAME VIA JOB L_JOBNAME NUMBER L_JOBCOUNT
                   AND RETURN.
      CALL FUNCTION 'JOB_CLOSE'
        EXPORTING
          JOBCOUNT = L_JOBCOUNT
          JOBNAME   = L_JOBNAME
          STRTIMMED = 'X'.
      L_JOBNAME2 = 'REQUEST_CLOSE'.
      CALL FUNCTION 'JOB_OPEN'
        EXPORTING
          JOBNAME = L_JOBNAME2
        IMPORTING
          JOBCOUNT = L_JOBCOUNT2.
      DO.
        SELECT SINGLE STATUS FROM TBTCO INTO L_STATUS
          WHERE JOBNAME = L_JOBNAME
          AND JOBCOUNT = L_JOBCOUNT.
        IF L_STATUS = 'F'.
          EXIT.
        ELSE.
          WAIT UP TO 1 SECONDS.
        ENDIF.
      ENDDO.
      SUBMIT Z_REQUEST_CLOSE_ZSD_P25
                USER SY-UNAME VIA JOB L_JOBNAME2 NUMBER L_JOBCOUNT2
                AND RETURN.
      CALL FUNCTION 'JOB_CLOSE'
        EXPORTING
          JOBCOUNT          = L_JOBCOUNT2
          JOBNAME           = L_JOBNAME2
          STRTIMMED         = 'X'
          PREDJOB_CHECKSTAT = 'X'
          PRED_JOBCOUNT     = L_JOBCOUNT
          PRED_JOBNAME      = L_JOBNAME.

Job schedule problem

Dear All,
I'm in confusion and want your expart comment on this -
One of my application user has scheduled a job in a schema at night 12:00 AM where job number was 154. Due some other requirement another job planned to schedule on the same schema on the same database at next day morning 7:00 am. The person who has schedule the job where job number is showing 183.
My question is that oracle provide the job number as per sequence. Is it possible to have a gap between two job number. Another question is that is it possible to know last few job numbers from the database.
we are using the oracle version 9i release 2 and OS is windows.

Hi,
See Basically the JOBNO column is performed via the JOBSEQ sequence, which has a default cache size of 20 and Coming to the Sequence Gap there may be Chance that another Jobs might be created by some user in other schema and due that you might found the difference "Gap" in the Job Number (that might be the thing,I suppose that)
- Pavan Kumar N

Problem with background job schedule

Hi friends,
How to schedule more than one data loading jobs in backround??
When i try to schedule the second job,the first scheduled job is getting overwritten,and only this job is active.
I tried in infopack,scheduler...
How to overcome this???
Regards
sudhakar

Hello Ragu,
How r u ?
Use Process Chains for this multiple Job Scheduling.
I think u r teying to schedule the same InfoPackage !
Could u elobrate ur issue ?
Best Regards....
Sankar Kumar
+91 98403 47141

Job scheduling tutorial - problem

Hi
I'm recognizing job scheduling mechanizm in NW 7.11. I have followed this tutorial:
https://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/90a95132-8785-2b10-bda5-90d82a76431e&overridelayout=true
And so far I cannot see job definition in NWA. Any suggestions will be appreciated.
Best Regards
Maciej

I've found the reason. In tutorial there is job-definitions.xml file suggested instead of job-definition.xml
Regards
Maciej

Standard Job SAP_CCMS_MONI_BATCH_DP is cancelling

Hello All
I am facing problem with standard job SAP_CCMS_MONI_BATCH_DP...It is scheduled on hourly basis.
But on some days at some time it is failing with only one error message as
08/04/2011 17:52:26 Job started
08/04/2011 17:52:26 Step 001 started (program RSAL_BATCH_TOOL_DISPATCHING, variant , user ID
08/04/2011 17:52:29 You can only work in client 320
08/04/2011 17:52:29 Job cancelled
There is no specific time that it is failing.Please suggest me how can i resolve this?
Manmohan Soni

Hi,
Looks like the client in which job is to run, is different from which client the job is called from.
Check thread: Sm37 job problem
Also check sm21 log to get more details.
Regards,
Srikishan

Job scheduling

Hi Friends,
i have a problem with job scheduling.
two jobs need to be scheduled. (job1 and job2)
i used
job_open.
submit job1 using parameters.
job_close.
then for second job.
job_open.
submit job2 using parameter2.
job_close.
when i go and look in sm37. i see when job1 is running the job2 is in release status.
but what we need is when job1 is running job2 should be in schedule status. it should start only after job1 is completed.
in the job2 job_close i used job1 as the PRED_JOBNAME.
but i when i run the program job2 is in released status , not in schedule mode.
is there any way we can make the job2 in scheduled mode instead of release.
can we use event to control this. if yes please let me know how we can do it.
Thanks

Hi,
As Appana wrote - i'm not sure there's a problem, but why don't u make one job with 2 steps? this way u will be perfectly sure that job2 (2nd step in the new job) will run only after job1 (1st step n the new job)...
Good luck
Igal

SAP Standard Jobs are getting canceled

Hi Basis Gurus,
In our Quality BW 3.5 system the SAP Standard jobs are getting canceled.
The jobs are as follows
SAP_APPLICATION_STAT_COLLECTOR
SAP_CCMS_CPH_HRCOLL
SAP_CCMS_MONI_BATCH_DP
SAP_COLLECTOR_FOR_JOBSTATISTIC
SAP_COLLECTOR_FOR_NONE_R3_STAT
SAP_COLLECTOR_FOR_PERFMONITOR
SAPCONNECT ALL SEND
SAP_REORG_ABAPDUMPS
SAP_REORG_SPOOL
SAP_RSICFDLT
In SM37 when i click on the job log for the above mentioned jobs the system is promting a message saying as "Error reading job log"
Please let me know how can troubleshoot it and resolve this issue.
Our is qulaity BW 3.5 system
Solaris OS
Oracle Database
Please help me.
Regards,
Anil.

Hi ,
For log display reason, try the note suggested. Jobs cancel reason may be due to that the user who schedule that job are locked or not exist on that client. Or other reason will be clear only after log display.
Ankit

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

What is the spool, what is its role in background job scheduling

Hi,
I want to know what is meant by Spool request and spool number generated.
Tell about transaction SP01.
How it is linked to Background job scheduling.
thanks.
sam.

Hi,
Refer this link.
https://www.sdn.sap.com/irj/sdn/inf?rid=/library/uuid/7a5f4061-0a01-0010-c9bc-a4e4cb100438
About SP01.
Printing does not work in SAP. There is a printer definition for your local printer, but it does not work. Presuming that you use the program SAPLPD on your computer.
Boot your computer and start only the SAPLogon and the SAPLpd program.
Delete all of your old print jobs in the SAP system (Transaction SP01).Generate only one new print job.
Check that there is enough resource in your computer. Check the free memory (Win 3.1x) and the free disk space (The lists are temporarily saved on your disk).
Open the SAPLPD and read the print log in the window. The printer definition must correspond with the parameters shown here.
Check that the standard printer is on the same lpt (Win 3.1: Control panel, Printer) as defined for the printer (usually lpt1).
In Transaction SP01 read the protocol of your print job. Do not generate new print jobs! Wait till the SAP system changes the status of the print job.
If you can not find the print job in SP01 anymore, then the print job was successfully printed out. If it didn't come out on your printer and the SAPLpd didn't indicate an incoming print job, then the connection was realised with another PC. Then SAP printer definition you used, does not correspond with your computer.
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 u201CSend to SAP spooler Only for nowu201D
b.        Name u2013 abbreviated name to identify the job output
c.        Title u2013 free form description for the report output
d.        Authorization u2013 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 u2013 set to appropriate department/functional area name. This field can be used in
a search later.
f.        Retention period u2013 set to u201CDo not deleteu201D 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 jobu2019s 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 u201CParametersu201D button on a SAP Printer selection dialog, it
allows to specify all the parameters as described in p. 3 of
u201CScheduling background jobsu201D 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 u201CScheduling background jobsu201D section).
Access to reportu2019s 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 u201CFurther selection
criteriau2026u201D button (e.g. to bring u201CSpool request name (suffix 2)u201D 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 jobu2019s outputs)
a.        Spool request name (suffix 2) u2013 corresponds to a spool name in p. 3.b in
u201CScheduling background jobsu201D section above).
b.        Date created u2013 to find an output of a job that ran within a certain date range.
c.        Title u2013 corresponds to spool Title in p. 3.c in u201CScheduling background jobsu201D
section above).
d.        Department - corresponds to spool Department in p. 3.e in u201CScheduling
background jobsu201D 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 u201CPrint with changed attributedu201D button   to print the spool request
with the different attributes (e.g. changing the printer name).
c.        Click the u201CDisplay contentsu201D button   to preview the spool request contents. A
Print    and Download   functions are available from the preview mode.
Exporting the Contents of a Spool Request
Use
You want to export the contents of a spool request as a text file to the SAP GUI working directory or to a directory of your choice. The content of the spool request is downloaded as plain text without, for example, graphics, images, or specific fonts.
The following procedures are irrelevant for the PDF-based form printing integrated as of SAP Web Application Server 6.40, since the print data can be opened and stored as a PDF. See also Displaying and Printing PDF-Based Forms.
Procedure
Exporting to the SAP GUI Working Directory:
Choose Spool Request ® Forward® Export as Text.
The entire text is stored in your SAP GUI working directory in ASCII format.
A file of this type is named using the following pattern:
.txt
Example: ABC0000004327.txt
You require appropriate authorization for this function.
Exporting to a Directory of Your Choice:
With this method of exporting a spool request, the content of the spool request is first displayed and you then download the screen list as a text file to the directory of your choice.
       1.      Select the spool request to be exported and choose Display Contents.
       2.      In the case of SAPScript/Smart Forms documents, activate list display by choosing Goto.
       3.      Choose System ® List ® Save ® Local File.
       4.      Choose one of the available formats and confirm your choice.
       5.      Choose a directory and save the spool request.
By default, only the first 10 pages of a spool request are saved in a file. You can increase the number of pages to be saved by choosing Goto ® Display Requests ® Settings and making the desired entries in the Display Area group box.

Data capturing in background job scheduling

HI,
I hava a specific requirement in background job scheduling.
in my layout i have to show <b>pagenumber / total number of page numbers.</b>
for that iam useing a variable with value '$$$' and iam replacing this variable with total number of pages..
when we run in foreground it is working fine. but in background the variable is not being replaced..
how can i modify the data in spool..

REPORT ztest no STANDARD PAGE HEADING
                                 MESSAGE-ID zfi
                                 LINE-COUNT 65(1)
                                 LINE-SIZE 165.
DATA:        v_sum(3) TYPE c VALUE'$$$'.
CONSTANTS: c_slash    TYPE c VALUE '/'.        "Stores /
parameters : p_1 type c.
START-OF-SELECTION.
WRITE : 'Hi'.
SKIP 80.
WRITE : 'Helloo'.
END-OF-SELECTION.
*To print the total no. of pages in report heading.
PERFORM f_replace_totpage.
TOP-OF-PAGE
TOP-OF-PAGE.
Display Standard Report Header
PERFORM f_report_header.
*&      Form f_replace_totpage
     To print the total no. of pages in report heading.
FORM f_replace_totpage .
DATA: l_tot_page(3) TYPE c,
        l_pgcnt TYPE i,
        l_licnt TYPE i VALUE '3'.
Assign value of total number of pages into l_tot_page.
l_tot_page = sy-pagno.
To replace the value of v_sum ($$$) by total number of pages after
reading the content of fourth line of each page.
WHILE l_pgcnt LE l_tot_page.
    l_pgcnt = l_pgcnt + 1.
    READ LINE l_licnt OF PAGE l_pgcnt.
    REPLACE v_sum WITH l_tot_page INTO sy-lisel.
    MODIFY LINE l_licnt OF PAGE l_pgcnt.
ENDWHILE.
CLEAR: l_tot_page,
         l_pgcnt,
         l_licnt.
ENDFORM.                    " f_replace_totpage
*&      Form f_report_header
      Report Header display
FORM f_report_header.
FORMAT COLOR 1 INTENSIFIED ON.
Text-246 - Page:
WRITE:/1 text-247, 45 text-241, 110 text-242, 150 space.
WRITE:/1 text-243, sy-repid, 110 text-244, sy-datum, c_slash, sy-uzeit,
         150 space.
WRITE:/1 text-245, sy-uname, 110 text-246, sy-pagno,c_slash,v_sum,
         150 space.
FORMAT COLOR OFF.
ULINE.
ENDFORM.                    " f_report_header

Standard job scheduling problem

Similar Messages

Maybe you are looking for