SAP Note 894279 - Background processing in SAP Solution Manager (Part III)

(Part II Continuation)


New job framework 'Solution Manager Job Configuration' of the SAP Solution Manager

• /SDF/MON_REORG report (Job SNAPSHOT MONITORING REORG): Reorganization of obsolete /SDF/MON analyses, scheduled daily since ST710 SP1 version.

• /TMWFLOW/CMSSYSCOL2 report (Job SM:TMWFLOW_CMSSYSCOL): Program for collecting data of transports, notes and support packages of each System defined in table /TMWFLOW/CMSCONF using asynchronous RFC-function calls, scheduled daily, since ST400.

• /TMWFLOW/RMO_STACKUPDATE report (Job SM:STACK_INFO_UPDATE): Update the stacks that are available for a product version (see SAP note 1581095), scheduled daily since ST400.

• AGSSISE_DELETE_TMP_RFC report (Job SM:REMOVE TEMPORARY RFC): Delete temporary RFCs created during solman setup in case this was not done there due to some error, scheduled hourly, since ST710 SP1.

• AGSSISE_SYSSOL_COLLECTOR report (Job SM:SISE_SYSSOL_COLLECTOR): The purpose of this report is to add all production systems to one standard solution, so that Early Watch can be scheduled automatically. A standard solution is created during the initial configuration of the Solution Manager (transaction SOLMAN_SETUP). This standard solution is used in this report. When the solution is created, the system proposes the name #SAP Solution#, which can be changed. If there is no standard solution, this report creates a standard solution #SAP Solution#. The report then selects all production systems belonging to the customer number using the installation number. All logical components containing one of the systems in the system role that correspond to the leading roles in the solution are then assigned to the solution. So that the Solution Manager is also included in this standard solution, the logical component #Z_SOLMAN_COMP# is created and assigned to the standard solution during the initial configuration. If this does not exist, it is created by the report. In addition, a special solution can be created for each customer number. This special solution is then used instead of the standard solution. You can maintain these customer-specific solutions in the view V_AISAPCUSTNOS (transaction SM30). The report automatically fills the customer number field in the settings of the corresponding solution for all solutions assigned to a customer number using V_AISAPCUSTNOS. Scheduled weekly since ST400.

• AI_CRM_AIDIAGNOTIF_CREATE report (Job AI_CRM_AIDIAGNOTIF_CREATE): This report takes care of notifications coming from LMDB or CMDB, stating that a system or a device has been changed or created. It creates or updates an IObject for the system or device related to the notification. This IObject is then used for referencing in an Incident Message or other CRM documents. Scheduled daily during night, since ST710 SP5.

• AI_CRM_IM_UPDATE_FROM_SAP report (Job REFRESH MESSAGE STATUS): This report is used for incident management in solution manager, to retrieve or replicate SAP messages. It replaces for ST 7.10 the old report RNOTIFUPDATE01 (see note 1566108). Scheduled hourly, since ST710 SP1.

• AI_SC_LISTENER report (Job SERVICE_CONNECTION_LISTENER): This report periodically checks whether a service connection is planned to be opened. It replaces the previously necessary reservation. If a future connection event is selected in the transaction SOLMAN_CONNECT, it is saved locally in the Solution Manager. This program is scheduled every 10 minutes, and opens the system if required. Since ST400.

• AI_SC_REFRESH_READ_ONLY_DATA report (Job REFRESH_ADMIN_DATA_FROM_SUPPORT): This report reads various information from the SAP Support Portal (like maintenance key data, system numbers of all known product systems in SMSY, installation numbers of these systems, contact persons, service types for remote connection, SAProuter) and saves it locally in the Solution Manager. If customer numbers are maintained in the maintenance view V_AISCUSTNOS, the report can create business partners per customer number, get installation numbers for customer numbers, put the product systems of these installations in SMSY. It is scheduled every day since ST400.

• AI_SC_SEND_SYSTEM_RELATIONSHIP report (Job SEND_SYSTEM_RELATIONSHIP_TO_SUPP): This report sends information to the SAP Service and Support Backend systems, which is required by the service connection types "SAP Solution Manager" and "SolMan Diagnostics". The numbers of all product systems known to transaction SMSY are sent. Systems which are known to the Solution Manager diagnostics are flagged, and the system numbers of Solution Manager and Solution Manager Diagnostic systems are sent to SAP. See SAP note 962516 for further information. It is scheduled every day since ST400.

• AI_SDK_FILL_FILE_TYPE_TABLE report (Job SM: GET FILE TYPES FROM SAP): For security reasons, only special file types are allowed as attachments in messages sent to SAP - all other attachments will be rejected. The program determines all relevant file types from CSS. Scheduled every 3 months since ST400.

• DSVAS_APPL_CSA_REORG_TASKTABLE report (Job SM:CSA SESSION REFRESH): This report clears the CSA task status icons in the graphical overview of central systems administration. It is scheduled every day since ST400.

• DSVAS_APPL_CSA_UPD_TASKSTATUS report (Job SM:CSA UPDATE TASKSTATUS) updates status symbols of CSA tasks in the graphical overview of central systems administration. It is scheduled every 30 minutes, since ST400.

• DSWP_BPM_REORGANIZATION report (Job SM:REORG BPMON ALERTS): This report performs the reorganization of Business Process Monitoring alert data for all solution which contain monitoring data. Scheduled daily during night, since ST710 SP5.

• DSWP_CI_ISSUE_BUFFER_TABLE report (Job SM:UPDATE ISSUE BUFFER). This report updates the buffer for the issue management (issues and their joins are stored in temporary tables for performance optimization). It is scheduled every day, since ST400.

• DSWP_GET_CSN_COMPONENTS report (Job SM:GET CSN COMPONENTS): this report gets the application components from CSN and saves them into tables. It is scheduled every week, since ST400.

• DSWP_GET_PPMS_DATA_AUS_OSS report (Job SM:GET_PPMS_DATA_AUS_OSS): This report retrieves PPMS data from the SAP Support Portal and saves it in the Solution Manager. This information is required for the Service Sessions. Scheduled daily (random execution time per customer system), since ST400 SP22.

• E2E_DCC_AGT_MON report (Job E2E DCC AGENT MONITORING): This report collects the diagnostic agents statuses (metric "Diagnostic Agent unavailable") into the Monitoring and Alerting Infrastructure. It is scheduled every 10 minutes, since ST710 SP1.

• E2E_EFWK_HOUSEKEEPER report (Job E2E EFWK HOUSEKEEPING): Housekeeping job for the extractor framework. Scheduled daily. Since ST710 SP1.

• E2E_EFWK_RESOURCE_MGR report (Job EFWK RESOURCE MANAGER): This job is checking if data extractors defined within the EFWK in table E2E_ACTIVE_WLI are due to execution regarding their actual status described in table E2E_EFWK_STATUS. If data extractors are due, then they are executed in the managed systems via RFC call due to the settings in table E2E_RESOURCES. If no data extractors are due, the report is finished immediately, generating no further workload. Scheduled every minute. Since ST710 SP1.

• E2E_HK_CONTROLLER report (Job E2E BI HOUSEKEEPING): This report performs housekeeping activities on the E2E Diagnostics BI Infocubes statistical records (see SAP note 1480588). Scheduled daily. Since ST710 SP1.

• GN_GENERATE_CHECK report (Job GN_GENERATE_CHECK). This report creates a worklist with objects (some industry specific function modules) which need generation. To be run before GN_WORKLIST_GENERATE, Scheduled every day, since ST400.

• GN_WORKLIST_GENERATE report (Job GN_WORKLIST_GENERATE): This report generates the objects (some industry specific function modules) in the worklist created before by GN_GENERATE_CHECK report. Scheduled every day, since ST400.

• HRBCI_ATTRIBUTES_BUFFER_UPDATE report (Job HRBCI_ATTRIBUTES_BUFFER_UPDATE): This report updates CRM organizational data (model and attributes) into the buffer for a specific day. The program also offers you the option of preparing mobile client distribution for the scenarios SALE and SERVICE. Scheduled daily. Since ST400.

• PR_DIAGLS_CLEANUP report (Job DIAGLS_CLEANUP): This report purges the E2E Diagnostics logs. Scheduled daily, since ST710 SP1.

• PR_DIAGLS_COMPUTE_STATUS report (Job DIAGLS_COMPUTE_STATUS): This report updates the status of the elements of the landscape API. Scheduled daily, since ST710 SP1.

• PRGM_DSWP_NA_SYNC_DLS report (Job SAP_NOTIFADMIN_SYNC_DLS): This report triggers a synchronization of distribution lists from mail server to the database. Scheduled daily, since ST710 SP1.

• RAGS_DSWP_SERV_CONTENT_UPDATE report (Job SM:Service Content Update): The job should run once a day if it is set to active in the SD Work Center.  The job performs an update of all the service content. For more details please see SAP note 1143775. As of ST400 Ehp1.

• RAGS_ENGAGE_CYCLE_DB_2_CRM report (Job SM: TRANSFER CYCLE (DB->CRM)): Since ST400 SP26, solution manager can handle transaction type 'SLFC' for Engagement Cycle in "SAP Engagement and Service Delivery" work center. As the DB structure was changed, this report transfers the data created before SP26 to the CRM and the new DB schema. Scheduled only once, since ST400 SP26 (Ehp1).

• RAGS_FILE_EXT_L_DL report (Job SM:LONG FILE EXT DOWNLOAD): Download from CSN and update the long file extensions that can be handled for incident exchange (Alert inbox and message creation). Scheduled weekly, since ST400.

• RAGS_SERVREQ_LOAD_FROM_SAP report (Job SM:SYNC SERVICE REQUESTS): This report regularly collects service requests from SAP. Scheduled hourly, since ST400 SP23.

• RAGS_WORK_BPM_CACHE report (Job SM:FILL BPM CACHE FOR WORKCENTER): After creating a solution (in DSWP or 'SAP Solution Manager Administration' work center), the new solution does not appear in Business Process Operation work center automatically. This report refreshes solution landscape buffers for BPO work center. Scheduled daily, since ST400.

• RAGS_WORK_SD_CACHE report (Job SM:FILL SD CACHE FOR WORKCENTER): This job fills the cache for the SAP Engagement and Service Delivery work center. Scheduled hourly, since ST400 (this report does nothing starting ST710 SP1, as buffers are not used anymore for both services and issues data which are read directly).

• RBM_REFOBJ_BUFFER_UPDATE report with SAP&ISSUES variant (Job SOLMAN_ISSUE_STATUS_REFRESH): The SAP Solution Manager buffers message attributes such as the current user and the processing status. This periodic job collects these message attributes from the message system and makes them available for analysis. Scheduled hourly, since ST400.

• RCSDCCHANDLETASKS report (Job SM:CSDCC HANDLE TASKS): This report synchronizes the list of requests for the SDCCN download with the list of SAP Solution Manager service sessions. Scheduled daily, since ST400.

• RDMD_ACCELERATE_DOC_USAGE report (Job SM:ACCELERATE DOC USAGE): This report accelerates the where-used list for documents in the Solution Manager. Scheduled daily, since ST400.

• RDMD_MIGRATE_TECH_INTERFACE report (Job SM:MIGRATE_TECH_INTERFACE): As of ST400 SP15, it is possible to create and use interfaces in the solution directory of SAP Solution Manager. This report generates the interfaces for any existing technical interfaces. Scheduled daily, since ST400.

• RDMD_REFRESH_INDEX report (Job SM:REFRESH_INDEX): This job updates the index for solutions once a day. This is updated on demand for changes in solutions, but this job should run in order to obtain a secure status. Scheduled daily, since ST400.

• RDMD_REMOVE_INCON report (Job SM:REMOVE INCONSISTENCIES): This report removes potential data inconsistencies in the solutions. Scheduled daily, since ST400.

• RDSMOPBACK_AUTOSESSIONS_ALL report (Job SM:EXEC SERVICES): This report executes service sessions in Solution Manager, carries out services daily (or weekly) and schedules new services. Scheduled daily, since ST400.

• RDSMOPCOLLECTSOLUTIONDATA report (Job SM:SEND_SOLUTIONS_TO_SAP): This report sends the data of the appropriately configured solutions to SAP. Scheduled daily, since ST400.

• RDSMOPSERVICEINFOS report (Job SM:SYNC SOLMAN INFO): To transfer the information about SAP Solution Manager usage (components used by customers) to SAP. Scheduled daily, since ST400.

• RDSWP_ARCHIVE_WMS report (Job DSWP_ARCHIVE_WORKMODES): This report archives work modes older than 30 days. See SAP note 1538133 for more details. Scheduled every 12 hours, since ST710 SP1.

• RDSWP_CLEAN_DSWPJOB report (Job SM:RDSWP_CLEAN_DSWPJOB): This report removes some unnecessary jobs. Scheduled monthly in ST400, daily in ST710.

• RDSWP_DTM_UPDATE_DT_STATUS report (Job UPDATE DOWNTIME STATUS): This report updates the Downtime Manager data (downtime status) to ensure semantic consistency. Scheduled daily, from ST400 SP15 to ST710 SP2.

• RDSWP_NA_DEL_NOTIF_ADMIN_DATA report (Job SAP_NOTIFADMIN_DELETE_USERS): This report deletes recipients or recipient lists used for notification for which the delete flag is true and last_changed_by date is older than 30 days (by default). Scheduled daily, since ST710 SP1.

• RDSWP_SC_MANAGED_SYSTEMS report (Job SM:SELFDIAGNOSISSELFCHECK): This report executes self checks on the managed systems of the solution manager. Scheduled weekly, since ST710 SP1.

• RDSWP_ISSUE_REFRESH report (Job SM:SYNC ISSUES FROM CRM): The table DSWPISSUE, which contains information from the CRM document and the support message (context), is updated by this report. This function is required for issue tracking and Service Plan. Scheduled hourly, in ST400 only.

• RDSWP_NM_SYNC_USER_DATA report (Job SM:SYNCHRONIZE USER DATA FOR NOT): This report synchronizes user data for the Notification Engine from Solution Manager satellite systems. Scheduled daily, in ST400 only since SP15.

• RDSWP_SELF_DIAGNOSIS (Job SM:SELFDIAGNOSIS): This report updates self-diagnosis information (solution-specific and cross-solutions yellow and red alerts used in service desk, issue management...). More details can be found in SAP note 1073382. Scheduled daily, since ST400.

• RDSWP_SELF_DIAGNOSIS_CRM_TRF report (Job SM:SELFDIAGNOSIS_SEND_TO_SAP): This report sends data from self-diagnosis application on customer's solution manager system to SAP (CSS system). Scheduled monthly, since ST400 SP26.

• RDSWP_SSA_MOVE_2_ARCHIVE_QUEUE report (Job SM:MOVE TO ARCHIVE QUEUE): This report triggers the archiving of the services and sessions (EWAs), for which the preset retention period was exceeded. Scheduled daily, since ST400.

• RDSWPCI_ISSUE_PROJECT_CONTEXT1 report (Job SM:MIGRATE_ISSUE_PROJECT_CONTEXT): This report migrates the project contexts for issues. Scheduled daily, since ST400.

• RDSWPCI_SURVEY_TRANSFER report (Job SM:SURVEY TRANSFER): This report transfers the questionnaires for customer satisfaction with the service session and issue processing to SAP. Scheduled weekly, in ST400 only.

• RDSWPCI_TOPISSUE_TRANSFER report (Job SM:TOP ISSUE TRANSFER): This report transfers the top issues that you have exchanged with SAP. Scheduled daily, since ST400.

• RDSWPCISERVICEPLAN report (Job SM:SYNC SAP SESSIONS): The session scheduling in the service plan is updated daily by SAP. This report is required to receive service plans from SAP. Scheduled daily, since ST400.

• RDSWPDOWNLOADDELETION report (Job SM:DOWNLOAD DELETION): This report deletes download data (transaction SDCCN), which is more than 30 days old. Scheduled every 3 days, in ST400 only.

• RDSWPJOBSCHEDULER report (Job SM:SCHEDULER): This report triggers all the other background jobs in the old job framework (job entries from the DSWPJOB table not in SMCONFIGJOBS table). Scheduled hourly, since ST710 SP1.

• RDSWPRULESUPDATE report (Job SM:UPDATE RULES): This report downloads a new set of rules for the Solution Manager. This set of rules controls the services and documents that can be offered (inline) for the information about system infrastructure and processes, which is maintained in the Solution Manager. Scheduled daily, in ST400 only.

• RMIGRATE_LANG_DEP_SAPSCRIPT report (Job SM:MIGRATE_LANG_DEP_SAPSCRIPT): This report optimizes the data for the document references to achieve an optimized access for the where-used list. Scheduled weekly, since ST400.

• RNOTIFUPDATE01 report (Job REFRESH MESSAGE STATUS): This report refreshes the contents of Support Desk or Expert-on-Demand messages that have been processed by SAP. Recommendation: use the Implementation Guide to schedule a customer-specific variant for the SAP Solution Manager. Scheduled hourly, in ST400 only. Replaced by AI_CRM_IM_UPDATE_FROM_SAP report since ST710 SP1.

• RS_WBA_REFRESH_POWL_BUFFER report (Job SM:RS_WBA_REFRESH_POWL_BUFFER): This job ensures that the system lists in the work centers for the technical system administrator (System Administration, System Monitoring and System Landscape Management) are updated in the Solution Manager (that is, adjusted to changes in the system infrastructure). Scheduled hourly, since ST400 (defined in the old DSWPJOB job framework for ST400, activated in SMCONFIGJOBS new job framework since ST710 SP1).

• RSGET_SMSY report (Job LANDSCAPE FETCH): This job gets system data for the Solution Manager system landscape by automatic data transfer from TMS/RFC or the System Landscape Directory (SLD). Scheduled daily, since ST400.

• RWBA_RFC_WATCHER report (Job SM:RFC MONITORING): This report checks RFC connections using RFCPING or RFC_PING. Scheduled hourly, only in ST400 (but part of the old DSWPJOB framework in ST710).

• SMO6_REORG2 report (Job SMO6_REORG2): This report reorganizes several kinds of data of CRM middleware such as BDOC messages and statistics, trace and key gen data... More details are available in SAP note 713173. Scheduled daily, since ST400.

• SMWP_BATCH report (Job SMWP_BATCH): This report updates the data displayed in the CRM middleware monitoring cockpit (SMWP transaction). Scheduled daily, since ST400.

Old job framework of the SAP Solution Manager (SM:SCHEDULER)

No separate job is created for jobs that are executed INLINE, and for this reason no separate job logs are created either. The relevant job log is actually in the overall log of job SM:SCHEDULER.

If job SM:SCHEDULER is not scheduled, you can use the function module DSWP_BATCH_JOB_START_SCHEDULER to schedule it or the Job Wizard in transaction SM36 (the report RDSMOP
JOBSCHEDULER). If you use function module DSWP_BATCH_JOB_START_SCHEDULER, define import parameter PF_START_TIME for the start time only, and leave PF_ACTIVITY at the default value 'S'.

If you want to run the jobs under another user, you must log on under this user and use the function module DSWP_BATCH_JOB_START_SCHEDULER and the parameter value 'PF_ACTIVITY' = 'D' to deschedule the job 'SM:SCHEDULER'. Afterwards, proceed as described above to schedule the job.

Affected Releases

Software Component Release From Release To Release And subsequent ST 700 400 400   ST 702 710 710

Correction delivered in Support Package

Support Packages Release Package Name ST 400 SAPKITL425

Read More @ https://service.sap.com/sap/support/notes/894279