Schedule Solution Manager Jobs

REFRESH MESSAGE STATUS
This periodic job gets SAP answers to messages sent by the SAP Solution Manager.
ABAP program: RNOTIFUPDATE01
Variant: SAP&WORKPLACE If you select the variant SAP&WORKPLACE for the report, only messages which were sent to the SAP Service Marketplace via the Service Desk, are processed. For further information about this variant, see SAP note 781163.
Start time: Immediate execution.
Execution interval: Twice a day.

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.
ABAP program: RBM_REFOBJ_BUFFER_UPDATE
Variant: SAP&ISSUES
Start time: Immediate execution.
Factory calendar ID: You must specify an ID.
Execution interval: Hourly.

REFRESH_ADMIN_DATA_FROM_SUPPORT
The job reads administrative data from the SAP support systems via the SAP-OSS RFC connection, periodically, and buffers it in the SAP Solution Manager system. This data is required for service connections and for the Support Desk (e.g. system data synchronization with the SAP Support Portal).
ABAP program:
AI_SC_REFRESH_READ_ONLY_DATA
Start time: Immediate execution.
Execution interval: Daily.
Note: The user under which the job runs, needs SAP Support Portal system data maintenance authorization.

SEND_SYSTEM_RELATIONSHIP_TO_SUPPORT
The job periodically sends information about which systems the Solution Manager is monitoring, to OSS. This data is required for the new services "SolMan Diagnostics" and "SolMan Classic".
ABAP Program: AI_SC_SEND_SYSTEM_RELATIONSHIP
Start time: Immediate execution.
Execution interval: Daily.

SERVICE_CONNECTION_LISTENER
The job periodically checks whether a service connection to be opened in the Solution Manager has been scheduled. If so, this information is sent to OSS. This job requires little system resources. It only connects to OSS as required. If the connection cannot be opened, it tries again at the next execution.
ABAP program: AI_SC_LISTENER
Start time: Immediate execution.
Execution interval: Every 10 minutes.
The job SM:TMWFLOW_CMSSYSCOL gets tracking data from systems, asynchronously.
ABAP program: /TMWFLOW/CMSSYSCOL2
Start time: Immediate execution.
Execution interval: Hourly

AI_SDK_FILL_FILE_TYPE_TABLE
The job sends the the attachments for the Service Desk messages you found to be sent to SAP. It updates the file type tables AISDK_FILETX and AISDK_FILETY.
Start time: Immediate execution.
Execution interval: Every 15 minutes.

SM:CSA SESSION REFRESH
This periodic job reorganizes the table DSMOPAPPL_CSATSK, which contains all Central System Administration tasks in the SAP Solution Manager, regularly.
The task table is used to create the Central System Administration 'Open Tasks List', which can be called with the graphic icon in SAP Solution Manager Operations.
This job requires little system resources.
ABAP program: DSVAS_APPL_CSA_REORG_TASKTABLE
Start time: 00:30
Execution interval: Daily.

SM:CSA UPDATE TASKSTATUS
This periodic job updates the Central System Administration Task Status icons in all SAP Solution Manager overview system graphics.
This job requires little system resources.
ABAP program: DSVAS_APPL_CSA_UPD_TASKSTATUS
Start time: 01:00
Execution interval: every 30 minutes.
Change Job Definition

1. Specify the job whose definition you want to change.
2. Choose Execute.
3. Choose the job whose conditions you want to change, in the list of jobs.
4. Select the job and choose: Job -> Change.
You can only change the definitions of scheduled and released jobs.
5. Change the start conditions of this job.