SAP Note 1538950 - Random scheduling of background jobs in SOLMAN_SETUP (Part I)

Symptom

Serious performance issue in OSS system caused by PPMS job (SM:GET_PPMS_DATA_FROM_OSS) running DSWP_GET_PPMS_DATA_AUS_OSS report


Other terms

DSWP_GET_PPMS_DATA_AUS_OSS, SM:GET_PPMS_DATA_FROM_OSS, random job scheduling, PPMS, dswp_dbppmscvsp table, SOLMAN_SETUP, Schedule Background Jobs


Reason and Prerequisites

SM:GET_PPMS_DATA_FROM_OSS job needs to be scheduled randomly on a 24hours basis. Until now this job was scheduled on each customer system at 23:25 due to a bug in the job scheduling automatic activity in solman_setup (from ST700 Ehp1 SP23 to SP25), which was responsible for a huge number of RFC calls to SAP Global Support Backbone (OSS) system at that point of time.

This was also the case for all the other existing jobs of the same category (communicating with SAP system and not started immediately), the same start time on all customer systems was used.
Solution

Step A:
------
For systems with ST700 Ehp1 from SP23 to SP25, please implement the attached correction instructions via SNOTE. These corrections contain the required random scheduling of jobs and a post-processing operation to remove the wrongly scheduled jobs.

Step B:
------
Then you also have to perform the following manual tasks concerning the log messages which can't be implemented via SNOTE.

1. In transaction SE91, choose the message class SISE_CONF in change       mode.

2. If you receive a message asking if you want to change the original    language of the message class, do not choose "Yes", as this will    bring you to the original language of the object.

3. Add the following new short texts 221, 222, 223 and 224

Remark: If the users in your system use only one language (for example Japanese), it is best to maintain the text in this language. When you import the next Support Package, the texts are overwritten in all implemented languages.

Enter the following texts:
221: &1 job planned the &2 at &3 by &4 was deleted
222: Re-execution of activity &1 is mandatory!
223: &1 job planned the &2 at &3 by &4 could not be deleted!
224: Some background jobs schedules were deleted by post-processing of note &1

Step C:
------
After successful implementation of changes (steps A and B), then (for ST700 SP 23, 24 or 25) you have to execute the post-processing operation available in SOLMAN_SETUP transaction under "Basic Configuration" scenario -> "Import Note" step, by clicking on the "Postprocessing" button (with change mode activated). This post-processing step will unschedule only the wrongly scheduled jobs (the ones scheduled at the specific time by the automatic activity containing the bug) and not the ones that may have been created/modified directly with SM36/SM37 transactions.

For ST700 SP25 this possibly impacts the following jobs (the ones defined in SMCONFIGJOBS table as communicating with SAP (=> COMM2SAP='X' flag) and not scheduled immediately (=> empty ISIMMEDIATE flag)):

JOBNAME:                                               REPORT NAME:
-------                                                         -----------
SM:GET_PPMS_DATA_FROM_OSS             DSWP_GET_PPMS_DATA_AUS_OSS
SM:EXEC SERVICES                               RDSMOPBACK_AUTOSESSIONS_ALL
SEND_SYSTEM_RELATIONSHIP_TO_SUPP  AI_SC_SEND_SYSTEM_RELATIONSHIP
SM:SERVICE CONTENT UPDATE              RAGS_DSWP_SERV_CONTENT_UPDATE
SM:SEND_SOLUTIONS_TO_SAP               RDSMOPCOLLECTSOLUTIONDATA
SM:SYNC SOLMAN INFO                         RDSMOPSERVICEINFOS
SM:SURVEY TRANSFER                          RDSWPCI_SURVEY_TRANSFER
SM:TOP ISSUE TRANSFER                      RDSWPCI_TOPISSUE_TRANSFER
SM:UPDATE RULES                               RDSWPRULESUPDATE

At the end of the post-processing, per each deleted job schedule a corresponding log message is displayed in the UI. In case of deleted schedules you will also receive a red log message to mention that it is MANDATORY to re-execute the "Schedule Background Jobs" activity in the "Automatic Configuration" step of "Basic Configuration" scenario. This automatic activity will be also marked red. Then re-execute this "Schedule Background Jobs" activity and check if the deleted job schedules also appear in the list of jobs scheduled. In case some jobs does not appear, it may indicate that some jobs running the same ABAP report are still scheduled (visible in SM37 transaction with status "Released", see explanation below).


-> To be Contd... Check Next Post