Solution : https://service.sap.com/sap/support/notes/1538950 (SAP Service marketplace login required)
Summary :
Significant performance degradation in an OSS system has been linked to the SM:GET_PPMS_DATA_FROM_OSS job, executing the DSWP_GET_PPDMS_DATA_AUS_OSS report, due to simultaneous scheduling on multiple customer systems. Scheduled at 23:25 historically, this led to excessive RFC calls to SAP's Global Support Backbone, precipitating bottlenecks. Suggested corrections include randomizing job schedules from ST700 Ehp1 SP23 to SP25 via SNOTE, with necessary manual interventions for logs in SE91. Additional steps involve post-processing to unschedule incorrect setups and confirmation in SOLMAN_SETUP. Future versions (ST700 SP26 and above) incorporate these schedule changes directly.
Key words :
exec services rdsmopback_autosessions_allsend_system_relationship_to_supp ai_sc_send_system_relationshipsm, sync solman info rdsmopserviceinfossm, - press execute button- select, service content update rags_dswp_serv_content_updatesm, top issue transfer rdswpci_topissue_transfersm, sap global support backbone, schedule background jobs reason, - run transaction sm37- enter, planned start time defined, job scheduling automatic activity
Related Notes :
| 1604572 | OSS performance problems due to solman_setup background jobs |
| 1468591 | SAP Solution Manager: Basic functions: SP25 - SP27 |
| 1405878 | SAP Solution Manager: Basic functions: SP22 to SP26 |
| 894279 | Background processing in SAP Solution Manager |