FAQs - Business Process Monitoring (Miscellaneous)

Can I transport my Business Process Monitoring configuration from my development SAP Solution Manager to my production SAP Solution Manager?

A: Yes and no. As the monitoring configuration is considered as master data, there is no transport mechanism available. But you can transfer a complete solution (including monitoring configuration) from one SAP Solution Manager to another via transaction SOLUTION_TRANSFER. This can be done as an one-time effort but there is no delta mechanism.

Is it also possible to monitor non-productive backend systems?

A: Yes. Although Business Process Monitoring was designed to monitor core business processes which are running on productive backend systems, it is technically also possible to monitor non-productive systems. The preferred way is to create a second solution in your SAP Solution Manager where the "Leading Role" is non-productive (e.g. Test or Development). You can then re-use the same business processes and the same logical components in order to monitor your test or development system. Alternatively you can make it "quick & dirty" and create a new logical component where your test or development system is put into the productive role.

Is it possible to track single documents with Business Process Monitoring?

A: The main BPMon functionality is not tracking single documents as this task is far too performance intensive (esp.for high-volume scenarios) and the added value is little.

The question is why you want to track the single document. In most cases customers are asking for this because at some point of time the support organization gets the single request "Some document was not created, so please tell me where my document is" and then the search for the needle in the haystack begins. With the BPMon approach of providing crucial key figures for important watch points this question is obsolete. You get to see the complete entirety of documents causing problems. So if you work on this problematic documents in a timely manner then you won't get the support calls for missed documents any longer.
The big advantage with our approach is that you can identify systematic errors as you see all problematic documents. Hence you can resolve the root cause of problems (e.g. customizing errors, process design gaps, process deviations from defined template) and avoid similar incidents in the future, instead of just solving a single incident (one document lost).

Some of the application related key figures return several thousand backlog documents. How can Business Process Monitoring help in analyzing this data more thoroughly in order to reduce the backlog?

A: The Business Process Monitoring as an alert monitoring is not designed to analyze such document backlogs in a systematic manner. It is designed to raise exceptions based on meaningful threshold values. As so many customers actually encounter exactly this problem of high document backlogs and as this backlog should be reduced to a meaningful and acceptable level before the Business Process Monitoring is switched-on, that is the reason why the Business Process Analytics application was developed on top of the Business Process Monitoring. With Business Process Analytics you can identify organizational units and document types with the highest backlog and you can also analyze the age structure of the identified documents.

Which SAP BW is used for Business Process Monitoring trend reporting?

A: You can decide which SAP BW should be used. Either you use the SAP BW 7.0 as part of SAP Solution Manager or you use an existing SAP BW solution in your system landscape. The large majority of customers chose option 1 in order to not mix business and IT reporting.

What is the difference between Business Process Monitoring/Analytics and the traditional SAP NetWeaver Business Warehouse?

A: Please refer to the blog Traditional Business KPI approach vs Business Process Monitoring in order to understand how the bottom-up approach with Business Process Monitoring/Analytics can possibly complement your current top-down approach when it comes to Business KPIs.

What is the difference between Business Process Monitoring and SAP NetWeaver BPM?

A: Business Process Monitoring tries to ensure the stable and smooth operation of a company's core business processes with a focus on traditional transaction-based processes  The target groups are 2nd or 3rd level Application Support on IT side, IT Basis Support team and on business department side the business process or functional owners
SAP NetWeaver BPM is focusing on the development of rule-based composite business processes as "own practices" (usually SOA-based and often workflow related). These composite processes target at enhancing existing application core business processes and should provide the fast competitive and innovative edge versus competitors. For this SAP NetWeaver provides a combination of a process modeling and execution environment with a complex rules engine (SAP NetWeaver Business Rules Management), where you can flexibly model your business process first, assign simple or complex business rules in order to automate business decisions and finally generate executable process logic. The monitoring part for these processes is mainly targeting business end-users and business managers.

What is the difference between Business Process Monitoring and SAP Event Management?

A: The difference between Business Process Monitoring and SAP Event Management is explained in Kevin Wilson's blog Explaining the difference between Solution Manager's BPMon (Business Process Monitor) and SAP Event Management (SAP's best kept secret) .

FAQs - Business Process Monitoring (Process Modelling)

Can business processes from the project part (SOLAR01) be reused for Business Process Monitoring?

*A: Yes, you can reuse your modelled business processes for the project. But they cannot be directly used. You have to copy them first from the project part into the "Solution Directory" for Operations. So go into the Solution Directory and use the F4 value help on business process level with the source "Project". Once the process is copied to the Solution Directory, this process can be used for Business Process Monitoring.

In what way can process models from other modelling tools like Aris be reused?

A: There is no direct integration between Aris or any other modelling tool. Aris process models can be interchanged with the project part of SAP Solution Manager (where SAP Solution Manager is supposed to be the leading tool). From the project part then business processes can be copied into the Solution Directory and then be used for Business Process Monitoring.
Remark: Please be aware that Aris processes are in 95% of the cases not immediately fitting in order to be used for Business Process Monitoring. Aris processes are usually too granular for a daily operational alert monitoring like Business Process Monitoring, i.e. you cannot overlook a complete process on just one screen. So usually Aris processes need to be brought to a different abstraction layer for a meaningful Business Process Monitoring. However, maintaining business processes in SAP Solution Manager is of low effort. Hence, SAP usually recommends to either maintain business processes in SAP Solution Manager from scratch or to adapt in SAP Solution Manager the business processes derived from ARIS.

How should a business process be modelled for Business Process Monitoring, i.e. what is the granularity expected?

A: The Business Process Monitoring is working with the 3 level hierarchy provided by SAP Solution Manager (business scenario, business process, business process step) where the lowest step level should be represented by a transaction code or a background job that is executed. This kind of granularity is SAP's general recommendation that is also expected from other SAP Solution Manager functionalities.

How is the performance of the backend affected by Business Process Monitoring?

A: So far no customers reported significant performance decreases on the backend due to Business Process Monitoring. A system resource consumption of 2% is already considered as high for Business Process Monitoring, while other monitoring tools often consume 10-20% of system resources.

Are there template processes available that can be used for Business Process Monitoring?

A: Yes, there are process templates available that contain Business Process Monitoring configuration. These templates can be downloaded from the SAP Service Marketplace under (login required) https://service.sap.com/bpm > Media Library > Technical Information and then uploaded into your SAP Solution Manager via transaction SOLUTION_TRANSFER.
Remark: The template processes in the Business Process Repository contain no monitoring configuration

FAQs - Business Process Monitoring (Auto-reactions)

Can I create other auto-reactions than email, SMS or SAP Service Desk messages?

A: Yes, everything that is supported by SAPConnect can be used as auto-reaction method. With the next release there will be also a BadI provided so that you can create your own auto-reaction methods, e.g. raising an event. Also refer to SAP note 455140 - "Configuration of e-mail, fax, paging or SMS using SMTP" for technical details on SMTP configuration. You can also program your own auto-reaction methods via BadI .

Can I send an email to more than one recipient?

A: Yes, you can send emails to "Shared distribution lists" that you defined within the SAP Business Workplace (transaction SBWP) within the SAP Solution Manager. Those distribution lists can contain different recipients of different types like email or SMS.

Can I influence the layout of an email that is sent as auto-reaction?

A: Yes, with the ST-SER release 701_2010_1 you are able to configure the email subject, provide text templates for the email body, generate URLs into the email or program your own auto-reaction methods via BadI .

Can I forward alerts to other monitoring consoles?

A: At the moment other consoles are usually just pulling BPMon data from CCMS. As mentioned above with ST-SER 2010_1 several BadIs are provided so that you can create your own auto-reaction methods , e.g. pushing an alert to another console. Nevertheless you should evaluate what benefit you will have from forwarding alerts to other consoles. As only Business Process Monitoring provides the possibility to analyze the root-cause behind an alert, a logon to SAP Solution Manager is necessary anyway. Any other console provides just an option to display alerts but no root-cause analysis for BPMon alerts.

Can I create other trouble tickets than SAP Service Desk messages?

A: Yes and no. There is no direct integration between Business Process Monitoring and non-SAP ticket tools. But you can connect SAP Service Desk and other ticketing tools via a bi-directional web service interface. For further information see http://help.sap.com/saphelp_smehp1/helpdata/en/b3/64c33af662c514e10000000a114084/frameset.htm. As mentioned above with ST-SER 2010_1 several BadIs are provided so that you can possibly use these BadIs in order to integrate with your ticketing system

Auto-reactions are not created or sent out. What can I do about it?

A: A complete Troubleshooting Guide for Business Process Monitoring is available under http://service.sap.com/bpm > Media Library > Technical Information or directly here

FAQs - Business Process Monitoring (Getting started - Prerequisites, functional scope, target groups & use cases)

Which prerequisites have to be met in order to setup Business Process Monitoring?

A: Technical prerequisites are described in SAP notes 784752 - "BPMon in SAP Solution Manager  - Prerequisites" and 521820 - "Availability of Business Process Monitoring".

Is there a list of available key figures that come out-of-the-box?

A: Yes, there are more than 500 out-of-the-box key figures shipped with Business Process Monitoring. Please look at the presentation "Business Process & Interface Monitoring - Part 2" under (login required) https://service.sap.com/bpm > Media Library > Customer Information.

Can I configure my own (customer-specific) key figures?

A: Yes, Business Process Monitoring offers a complete Customer Exit framework in order to develop customer-specific key figures. Please also have a look at the document "Setup Guide - Customer Exit" under (login required) https://service.sap.com/bpm > Media Library > Technical Information. In many cases you can even have it simpler than this. If your new key figure shall only consist of one select statement on one table with up to 5 fields within the where clause then you can use the Table Entry Counter

Who is the target group for Business Process Monitoring?

A: In general the target groups are 2^nd or 3^rd level Application Support on IT side, IT Basis Support team and on business department side the business process or functional owners.

What are typical use cases that Business Process Monitoring in SAP Solution Manager can be used for?

A: Typical use cases are 1) Automating labor intensive monitoring tasks, 2) Internal benchmarking and gaining business process transparency, 3) Support and safeguard GoLives, 4) Monitor SOX compliance.

What is the typical effort to implement Business Process Monitoring?

A: The technical implementation of Business Process Monitoring is very simple and quick, as so many key figures are provided out-of-the-box. A simple pilot is always implemented within a day during the SAP CQC service for Business Process Monitoring. it is even possible to implement a Business Process Monitoring pilot within half a day. A comprehensive monitoring pilot including the configuration of auto-reaction methods takes usually up to a week. But if you want to make a big global or regional roll-out of Business Process Monitoring which covers many different countries and organizational units then this might easily take 6-12 or even 18 months. Hence the challenge is the organizational change management and the collection of monitoring requirements, but not the technical implementation.

Can I also monitor non-SAP and non-ABAP?

A: Yes, everything that is written into the CCMS within your whole system landscape can be included per copy & paste into the Business Process Monitoring. You can also use SAPCCMSR agents in order to monitor on operating system level. Besides you can use the Customer Exit framework as mentioned above in order to write your own data collectors. With the upcoming release there will be further options provided to simplify non-SAP and non-ABAP monitoring. But of course SAP will not provide similar out-of-the-box key figures for non-SAP as are provided for SAP applications.

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" ( attached to this message) 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 Management Work 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 Job Document 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.