You can run reports in SAP NetWeaver BW to monitor job processing. The reports are part of the health checks for job management. You use data from business process monitoring and from the managed systems.
The Job Scheduling Management (JSM) analyses contain further reports, including an SAP NetWeaver BW report for job alerts with trend analysis. With this report, you can examine the data for a positive or negative trend. For more information, see Reports: Business Processes Operations
Activities to set up SAP NetWeaver BW reports in Customizing for SAP Solution Manager, under :
You have activated the BI content
This activates all SAP NetWeaver BW objects in the BI content which are relevant for the JSM health check.
You have set up data aggregation.
You have specified the periods (e.g. week or month) over which the system report data is summed.
Note
You only need to set up SAP NetWeaver BW reporting once, before the first reports are created.
You have performed the administrative activities for analyzing JSM, in the Job Management work center, in the Administration view:
Assign data collections
You must activate the following extractors:
Extractor |
Description |
---|---|
F86_JSMHC_EXTRACTOR_JOBS |
JSM Health Check - at job level The system extracts this data into the table TBTCO. |
F87_JSMHC_EXTRACTOR_STEPS |
JSM Health Check - at job step level The system extracts this data into the tables TBTCO and TBTCP. |
Note
Activation of the extractors for the managed systems requires the latest version of the solution tool plug-in (ST-PI) und the application service tool (ST-A/ PI, type M), in the managed system. You can download ST-PI and ST-A/PI from SAP Service Marketplace (http://service.sap.com) using the quick link support tools. Call the program RTCCTOOL in the managed system, after installation, in the ABAP editor (transaction SE38). It checks whether certain transports or SAP notes are missing in your system.
Configure the JSM health check
You have specified which reports the system is to run, to inform you about the duration and delays in job processing, using job and business process monitoring data.
You can call the following JSM health check reports:
Report |
Data source |
Template ID |
---|---|---|
Daily job view |
Managed system |
0SM_JSM_HC_XBP_DAILY_JOBS |
Daily view of steps |
Managed system |
0SM_JSM_HC_XBP_DAILY_STEPS |
Weekly view of jobs (aggregated) |
Managed system |
0SM_JSM_HC_XBP_WEEKLY_JOBS |
Weekly view of steps (aggregated) |
Managed system |
0SM_JSM_HC_XBP_WEEKLY_STEPS |
Monthly view of jobs (aggregated) |
Managed system |
0SM_JSM_HC_XBP_MONTHLY_JOBS |
Monthly view of steps (aggregated) |
Managed system |
0SM_JSM_HC_XBP_MONTHLY_STEPS |
Weekly view of business process management |
Business Process Monitoring |
0SM_JSM_HC_BPMON |
Weekly view of business process management (job chains) |
Business Process Monitoring |
0SM_JSM_HC_BPMON_CHAIN |
Note
For further information about running a health check report, see Monitoring Process Chains.
You can, for example, analyze the following key figures for job management:
Kex figure |
Analysis object |
Value range or interval |
---|---|---|
Runtime distribution |
All jobs |
|
Runtime distribution |
Long jobs |
|
Job status: Canceled or Completed |
Job comparison by number of jobs |
|
Job status: Canceled or Completed |
Job comparison by job runtime |
|
Workload distribution |
User comparison by number of jobs |
|
Workload distribution |
User comparison by cumulated job runtime |
|
Workload distribution |
Server comparison by number of jobs |
All servers on which the system runs jobs in the background |
Workload distribution |
Server comparison by cumulated job runtime |
All servers on which the system runs jobs in the background |
For further information about the dataflow in IT performance analysis, see Data Flow.