<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Batch Job Scheduling - limiting periodic jobs to business hours in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/batch-job-scheduling-limiting-periodic-jobs-to-business-hours/m-p/2115635#M442760</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Use SM36 for this, Create a JOB and go to "Start Condition" &amp;gt; Click on the DATE/TIME, now click on the button below "Period values", this will give you oprion of jobs to be scheduled, HOURLY / DAILY/ WEEKLY / monthly / other.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Now select HOURLY and SAVE, in Date and Time screen give the relevant criterias.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope this will help&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Vishal&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 10 Apr 2007 05:21:45 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2007-04-10T05:21:45Z</dc:date>
    <item>
      <title>Batch Job Scheduling - limiting periodic jobs to business hours</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/batch-job-scheduling-limiting-periodic-jobs-to-business-hours/m-p/2115633#M442758</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Folks,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We have a periodic batch job that is set up to execute hourly.  Is it possible in SM36/7 to limit the runtime to only execute between business hours (ie run every hour between the hours of 9:00am to 6:00pm)?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If not with SM36/7, is there another transaction that is used to manage this?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Steve&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 10 Apr 2007 01:51:00 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/batch-job-scheduling-limiting-periodic-jobs-to-business-hours/m-p/2115633#M442758</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-04-10T01:51:00Z</dc:date>
    </item>
    <item>
      <title>Re: Batch Job Scheduling - limiting periodic jobs to business hours</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/batch-job-scheduling-limiting-periodic-jobs-to-business-hours/m-p/2115634#M442759</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;based on load , u can distribute ur jobs over application server based on the timiings, So have a word with ur basis person u can help u out.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;Prabhu&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 10 Apr 2007 05:12:11 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/batch-job-scheduling-limiting-periodic-jobs-to-business-hours/m-p/2115634#M442759</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-04-10T05:12:11Z</dc:date>
    </item>
    <item>
      <title>Re: Batch Job Scheduling - limiting periodic jobs to business hours</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/batch-job-scheduling-limiting-periodic-jobs-to-business-hours/m-p/2115635#M442760</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Use SM36 for this, Create a JOB and go to "Start Condition" &amp;gt; Click on the DATE/TIME, now click on the button below "Period values", this will give you oprion of jobs to be scheduled, HOURLY / DAILY/ WEEKLY / monthly / other.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Now select HOURLY and SAVE, in Date and Time screen give the relevant criterias.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope this will help&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Vishal&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 10 Apr 2007 05:21:45 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/batch-job-scheduling-limiting-periodic-jobs-to-business-hours/m-p/2115635#M442760</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-04-10T05:21:45Z</dc:date>
    </item>
    <item>
      <title>Re: Batch Job Scheduling - limiting periodic jobs to business hours</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/batch-job-scheduling-limiting-periodic-jobs-to-business-hours/m-p/2115636#M442761</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;Go to SM36 create a Job&lt;/P&gt;&lt;P&gt;click on Start Condition&lt;/P&gt;&lt;P&gt;Click on DATE and TIME enter date scheduled Start (9.00)and END times(18.00)&lt;/P&gt;&lt;P&gt;click on Period Values&lt;/P&gt;&lt;P&gt;Click on HOURLY&lt;/P&gt;&lt;P&gt;so your job will be scheduled and run as per your requirement.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;reward points if useful&lt;/P&gt;&lt;P&gt;regards,&lt;/P&gt;&lt;P&gt;ANJI&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 10 Apr 2007 05:24:24 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/batch-job-scheduling-limiting-periodic-jobs-to-business-hours/m-p/2115636#M442761</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-04-10T05:24:24Z</dc:date>
    </item>
    <item>
      <title>Re: Batch Job Scheduling - limiting periodic jobs to business hours</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/batch-job-scheduling-limiting-periodic-jobs-to-business-hours/m-p/2115637#M442762</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Stephen,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;  This useful one for you .&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Scheduling Background Jobs:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1.        Background jobs are scheduled by Basis administrators using transaction SM36.&lt;/P&gt;&lt;P&gt;2.        To run a report in a background, a job needs to be created with a step using the report name &lt;/P&gt;&lt;P&gt;and a variant for selection parameters. It is recommended to create a separate variant for each &lt;/P&gt;&lt;P&gt;scheduled job to produce results for specific dates (e.g. previous month) or organizational units (e.g. &lt;/P&gt;&lt;P&gt;company codes).&lt;/P&gt;&lt;P&gt;3.        While defining the step, the spool parameters needs to be specified&lt;/P&gt;&lt;P&gt;(Step-&amp;gt; Print Specifications-&amp;gt;Properties) to secure the output of the report and help authorized users &lt;/P&gt;&lt;P&gt;to find the spool request. The following parameters needs to be maintained:&lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;a.        Time of printing: set to &amp;#147;Send to SAP spooler Only for now&amp;#148;&lt;/P&gt;&lt;P&gt;b.        Name &amp;#150; abbreviated name to identify the job output&lt;/P&gt;&lt;P&gt;c.        Title &amp;#150; free form description for the report output&lt;/P&gt;&lt;P&gt;d.        Authorization &amp;#150; a value defined by Security in user profiles to allow those users to access &lt;/P&gt;&lt;P&gt;this spool request (authorization object  S_SPO_ACT, value SPOAUTH).  Only users with matching &lt;/P&gt;&lt;P&gt;authorization value in their profiles will be able to see the output.&lt;/P&gt;&lt;P&gt;e.        Department &amp;#150; set to appropriate department/functional area name. This field can be used in &lt;/P&gt;&lt;P&gt;a search later.&lt;/P&gt;&lt;P&gt;f.        Retention period &amp;#150; set to &amp;#147;Do not delete&amp;#148; if the report output needs to be retained for more &lt;/P&gt;&lt;P&gt;than 8 days. Once the archiving/document repository solution is in place the spool requests could &lt;/P&gt;&lt;P&gt;be automatically moved to the archive/repository. Storage Mode parameter on the same screen &lt;/P&gt;&lt;P&gt;could be used to immediately send the output to archive instead of creating a spool request.&lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;Configuring user access:&lt;/P&gt;&lt;P&gt;1.        To access a report output created by a background job, a user must have at &lt;/P&gt;&lt;P&gt;least access to SP01 (Spool requests) transaction without restriction on the user &lt;/P&gt;&lt;P&gt;name (however by itself it will not let the user to see all spool requests). To have &lt;/P&gt;&lt;P&gt;that access the user must have S_ADMI_FCD authorization object in the profile with &lt;/P&gt;&lt;P&gt;SPOR (or SP01) value of S_ADMI_FCD parameter (maintained by Security).&lt;/P&gt;&lt;P&gt;2.        To access a particular job&amp;#146;s output in the spool, the user must have &lt;/P&gt;&lt;P&gt;S_SPO_ACT object in the profile with SPOAUTH parameter matching the value used &lt;/P&gt;&lt;P&gt;in the Print Specifications of the job (see p. 3.d above).&lt;/P&gt;&lt;P&gt;3.        Levels of access to the spool (display, print once, reprint, download, etc) are &lt;/P&gt;&lt;P&gt;controlled by SPOACTION parameter of S_SPO_ACT. The user must have at least &lt;/P&gt;&lt;P&gt;BASE access (display).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;On-line reports:&lt;/P&gt;&lt;P&gt;1.        Exactly the same configuration can be maintained for any output produced &lt;/P&gt;&lt;P&gt;from R/3. If a user clicks &amp;#147;Parameters&amp;#148; button on a SAP Printer selection dialog, it &lt;/P&gt;&lt;P&gt;allows to specify all the parameters as described in p. 3 of&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;#147;Scheduling background jobs&amp;#148; section. Thus any output created by an online report &lt;/P&gt;&lt;P&gt;can be saved and accessed by any user authorized to access that spool request &lt;/P&gt;&lt;P&gt;(access restriction provided by the Authorization field of the spool request &lt;/P&gt;&lt;P&gt;attributes, see p. 3.d of &amp;#147;Scheduling background jobs&amp;#148; section).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Access to report&amp;#146;s output:&lt;/P&gt;&lt;P&gt;1.        A user that had proper access (see Configuring user access above) can &lt;/P&gt;&lt;P&gt;retrieve a job/report output through transaction SP01.&lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;2.        The selection screen can be configured by clicking &amp;#147;Further selection &lt;/P&gt;&lt;P&gt;criteria&amp;#133;&amp;#148; button (e.g. to bring &amp;#147;Spool request name (suffix 2)&amp;#148; field or hide other &lt;/P&gt;&lt;P&gt;fields).&lt;/P&gt;&lt;P&gt;3.        The following fields can be used to search for a specific output (Note that &lt;/P&gt;&lt;P&gt;Created By must be blank when searching for scheduled job&amp;#146;s outputs)&lt;/P&gt;&lt;P&gt;a.        Spool request name (suffix 2) &amp;#150; corresponds to a spool name in p. 3.b in &lt;/P&gt;&lt;P&gt;&amp;#147;Scheduling background jobs&amp;#148; section above).&lt;/P&gt;&lt;P&gt;b.        Date created &amp;#150; to find an output of a job that ran within a certain date range.&lt;/P&gt;&lt;P&gt;c.        Title &amp;#150; corresponds to spool Title in p. 3.c in &amp;#147;Scheduling background jobs&amp;#148; &lt;/P&gt;&lt;P&gt;section above).&lt;/P&gt;&lt;P&gt;d.        Department - corresponds to spool Department in p. 3.e in &amp;#147;Scheduling &lt;/P&gt;&lt;P&gt;background jobs&amp;#148; section above).&lt;/P&gt;&lt;P&gt;4.        Upon entering selection criteria, the user clicks the Execute button   to &lt;/P&gt;&lt;P&gt;retrieve the list of matching spool requests.&lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;5.        From the spool list the user can use several function such as view the &lt;/P&gt;&lt;P&gt;content of a spool request, print the spool request, view attributed of the spool &lt;/P&gt;&lt;P&gt;request, etc. (some functions may need special authorization, see p.3 in &lt;/P&gt;&lt;P&gt;Configuring user access)&lt;/P&gt;&lt;P&gt;a.        Click the Print button   to print the spool request with the default attributes &lt;/P&gt;&lt;P&gt;(usually defined with the job definition). It will print it on a printer that was &lt;/P&gt;&lt;P&gt;specified when a job was created.&lt;/P&gt;&lt;P&gt;b.        Click the &amp;#147;Print with changed attributed&amp;#148; button   to print the spool request &lt;/P&gt;&lt;P&gt;with the different attributes (e.g. changing the printer name).&lt;/P&gt;&lt;P&gt;c.        Click the &amp;#147;Display contents&amp;#148; button   to preview the spool request contents. A &lt;/P&gt;&lt;P&gt;Print    and Download   functions are available from the preview mode.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Don't forget to reward if useful&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 10 Apr 2007 05:29:14 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/batch-job-scheduling-limiting-periodic-jobs-to-business-hours/m-p/2115637#M442762</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-04-10T05:29:14Z</dc:date>
    </item>
    <item>
      <title>Re: Batch Job Scheduling - limiting periodic jobs to business hours</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/batch-job-scheduling-limiting-periodic-jobs-to-business-hours/m-p/2115638#M442763</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks for your help all.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 21 May 2007 01:26:45 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/batch-job-scheduling-limiting-periodic-jobs-to-business-hours/m-p/2115638#M442763</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-05-21T01:26:45Z</dc:date>
    </item>
  </channel>
</rss>

