2014 Jun 23 1:57 PM
Dear gurus,
here is a complete mystery to me:
We have a program that is supposed to change certain PRs. The PRs are selected from EBAN like this:
SELECT * FROM eban
INTO CORRESPONDING FIELDS OF TABLE gt_eban
WHERE banfn IN so_banfn
AND bsart IN so_bsart
AND knttp EQ 'F'
AND loekz NE 'X'
AND ekgrp IN so_ekgrp
AND erdat IN so_erdat
AND matnr IN so_matnr
AND werks IN so_werks.
The program is started hourly as a job. In the variant used, SO_ERDAT is set by Dynamic Date Calculation (Local Date) with “Current date - 1 ,current date - 0”.
In my view and according to my tests, that means, that all PRs created today and yesterday should be selected. And this works fine most of the time, BUT:
At every execution of the job on Mondays between 0:00 and 04:00 AM the job runs amok, selecting even PRs created in 2002, thus increasing its running time from a little over a minute to more than an hour and causing other problems, too.
Does anyone have an idea what could cause this?
Cheers
Alicia
2014 Jun 23 2:14 PM
Hi Alicia Moore,
as long as you provide the ERDAT in your job, it should work as you expected.
only when ERDAT is empty, it would select everything - not checking for ERDAT.
with job scheduling i faced, that mostly it was an old job, with other settings, causing errors like this.
or if ur testing on a system with more than 1 Mandant and using the event-scheduling , u may have started the job defined on the other mandant.
regards
Stefan Seeburger
2014 Jun 23 4:50 PM
Alicia,
Is the job scheduled via se38 or sm36? Check OSS note - 1917960.
Thanks