Job Schedule (SM36)  query

I have a requirement:
I want to process something (Send a mail to the user) once a job is finished / cancelled / Errored.
I think one way of doing this is create a new step in the job and process it depending on the status of earlier step (But I doubt whether this can be achieved).
Is there a way of doing conditional exceution of any step (i.e The execution of a step  depends on the success/ failure of earlier steps)
Is there a better way of achieving this?
Thanks
Amit Jain

Thanks for your replies,
To be specific.. I have 30 jobs and if any of the 30 job errors (Status: Cancelled), a mail needs to be sent.
Some options I think of is:
1> create 30 new jobs which depends on the status of original 30 jobs and my job triggers only if the corresponding original job errors (Is there a way to accomplish this and how?)
2> Create an additional step in each 30 original job. This step should execute (which sends an email) if and only if any of the above steps has errored.
Can this be accomplished and how?
Thanks
Amit Jain

Similar Messages

  • Back Ground Job Scheduling SM36

        Hello Experts
    I have Created Variants for Reports and trying to schedule a back ground job based on the Variants.
    for 1 Report KOK5 The Program is SAPMKAUF of Type M. I get a Message i cant schedule a Job for Program Type  Other Than 1 or J. how Can i solve this Problem.
    I want the output in excel on schedule basis
    am new to SAP
    Thanks in Advance
    Sandeep

    Hi Sandeep,
    You will need to wrap that module pool program using a Transaction code then create  BDC, and execute this BDC coding in a report program.
    how to create background job please see the link : Scheduling Background Jobs (SAP Library - Configuration (New Technology))
    Reward if helpful
    Thanks

  • Job Scheduling -- About SM36

    Hi,
           can any tell me ..how to run the bdc thru job scheduling ( SM36 ). In my BDC I have Used GUI_UPLOAD function.So I want to Upload the data thru scheduling.
    Thx & Regards,
    Sunder.

    report zmiro
           no standard page heading line-size 255.
    include bdcrecx1.
    selection-screen begin of block blk3 with frame title text-019.
    parameters : pa_fname type localfile.
    selection-screen end of block blk3.
    data : lv_fname type string.
    data: begin of record occurs 2,
            bldat_003(010),
            xblnr_004(016),
            ebeln_008(010),
            zfbdt_021(010),
            xmwst_030(001),
            mwskz_031(002),
            wrbtr_050(016),
          end of record.
    at selection-screen on value-request for pa_fname.
      call function 'F4_FILENAME'
        exporting
          program_name  = syst-cprog
          dynpro_number = syst-dynnr
          field_name    = 'PA_FNAME'
        importing
          file_name     = pa_fname.
    start-of-selection.
    lv_fname = pa_fname.
    perform open_group.
    call function 'GUI_UPLOAD'
      exporting
        filename                      = lv_fname
        filetype                      = 'ASC'
        has_field_separator           = 'X'
      tables
        data_tab                      = record
    loop at record.
    if sy-subrc <> 0. exit. endif.
    perform bdc_dynpro      using 'SAPLMR1M' '6000'.
    perform bdc_field       using 'BDC_OKCODE'
                                  '/00'.
    perform bdc_field       using 'INVFO-BLDAT'
                                  record-bldat_003.
    perform bdc_field       using 'INVFO-XBLNR'
                                  record-xblnr_004.
    perform bdc_field       using 'BDC_CURSOR'
                                  'RM08M-EBELN'.
    perform bdc_field       using 'RM08M-EBELN'
                                  record-ebeln_008.
    perform bdc_dynpro      using 'SAPLMR1M' '6000'.
    perform bdc_field       using 'BDC_OKCODE'
                                  '=HEADER_PAY'.
    perform bdc_dynpro      using 'SAPLMR1M' '6000'.
    perform bdc_field       using 'BDC_OKCODE'
                                  '=HEADER_TOTAL'.
    perform bdc_field       using 'BDC_CURSOR'
                                  'INVFO-ZFBDT'.
    perform bdc_field       using 'INVFO-ZFBDT'
                                  record-zfbdt_021.
    perform bdc_dynpro      using 'SAPLMR1M' '6000'.
    perform bdc_field       using 'BDC_OKCODE'
                                  '=DUMMY'.
    perform bdc_field       using 'INVFO-XMWST'
                                  record-xmwst_030.
    perform bdc_field       using 'INVFO-MWSKZ'
                                  record-mwskz_031.
    perform bdc_dynpro      using 'SAPLMR1M' '6000'.
    perform bdc_field       using 'BDC_OKCODE'
                                  '=DUMMY'.
    perform bdc_field       using 'BDC_CURSOR'
                                  'INVFO-MWSKZ'.
    perform bdc_dynpro      using 'SAPLMR1M' '6000'.
    perform bdc_field       using 'BDC_OKCODE'
                                  '/00'.
    perform bdc_field       using 'BDC_CURSOR'
                                  'INVFO-WRBTR'.
    perform bdc_field       using 'INVFO-WRBTR'
                                  record-wrbtr_050.
    perform bdc_dynpro      using 'SAPLMR1M' '6000'.
    perform bdc_field       using 'BDC_OKCODE'
                                  '=PB'.
    perform bdc_dynpro      using 'SAPLMR1M' '6250'.
    perform bdc_field       using 'BDC_CURSOR'
                                  'RM08R-SUMME_SOLL'.
    perform bdc_field       using 'BDC_OKCODE'
                                  '=BU'.
    perform bdc_transaction using 'MIRO'.
    endloop.
    perform close_group.
    Hi the above is my program ..thru this program i want to upload thru scheduling how can i do ..kindly modify and give me the procedure for sm36...i dont any thing..about this..
    thx& Regards,
    sunder

  • Job Schedule Custom ABAP Class Every 2 weeks

    Hi Folks,
    I would like to ask if  possible to run custom ABAP class using JOB Schedule (SM36). I have created a custom class that needs to be run every two weeks.
    Thanks,
    Robert

    Hi,
    what do you mean by "run custom class"? If you mean calling methods of that class then no. But it is easy to write a simple report which will call required methods.
    Cheers

  • JOB SCHEDULING QUERY

    PLS HELP IN THIS REGARD
    WHEN TO USE  JOB SCHEDULING FMS EG: JOB_OPEN / JOB_SUMBIT / JOB_CLOSE  AND WHEN TO SCHEDULE JOBS THRU SM-36?  PLS TELL ME IN RESPECT TO DEV / PRD SERVERS IE: IF I AM WORKING ON DEV SERVER WHICH PROCESS WILL I OPT  AND WAT TO USE IN PRD SERVER ?  WAT IS THE USE OF GET_PRINT_PARAMETERS IN JOB SCHEDULING?

    Hi,
    JOB_OPEN / JOB_SUMBIT / JOB_CLOSE -> Used to schedule a report/program in background i.e on background workprocess.
    AND WHEN TO SCHEDULE JOBS THRU SM-36?- PLS TELL ME IN RESPECT TO DEV / PRD SERVERS IE: IF I AM WORKING ON DEV SERVER WHICH PROCESS WILL I OPT AND WAT TO USE IN PRD SERVER ?-> Background WP
    WAT IS THE USE OF GET_PRINT_PARAMETERS _. used to find the print parameters e.g in case you wnat to write data to spool

  • How to do the job scheduling in BDC Call transaction

    Hi Experts,
    I've a Query like how to do the job scheduling in BDC Call transaction
      If anybody knows the answer please send me the reply.
      Thanks.
       Regards,
        Rekha

    Hi ,
    any progarm can be scheduled, wether it may be BDC or report thru SM36 Tcode.
    But do rememeber that if ur BDC is using GUI_UPLOAD function module, then it wont work , coz the function Gui_upload or GUI_DOWNLOAd wont work in back ground.
    If u r going to use OPEN_DATASET , READ dataset ....then it can be scheduled. i.e BDC can work if ur program retrievesz the data from Application server.
    Rvert back if any issues,
    Reward with poinst if helpful.
    Regards,
    Naveen

  • 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 job’s 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 system’s 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 job’s 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 job’s 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 you’ve 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

  • Hi any one please explain background job scheduling

    Hi any one please explain background job scheduling . Good answer can be rewarded.
    Thanks

    Background jobs are pgms that are scheduled to be run in the Background without user interaction. So this can be done only for Type 1(executable) Program and not for Module-Pool Programs. Typically, a variant is defined and the pgm is run using the same.
    The transaction code is sm36 -Define Background job. Using the Start Condition tab you can define when you want the job to run (specific time or if it has to follow after a particular job is done etc.,) Using the Step tab you can assign the pgm name and variant.
    After the job is scheduled, you can check the status in sm37, along with the Job log and Spool.
    For more info:
    http://help.sap.com/saphelp_bw30b/helpdata/en/c4/3a7f87505211d189550000e829fbbd/content.htm

  • Background job schedule and mail triggering

    Hi Experts,
    I schedule a background job to run a custom program for project closure.The job is running successfully. But,the mail I am getting from this job run is same all the time (means it's showing same project closure again and again though I am running job for different projects). Is it some bug in our custom program or any parameters required to be check in job schedule?
    Kindly suggest.
    Thanks & Regards
    Saurabh

    Yes. That is the point I am missing. Just one 'date' is checked and project is taken into account for the custom program and after its successful run the mail is sent to users.
    And when the same program I am assigning in SM36,it is actually running the program accurately for project/s but sending the same mail which it send for very first project earlier.
    Can you please guide me on the way to create these variants? 
    You will need to Save different variants for different projects and then assign the variants with your job.
    Will it be required to create variant again and again and assign different projects individually? As, we are not sure that which project is gonna be created in future. So, need guideline how these variants can help me to sort out the e-mail issue.
    Regards
    Saurabh

  • 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.

  • How to create a job in sm36

    How to create a new job in sm36 and how do we know the job has been created. where to look for that job name.
    please explain.
    thanks,
    phyrose

    Hi,
    Save the variant of report.
    Go to sm36. create a new job.
    In start condition, specify all the day and time.
    and in Step specify the report name and variant.
    and then go to sm37 and run that report..........
    In sm37, got to that job, select that job and click on display spool list to see the output of that job.
    See the status of the JOB whether it is finised or executed with errors etc
    If it is executed and the status shows FINISHED then go to the related transaction and see the output of that Report.
    see the details for JOb secheduling
    Scheduling JOB in background:
    Go to SM36 create a Job
    click on Start Condition
    Click on DATE and TIME enter date scheduled Start and END times
    click on Period Values
    Click on HOURLY/WEEKLY etc
    CLick on RESTRICTIONS also to use further criteria.
    so your job will be scheduled and run as per your requirement.
    and in SM37 Transaction check the status of that JOB
    Check this link for scheduling jobs..
    http://help.sap.com/saphelp_nw2004s/helpdata/en/c4/3a7f87505211d189550000e829fbbd/content.htm
    regards,
    Ruchika
    reward if useful........

  • Back ground job scheduling(urgent)

    Hi all,
      can anybody will help me ,regarding the step by step procedure to schedule the background job.
    i have to do back ground job scheduling for one program so that in that specified time my report will execute?
    plz suggest.
    ur idea will be highly appreaciated.
    Regards
    pabitra

    HI
      Please follow the below steps to schedule a background job.
    First - create a Report-Variant for your print programm using the SE38.
    Then...
    1.) Call the transaction SM36
    Enter a Job Name / You may set a job class other
    than 'C' (See online Help on that field).
    2.) Push the STEP Button
    3.) Push the ABAP Program button
    Enter der programm name an the variant name
    save that window
    4.) Push "BACK"
    5.) Push "Start Condition"
    6.) Push Date/Time
    Enter Date + Time for the first start
    Mark "Periodic Job" !!
    7.) Push "Period Values"
    Set the period you want the job to be started
    Save everything
      For more info please refer to this link:
    <a href="http://help.sap.com/saphelp_nw2004s/helpdata/en/c4/3a7ed1505211d189550000e829fbbd/content.htm">Background Processing</a>
    Kind Regards
    Eswar

  • Job scheduled at month end.

    Hello,
    Does anyone know how to set job schedule at each month end?
    as you all know, for each month, end date is different from month to month.
    but we need to execute a job at month end... is there any good method?
    thanks advance for your kind reply and advice.

    Hi,
    It is possible using SM36 , read the solution provided by Thomas (Schedule on 31st )
    Re: How to run a job on last day of every month
    Regards,

  • Delay between step in job scheduling

    Hi Experts,
          Can anyone give me a idea about steps in job scheduling,and how to set a delay between steps in job scheduling in Tcode SM36 metion if there is any settings available or i have to code it in SE38.
                                                Thanks in advance.

    Check this link:
    http://help.sap.com/saphelp_nw70/helpdata/en/c4/3a7f87505211d189550000e829fbbd/frameset.htm
    Regards,
    Ravi

  • Errors in job scheduled SSIS package

    A job scheduled for SSIS package failed with the below errors:
    Microsoft (R) SQL Server Execute Package Utility  Version 10.50.4321.0 for 64-bit  Copyright (C) Microsoft Corporation 2010. All rights reserved.    
    Started:  5:00:02 AM  
    Error: 2015-01-02 05:06:39.25     
    Code: 0xC0202009     
    Source: Data Flow Task OLE DB Destination [46]     
    Description: SSIS Error Code DTS_E_OLEDBERROR.  An OLE DB error has occurred. 
    Error code: 0x80004005.  An OLE DB record is available.  
    Source: "Microsoft SQL Server Native Client 10.0"  
    Hresult: 0x80004005  
    Description: "Could not allocate a new page for database because of insufficient disk space in filegroup 'PRIMARY'. Create the necessary
    space by dropping objects in the filegroup, adding additional files to the filegroup, or setting autogrowth on for existing files in the filegroup.".  End Error  Error: 2015-01-02 05:06:39.42     
    Code: 0xC0209029     
    Source: Data Flow Task OLE DB Destination [46]     
    Description: SSIS Error Code DTS_E_INDUCEDTRANSFORMFAILUREONERROR.  The "input "OLE DB Destination Input" (59)"
    failed because error code 0xC020907B occurred, and the error row disposition on "input "OLE DB Destination Input" (59)" specifies failure on error. An error occurred on the specified object of the specified component.  There may be
    error messages posted before this with more information about the failure.  
    End Error  Error: 2015-01-02 05:06:39.44     
    Code: 0xC0047022     
    Source: Data Flow Task SSIS.Pipeline     
    Description: SSIS Error Code DTS_E_PROCESSINPUTFAILED.  The ProcessInput method on component "OLE DB Destination" (46) failed
    with error code 0xC0209029 while processing input "OLE DB Destination Input" (59). The identified component returned an error from the ProcessInput method. The error is specific to the component, but the error is fatal and will cause the Data Flow
    task to stop running.  There may be error messages posted before this with more information about the failure.  
    End Error  Error: 2015-01-02 05:06:39.48     
    Code: 0xC02020C4     
    Source: Data Flow Task Flat File Source [1]     
    Description: The attempt to add a row to the Data Flow task buffer failed with error code 0xC0047020.  
    End Error  Error: 2015-01-02 05:06:39.50     
    Code: 0xC0047038     
    Source: Data Flow Task SSIS.Pipeline     
    Description: SSIS Error Code DTS_E_PRIMEOUTPUTFAILED.  The PrimeOutput method on component "Flat File Source" (1) returned
    error code 0xC02020C4.  The component returned a failure code when the pipeline engine called PrimeOutput(). The meaning of the failure code is defined by the component, but the error is fatal and the pipeline stopped executing.  There may be error
    messages posted before this with more information about the failure.  
    End Error  Error: 2015-01-02 05:16:23.49     
    Code: 0x00000000     
    Source: Execute SQL Task 1      
    Description: Could not allocate space for object 'bo.TLE'.'PK_new' in database because the 'PRIMARY' filegroup is full. Create disk space
    by deleting unneeded files, dropping objects in the filegroup, adding additional files to the filegroup, or setting autogrowth on for existing files in the filegroup.  
    End Error  Error: 2015-01-02 05:16:23.70     
    Code: 0xC002F210     
    Source: Execute SQL Task 1 Execute SQL Task     
    Description: Executing the query "Sp_load" failed with the following error: "Warning: Null value is eliminated by an aggregate
    or other SET operation.". Possible failure reasons: Problems with the query, "ResultSet" property not set correctly, parameters not set correctly, or connection not established correctly.  
    End Error  DTExec: The package execution returned DTSER_FAILURE (1).  
    Started:  5:00:02 AM  
    Finished: 5:16:27 AM  
    Elapsed:  984.928 seconds.  The package execution failed.  The step failed.
    Please help!!!!

    Hi,
    Based on the error message” Could not allocate a new page for database because of insufficient disk space in filegroup 'PRIMARY'. Create the necessary space by dropping objects in the filegroup, adding additional files to the filegroup, or setting autogrowth
    on for existing files in the filegroup”, we can know that the issue is caused by the there is no sufficient disk space in filegroup 'PRIMARY' for the database.
    To fix this issue, we can add additional files to the filegroup by add a new file to the PRIMARY filegroup on Files page, or setting Autogrowth on for existing files in the filegroup to increase the necessary space.
    As to the issue that the job executed successfully for the next run when executed, I think it can be caused by someone or something had made something to increase the space. 
    The following document about Add Data or Log Files to a Database is for your reference:
    http://msdn.microsoft.com/en-us/library/ms189253.aspx
    If there are any other questions, please feel free to ask.
    Thanks,
    Katherine Xiong
    Katherine Xiong
    TechNet Community Support

Maybe you are looking for