Job Scheduling-restriction based on time

Hi Everybody,
I want to schedule a job so that it should not run between 5pm to 6pm everyday and rest of time it should run.
I am not getting any restriction option to satisfy this condition.
Anybody having any idea ??
Regards.

Hi again,
In that case, we can create a Wrapper Program.
ie.
1. Create a Z program. (It will be a very small program)
2. Inside this Z Program, call/submit the standard program
3. Before submitting, write the logic of 5-6.
Now for background scheduling , use the Z program instead of the std. one.
Hope this helps.
regards,
amit m.
Edited by: Amit Mittal on Jan 7, 2010 6:44 PM

Similar Messages

Requested start time during job scheduling population in local time.

Hello Experts,
Could you please help on the issue.
Requested start time during job scheduling populated with local time even though we have assigned the GMT time zone.
Could you please help , how to change the settings of request start time calender icon to populate the GMT time.
thanks,
Suresh.

Hello Gerben,
Thanks for the reply, even though the default time zone set as GMT in user settings, the requested start time calender pop up the local time instead of GMT time.
Previously requested start time poped up the GMT time, we have observed this change once we have ran the redwood script for time window elements change and imported some of the job definitions, applications & time windows from other system.
Below is the script we have ran thought shell script
Script Fuctionality
1. Take the mentioned time window
2. iteratate thought the time window elements and add 1 hour to the "time to day from" & "time to day to" parameters.
3. set the changed parametes to time window and persist the changes.
// Variable Declarations
String timewindow = null;
String query = null;
TimeWindow tw = null;
TimeWindowElement twe = null;
long otdvalue = 3600000;
long l1 = 0;
long l2 = 0;
long threshold = 0 ;
long expvalue = 82800000;
long expvalue1 = 85500000;
long indto1 = 0;
long indfrom1 = 300999;
long indto2 = 2700000;
long indfrom2 = 3000999;
Job job = null;
//Declare all the time windows in array
String[] timewindows = {"XX_TIMEWINDOW_01_GMT"};
          for( int i = 0 ; i < timewindows.length; i++)
          timewindow = timewindows<i>;
          jcsOut.println("TimeWindow"i":"+timewindows<i>);
          tw = jcsSession.getTimeWindowByName(timewindow);
          for (Iterator it1 = tw.getTimeWindowElements(); it1.hasNext();)
               twe = (TimeWindowElement) it1.next();
               Long otd = new Long(otdvalue);
               jcsOut.println("************************");
               jcsOut.println(twe.getTimeOfDayFrom());
               jcsOut.println(twe.getTimeOfDayTo());
               jcsOut.println("************************");
               Long todf = (Long) twe.getTimeOfDayFrom();
               Long todt = (Long) twe.getTimeOfDayTo();
                                  threshold = todf.longValue();
                        // if timeday from equal to 23 GMT assign the 0 GMT
                                  if(threshold == expvalue )
                jcsOut.println("timewindow with 23 GMT");
               l1 = indto1;
               l2 = indfrom1;
                        //if timedayfrom equal to 23:45 GMT assign 0:45 GMT
               else if(threshold == expvalue1)
               jcsOut.println("timewindow with 23:45 GMT");
               l1 = indto2;
               l2 = indfrom2;
                        // Add 1 hour for current time of day from
               else
               l1 = todf.longValue() + otdvalue;
               l2 = todt.longValue() + otdvalue;
               Long ll1 = new Long(l1);
               Long ll2 = new Long(l2);
               twe.setTimeOfDayFrom(ll1);
               twe.setTimeOfDayTo(ll2);
               jcsOut.println("After Change:"+ twe.getTimeOfDayFrom());
               jcsSession.persist();
Once after the script competetion the time window time zone remains in GMT.
Could you please check script once and help us the time zone change caused the by script or not?
Thanks,
Suresh

Job Scheduling --- Both Event and Time driven

Hi,
We have a Job X scheduled to run on 23:30 hrs everyday. The run of the Job varies from 15 min to 45 min. Now as per Business need we are to schedule a Job Y that runs immediately after finish of Job X. We have another criteria, which is the Job Y should run the following day and not the present day.
So, if Job X finishes on current day then Job Y too runs on the same date.
Is there a way in which, we could combine both the Time driven and Even Driven option together and schedule the Job Y.
Job Y checks that Job X got finished and if date is current date it waits and runs the following day at 00:00 hrs.
Job Y checks that Job X got finished and if date is following day it runs immediately.
Please suggest.
Regards,
Subhram

[How to run chained jobs|http://wiki.sdn.sap.com/wiki/display/Basis/Howtorunconsequentorchainedbackground+jobs]
Hope it helps
Regards,
Nick Loy

Running Job Scheduler in Restricted Session

I want the database to be in Restricted Session while my ETL load is running via the Job Scheduler so that users will not be able to access tables during the load. When I put it in restricted session however all scheduled jobs cease to run. What user needs Restricted Session privilege? Is it DBSNMP? Is this an acceptable practice?
Thanks,
Susan

Hi Susan,
Sorry for the delay in replying, I was testing this out and talking with another developer. It turns out that you are right.
The Scheduler will not begin running any new jobs or new job chain steps while the database is in restricted mode.
This is intended behaviour and there is no workaround for this. The job coordinator will simply not start any new jobs if it sees that the database is in restricted mode.
This design choice was made a long time ago and isn't currently planned to be changed (although there have been some questions about it so it may in future).
Unfortunately you will need to find another way around this.
-Ravi

Batch job scheduling based on Event AND for the job to complete

I am trying to schedule a background job based on an event AND based on the job finishing itself.
Example:
Job name: Send_Message
After Event: SAP_NEW_PROCESS Message
Program: Program xxxx
I want that the Send_Message job only runs when the Event SAP_NEW_PROCESS message happens AND the Send_Message job is not running.
Right now, I could only schedule it based on the event SAP_NEW_PROCESS Message which means that everytime this event happens the job runs and I end up having the job "Send_Message" in multilple intances where the others will immediately cancel since the first job is still running and so I end up with a lot of Cancelled job when it is not necessary to run them all when there is already 1 instance of the Job running.
How do I set it up in SAP?

Thanks but I am new to SAP having to set up a batch job.
The Event "SAP_NEW_PROCESS_MESSAGES" is a standard SAP Event. We used that such that when a new transaction comes in, the batch job will run but we don't want to run the batch job if the same batch job is already running.
YOu mentioned that I should set up Job_0. Do I need to create an ABAP prorgram to check if JOB_1 is running? How do I set up Job_0? What is the trigger for my Job_0 to run?
You also said that I set up Job_1 and trigger that based on the outcome of Job_0 AND at the same time be triggered by the event "SAP_NEW_PROCESS_MESSAGES". How do I set up this Job_1 so that it can be triggered by both Job_0 and a new transaction coming in(SAP_NEW_PROCESS_MESSAGES).
if you can provide me the step by step guide as I am new to this and I only know basic.
The current set up I have is
Job_1
Job Start:
      After Event
            Event: SAP_NEW_PROCESS_MESSAGES
      Step 1: program to run RCOCB002
I was thinking following your suggestion is this:
Job_0
Job Start
      After Event
            Event: SAP_NEW_PROCESS_MESSAGES
      Step 1: program to run - What will be my program to run?
Job_1
Job_Start
      After Event
            Event: What will be my trigger for Job_1 and how do I set it up?
      Step 1: program to run RCOCB002
Edited by: Shirley Te on Mar 10, 2010 3:25 PM

Variant based job schedule

Hello,
I want to schedule a background job using Function module.
I have searched on SDN forums for the same, n got some function modules but they are not variant based.
I am providing job name, report name, date , time & variant name to the code.
I want a function module for the same.
Please if anyone can help me out with this?
Regards,
Krutika

Hello Krutika,
You need to use JOB_OPEN, JOB_SUBMIT & JOB_CLOSE.
Also, you can use RS_CREATE_VARIANT for creating dynamic variants.
In JOB_CLOSE you can use following parameters:
CALL FUNCTION 'JOB_CLOSE'
EXPORTING
*   AT_OPMODE                         = ' '
*   AT_OPMODE_PERIODIC                = ' '
*   CALENDAR_ID                       = ' '
*   EVENT_ID                          = ' '
*   EVENT_PARAM                       = ' '
*   EVENT_PERIODIC                    = ' '
    jobcount                          =
    jobname                           =
*   LASTSTRTDT                        = NO_DATE
*   LASTSTRTTM                        = NO_TIME
*   PRDDAYS                           = 0
*   PRDHOURS                          = 0
*   PRDMINS                           = 0
*   PRDMONTHS                         = 0
*   PRDWEEKS                          = 0
*   PREDJOB_CHECKSTAT                 = ' '
*   PRED_JOBCOUNT                     = ' '
*   PRED_JOBNAME                      = ' '
*   SDLSTRTDT                         = NO_DATE
*   SDLSTRTTM                         = NO_TIME
*   STARTDATE_RESTRICTION             = BTC_PROCESS_ALWAYS
*   STRTIMMED                         = ' '
*   TARGETSYSTEM                      = ' '
*   START_ON_WORKDAY_NOT_BEFORE       = SY-DATUM
*   START_ON_WORKDAY_NR               = 0
*   WORKDAY_COUNT_DIRECTION           = 0
*   RECIPIENT_OBJ                     =
*   TARGETSERVER                      = ' '
*   DONT_RELEASE                      = ' '
*   TARGETGROUP                       = ' '
*   DIRECT_START                      =
Hope this resolves your issue!
Thanks,
Augustin.

TIME FRAME IN JOB SCHEDULING

Hi all,
I am doing job scheduling in background.
But i am not able to do it twice a day, it means every 12 hours it should be done automatically.
Can anyone suggest me how to do with code.
Thanks in advance
Venkat

Hi venkat,
1. In that case ,
2. U can schedule TWO different jobs,
(with the same program name and variant)
3. DAILY
AT TWO DIFFERENT TIMES.
regards,
amit m.

Scheduler Jobs that run between certain times?

Is there an easy way to query which dbms_scheduler jobs run between any given times?
If I look at repeat_interval in user_scheduler_jobs, for example, I've got things like "FREQ=DAILY; BYHOUR=14,16,18,20,8,10,12; BYMINUTE=30" and "FREQ=HOURLY; INTERVAL=2;" and "FREQ=DAILY;", and it's not therefore clear to me how I could write a query that would find which jobs run between (say) 17:00 and 19:00.
Is there a function, or a neat bit of sql, that will 'explode' the repeat interval (presumably, in the case of the last two examples above, with reference to the start_date) into standardized times which I could then query? Or is there some other way of doing it?

There are no schedules used here. The repeat interval is specified for all jobs at the time of creating the job.
Besides, that wouldn't address the issue, even so. Even if schedules are in use, they declare their repeat interval in the form "freq=daily;byhour=3,4,5,6;byminute=0;bysecond=0", stored in a text field. Exactly the same, in fact, as the repeat_interval column in the user_scheduler_jobs column.
So how do you derive from that the knowledge that the job can run some time between 2 and 8AM?
I want to list all jobs which might start between those two times, but I do not know syntactically or logically how it is possible to query either user_scheduler_jobs or all_scheduler_schedules to select all rows where repeat_interval "is somehow covered by the time range 2 to 8".
Thanks for replying, though.

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 youve completed specifying the job start conditions, choose the Save button at the bottom of the Start Time screen to return to the Define Background Job screen.
No job can be started until it is released, including jobs scheduled to start immediately. Since releasing jobs can be done only by a system administrator from the job management screen (Transaction SM37) or by other users who have been granted the appropriate Authorizations for Background Processing, no unauthorized user can start a job without explicit permission.
i got this from link,
http://help.sap.com/saphelp_nw04/helpdata/en/c8/6a56389f64246fe10000009b38f889/frameset.htm
Regards,
Arunsri

SQL Server Agent Job Scheduler- Set time less than 10 seconds

Hi,
Could any one please let me know how to change the SQL server agent Job scheduler time to less than 10 secs?
I wan to schedule a SSIS package run for every 5 secs.
Thanks..

Be careful, it is a bad idea to blindly just issue a new package run without knowing whether the previous package ended.
It may lead to locking/dead-locking.
Now re the Agent: the seconds are not exposed at all, why you say 10?
But, there is a way, not through the UI, explained there:http://stackoverflow.com/questions/5569415/is-there-a-way-to-set-a-sql-server-job-scheduled-to-run-every-30-seconds + http://www.sqlservercentral.com/articles/Administration/sqlserverjobscheduling/2288/
PS you can have it every sec
Arthur My Blog

Job Scheduler Timer issue in Cisco Prime Infrastructure 1.2 ?

Has anyone run into this issue where the job scheduler in CPI 1.2 report that the job that is being scheduled is before the current time even though it isn't ?
This only started happening after our time change yesterday. The system is setup for the correct time (NTP) this is confirmed in the app and also on the CLI console access (show clock)
Anyway we get this error message (attachment) in the lower right corner of the attachement.
It's not allowing the jobs to be scheduled. Rebooted the system yesterday and thought that it fixed it, but evidently I tried another scheduled job today and it's got the same issue.
TAC Case is already opened on this but I thought I'd ask here as well.
Regards,
Tom W.

I'm answering my own question: upgrade to 1.3 from 1.2 and the problem is resolved. Rebooting the VM on 1.2 did help for 1 day but then the problem came back, so my advice is simply to upgrade to 1.3 which I would have done initially if I had known that 1.3 was available. Hope this helps. The problem itself in 1.2 is unclear what is causing it because NTP and the APP and the underlying time in the console (cli) are all good; so somewhere in the scheduler it may have gone off track after the daylight savings time shift this past week. Bottom line: 1.3 upgrade and keep hope alive, bro.

Job Chain. How to create Rule based on Time also?

Hi ,
I need to check at 9:30 AM that one of the previous step in the existing chain has been completed.
If not I'd like to do some 'send_notification' Step.
So, I need to create rule based on Time and 'step_n succeeded'.
Could you please tell me how to do that?
Thanks for your help,
LSY.

Hi,
Alberto is right in his approach. You can't say to evaluate the chains rules at 9:30am but you can set an evaluation context of 10 minutes so that the chains rules are reevaluated every 10 minutes.
Then you can create a rule that says
if the time is between 9:30am and 9:40am and step_to_check is running or not_started
then start send_notification_step
Hope this helps,
Ravi.

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.

Automatic lot creation based on time Frequency

Hi,
For 01 inspection incoming inspection ,
F or certified vendors, without inspection , material is getting posted to UUS without lot creation. ( QI info record settings).
but for this case , business requirement is to get automatic lot creation based on time like 6 months once .
Automatic lot to be created for this certified vendor on time frequency basis. how to trigger this Lot creation based on time.
Help.
VV.

Hi,
In std SAP we dont have option of generating Automatic lot creation based on periodic basis. But we can provide some workaround soultion.
Option 1:
USe Source Insepction concept. Here Inspection lot will be created for every P.O. Here u can relase P.O line items in QI07 which can sceduled in Job planning on periodic basis. Use Skip inspection lot concept to skip unwanted lots. This has direct relation with Q-Info record.
Option 2:
U can generate automatic lot creation based on Stability study concept. Here are the following steps
Initiate Stablility study
Create Initial sample
Perform intial test
Confirm initail sample
stability planning
Define storage condition
create testing schedule
store stability sample
define cycle start
schedule
complete stability study.
Option 3:
To get Automatic lot creation u can use BAPI QPL1_INSPECTION_LOT_CREATE . When a due date come for inspection,it created a lot of 01 / Z-01 inspection type automatically through QA01( call the program ,enter the inspection lot origin & material,vendor & save). Create Z-T code which has vendor material plant combination.
Execute the above T-code based on Periodic basis.
Explore above 3 options and choose best one according to ur requirements.
Edited by: Lokesh K on Oct 12, 2010 11:27 AM

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

Job Scheduling-restriction based on time

Similar Messages

Maybe you are looking for