Schedule a daily job using JOB_CLOSE

Hello,
I want to schedule a daily job using job_open, job_submit & job_close.
This job should run everyday at 22:00 hrs.
What are the parameters I need to set for the FM JOB_CLOSE?
Thanks,
A Pothuneedi

Look at this sample provided by SAP : <a href="http://help.sap.com/saphelp_sm32/helpdata/en/fa/096d8e543b11d1898e0000e8322d00/content.htm">Sample Program: Start-Time Window with JOB_CLOSE</a>
Sample Program: Start-Time Window with JOB_CLOSE Locate the document in its SAP
<b>Library structure</b>
* Submit job: start-time window defined, with periodic repeat and
* with target system upon which the job is to run.
* In this case, you must provide start date settings. You can
* have the job started immediately with a JOB_CLOSE parameter,
* set the start date yourself, or ask the user with
* BP_START_DATE_EDITOR.
* Example: Provide start-date specifications yourself.
STARTDATE = '19970101'.
STARTTIME = '160000'.
LASTSTARTDATE = '19970101'.
LASTSTARTTIME = '180000'.
CALL FUNCTION 'JOB_CLOSE'
EXPORTING
JOBCOUNT = JOBNUMBER " Job identification: number
JOBNAME = JOBNAME " and name.
SDLSTRTDT = STARTDATE " Start of start-time...
SDLSTRTTM = STARTTIME " window
LASTSTRTDT = LASTSTARTDATE " Optional: end of...
LASTSTRTTM = LASTSTARTTIME " start-time window
PRDMONTHS = '1' " Restart at intervals of
PRDWEEKS = '1' " the sum of the PRD*
PRDDAYS = '1' " parameters
PRDHOURS = '1'
PRDMINS = '1'
STARTDATE_RESTRICTION = BTC_DONT_PROCESS_ON_HOLIDAY
" Restrict job start to work
" days; don't start job if
" scheduled on holiday.
" Other values:
" BTC_PROCESS_BEFORE_HOLIDAY
" BTC_PROCESS_AFTER_HOLIDAY
CALENDAR_ID = '01' " ID of R/3 factory calendar
" for determining workdays
TARGETSYSTEM = 'hs0011' " Optional: name of the host
" system on which the job is
" to run. Set only if
" absolutely required.
" Example: A required tape
" drive is accessible only
" from a single host system.
IMPORTING
JOB_WAS_RELEASED = JOB_RELEASED " If user has authorization
" to release jobs to run, job
" is automatically released
" when it is scheduled. This
" field is set to 'x' if the
" job has been released.
" Otherwise, the job is sche-
" duled but must be released
" by an administrator before
" it can be started.
EXCEPTIONS
INVALID_STARTDATE = 01
JOBNAME_MISSING = 02
JOB_CLOSE_FAILED = 03
JOB_NOSTEPS = 04
JOB_NOTEX = 05
LOCK_FAILED = 06
OTHERS = 99.
IF SY-SUBRC > 0.
<Error processing>
ENDIF.
Regards

Similar Messages

  • How to schedule the background job using current selection screen field val

    Hello Friends,
    How to schedule the background job using current selection screen field values.
    after completion of the job the spool should be sent as a mail to SAP Inbox.
    Is there any way to create the variant dynamically by reading the current selection screen values.
    Thanks,
    Ravi

    Hi,
    To get the variant details you can use teh following FM.
    'RS_VARIANT_CONTENTS'.
    Regards,
    Ankur Parab

  • How to schedule a background job using the Event concept..?

    Hi Folks,
    I have a requirement that, I need a schedule a background job.
    Once after the previous job successful only, new job should get triggered. How to go ahead with this..?
    For Eg, I am scheduling a job called ZTEST periodically for 1 minute. If the job is not get completing with in 1 minute, I dont want to start my new job. Only after the success of my old job, I want my new job to run.
    Waiting for ur replies.
    Regards,
    Savi.

    Hi,
    You can use events that have already been defined, or you can create new events for scheduling background jobs.
    If you wish to use new events, do the following to implement the event scheduling:
    Define and transport the event as a user event with transaction SM62.
    You must define only event IDs; event arguments are not defined in the R/3 System. Instead, you specify event arguments when you schedule a job to wait for an event and when you trigger the event.
    If you define a new event, you must also transport it to your production systems. The event transaction does not have a connection to the transport system. Instead, you must create a transport request for the event yourself.
    Do this to transport an event:
    Create a transport request.
    Start the editor in the transport request and enter the following:
    R3TR TABU <table name> where table name is BTCSEV for a system event ID, BTCUEV for a user event ID.
    Press F2 with the cursor on the table name to call up the screen for specifying the table entries to transport. In this screen, enter the event ID’s that you have created.
    Save and release the transport request. Ensure that it is imported into your production system(s).
    To trigger an event, add:
    – the function module BP_EVENT_RAISE to your ABAP program, or
    – the program SAPEVT to your external script, batch file, or program.
    When your programs execute these keywords, an event will be triggered in the R/3 background processing system. The event-based scheduler is started immediately. It in turn starts all jobs that were waiting upon the event, subject to normal background processing restrictions, such as the requirement that the job has been released to start.
    Schedule the jobs that are to run when your events are triggered.
    You can schedule jobs for one-time start or to be started whenever an event is triggered.
    Regards,
    Raj.

  • Scheduling an Export Job Using Grid Control

    Hi,
    I got a requirement to schedule export jobs in Oracle Grid Control 10.2.0.5 (Windows). Is this possible and have any one done this? If so please share the steps. The idea is to get alerts if the job fails.
    Thanks.
    GB

    Here is the easy steps (There might be slight differences as I am posting it based on 11g screen)
    1. On grid control console, click on the relevant database
    2. click on 'Data Movement' tab
    3. Click on 'Export to Export Files'
    4. chose the Export type (Database / Schema / Tables/ Tablespace)
    5. Provide Host credentials (OS username and Password) and click on 'Continue'. You will get a new screen called 'Export: Options'
    6. Click the checkbox called 'Generate Log File' and select the Directory object where you wants to create the dump files. (You need to create a directory object in database, if you don't have one)
    7. Chose the contents option as you required, and click '*Next*'. You will get a new page called 'Export: Files'
    8. Select the directory object from the drop-down box and provide a name format for file name, and click 'Next'
    9. Here you provide the Job name and description, and chose repeat options (daily, weekly etc), and click 'Next'
    10. You will get a summary screen called 'Export: Schedule'. review your job details and click on 'Submit'.
    This is the solution, and it works well.

  • Scheduling Time Based Jobs using Web Dynpros.

    Hello Again,
    I would like to know if it is possible to perform time based jobs using Web Dynpros, I have a situation where a Web Dynpro application updates a Database and then later during the day say at around 9:00 PM, I would like the Web Dynpro application to transfer all the updated Data to another Database, I know we can run a batch job but can we run create a Web Dynpro application to programatically fire a batch job at the required time.
    I am welcome to any suggestions.
    Best Wishes,
    John.

    Hi John,
    WD is not good option for this. I would suggest you to "extract" logic to separate layer and use Timeout service (http://help.sap.com/saphelp_webas630/helpdata/en/6b/2550d23ef1994580114d6064bc44a1/frameset.htm) - call logic from service.
    Best regards, Maksim Rashchynski.

  • Scheduling a background job using Job_Submit and Job_Close FM

    Hi Guys,
                  I am calling a report in background using Job_Submit and Job_Close FM's.
    I am not providing start time and date in the Job_close FM, in this case, when the job will be scheduled to start.
    Even after an hour, job status is still scheduled.
    I am not exporting variant, since I am using memory ID.
    Thanks
    Edited by: sapgeek007 on May 11, 2009 4:11 AM

    In Job_close fm use the parameter 'STRTIMMED'
    CALL FUNCTION 'JOB_CLOSE'
      EXPORTING
        jobcount                          = LV_NUMBER
        jobname                           = LV_NAME
        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
       INVALID_TARGET                    = 8
       OTHERS                            = 9
    IF sy-subrc <> 0.
    MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
            WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
    ENDIF.
    That would start the background job immediately.
    Regards,
    Deepak

  • How to Schedule a daily job for ELM

    Hi All, 
      We have a requirement to create prospects using ELM.However, we have to automate this process and run this as a regular batch job. 
      When checked ELM does not provide an option to run the job periodically. 
      Please suggest to resolve this .
    Thanks & Regards,
    Shwetha.

    Hi Shwetha,
    Please refer to this thread.
    http://scn.sap.com/thread/2026686
    Best Regards,
    Yoro

  • Schedule job with JOB_CLOSE until a certain time

    Hello all,
    I'd like to schedule a background job with JOB_CLOSE until a certain time, i.e. first start time at 10 a.m., repitition period 15 min., last start time 1 p.m.
    I tried this using parameter LASTSTRTTM, e.g.:
    i_startdate = sy-datum.
    i_starttime = '100000'.
    i_prdmins = '15'.
    i_laststrtdt = sy-datum.
    i_laststrttm = '130000'.
    CALL FUNCTION 'JOB_CLOSE'
        EXPORTING
          jobcount             = l_jobcount
          jobname              = 'MY_JOB'
          sdlstrtdt            = i_startdate
          sdlstrttm            = i_starttime
          laststrtdt           = i_laststrtdt
          laststrttm           = i_laststrttm
          prdmins              = i_prdmins
        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.
    but I didn't succeed - the job didn't stop at 1 p.m. Any hints?
    Best regards
    Martin Lehmann

    Hi Martin,
    i_startdate = sy-datum.  " 1st time Job Start Date
    i_starttime = '100000'.
    i_prdmins = '15'.
    i_laststrtdt = sy-datum.  " If Job is not started by this date, then it wont be started once this date is completed
    i_laststrttm = '130000'.
    What it means is, if i want to start a job by 10th Oct.. & expect that it should be started maximum by 20th Oct.. If its 20th Oct & still the job is not started,... then terminate the job & do not start it..
    If the job is already started, then it wont stop.
    Hope its clear.
    Best regards,
    Prashant

  • Schedule Background job using transaction CATM

    Hi all,
    Since we cannot schedule a background job using transaction CATM, I have created a program calling the CATM transaction through batch-input.
    I have done a recording and entered the coding in a Z-program. For a vendor, I have recorded time in CAT2 for multiple purchase orders.
    After entering the vendor number in CATM, all the purchase orders showed up. I have clicked 'select all' and posted.
    When I run the program in the background, it posts only for one purchase order.
    When I  run the program in the foreground, using the Select All-button it only proceeds with the first line in my list of PO's.
    How to read the whole stack and post the whole stack of purchase orders? 
    Please help me out with this.
    Thanks
    Regards
    Srinivasan Desingh
    408 368 3837

    Hi,
    When I run the program in the background, it posts only for one purchase order.
    When I  run the program in the foreground, using the Select All-button it only proceeds with the first line in my list of PO's.
    See..it's a Z-program so Its difficult to answer without checking the program. But I think, you should check your BDC again from Debugging, with the help of your abaper. You will find, why its is processing only one entry.
    Regards
    Shishir

  • Re-Scheduling the background job.

    Hello All,
    How do you schedule the daily job for closing the reconciliation key FPG4 and transferring them to R3 FPG1.
    Regards
    Charvi

    Hi,
    I seen this transaction running on back ground, unfurtunately I didnt run it but this is my experience.
    We used it to run availability check every 4 hours and the system performance gets lows, of course it depends on technical architecture and volume of material. It reads every line on sales ordes that, in ours scenarios was so high (about 5000 lines in one day or more).
    It works perfectly, but buffers get alarme on pics of the operations.
    If you program it on low transaction volume, if can be very good, you may also talk before with your basis and explain him this performance issue, maybe he can help.
    I hope you find this hopeful.
    Regards,
    RP

  • Scheduling a Background Job for PM/CO Settlements (KO8G)

    Hi All,
    I've created variants for settlements of PM & CO orders using transaction KO8G. Now I want to schedule a background job using TCode SM36. What program name/ABAP name should I use for settlements when scheduling background jobs?
    Regards,
    Tso

    Hello Tso,
    Try transaction SCMO which provides you the option to set
    the start date to finish date and can also set the start time and
    finish time and allows you to specify the variant to be used.
    When in transaction KO8G fill out the fields as you wish them for
    the background job and then same the selection as a variant. There is
    an option to have the variant for background jobs and save the variant
    then you can specify this variant in the SCMO screen.
    SCMO is the sceduele manager which will allow you to scehedule many
    jobs as necessary.
    Some notes:
      332149  SCMA: Required workflow settings
      325118  Schedule Manager: link customer-specific reports
      317601  Schedule Manager: Customer reports for multilevel worklist
      332149  SCMA: Required workflow settings
      891042  SCHEDMAN: Automatic start of several flow definitions
    I hope this helps.
    Regards,
    Lucas

  • Job Scheduling using job_close

    Hi gurus,
    im trying to scheduke several jobs using the FM Job close, but the jobs are running paralel..
    The first job its' schedule with a start date or imediate, and the letf ones are schedule to start after his precessor finish, but once i run the programa 4 jobs start running ...
    Can any one help me on this?
    Below goes my code...
      DO njobs TIMES.
    **Nome de Job
        CLEAR: jobname, jobcount, job_release.
        CLEAR: job_imediate, str_job.
        ADD 1 TO ind_job.
        WRITE ind_job TO str_job.
        CONCATENATE 'EXECORC' sy-uname sy-uzeit str_job
                     INTO jobname SEPARATED BY '-'.
        CALL FUNCTION 'JOB_OPEN'
             EXPORTING
                  jobname          = jobname
             IMPORTING
                  jobcount         = jobcount
             EXCEPTIONS
                  cant_create_job  = 1
                  invalid_job_data = 2
                  jobname_missing  = 3
                  OTHERS           = 4.
        IF sy-subrc <> 0.
          MESSAGE i003(zmapas).
          EXIT.
        ENDIF.
        IF gv_global EQ 'X'.
    **Submit job
          SUBMIT z_mapa_execucao_orcamental
                 VIA JOB jobname NUMBER jobcount
                 WITH ano EQ ano
                 WITH so_perio IN so_perio
                 WITH so_date IN so_date
                 WITH so_org EQ so_org
                 WITH so_num IN so_num
                 AND RETURN.
        ELSE.
    ***Limites
          CLEAR: upper_bound, lower_bound.
          upper_bound = njobs * ind_job.
          lower_bound = upper_bound - njobs + 1.
          CLEAR so_num.
          REFRESH so_num.
          LOOP AT tab_prog FROM lower_bound TO upper_bound.
            so_num-sign = 'I'.
            so_num-option = 'EQ'.
            so_num-low = tab_prog-zlinha.
            APPEND so_num.
          ENDLOOP.
          SUBMIT z_mapa_execucao_orcamental
                 VIA JOB jobname NUMBER jobcount
                 WITH ano EQ ano
                 WITH so_perio IN so_perio
                 WITH so_date IN so_date
                 WITH so_org EQ so_org
                 WITH so_num IN so_num
                 AND RETURN.
        ENDIF.
        IF ind_job EQ 1.
          IF stdt_output-startdttyp EQ 'I'.
            job_imediate = 'X'.
          ENDIF.
          CALL FUNCTION 'JOB_CLOSE'
               EXPORTING
                    jobcount             = jobcount
                    jobname              = jobname
                    sdlstrtdt            = stdt_output-sdlstrtdt
                    sdlstrttm            = stdt_output-sdlstrttm
                    strtimmed            = job_imediate
               IMPORTING
                    job_was_released     = job_release
               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 i003(zmapas).
            EXIT.
          ELSE.
            CLEAR: predjob, predjobcount, stdt_output.
            predjob = jobname.
            predjobcount = jobcount.
            MESSAGE s004(zmapas) WITH jobname.
          ENDIF.
        ELSE.
          CALL FUNCTION 'JOB_CLOSE'
               EXPORTING
                    jobcount             = jobcount
                    jobname              = jobname
    *                predjob_checkstat    = 'X'
                    pred_jobcount        = predjobcount
                    pred_jobname         = predjob
    *                strtimmed            = 'X'
               IMPORTING
                    job_was_released     = job_release
               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 i003(zmapas).
            EXIT.
          ELSE.
            CLEAR: predjob, predjobcount, stdt_output.
            predjob = jobname.
            predjobcount = jobcount.
            MESSAGE s004(zmapas) WITH jobname.
          ENDIF.
        ENDIF.
    Thanks in Advance,
    Best Regards,
    João Martins

    Hello.
    First of all, parameter predjob_checkstat makes the second job to start only if the previous one ends without error. Probably this solves your problem at all ... the second waits to the end of the first to see if it ended with error or not.
    I was analysing your problem. Parameter strtimmed can only be set in the first JOB_CLOSE. All the others cannot have this parameter set to 'X' if you want them to wait for the end of the previous ones.
    So, try predjob_checkstat = 'X' and strtimmed = space.
    Also, I have one example that is working:
    *** Escalona um JOB para cada ficheiro encontrado.
        LOOP AT t_processar.
          CLEAR: w_jobcount, w_jobname, l_liberado.
          ADD 1 TO l_conta.
          MOVE l_conta TO l_conta2.
          CONDENSE l_conta2.
          CONCATENATE t_jobs-jobname l_conta2 INTO w_jobname.
          CALL FUNCTION 'JOB_OPEN'
               EXPORTING
                    jobname          = w_jobname
               IMPORTING
                    jobcount         = w_jobcount
               EXCEPTIONS
                    cant_create_job  = 1
                    invalid_job_data = 2
                    jobname_missing  = 3
                    OTHERS           = 4.
    ***   Criou-se o JOB com sucesso
          IF sy-subrc = 0.
            CLEAR seltab_wa.
    ***     Monta o parâmetro
            MOVE: t_jobs-param TO seltab_wa-selname,
                  t_processar-line+34 TO seltab_wa-low.
            APPEND seltab_wa TO seltab.
            seltab_wa-selname = 'P_LOJA'.
            seltab_wa-low = t_processar-ficheiro+7(4).
            APPEND seltab_wa TO seltab.
    ***     Submete o programa para o JOB
            SUBMIT (t_jobs-repid)
                   WITH  SELECTION-TABLE seltab
                   USER sy-uname
                   VIA JOB w_jobname NUMBER w_jobcount
                   AND RETURN.
    ***     Encerra o JOB
            IF l_conta EQ 1.
              l_hora = sy-uzeit.
              ADD 120 TO l_hora.
              CALL FUNCTION 'JOB_CLOSE'
                   EXPORTING
                        jobcount             = w_jobcount
                        jobname              = w_jobname
                        sdlstrtdt            = sy-datum
                        sdlstrttm            = l_hora
                        targetserver         = w_servidor
                   IMPORTING
                        job_was_released     = l_liberado
                   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.
            ELSE.
              CALL FUNCTION 'JOB_CLOSE'
                   EXPORTING
                        jobcount             = w_jobcount
                        jobname              = w_jobname
                        predjob_checkstat    = 'X'
                        pred_jobcount        = w_jobcount2
                        pred_jobname         = w_jobname2
                        targetserver         = w_servidor
                   IMPORTING
                        job_was_released     = l_liberado
                   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.
            ENDIF.  "l_conta eq ...
          ENDIF. "sy-subrc = 0 do JOB-OPEN
          w_jobname2  = w_jobname.
          w_jobcount2 = w_jobcount.
          PERFORM f_limpa_param.
        ENDLOOP. "at t_processar
    Regards.
    Valter Oliveira.

  • How can i schedule jobs daily by using fm's

    hi all,
    am using open job ,submit job,close job fm's to schedule back ground jobs,
    want to schedule it daily which parameter i need to pass in close_job for daily job scheduling

    you can get the clear documentation by using ABAPDOCU transaction.
    Regards
    Mani.

  • 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 job’s 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 report’s 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 job’s 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.

  • Exact Steps to schedule a background job a specific time daily :

    Dear  All,
               Please let me know  the whole process involved in schedule a background job a specific time daily. what is calender id. I could not understand what it has given in SM36.
    Thanks in advance.
    Rgds
    Prem.

    Hi prem
    this is complte procedure for ur requirment.
    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
    Call Transaction SM36 or choose CCMS ® Jobs ® Definition .
    Assign a job name. Decide on a name for the job you are defining and enter it in the Job Name field.
    Set the jobu2019s priority, or "Job Class":
    High priority: Class A
    Medium priority: Class B
    Low priority: Class C
    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.
    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.
    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.
    Define the jobu2019s steps by choosing Step, then specify the ABAP program, external command, or external program to be used for each step.
    Save the fully defined job to submit it to the background processing system.
    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.
    pls give points if it is usefull
    Regards
    Saimedha

Maybe you are looking for