Technical Operations
Page tree
Skip to end of metadata
Go to start of metadata

Two general installation steps have to be executed:

Two features can be used in addition (optionally). Both have to be customized in BPMon Setup and are therefore Solution related:

Activation in BI System

1. DVM Objects activation in RSA1

  • Prerequisite: BI has been activated (check: SOLMAN_SETUP > Basic Configuration > Step 6: Manual Configuration)
  • Use tx. RSTCO_ADMIN to check if BI activation was successfully (a green status should be displayed)
  • Remember: RSA1 has to be called in BI client (if separate client)

Select DVM cubes

Select DVM queries

Select DVM web templates

Drag and drop to personal worklist

Via Select Objects > Find SAP Solman > DVM > Cubes > Enlarge > Mark all > Transfer selected objects to personal worklist

Via Select Objects > Find objects with "DVM" and MyHome template with "myhome" > Transfer selected objects to personal worklist

After these steps install with option "In Dataflow Before and Aftrwds"

The result should look like this:

Note:

Some yellow alerts in the result protocol can be ignored

2. Execution of tx RSKC

Use tx. RSKC, maintain "ALL_CAPITAL" > execute
See SAP Note 173241 for detail information

Activation in EFWK (for each Managed System separately)
  • Start EFWK UI in Root Cause Analysis Work Center, work in "Managed System" View
  • Always use the "Select" button after system selection, filter with "DVM"
  • Switch on 12 extractors per system. This process may take a while...
  • Progress can be checked with tx. SM50
    on Solman: SMD_RFC respectively user in READ RFC connection to solman itself e.g. SOLMAN<Solman's SID><Solman's client>
    on managed system: e.g. SM_<satellite's SID>
  • Link to EFWK feature description

Note:

Best Practise: checking the parameter rdisp/max_wprun_time on each target system

  • A result should look like this

Note:

Result after finishing this step: EFWK runs (note: each extractor has its own periodicity)

Further information

At this stage data transfer into DVM cubes is established, data can be checked by using DVM web reports.

BPMon - general things

Always keep in mind:

BPMon related setup is about 2 different things: At first setting up a mechanism for triggering the automatic table analysis (which is done via Logical Components) and secondly setting up alerting on DVM relevant key figures (which needs Business Processes).

  • All further (optional) customizing has to be done in a productive solution
  • This is a conceptional matter > link to BPMon
  • Tx. DSWP (initial screen) can be used to get an overview on all solution
  • In solution Overview screen a new solution can be created (only solution name required)


If you see a screen like this: Use the Solution Overview button to get the overview of solutions.

Note:

In order to get a fast result a newly created "dummy" solution can be used. The customizing can easily be changed later.

Note:

Be aware of the fact, it is not possible to change the mapping in BW for already collected data.

Where to change after a solution has been created/chosen:

  • Solution Landscape Maintenance: Solution relevant settings, e.g. involved systems, process design, etc.
  • Work in Change mode
  • Ensure the Leading Role of the Solution is set to Production (can never be changed after starting solution maintenance)
  • Ensure a Business Process has been defined / assigned
  • Ensure Logical Components have to be added to the solution at first and then have been assigned to relevant process steps


Following:

Note:

Scenario and process have to be in status Productive.

Note:

Finally, all relevant systems should be seen in green Production System column.

Entry point for technical setup:

  • Operations Setup: "Setup Business Process Monitoring" session

Make sure when entering the "Setup Business Process Monitoring" session:

  • Reload monitors via the "Load Monitor" button
  • Performing this action for your target system only is sufficient, just select it as shown in right picture

If target TABLE ANALYSIS: Find your target Logical Component:

  • In left tree below Logical Components (quite the same as below, but nor pictured here)
  • The result in right window depends on how many Logical Components have been maintained in solution.

If target ALERTING: Find your process in mind:

  • In left tree below Business Processes
  • The result in right window depends on how many processes have been maintained in solution.
  • Select the relevant ones (lines)

Note:

This view covers all processes in a solution. The assignment of monitor objects is always performed one level down, on process step level.

2 Application Monitors can be found for DVM Cockpit (out of Cross Application Application Monitors range):

for Option: Saving Potential Analysis

for Option: DVM Alerting

DVM Cockpit: Table Analysis

BI Query Alert Collector - KPI in BI Query

BODVMANA

BOBIQUAC

Setup below Logical Components

Setup below Business Processes on step level

Note:

Reloading of monitors is always recommended after ST-A/PI had been updated.
What monitoring types are visible depends on the SAP Product of the target system.

Seeking for monitors:

  • After saving Monitoring Type: Cross Application
  • Use F4-Help
  • For particular customizing see further down.

Note:

Same procedure, no matter if below Logical Components or Business Processes.

ALWAYS FINAL STEP: It is always necessary to activate initial customizing respectively any changes made to it. Check the protocol.

Note:

Only a first setup requires the Generate step.

Further information

Best Practice General Business Process Management

Business Process Monitoring Set-up and User Guide

Option: Saving Potential Analysis

Preparation: Update DVM Content / Preparation of Virtual Fields

This step has to be performed on each target system.

  • Start transaction ST13 executing service tool: DVM_SETUP
  • Confirming all following info screens, including the right one
  • Results finally in the view shown below

Note:

DVM Content: pre-defined Virtual Fields, Best Practice Residence times, analysis variants, etc.

Proceed with button "Virtual Fields"

Start:

Result:

Setup: Saving Potential Analysis: TAANA trigger setup (below Logical Components)

Setup using the DVM Cockpit: Table Analysis monitor below a relevant Logical Component (which defines on what system the table analysis is actually performed). Customizing on 2 different levels has to be made (see further down):

  • On Monitoring Object level
  • On Key Figure level

Note:

In the screenshot an analysis of table BALHDR, which is located on SAP Solution Manager is exemplarily shown. It is also possible and recommended to target other tables on different systems.

Customizing on Monitoring Object level

There are always 3 key figures:

  • always use (select) Age of records
  • decide between Archiving Potential OR Deletion Potential

Note:

The difference between Archiving Potential and Deletion Potential is how the result is sorted in BW web report, under Archiving Potential respectively Deletion Potential. The result is the same in both cases.

Further data has to be maintained in Detailed Information tab

  • Double click on the counter field
  • Review the help text right above in the BPMon setup session for more (background) information!!

Note:

In the screenshot an analysis of table BALHDR is exemplarily shown. Of course, you have to maintain the table you want to be analyzed.
Some data is read from Managed System > logon necessary

Further data has to be maintained in Monitoring Schedule tab

  • Define a plausible execution time
  • Review the help text right above in the BPMon setup session for more (background) information!!

Note:

Do not schedule too often, e.g. execution once per week.

Customizing on Key Figure level

Age of Records

  • Only save

Archiving respectively Deletion Potential

  • Only maintain MANDANT (can be taken by F4 help) and
  • save

Note:

Don't forget to activate, as mentioned above in chapter BPMon - general things

Option: DVM Alerting (based on Business Process Monitoring)

Preparation: Check / Prepare Back RFC connection

For alerting a RFC connection is needed which points (back) to BW client (could be different to SAP Solution Manager client). An user with appropriate authorizations needs to be assigned. Regarding the authorizations check chapter DVM Cockpit Preparation. In general there are 2 options:

Using Logical Component of SAP Solution Manager

  • Check for available RFC connection(s) and assigned user(s)
  • Add authorizations

Just check in transaction SM59 for connections like BI_CLNT<BI client>, usually with user SMD_BI_RFC, or <SID>CLNT<BI client> and assigned user.

Note:

This way makes things easier. Data collection takes place only on SAP Solution Manager.

Using Logical Component of Managed System

  • Check / Create RFC connection
  • Maintain user and add authorizations

You obviously have to create a RFC connection...

Note:

Data collection takes place on Managed System and data is sent back to SAP Solution Manager.

Info:

The difference between the 2 options is where in a solution's graphic the alerting is visible. The alert information is always the same!

Setup: Alerting: (below business process)

Only one monitor (the BI Query Alert Collector - KPI in BI Query monitor) is used. It always queries the BW, no matter on what system it is executed.

Setup using the BI Query Alert Collector - KPI in BI Query monitor below a business process, on step level (which defines where in process graphic the alerting appears). Customizing on 2 different levels has to be made (see further down):

  • On Monitoring Object level
  • On Key Figure level

Note:

The 3 Key Figures can be used together or separate.

On Monitoring Object level

Information source definition, it is done across all selected Key Figures

  • Definition of: BI Infor Provider (Cube)
  • Definition of: Query
  • Review the help text right above in the BPMon setup session for more (background) information!!

Note:

4 different cubes:

  • Object Sizs
  • Age of Records + Potential Savings
  • 2x Archiving information

Definition of how often the monitor checks the data in BW, it is done across all selected Key Figures

  • Scheduling definition is possible on weekly or monthly basis
  • Review the help text right above in the BPMon setup session for more (background) information!!

Note:

The data in BW is basically updated on a daily basis, sometime less often. So it makes no sense to schedule the monitor in a shorter periodicity.

On Key Figure level

It is done for each selected Key Figure separately

  • Maintain technical information
  • Maintain thresholds for alert definition
  • Review the help text right above in the BPMon setup session for more (background) information!!

Note:

Use meaningful thresholds. Avoid getting too much alerting information.

KPI in BI Query (single value): This Alert Keyfigure will select exactly one KPI from the BI Query (typically on cell of the query result).

KPI in BI Query (max. values): This Alert Keyfigure will select all values returned by the BI Query, then sort those values descendingly and return the first x values (similar to a Top-N-Query). The value for x can be specified via a parameter.

Note:

Be careful with show green alerts option > could generate performance problem.

KPI in BI Query (# of values): This Alert Keyfigure will count the number of values returned by the BI Query, that are exceeding either the red or the yellow threshold specified.

Note:

Don't forget to activate, as mentioned above in chapter BPMon - general things

After Activation

After Activation step go back to that node and flag option DVM in relevant line

Note:

This is a prerequisite in order to get alerts visible in Work Center.

  • No labels

3 Comments

  1. Former Member

    Can the same steps be followed in setting up DVM Cockpit in Solman 7.1?

  2. Former Member

    I'd love to know that too - documentation on implementation in 7.1 is very light

  3. Krishnakumar Chamiyar

    We are on Solution Manager 7.1 but  there is no KPI tab visible under DVM statistics and  trend.