Analyzing the availability of systems for a solution

Prerequisites

You have scheduled and performed at least one SAP EarlyWatch Alert, if you want to analyze the SAP EarlyWatch Alert availability data.

 

 

Activities

       1.      Choose the transaction SOLUTION_MANAGER.

       2.      Choose Solution Reporting in Operations.

       3.      Choose Administration.

       4.      Choose System Availability Reporting.

The report selection screen appears.

 

Selection

○       Choose the parameters.

■       Analysis of

■       Analysis period

■       Select analysis content

 

System availability from EarlyWatch

 

 The system availability data from SAP EarlyWatch Alert is analyzed.

 

System availability maintained by Administrator

If you want to analyze system availability data such as duration or reason for downtime, independently of the EarlyWatch Alert reports, choose Edit System Availability.

You can add systems and maintain availability data for them.

 

 

Output

                            a.      Perform the analysis.

The analysis is presented in ALV grid format. You can adjust the layout to your requirements.

 

If you want to save the analysis as a document in the SAP Solution Manager as a *.csv file, choose Export Table as Attachment.

 

                            b.      Go back to the initial screen.

You can download the analysis to your local PC as an Excel file.

 

 

You can also schedule the report as a background job, SM_REP:RDSWP_REP_SYSTEM, to send it automatically by mail. You have created a variant for your report. Proceed as follows:

                                               i.       Choose the symbol  in the initial screen of your report.

                                               ii.       Select your variant.

                                               iii.       Choose Schedule.

You are in the job definition screen.

                                               iv.       Define the processing for the report.

                                               v.       Schedule the report.

The system runs the report.

 

 

Generate RFC Connections in Solution Manager

RFC connections to the managed systems are a prerequisite for the following Solution Manager functions:

• Generate Project IMGs in the Project Administration

• Go to the managed systems in the Configuration phase

• Customizing Synchronization (Synchronization Group Editor, Customizing Scout, Customizing Distribution)

• Read system data via the Service Data Control Center

• Managing Business Function Sets and Business Functions in the Switch Framework Cockpit

• Monitor change requests (Change Request Management)

You can only generate RFC connections for ABAP-based main instances.

 

 

Prerequisites

 

You are in the Solution Manager System Landscape transaction (SMSY), and have saved your last change.

The system for which you want to generate RFC destinations is not flagged as Planned.

 

Procedure

1. Choose the ABAP-based product instance of the system for which you want to generate RFC connections, in the left-hand frame.

2. Go to change mode.

3. Select a client in the Clients tab.

   Note : You can also generate RFC destinations using an assistant. To call the assistant, choose Generate RFC with Assistant in the Clients tab. Or proceed from 4).

    

4. Choose Generate RFC Destinations.

5. Choose the types of the RFC connections in the following dialog box.

    Recommendation

   Choose the RFC connection type Trusted System for the SAP Solution Manager, whenever possible. This avoids having to logon again every time that you go to a managed system when using the SAP Solution Manager.

   End of the recommendation.

   The details of the RFC connection to be generated, are shown at the bottom of the screen.

6. Choose the user options. If, for example, you use the central user management, you can assign existing users in the managed system.

7. You can specify a server group for load sharing, in the RFC Destination Attributes group box.

8. If the specification of the message server is not sufficient to set-up an RFC connection in your network, or your network contains routers:

   1. Choose Routing Information in the RFC Destination Attributes group box. The following dialog box displays the message server data. If you have not yet created the system message server as a server, it is created automatically and displayed at the left-hand side under Landscape Components, when you restart the Solution Manager System Landscape transaction.

   2. You can specify an IP address.

   3. Specify the routing information for the direction Solution Manager -> Router -> Server, e.g. /H/1.2.3.4/H/5.6.7.8/H/9.10.11.12

   4. Specify the routing information for the direction Server -> Router -> Solution Manager, e.g. /H/5.6.7.8/H/1.2.3.4/H/20.21.22.23

       Note : The Solution Manager System Landscape calls information to generate RFC connections in the following sequence:

      • Detailed routing information (e.g. /H/1.2.3.4/H/5.6.7.8/)

        If there is none:

      • Server IP address

        If there is none:

      • Server name

       

   5. Save your entries.

9. Remote read is the default for system data, because the SAP Solution Manager requires current system data, for example, to read the data of imported Support Packages. You should not reset the flag in the Actions after Generation group box.

10. Set the Assign RFC Dest. for System Monitoring flag, to be able to use the RFC destinations which you generate in the Solution Manager System Landscape, in the central system monitoring (transaction RZ21), and in the SAP Solution Manager for operational processing, in your solution landscape. You only need to set this flag for one client per ABAP system.

    The system enters the RFC destination data in the overview of the monitored remote SAP systems, in central  System Monitoring (transaction RZ21) Techn. Infrastruktur Display Topology .

11. Choose Generate RFC Destinations.

    You go to logon screens for each of the managed systems involved, consecutively, depending on the connection type selected.

12. Logon to the systems.

    Note : The system generates a log with information about the checks made, and all messages sent while making the connection.

     

Manage Tool List in Solution Manager

There are tool lists for various administration tasks. You can manage the tool lists by adjusting the selection of tools available for specified systems and components.

Add tools

1. Choose Add Tool in the Detail area. A dialog box appears.

2. To add a tool, add a meaningful name under Description.

3. Enter the technical name of the tool.

4. Under Type, you can choose:

   • ABAP Transaction:

     The system selected for the function call is a Managed System. RFC connections between the managed system and the Solution Manager system are a prerequisite.

      Note : You can choose whether the local Solution Manager system is to run the transaction.

      

   • ABAP WebDynpro:

     The selected system for the function call is the local system (the Solution Manager).

5. To put the tool in the list, confirm your entries.

 

Remove Tool

You can remove tools which you previously inserted manually.

To remove a tool from the list, select it, and choose Remove Tools from List, in the Detail area.

 

Analyzing Solution in Solution Manager

This procedure monitors the functions of SAP Solution Manager with Self Diagnosis and diagnoses any problems. For example, you can monitor the status of the SAP Solution Manager Early Watch Alert function, and diagnose problems based on the description in the alert.

The self-diagnosis analysis runs daily in the background by default. You can perform a new analysis at any time. For example, to check whether the problems shown by alerts have been resolved.

You can display the self-diagnosis results in various levels of detail:

• Solution-specific: You analyze a particular solution.

  For example, to check the consistency of the master data of a solution.

• Cross–solution: You analyze the entire system, or several solutions.

  For example if there are problems that affect all solutions.

 

Prerequisites

• You have configured at least one solution for solution-specific analysis.

• To view the results of Solution Manager Diagnostics in self-diagnosis:

  • You have installed the Solution Manager Diagnostics.

    More information: Installation Guide for SAP Solution Manager on SAP Service Marketplace at  http://service.sap.com/instguides SAP Components .

  • You have generated a report in the Solution Manager Diagnostics.

Procedure

1. Enter the SOLUTION_MANAGER transaction, or go to the System Monitoring work center.

2. Specify Scope of Analysis

1. Choose  Self Diagnosis Settings .

2. To execute an alert during analysis, on the Alert Types tab page, activate the required alert type.

3. To monitor a function during analysis, on the Alert Types by Functionality tab page, activate the function.

   Deactivate the functions that you do not use, to avoid irrelevant alerts.

4. To monitor a solution during analysis, on the Solution-Specific Alert Types by Solution tab page, activate the solution.

   Deactivate the solutions that you do not use, to avoid irrelevant alerts.

5. Save your entries.

3. Analyze the Status

1. To view the result of the analysis, choose Self Diagnosis.

   The status of various functions is displayed in the Functionality Status tab page.

2. To perform an analysis with the latest status, choose Execute.

3. To diagnose functionality, which has critical or very critical status, perform the following:

   1. Select the functionality.

      The status of the active alerts and message texts relevant to the functionality is displayed in the Alerts which determine the Functionality Status table.

   2. To resolve the alert, click Alert Resolution.

   3. Perform the instructions in the details of the Alert <message text> window.

4. To view the status of all alerts, irrespective of functionality, choose the Alert Status tab page.

5. To view the status of a solution, choose the Solution Status tab page.

6. To diagnose a solution which has critical or very critical status, perform the following:

   1. Select the solution.

      The status of the active alerts and message texts relevant to the functionality is displayed in the Alerts which determine the Solution Status table.

   2. To resolve the alert, click Alert Resolution.

   3. Perform the instructions in the details of the Alert <message text> window.

7. To view the details of execution, choose the Processing Information tab page.

Setting-Up System Monitoring in Solution Manager

1.      Start the transaction SOLUTION_MANAGER.

2.      Choose Solution Monitoring -> System Monitoring, in the Operations Set-Up area.

You go to an overview screen, from which you can go to the system monitoring set-up in change mode, and call Best Practice documents.

3.      Choose Set-Up System Monitoring.

You go to Change Mode: Solution Monitoring.

4.      Perform the following checks in change mode:

                            a.      Select Active Systems

                            b.      Check CCMS Connectivity

                            c.      Copy Default Settings

                            d.      Perform System-Specific and System Component-Specific Checks

                            e.      Insert Additional Hardware Components (optional)

                            f.      Insert Additional Software Components (optional)

 

System Monitoring Work Center in Solution Manager

This work center is the central point of access to the functions to monitor the status of your systems.

System status

Note : The following queries are specified by default:

• All systems

• ABAP systems

• Java systems

• Favorites

 

The following information is available, depending on the current query:

• The system list contains system availability status symbols.

  The status is checked according to CCMSPING. If no CCMSPING agent is installed or configured in your SAP Solution Manager system, a gray symbol with the quick info No CCMSPING Data is displayed for all systems.

• The details area contains information about the instances and servers of a selected system.

  You can get service status information with Service Details.

IT Performance Reporting takes you to analyses which show the development of the performance and load of monitored systems over a specified period.

 Note : This function is available if you have configured BI reporting

 

Alert Inbox

You have a list of alerts for the selected solution. The Detail area contains the previous status and KPI values for a selected alert. The Alert Details tab page contains detailed information about the alert, for example, the alert ID and the threshold values for the status.

The Documentation tab contains information about the cause of the alert, and processing suggestions, if they are in CCMS.

Select a time period under Reset, if you want to temporarily hide an alert, e.g. while processing it. The alert is not shown in the alert inbox during this period. It appears again afterwards. You can reset several alerts at the same time.

Display Downtimes goes to a dialog window with a status overview of planned and unplanned downtimes of the systems in the selected solution.

 

Self-Diagnosis

This view contains the following functions for the self-diagnosis of your SAP Solution Manager system and solutions:

• Specify analysis scope

• Display Analysis Results

• Display current alert status, sorted by functions, alert types or solutions

• Notes for resolving alerts

 

Proactive Monitoring

You can check the status of your systems before alerts are created. You can use the following functions:

• ABAP application server status, grouped by solutions

  The list contains the up-to-date rating of various performance values. The History column contains information about the development of the selected performance values, over time.

• ABAP application server monitoring tools

• Java application server monitoring tools

• Various monitoring tools for product instances

 

 Note : The client and RFC connection selection influences the selection of available tools for ABAP-based systems. You can check whether there are RFC connections for your system and client, in the RFC Information.

 

Connectivity

Based on the results of monitoring the connectivity, you can check the status of existing RFC connections in the following views:

• From Solution Manager to managed systems

  • ABAP destinations

  • HTTP destinations in ABAP systems

  • TC/IP destinations

• Between managed systems

  • ABAP destinations

  • TC/IP destinations

 

Job Monitoring

You have lists of background jobs with detailed information, sorted by job status. If you select a background job, there is further information in the detail area.

 Note :

By default, queries are defined for the following, as well as for various Standard Jobs and the display of scheduled and cancelled background jobs:

• Service Desk

• Issue Management

• Central System Administration

• Change Management

• My Jobs

 

This view contains the following actions:

• Job Analysis

• Job Scheduling

• Display Job Logs

• Job Documentation Overview

 

Set-Up

There are hyperlinks with which you can make basic settings for various system monitoring diagnosis tools, for example:

• EarlyWatch Alert

• Service Level Reporting

• Connectivity Monitoring

 

Reports

The following reports are available in various views:

• EarlyWatch Alerts for systems

• EarlyWatch Alerts for solutions

• Service Level Reporting

   Note : The overview contains EarlyWatch Alerts and Service Level Reports for the last 60 days. If you select a system or solution, all of its EarlyWatch Alerts and reports are displayed in the Detail area.

 

• System availability analysis

  Shows an overview of various system administration and availability reports for specified solutions. You can upload the documents with background information, for a solution. You can open the selected document with a hyperlink to the document name.

FAQs - Root Cause Analysis

How to solve error "No configuration for main instance" in E2E Diagnostics applications ?

Although your system your system is not listed in the SAP note 1010428, you can always define your system as one of the products supported in the note.

For example: if you look at SAP note 1010428 you won't find SAP E-recruiting, hence we can conclude it is not supported as a product.
However, SAP E-recuiting might have ECC or ERP system altogether with E-recruiting components installed. If this is true, you must use these components in SLD/SMSY so they can be used for E2E Diagnostics.

I'm getting a pop up screen asking for User name and Password each time I navigate in E2E Workload Analysis tabs.

This is a known issue in SAPGui with WebDynpro, BSP and SSO. Because of this behaviour the usage of WebDynpro is not officially supported in SAPGui, but only in Standalone Browsers or the NWBC. SAP note 1098009 states:  " Web Dynpro ABAP does not provide a controled behavior for the new  window (Ctrl+N) functionality of Web browsers. This browser  function should not be used as part of the application flow. " It is exactly what happens when you click on the E2E Workload Analysis tabs, it opens a IFRAME, hence it is a new window.

The solution is to call the Solution Manager Workcenter in the Web Browser. You can use the following URL:
http://:/sap/bc/webdynpro/sap/ags_workcenter

Last but not least, remember to properly set SSO to ensure there's no issue with HTTPS. Refer to SAP note 1121248.

The issue is not related to Solution Manager directly but a general restriction of displaying BI web templates in a WebDynpro iFrame User Interface element within an HTML control in SAPGUI.

You can assume that this will not change in future Solution Manager releases as it is a limitation of the infrastructure rather than of the application itself.

I have performed a system copy but the old host name is still in use in the URLs.

In transaction rz10, select Instance Profile, Extended Maintenance, maintain the proper icm host name parameter. Please restart the system after change the icm parameter, as it is a non-dynamic parameter.

The main notes to perform URL and PORT changes are 1297849 & 805344

Once the Diagnostics Agent is installed, do we need to update the kernel files to a new version?

Unlike other SAP System the Diagnostics Agent is updated automatically and therefore there is no need to upgrade it. The update is deployed to the Agent by the Solution Manager.

The release of the agent is linked to SAPinst only as long as the agent is not connected to the Solution Manager.  The SMD Agent 7.11 is refereed as 7.11 because it uses SAPINST 7.11, SMD Agent 7.20 because it uses SAPINST 7.20,  and so on.

As soon as it is connected to its release is upgraded automatically and therefore the release of the agent follows the release of Solution Manager system it is connected to.

If you check the Agent Administration link, you will be able to see the current agent version.

You must not mix up the release of the agent (given in the Agent Administration UI  - SOLMAN) and the release of the binaries installed with the agent (/usr/sap//SYS/exe) or the release of SAPinst.

The release of the EXE can stay as it is except if a big issue is detected with the SAP EXE.

Having this said, if you install an agent using SAPinst 711 and another one using SAPinst 720, both connected to the same Solution Manager, their releases will be the same and they will behave the same way.

What is the correct SMD version to install? Is it necessary to upgrade the SMD Agent according to the Solution Manager SP?

Several documents points to different directions. See below what the documentation states:

 According to SAP Note 1365123 - Installation of Diagnostics Agents
"24/11/2009 -> When using at leastSolution Manager 7.0 EhP1 SP20 install on the managed systems Diagnostics Agents 7.11 and SAP Host Agents"

According to the Agent_Installation_Strategy.ppt attached to SAP Note 1365123 - Installation of Diagnostics Agents"
Slide 24 states that with Solman 7.01 >=SP20 we should be using Diagnostics Agent 7.11 + SAP Host Agent

According to the "Diag Agent Troubleshooting Guide 2009 v.1.5"  Section 2.3 Managed System, page 8:
"To avoid libraries conflicts it is highly recommended to install a Diagnostics agent which has the same kernel release than the SAP systems already installed on the host.
Ex: On a NW04 or NW04s Managed System, you should install a Diagnostics agent 700 or 701, On a 711 or 710 Managed System, you should install a Diagnostics agent 711,"

The installation guides refers to new installations. That is, if you are  planning to install a Diagnostics Agent on a system that has no agent.

If you already have a agent installed, it's not necessary to upgrade it

The release of the managed system has no impact on the Diagnostics Agent  to install. Only the Solution Manager release is important.

The reason is that, once connected, the Solution Manager deploys applications to the Diagnostics Agent. The applications are inside the LM-SERVICE package, hence it's important to make it leveled with ABAP ST400 according to 1274287, as well as look for Patch Levels for the SPs.

"In case of Solution Manager uprade, it is not mandatory to upgrade the Diagnostics Agent version. This specification applies only to new installations."

FAQs - Job Scheduling Management in Solution Manager

Which SAP roles and customizing activities (transaction SPRO) are required in order to get started with the Job Management functionality in SAP Solution Manager?

A: SAP note 1054005 - "FAQ: Job Scheduling Management with SAP Solution Manager" describes roles and SPRO activities that are required in order to get started with Job Management in SAP Solution Manager.

Do I need to perform additional activities in order to use the Job ManagementWork Center in SAP Solution Manager?

A: Your user needs at least the two roles SAP_SMWORK_BASIC and SAP_SMWORK_JOB_MAN assigned. SAP note 1117355 - "Job Scheduling Management: Work Center" describes which steps are required in order to activate and use the Job Management Work Center.

If I want to use the integration between the Job Request and the JobDocument in SAP Solution Manager, do I need some specific CRM configuration?

A: SAP notes 1111310 - "Job Scheduling Management: Extended Configuration" and 1225906 - "Customizing of the Job Request for Job Management" describe configuration steps for CRM so that Job Request and Job Documentation can be linked.

If I want to use the integration between SAP Solution Manager and SAP Central Process Scheduling by Redwood, do I need to perform additional configuration steps?

A: SAP note 1122497 - "Process scheduling for SAP Solution Manager" gives a general overview on what needs to be configured in order to establish the integration between SAP Solution Manager and SAP Central Process Scheduling by Redwood. An integral part of this integration is an interface called Business Application Enabler (BAE). You can learn more about the setup of this interface in SAP note 1265635 - "How to setup BAE (Business Automation Enabler)".

What kind of document is a Job Request?

A: The Job Request is a CRM document usually of transaction type SLFJ. In older releases transaction type SLFN was used, i.e. the normal Service Desk document.

Which systems are shown in the value help of the Job Request form?

A: When you access a Job Request form it is automatically assigned to your CRM Business Partner. Now when opening the value help for System/Client you only get to see those systems where your Business Partner is assigned to, i.e. those system/client combinations that you see in transaction BP under general information in tab strip "Identification" for each entry IDType "CRM001".

What do I need to fill-out in order to send a Job Request?

A: Generally speaking you need to fill out the basice information required for a CRM document, i.e. the System/Client information which results in an IBase, the Short and Long Text (could be pre-filled when influencing the layout of the request form - see some question below) and the Business Partner for a reporter (automatically derived from the usere that calls the application) and sold-to-party (normally automatically derived in the background.

Is the Job Request a necessary prerequisite for creating a Job Document?

A: No, the Job Documentation application can also be used stand-alone. You can directly create/change/delete a Job Document. But in order to streamline and standardize the process of how job requirements from the business department or project team can be brought into the backend system, it is recommended to use the Job Request and Job Documentation application in an integrated manner.

Can I influence the layout of the Job Request form?

A: Yes, on the one hand you can configure static F4 value helps for selected fields. This can be defined in transaction SPRO under SAP Solution Manager > Scenario-Specific Settings > Job Scheduling Management > Extended Configuration > Adapt Organization Data.
On the other hand you can hide or pre-fill selected fields or declare selected fields as mandatory. This can be defined in transaction SPRO under SAP Solution Manager > Scenario-Specific Settings > Job Scheduling Management > Integration with Service Desk > Adapt Job Request Form > Create WebDynpro Component Configuration. 

Can I create a Job Request from the "outside"?

A: Yes, function module AGS_EJR_CREATE_JOB_REQ can be used to create Job Requests from remote systems. You can also refer SAP note 1327024 - "Integration into and Migration to Job Documentation"

What kind of document is a Job Document - is it a CRM document like the Job Request?

A: No, the Job Document is no CRM document. The Job Document is a "normal" document stored in a flat table. By the way it is also no document in the Knowledge Warehouse of SAP Solution Manager.

Can I influence the layout of the Job Document?

A: Yes, you can decide whether the respective tab strip of the Job Document shall be visible or not. This can be defined in transaction SPRO under SAP Solution Manager > Scenario-Specific Settings > Job Scheduling Management > Extended Configuration > Adapt Job documentation > Adjust Job Documentation Tab Visibility.

Can I change the building blocks that are proposed as naming convention for the background job?

A: Yes, the proposed naming convention can be adjusted to your company's needs. For this purpose you need to implement a corresponding BAdI. This can be defined in transaction SPRO under SAP Solution Manager > Scenario-Specific Settings > Job Scheduling Management > Extended Configuration > Adapt Job documentation > Set Up Own Naming Convention for Job Documentation. 

Are there also Job Templates available?

A: Yes, SAP also provides Job Templates in order to ease the documentation of background if the same documentation can be applied to several systems, processes, or even customers. 

In case I have to create many Job Documents. Is there some automatic help to fill-out some reoccurring information?

A: Yes, you can use macros in order to assign Contact Persons, Organizations, Logical Components (i.e. Systems) automatically. 

Can I see, within the respective backend system, whether a Job Document exists for the respective job or not?

A: Yes, if your backend system runs on a recenter SAP NetWeaver support package then transaction SM37 provides an additional column that indicates if a corresponding Job Document exists. By clicking on this new icon you can directly access the Job Document.

Can I delete a Job Document?

A: Yes and no. You can use the activity "Delete Job Documentation" from within the "Job Management" Work Center or you can directly set the Document Status "Deleted" within the Job Document itself. Then a corresponding deletion indicator is set in some database table and hence the Job Document disappears from all document lists, i.e. it is no loger displayed in those lists. But the document is actually not deleted from the database as there may be references to other (still) existing documents like Job Requests, Issues, Service Desk or Change Request messages.

Can I export a Job Document?

A: Yes, you can export a Job Documentation as an XML file. Please refer SAP note 1327024 - "Integration into and Migration to Job Documentation"

If I schedule a job via a Job Document (type BC-XBP) which interface is used and is SAP Solution Manager then controlling this job?

A: As the name implies the SAP Solution Manager uses the BC-XBP interface, just like any other external scheduling tool, in order to schedule the job. But unlike other scheduling tools the SAP Solution Manager "fires and forgets", i.e. the SAP Solution Manager is only creating the job in the respective backend system but does not control it. The full control is taken over by the CCMS infrastructure of the respective backend system. Hence the SAP Solution Manager cannot be considered a real scheduling tool.
The preferred SAP scheduling tool is SAP Central Process Scheduling by Redwood as this tool also provides many additional features that transaction SM36 does not provide, e.g.

                               Handling job interceptions

                               Providing logical queues and priorities from 1-100

                               Enhanced workload balancing based on CPU and memory consumption

                               Providing job chain functionality allowing complex job dependencies and event-based scheduling

I am using an external job scheduling tool. Can I somehow identify whether end users are bypassing my central scheduling?

A: Yes, actually there is a rather easy way to identify end user scheduled jobs that are bypassing your central scheduling efforts. The key to the solution is the job status "Released". 

Can I somehow control jobs that are (de-centrally) scheduled by end users without taking scheduling authorization away?

A: Yes, that is possible. Actually SAP provides two complementary solutions for this problem. On the one hand you can intercept jobs that are scheduled by certain users . On the other hand you can re-direct end users into a Job Request form once they want to schedule a job via transaction SM36, SM37 or SA38

Which external scheduling tools can be integrated with SAP Solution Manager?

A: The SAP Central Process Scheduling by Redwood is the only external scheduling tool that is tightly integrated with SAP Solution Manager. Nevertheless you can of course also use Job Request, Job Documentation and Business Process Monitoring functionality in combination with every other external scheduling tool. But then you have to transfer scheduling information manually from the Job Document to your respective scheduling tool (like you probably trasnfer data nowadays from MS Excel to your scheduler). And other external scheduling tools do not provide any feedback loop to SAP Solution Manager like SAP Central Process Scheduling by Redwood does.

Where can I find answers to FAQs around the job scheduling itself in the SAP system?

A: SAP note 31503 "FAQ: Background jobs" answers frequently asked questions around background jobs in general in the SAP system, e.g. "Can I reserve background work processes for individual applications or users?" or "Can job definitions be transported into other clients or systems?"

Where can I find some help for troubleshooting if I encounter problems with SM36/SM37 scheduling?

A: SAP note 37104 "Error analysis: Background processing system" helps with analyzing the most typical error situations when it comes to problems with SM36/SM37 scheduling.

Can I also monitor non-SAP jobs with Business Process Monitoring?

A: Only if you use the integration between SAP Central Process Scheduling by Redwood (SAP CPS) and SAP Solution Manager and only if you bought licenses that allow to schedule also non-SAP jobs with SAP CPS, then you can extend the Business Process Monitoring also to non-SAP jobs.

If I use Business Process Monitoring in order to monitor job runtimes, is it then also possible to report on the trend how the runtime evolved over the last couple weeks or months?

A: Yes, this kind of trend reporting is possible. You can transfer the monitoring results to SAP BW and evaluate trend lines via pre-defined web templates. The setup is described in transaction SPRO under SAP Solution Manager > Scenario-Specific Settings > Job Scheduling Management > Set Up BI Reporting for Job Scheduling Management.

Can I also monitor complete BW Process Chains?

A: Yes, you can use Business Process Monitoring in order to monitor complete BW Process Chains (identified by the respective chain ID) and monitor specific elements within a chain. The setup has to be done directly in the Business Process Monitoring setup and not within a Job Documentation. The Job Documentation application cannot really be used (yet) for BW Process Chains as those chains are always using generic job names.

If I am simply interested in monitoring a certain job status like "canceled", can I do this without Business Process Monitoring?

A: Yes, you can simply use the Job Management Work Center within the SAP Solution Manager in order to centrally check for a certain job status on the respective backend system. But this is then only a manual monitoring and no automated monitoring. 

What happens when I activate Change Control for some Job Document?

A: If the Change Control is activated for some Job Document then this document can only be changed together with a valid Change Document as part of the Change Request Management. So only if your CRM Business Partner is assigend as processor for the Change Document then you can change the corresponding Job Document. All other users have no authorization to perform any changes on the Job Document.