아주가끔은제정신

Setup example: BW Process Chain monitoring as part of Business Process Monitoring

This blog is the second part of a series describing best practices for BW Process Chain monitoring with SAP Solution Manager. You can read the first part of this series here. 

Before describing the single steps that need to be performed for setting up the BW Process Chain monitoring, we assume that the following steps are already performed:

• The BW system containing the process chains is successfully connected as a managed system in the Solution Manager.
• A solution containing the managed BW system is already created.
• The prerequisites mentioned in the first part of this series are met.

First of all we recommend creating a suitable structure in the "Business Scenarios" section of the Solution Directory (this can be found in the Solution Manager under "Solution Landscape Maintenance"). In our example we use the following structure:

 

Now we can start the "Setup Business Process Monitoring" session for our solution. The above created "Business Process" must be selected:

 

Then choose the process chains ("Business Process Steps") that you have maintained:

 

Now select the Monitoring Type "Background Processing":

 

Save your changes and proceed to the next check called "Background Processing". Here you have to choose an "Object identifier". Usually this identifier is identically to the name of your process chain. As "Job Type" you have to choose "BW Process Chain". The "Schedule Type" is usually "On Weekly Basis".

 

After saving your changes you have to provide the name of the process chain(s) that you want to monitor - in our case "DM_TEST_CHAIN_1". You can enter wildcards in the column "BW Process Chain ID" and search for the process chain in the managed BW system by choosing the option "Save + Check Identification". Then choose a process chain in the result list. Please enter "use chain start condition" as the "Start Procedure" of the process chain:

 

In the tab "Schedule on Weekly Basis", please activate the days on which you want to have the monitoring of the process chain(s) active:

 

Then, we need to enter the thresholds for the single key performance indicators that we want to monitor (e.g. "Start Delay", "Not Started on Time", ...). Additionally you can enter multiple chain elements. The same logic applies here: you have to enter and search for the "Process Type" and "Variant" of the single step of the Process Chain step and provide the thresholds. For example:

 

Finally, we need to generate and activate this monitor in the Solution Manager and the managed BW system. This can be done using the check "Generation/Activation/Deactivation":

 

Please note that the generating of the customizing and the activation must not result in errors.

Now you can switch to the "Operations" section of the solution. Here you will see now the previously created hierarchy in the Solution Directory that results in a graphical overview like this:

 

By clicking on the alert icon (in our example a red alert in the business scenario "BW Process Chains", business process "ERP Loads"), the Business Process Monitoring session starts and we can check for details on the alert(s) that have been raised:

 

By choosing the RSPC icon, you can directly jump into the managed BW system for further analysis of the alerts.

Frequently Asked Questions about Business Process Monitoring are answered under http://wiki.sdn.sap.com/wiki/display/SM/FAQ+Business+Process+Monitoring.

The previous blogs provide further details about Business Process Monitoring functionalities within the SAP Solution Manager.

• SAP Solution Manager – ALE / IDoc Monitoring
• SAP Solution Manager - qRFC Monitoring
• SAP Solution Manager - Functionalities For Inconsistencies
• SAP Business Process Monitoring within SAP Solution Manager
• SAP Solution Manager - BPMon Trend Analysis Reporting
• Best Practice - Business Process Monitoring for a typical manufacturing process
• Best Practice - Business Process Monitoring for Procure to Pay  
• Best Practice - Business Process Monitoring for a typical Order to Cash process
• Business Process Monitoring - Template configuration available for download
• FAQs about Business Process Monitoring
• Typical Use Cases for Business Process Monitoring in SAP Solution Manager
• New Business Process Monitoring functionalities in SAP Solution Manager - Customer Exit
• New key figure catalog for Business Process Monitoring available
• Why SAP offers different tools for Business Process Monitoring & Business Process Optimization
• Create your own auto-reaction messages in Business Process Monitoring via BAdI exit
• Protect your SAP ERP investment & improve your core business processes
• Refresh Solution Landscape cache for Business Process Operation Work Center

 


http://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/20213%3Futm_source%3Dtwitterfeed%26utm_medium%3Dtwitter%26utm_campaign%3DFeed%253A+SAPNetworkWeblogs+%2528SAP+Network+Weblogs%2529

Nearly every SAP customer who operates an SAP BW or SAP APO system encounters one main challenge - how to control and monitor BW Process Chains?! The definition of Process Chains is normally directly performed with the help of standard BW transactions like RSPC. The scheduling of the Process Chains is then usually also performed directly from within BW. Some customers schedule their Process Chains via external scheduling tools like SAP Central Process Scheduling by Redwood. Then perhaps comes the "toughest" part: How to monitor those Process Chains, especially if you have several hundred or even thousand Process Chains running per day?

• Manual monitoring via transaction RSPC or RSPCM. A very time-consuming way of monitoring and especially for complex chains it is nearly impossible to keep an overview. Further, the defined process chains that are monitored by RSPCM are user-individual.
• Automated monitoring via Business Process Monitoring in SAP Solution Manager as described in the Best Practice document "Background Job monitoring with SAP Solution Manager". Up to now the setup was also somewhat time-consuming and only single jobs within the Process Chain could be monitored so that only a milestone monitoring could be achieved. Further, the monitoring definition requires manual adoptions as soon as a process chain is activated.
• Automated monitoring via SAP CCMS described in the Best Practice document "Background Job monitoring with SAP Solution Manager". Here the setup was very easy but the monitoring functionality was somewhat limited as only the status of a complete chain could be monitored. No details of chain elements were available and no other monitoring capabilities than just the chain status were available.

Have you seen the John Cusack movie High Fidelity?  (or even better, read Nick Hornby's book)  Like his character in the movie, I'm a fan of Top 5 lists.  Top 5 Dream Jobs; Top 5 Artists; Top 5 Side 1, Track 1 Songs; Top 5 Most Painful SQL Statements...  OK, maybe that last one wasn't in the movie, but if he had been a DBA or Basis Administrator, it would surely have made it onto the DVD release.

Introduction

Once a variable has been created, the definition of some parameters (Processing By, Variable Represents and some others) can't be modified within Bex Query Designer or IP Modeler.

 

Goal

This blog describes how to change some variable parameters after it has been created and saved.

 

Business scenario

Let us consider a scenario where we have a variable represented by single value, but according to some business process, we need this variable to be represented by multiply single value instead of single value.

As mentioned above it is not possible to modify some parameters within Bex Query Designer or IP Modeler after a variable has been saved.

 

SAP recommended way to solve this issue is to delete this variable and create a new one with suitable parameter.

But what should we do if this variable already has been used within 100 queries ?

In this case we can use not recommended, but proper way - change these parameters directly via RSZGLOBV table.

 

Implementation

Go to TC SE16 -> Table RSZGLOBV and enter variable's technical name in Variable Name (VNAM) field.

When a result has been retrieved (it should be 2 records for one variable - M and A versions) select A version and press Change button (F6).

 

In the next screen it is possible to change any parameter of variable. In our case we want to change Variable Represents (Select parameters in RSZGLOBV table) parameter.

Change the content of Select parameters (VPARSEL) field from P to M and save the changes.

 

Do the same for M version entry in RSZGLOBV table.

Now we need to generate all the queries that use this variable.

Go to TC RSRT - > Environment - > Gen. Queries Directly.

 

Type info provider technical name with the queries to be generated and press Execute (F8).