Wednesday, November 21, 2007

Job Scheduling Management in Solution Manager

Purpose

This application manages and documents the background processing in your entire system landscape. Document the business processes based on each job, and the scheduling of the job in your production system. Specify with which thresholds you monitor the job with SAP Solution Manager business process monitoring.

The function documentats your background processing centrally. You can create new documentation and change existing documentation.

SAP Solution Manager Job Scheduling Management provides:

Structured job documentation (technical and business) for

Your jobs and their steps.

Your relevant business processes.

Your job scheduling parameters (automatically copied from SAP systems via the BC-XBP interface).

You monitoring parameters (manual copy of Business Process Monitoring session settings).

Problem-handling procedures.

Your contacts for scheduling, monitoring, development and system landscape.

Your Service Desk messages, change requests and issues for tracing.

Job request via SAP Service Desk message: Documentation of end user background processing change requests, by assigning the message to the job documentation.

Job monitoring is supported by SAP Solution Manager Business Process Monitoring. You also document your configuration centrally, in the Scheduling Management Job.

Prerequisites

You have the SAP Solution Manager, and have configured the Scheduling Management application job.

Note

To use the application optimally, maintain the following data:

· Document all the background processing jobs in the Scheduling Management job in the SAP Solution Manager.

· Schedule and release jobs in your production system (transaction SM36/SM37).

· Put the solutions for the background processing business processes, in the SAP Solution Manager Solution Landscape Maintenance.

· Configure the solutions for the background processing business processes and business process steps, in the SAP Solution Manager Business Process Monitoring.

End of Content Area

No comments:

Blog Archive