SM37 Job schedule in BW

Hi,
    I had a 2 SM37 Jobs in BW.
    for the next 3 Weeks my requirment is to schedule One Job to run from MON-WEd and Another jon to run THu-SAT
How can i schedule/release a job in SM37 and meet my requirment

hi friends..
your solution might be correct, but we need to create 3 jobs with different timings (MON, TUE, WED) and same for the second also then the number of jobs created are 6, here time is wasted i think so.
so i have one small idea, i hope it works.
make a FACTORY CALENDAR such with MON, TUE, WED as working days and while scheduling the job use that factory calendar. and create one more FACTORY CALENDAR with THU, SAT as working days and us it for scheduling the second job.
hope it works.
Edited by: ahamad4sap on Aug 23, 2010 11:30 PM

Similar Messages

  • 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

  • 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

  • Job Scheduling in Solution Manager - Error creating Periodic Job

    Hi all,
    I am in the process of testing the Job Scheduling functionality using the Solution Manager.  I have setup the criteria manager, ec. in the satellite system, and done the config in Solman as well. 
    I am able to successfully setup up a 'on-time' job.
    it's only when I try to setup a periodic job, I end up getting following error
    Any thoughts?  Is there any piece of config that's missing?  All the SICF services needed for this functionality are running fine.
    Thanks for the help.
    500 Internal Server Error
    Error when processing your request
    What has happened?
    The URL https://fsspsm.target.com:/sap/bc/webdynpro/sap/wd_ags_ejr_job_req_gaf_app was not called due to an error.
    Note
    The following error text was processed in the system PSM : Message was not created
    The error occurred on the application server fsspsmap01_PSM_00 and in the work process 1 .
    The termination type was: ERROR_MESSAGE_STATE
    The ABAP call stack was:
    Function: BAPI_NOTIFICATION_CREATE of program SAPLDSWP_NOTIF
    Method: MSG_SUBMIT of program CL_DSMOP_BSP_NOTI_MODEL=======CP
    Method: SUBMIT_REQ_CRM_DATA of program CL_AGS_EJR_JOB_REQUEST_FACTORYCP
    Method: SUBMIT of program CL_AGS_EJR_JOB_REQUEST_FACTORYCP
    Method: PROCESS_SCENARIO_PERIODIC of program CL_AGS_EJR_JSM_PROC_STANDARD==CP
    Method: PROCESS_JOB_SCENARIO of program CL_AGS_EJR_JSM_PROC_STANDARD==CP
    Method: IF_AGS_EJR_JSM_PROC_FPM_CTRL~AFTER_PROCESS_EVENT of program CL_AGS_EJR_JSM_PROC_STANDARD==CP
    Method: AFTER_PROCESS_EVENT of program /1BCWDY/K54G9RCMK7J4Z427H49S==CP
    Method: IWCI_IF_FPM_APP_CONTROLLER~AFTER_PROCESS_EVENT of program /1BCWDY/K54G9RCMK7J4Z427H49S==CP
    Method: CALL_UIBB_PROCESS_EVENT of program CL_FPM========================CP

    Hello,
    This is the basic Job Scheduling functionality and not the Redwood Job scheduling, correct?
    Have you performed the IMG Activiteis in SPRO?
    See the following Help link:
    http://help.sap.com/saphelp_sm70ehp1_sp23/helpdata/en/c5/7edcbd58ce4e29bc1baf1c4761d71f/frameset.htm
    Change a job
    You can change the scheduling of a job as long as it has not been completed. Proceed as follows:
    Make changes.
    Note
    When you change a periodic job, the system searches for the changeable successor and only changes this successor.
    If there is more than one changeable job with the same name, the system does not change any of these jobs.
    End of the note.
    Save your entries.
    To release the job in the target system, select Release.
    You go to the transaction SM37 in the target system.
    You just may want to ensure HTTP Services have been enabled. I realize you said the services workin SICF, but this needs to be verified as 500 Internal Server Error most often means the HTTP services are not activated.
    Regards,
    Paul

  • 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 Scheduling for MC.9

    Dear All,
    Transaction : MC.9
    Program Name: RMCB0300
    This transaction is running fine on foreground run but i am not able to schedule a background run for it. It's giving an Error message "No List available" when i try to check the output in SM37 Job Selection transaction. Please help me in this regard.
    Regards,
    Sushant L

    Dear All,
    Transaction : MC.9
    Program Name: RMCB0300
    This transaction is running fine on foreground run but i am not able to schedule a background run for it. It's giving an Error message "No List available" when i try to check the output in SM37 Job Selection transaction. Please help me in this regard.
    Regards,
    Sushant L

  • NWA Job scheduler, how to change parameters?

    Dear guys,
    moving to AEX (java-only) the ABAP Stack is gone.
    Regarding job scheduling there is no more transaction sm37, but Job scheduler within NWA to be used for scheduling jobs.
    I configured a job for the predefined job definition AlertConsumerJob to get emails in case of alerts.
    Doing this the questions arises how to change parameters once a job is scheduled e.g. add additional email receiver.
    So far is seems you have to stop the configured job and define a NEW one from scratch by providing all job parameters. It seems not possible to adjust a job.
    This is not very comfortable?
    Is there an workaround / solution for this?
    Best regards
    Jochen

    Hello Gaurav
    thanks for your reply.
    It's a pity, but shows that there is still some room of improvement regarding AEX functionality (java only)
    Best regards
    Jochen

  • How to lock targetserver execution in job scheduling

    Hi,
    I've a SAP System with a central instance and two application servers.
    I would set authorizations so that users when they schedule their jobs (example in SM37), the field target server is locked and set to a particular application server.
    Any idea ?
    Thanks
      Maurizio Manera

    Hi,
    Giving an overview of the tables involved in batch processing. The jobs details are stored in the system on the following tables.
    TBTCO      - the overall state and information of a background job
    TBTCS      - the view of the jobs that the time based job scheduler has
    TBTCP      - the steps a background job consists of.
    BTCEVTJOB  - the view of the jobs that the event based scheduler has
    BTCCTL     - Controls what BTC schedules runs in system
    Fields include:
    ===============
    JOBNAME, JOBCOUNT: unique identifiers(i.e. key fields)
    SDLDATE, SDLTIME: scheduled date & time of when job is created
    SDLSTRTDT, SDLSTRTIM: scheduled start date & time
    These are the two fields EXECSERVER & REAXSERVER you should be concerned
    EXECSERVER: executing server; filled if you specify a target server
    REAXSERVER: filled at run-time; gets same server as EXECSERVER if target.
    Regards,
    Snow

  • Background Jobs scheduled through ABAP Editor

    Dear SRMer's
    System Info : SRM 5.0
    Can you please let me know what is the tcode to check Background jobs scheduled through the ABAP Editor(SE 38) or through SA38 tocdes in SRM.
    Points will be rewarded for answers.
    Thanks in advance,
    Bobby

    Hi Bobby,
    Try this steps...
    1.  Log on to the appropriate SAP instance and client as either the user ID owning the job or an administrator ID.
    2.  Go to transaction SM37.
    3.  On the Simple Job Selection screen, fill in the Job name field or use any of the screens filtering options to produce a list from which you can see the job you want to view.  In order for all occurances of a job to be viewed, all statuses of the job should be checked “on”.  Click on the Execute button.
    Regards
    Rajesh.

  • Changing job schedule time

    Hi,
    I have scheduled a job to execute at a specific time daily.
    But now I want to change the execution time, job will execute daily.
    How to do that ?
    Regards,
    Amit R.

    hi,
    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.
    i got this from link,
    http://help.sap.com/saphelp_nw04/helpdata/en/c8/6a56389f64246fe10000009b38f889/frameset.htm
    Regards,
    Arunsri

  • How to edit job scheduled in SM36

    Dear All,
    I have defined some background job (run weekly) by SM36, everything run fine except later I found that I forgot to change the output device to follow user's output device.
    I can't find edit button in SM36 when I go back to my scheduled job, is that possible to edit the background job ? How to do that ?
    Thank You.

    Once your Job is finished than it wound not be possible.
    But yes once your job is scheduled and for change your print parameters than follow this steps:
    SM37>Job name>execute>select the job>From menu path JOB>change(Ctrl+F11)>Steps>From menu STEP>Change>pop up will prompt press Print specifications(F5)>Change printer from here.
    PS:Again this would only possible once your job is only scheduled but not finished.

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

  • SM37 Job  in BW

    Hi
       How to cancel or put on hold a Released/Scheduled SM37 Job in BW
    Thanks

    Hi,
    Please go to SM37 and select the job and click on Job Details and copy the PID and note down the application Server where it is running and go back to the Job Overview screen and Click on Application Server at the right top corner and double click on the Corresponding server and it will take you to the SM50 Screen where you can give a search for the PID(Delete the Dot and Search). once you found the PID click on Process Menu and Select the option Cancel Without Core.
    Regards,
    Syed

  • Sm37 jobs

    Hi all,
    We can monitor r cancel a background job through SM37.
    then how to identify the jobs scheduled in foreground
    any ideas please.
    thanks and regards
    Harish

    hi dinesh,
    thanks for the info, so how to recognize the job and which process is runing that job. Because we have different names for example if i am filling setup tables how to recognize the process which is doing this.
    thanks and regards
    Harish

  • SM37 Job Delay Seconds

    Hi, When my scheduled LIS Jobs run on R3 I am noticing that they all show some kind of Delay in SM37 before they run.  The Jobs run every 4 hours and during most of the runs there isn't any real amount of system activity going on so I'm guessing this shouldn't be happening.
    Can anyone tell me what would cause this delay and what/should I do anything about it?
    Thanks!

    Ken,
    How much is the delay? Is it < 60 seconds or more than that? The job scheduler wakes intermittently to run the background jobs (parameter rdisp/btctime in the instance profile). If it is more than that, then it usually there are no available jobs on the designated server or in the system.
    -regards

Maybe you are looking for