The workload monitor reads the workload statistics from the workloadcollector database. Various collectors must run at regular time
intervals so that this database always contains current data.
The background job SAP_COLLECTOR_FOR_PERFMONITOR starts the program RSCOLL00 and this program checks the TCOLL table for program which needs to be started.
Workload collector program starting from system release 7.00 the background job SAP_COLLECTOR_FOR_PERFMONITOR should always be scheduled
in client 000 and the #System Time Zone# which is maintained in the transaction STZAC in client 000 should be exactly the same as the OS time zone setting.
The job SAP_CCMS_MONI_BATCH_STARTUP_DP is an event triggered job and it is started automatically by the background dispatcher.
Please check followoing notes:
926290 – SWNCCOLL: SAP workload NW collector collects no data
12103 – Contents of the TCOLL table
16083 – Standard jobs, reorganization jobs
198411 – Current data and information about time zones
481835 – Analyzing the time zone settings
741734 – Incorrect times due to the time zone settings
910897 – ST03N: Configuration of the time profile
The job SAP_CCMS_MONI_BATCH_STARTUP_DP is an event triggered job and it is started automatically by the background dispatchert.
Configuring the Workload Monitor
Displaying and Changing the Scheduling of Performance Collectors
Workload Monitor (ST03 or ST03N)
SAP Netweaver online documentation new workload collector
Recommended SAP notes:
1625354 – ST03n: BI Workload Data is not displayed or incomplete
1888095 – ST03/ST03N gets popup “No system load data available”
1300273 – SAP_COLLECTOR_FOR_PERFMONITOR: New architecture as of 7.20
1841778 – LOAD_PROGRAM_NOT_FOUND in RSCOLL00
At every transaction step, ABAP work processes first write kernel statistics and application statistics data to a buffer. This data is then saved in an OS file in
the directory on the host of ABAP instance.