Step D: (optional in case Step C fails)
------
In case the post-processing of the note did not work as expected (error logs messages), then you still have the possibility to perform the same operation manually using the SM37 transaction (or the RSBTCDEL standard report for mass deletion if you are familiar with) for each job listed above, as described below:
- Run transaction SM37
- Enter * for the Job Name
- Enter * for User Name
- You have to select at least the "Released" job status
- You have to set a quite large interval from today to at least 10 days later (one of the job listed above is scheduled weekly) for the start condition
- Enter the ABAP program name (right column from the list above)
- Press Execute button
- Select the job(s) with status "Released" (you can have several jobs with different job names, if you do not delete all of them you will not get a new schedule)
- In menu "Job", either select "Delete" (unschedule is recommended) or "Change"
- If you prefer to "Change", then choose "Start Condition" button and enter a new start time of your choice
- Then save
WARNING: If you have deleted some jobs, then you have to re-execute the "Schedule Background Jobs" automatic activity. The problem of this manual job by job deletion is that it is not possible to know if the start time of the jobs are correct (means not with a fixed offset time of 25 minutes) without knowing the planned start time defined in table SMCONFIGJOBS. So you have to unschedule or change all the jobs you will find from the list above (unschedule all the jobs is preferable because when the jobs are scheduled again by the automatic activity, the sequence of jobs execution is optimized so that each job may receive the most up-to-date data from predecessor jobs).
Additional information:
----------------------
From ST700 Ehp1 SP26 and ST710 SP01, the new random scheduling of jobs with communication with SAP systems not triggered immediately is included, there's no need to implement any correction. In case of an upgrade from ST700 SP 23, 24 or 25 to ST700 SP >= 26 or ST710 SP >= 01, the possible wrongly scheduled jobs have to be unscheduled manually via SM37 as explained above and the "Schedule Background Jobs" automatic activity has to be re-executed.
Starting from ST700 SP26 or ST710 SP01, the existing job SM:SELFDIAGNOSIS (RDSWP_SELF_DIAGNOSIS report) was moved to this category of jobs randomly scheduled. In case this job was already scheduled using an older ST version, it has to be unscheduled manually with SM37 as explained above then scheduled again using the automatic activity.
Affected
Releases
|
Correction delivered in Support Package
|
Corrections Instructions
|
More Info @ https://service.sap.com/sap/support/notes/1538950
No comments:
Post a Comment