Technology Blogs by Members
Explore a vibrant mix of technical expertise, industry insights, and tech buzz in member blogs covering SAP products, technology, and events. Get in the mix!
cancel
Showing results for 
Search instead for 
Did you mean: 
Nibu
Contributor

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 .

2 Comments
Labels in this area