Skip to Content
Author's profile photo Nibu Antony

NO START AFTER won’t work for periodic Jobs

Hi All ,

Its quite surprising for me , so am sharing this,  you can take care of this in future .  This issue with the background job scheduling of ABAP systems .

The Phrase NO START AFTER won’t work for periodic jobs 

I will explain with a simple eg:

I am Scheduling a backgound Job in my  SAP Dev System

So , I have given as follows: Schedule Start 13:30:00 and No Start After 14:00:00

I made it as a periodic job as below

The program running is RSCOLL00 , just for testing

So the Job is schedules and released . As per the above logic , the job should run from 13:30:00 to 14:00:00 (Half an Hr) , so 6 times it should run . surprisingly , it is still getting released after 14:00:00, even we give ” NO START AFTER 14:00:00

At 14:00:00 ,the NO START AFTER time is getting increased automatically  as below.

So take care on “NO START AFTER” in Background job scheduling for periodic jobs . I don’t understand why there is no  condition checking implemented to check the end date of the job even if it is a periodic one .

Assigned Tags

      You must be Logged on to comment or reply to a post.
      Author's profile photo Former Member
      Former Member

      Yes you are right. I too did the same with a sample job, same result . Hope SAP will implement a resolution like a condition check...Thanks for the information.

      Author's profile photo Prithviraj Rajpurohit
      Prithviraj Rajpurohit

      No start after is only to determine and restrict a job to run within mentioned time frame. i.e if there is delay more than what is mentioned in the field the job will not run. This does not mean an end date or time for a job.

      Please read sap note 434011 - "no start after" restriction does not work

      Reason:You schedule a job with the period 'Hourly'.
      First start time: 15:00 No start after 15:30.

      The following then applies for the successor:
      Start time: 16:00 No start after 16:30.