DVM Cockpit Juni2010

.
How-to Guide
SAP Solution Manager
7.0 EhP1
Configuration of
SAP Data Volume
Management
Cockpit (DVMC)
Version 1.3 – June 2010
Applicable Releases:
SAP Solution Manager 7.0 EhP1 SP22+
BI_CONT 7.04 SP 07
SAP Data Volume Management Cockpit – Configuration Guide
© Copyright 2006 SAP AG. All rights reserved. contained in this document serves informational
purposes only. National product specifications may
No part of this publication may be reproduced or vary.
transmitted in any form or for any purpose without
the express permission of SAP AG. The information These materials are subject to change without
contained herein may be changed without prior notice. These materials are provided by SAP AG and
notice. its affiliated companies ("SAP Group") for
informational purposes only, without representation
Some software products marketed by SAP AG and or warranty of any kind, and SAP Group shall not be
its distributors contain proprietary software liable for errors or omissions with respect to the
components of other software vendors. materials. The only warranties for SAP
Group products and services are those that are set
Microsoft, Windows, Outlook, and PowerPoint are forth in the express warranty statements
registered trademarks of Microsoft Corporation. accompanying such products and services, if any.
Nothing herein should be construed as constituting
IBM, DB2, DB2 Universal Database, OS/2, Parallel an additional warranty.
Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390,
OS/400, iSeries, pSeries, xSeries, zSeries, z/OS, These materials are provided “as is” without a
AFP, Intelligent Miner, WebSphere, Netfinity, Tivoli, warranty of any kind, either express or implied,
and Informix are trademarks or registered including but not limited to, the implied warranties of
trademarks of IBM Corporation in the United States merchantability, fitness for a particular purpose, or
and/or other countries. non-infringement.
SAP shall not be liable for damages of any kind
Oracle is a registered trademark of Oracle including without limitation direct, special, indirect, or
Corporation. consequential damages that may result from the use
of these materials.
UNIX, X/Open, OSF/1, and Motif are registered SAP does not warrant the accuracy or completeness
trademarks of the Open Group. of the information, text, graphics, links or other items
contained within these materials. SAP has no control
Citrix, ICA, Program Neighborhood, MetaFrame, over the information that you may access through the
WinFrame, VideoFrame, and MultiWin are use of hot links contained in these materials and
trademarks or registered trademarks of Citrix does not endorse your use of third party web pages
Systems, Inc. nor provide any warranty whatsoever relating to third
party web pages.
HTML, XML, XHTML and W3C are trademarks or SAP NetWeaver “How-to” Guides are intended to
®
registered trademarks of W3C , World Wide Web simplify the product implementation. While specific
Consortium, Massachusetts Institute of Technology. product features and procedures typically are
explained in a practical business context, it is not
Java is a registered trademark of Sun Microsystems, implied that those features and procedures are the
Inc. only approach in solving a specific business problem
using SAP NetWeaver. Should you wish to receive
JavaScript is a registered trademark of Sun additional information, clarification or support, please
Microsystems, Inc., used under license for refer to SAP Consulting.
technology invented and implemented by Netscape. Any software coding and/or code lines / strings
(“Code”) included in this documentation are only
MaxDB is a trademark of MySQL AB, Sweden. examples and are not intended to be used in a
productive system environment. The Code is only
SAP, R/3, mySAP, mySAP.com, xApps, xApp, and intended better explain and visualize the syntax and
other SAP products and services mentioned herein phrasing rules of certain coding. SAP does not
as well as their respective logos are trademarks or warrant the correctness and completeness of the
registered trademarks of SAP AG in Germany and in Code given herein, and SAP shall not be liable for
several other countries all over the world. All other errors or damages caused by the usage of the Code,
product and service names mentioned are the except if such damages were caused by SAP
trademarks of their respective companies. Data intentionally or grossly negligent.
2
Table of Contents
HOW-TO GUIDE 1
SAP SOLUTION MANAGER 7.0 EHP1 1
1 INTRODUCTION 4
1.1 ARCHITECTURE OVERVIEW 5
2 PREREQUISITES 7
2.1 TECHNICAL PREREQUISITES 7
2.2 ORGANIZATIONAL READINESS 7
3 PREPARATION STEPS 9
3.1 AUTHORIZATIONS 9
3.2 SMSY CONNECTIVITY 11
3.3 TECHNICAL READINESS CHECK - SAP NOTES (RTCCTOOL) 13
4 INSTALLATION & CONFIGURATION 16
4.1 SAP SOLUTION MANAGER SYSTEM 16
4.1.1 Diagnostics Setup - SMD Agent Setup 16
4.2 SAP NETWEAVER BUSINESS WAREHOUSE PREPARATION 19
4.3 EXTRACTOR FRAMEWORK SETUP 22
4.3.1 Technical Information on DVM Cockpit Extractors 24
4.3.2 Technical Restrictions for specific Extractors 26
4.4 BUSINESS PROCESS MONITORING SETUP SESSION 26
4.4.1 Entering Business Process Monitoring Setup Session 26
4.4.2 Saving Potential Analysis Configuration 28
4.4.3 Setting up Data Volume Management specific Alerting 31
4.5 MANAGED SYSTEM RELATED STEPS 37
4.5.1 Generation of TAANA – Virtual Fields (managed system) 37
5 INTEGRATION INTO WORK CENTER OF SOLUTION MANAGER 40
6 TROUBLESHOOTING 45
6.1 INCONSISTENT PPMS MODELING / NO DVM EXTRACTORS AVAIL. IN EFWK ADMIN UI 45
6.2 HOW TO SUPPORT PRODUCT EHP X FOR SAP ERP 6.0 46
6.2.1 Solution Manager version  EhP1 SP5 46
6.2.2 Solution Manager version < EhP1 SP5 46
6.2.3 Additional information 47
6.3 MANUAL RESTARTING OF EXTRACTORS 48
6.3.1 Determine failed extractor 48
6.4 IDENTIFYING AUTHORIZATION ISSUES (ALERTING & SAVING POTENTIAL CALCULATION) 50
7 APPENDIX 1: EXAMPLE QUERIES AND DASHBOARDS 52
7.1 EXAMPLE QUERIES PER INFOPROVODER 53
7.1.1 DVM Age of Records & Potential (0SM_DVPOT) 53
7.1.2 DVM Archive Job Information (0SM_ARCHJ) 55
7.1.3 DVM Archiving History (0SM_ARCHH) 57
7.1.4 DVM Object Sizes (0SM_ SIZES) 58
8 APPENDIX 2: LINKING QUERIES TO QUERIES 61
3
1 Introduction
The following “how- to” guide covers all of the steps required to implement the Data Volume
Management Cockpit (DVMC) as part of the SAP Solution Manager 7.0 EhP (respectively SP18
onwards).
The intention of this SAP Solution Manager scenario is to provide all necessary information for
every phase related to Data Volume Managemen in one single platform. Please see the following
high level summary on possible use cases.
Data Volume Management Cockpit

Objectives
Establish a Centralized Information Cockpit for

Data Volume Management
Get Transparency on Landscape’s Data
Detect biggest ‚Consumer‘ of data
Reveal Potential for Creating / Optimizing

a Data Volume Strategy
‘Simulate’ different Data Volume Scenarios

Provide Monitoring/Reporting/Alerting Capabilities
Enable automatic Compliance Checks of

Corporate Data Volume Strategy
© SAP AG 2009. All rights reserved. / Page 5
Figure 1: DVM Cockpit Use Cases

For more information about SAP Data Volume Management in general (Powerpoints,
Documentation, Offline Demos) please visit the Application Lifecycle Management Area in the
Service Marketplace (also available via alias „DVM‟, http://service.sap.com/DVM).
4
1.1 Architecture Overview

To understand the setup procedure described in this document the following graphics are provided.
The intention of this chapter is to provide the „big picture‟ of the overall implementation scenario.

Architecture Overview
Work Center,
SAP Business
Scenarios Extractor Framework
Process Monitoring
BI Dashboards &
Queries
SAP Solution Manager

Customer
Extractors SCM CRM ERP …
Database
Data ST-A/PI
Statistics TAANA
Collectors (DVM Content)
(DB02)
Figure 2: Architecture Overview
From an integration perspective the DVM Cockpit is to be considered as a „Cross Application‟

Scenario on top of the SAP Solution Manager 7.0. It concentrates information into the “MyHome”
workcenter.
The central platform of the SAP Solution Manager allows us to be connected to most of the
systems of a whole landscape (e.g. via SMSY, SLD and SMD / SMD Agents) which is key for the
creation of a centralized information platform. In addition the SAP Netweaver BW 7.0 which comes
with the Solution Manager installation is used as a data store.
On the scenario side we will setup the Extractor Framework which is in charge of controlling and
scheduling the related DVM extractors as well as the inbuilt resource manager for both system
roles, SAP Solution Manager as the managing system as well as any target system (such as ERP
6.0) as the so-called managed system.
5

Architecture Details Extractor Framework
Setup
Operations
Wizard
Introscope EM
Administration &
Native DB Control
DB Cockpit
Access
E2E WA
SSR
SSR
Extractor
BI E2E EA
SMD Agent
Application
SMD (Java) EFWK E2E CA
Web
Web DB Tables DVM
Service
Service Cockpit
Client
ST-A/PI ST-A/PI …
Extractor Wrapper
Data Enrichment
ST-PI
Extractor
Managed Systems Solution Manager Persistence Layer Applications

Landscape
Model
© SAP 2007 / Page 21
Figure 3: Extractor Framework
The DVM specific extractors and related data collectors are mainly application independent and
more technically (i.e. SAP Basis) related. Most of the DVM Cockpit related functionality runs as of
SAP Basis 4.6C (in addition with specific SP levels, please refer to the chapter “prerequisites” for
more details).
6
2 Prerequisites
The following prerequisite SAP Notes ensure that all relevant steps are performed in order to be
able to configure the DVMC. Please be aware that those notes always focus on SAP Solution
Manager as well as the managed system. For both system roles the prerequisites need to be
checked and established.
2.1 Technical Prerequisites

There are several main SAP Notes which are updated on a regular basis. Please always refer to
these notes as well as to the automatic procedure described in the notes (based on report
RTCCTOOL):
1. SAP Note 1159758 - Data Volume Management: Central Preparation Note

https://service.sap.com/sap/support/notes/1159758
2. Note 1233709 - Prerequisites for Data Volume Cockpit (DVM Cockpit)

3. SAP Note 521820 - Availability of BusinessProcessMonitoring

4. SAP Note 784752 - BPMon in SAP Solution Manager - Prerequisites

5. SAP Note 1172948 - SAP Solution Manager - Basic functions

6. SAP Note 1365123 - SMD Agent Strategy

7. SAP Note 1234387 - SMD Agent Installation

8. General SMD documentation

http://service.sap.com/diagnostics
2.2 Organizational Readiness

Apart from the technical readiness of the involved systems there are some organizational things to
be considered, such as organizational roles, tasks and responsibilities in the area of Data Volume
Management. To get the overall idea of the operational area surrounding the topic of Data Volume
Management SAP has released the SAP Standards for Solution Operations, among others you will
find the standard document for Data Volume Management.
For more details please refer to the Support Standards Information page in the Service
Marketplace (-> alias supportstandards) or follow this link.
Specific configuration steps are done in the context of a Solution in the SAP Solution Manager.
Therefore we highly recommend to follow our recommendations and best practices for a Solution
7
Concept and Design to understand the background of a solution and to determine a suitable
solution for the configuration of the Data Volume Management Cockpit.
8
3 Preparation Steps
3.1 Authorizations
The table (figure A) below shows the minimum selection of authorizations a user should have in the solution
manager in order to execute the entire setup scenario.
Role name Description

SAP_BW_ALL SAP_ALL
SAP_BI_E2E SAP Solution Manager / SMD & E2E authorizations
SAP_BW_PCC_BRAND_MANAGER BI Role for CRM Portal Role Brand Manager
SAP_J2EE_ADMIN Administration User for the SAP J2EE Engine
SAP_SMDIAG_WIZARD Solution Manager Diagnostics Wizard
SAP_SMWORK_BASIC Work Center: Basic Authorization Objects
SAP_SMWORK_BPM Work Center: Business Process Operations
SAP_SMWORK_DIAG Work Center: Root Cause Analysis
SAP_SMWORK_LANDSCAPE_MAN Work Center: System Landscape Management
SAP_SOLMANDIAG_E2E RFC Diagnostics - SAP Solution Manager (Technical User SMD_RFC)
SAP_BW_CCMS_SETUP Installation and Configuration of CCMS BI Content
SAP_OP_DSWP_BPM Solution Monitoring Operations BPMonitoring
SAP_SM_BI_EXTRACTOR Solution Manager: BI Extractor Framework
SAP_SOLMAN_ONSITE_ALL_COMP Composite role for SAPSUPPORT user
SOLMAN_CONFIG Solution Manager Configuration User
SAP_SETUP_DSWP_BPM Operations Setup BPMonitoring
SAP_SMWORK_SETUP Work Center: SAP Solution Manager Administration
SAP_SMSY_ALL Solution Manager System Landscape - full authorizations
SAP_RCA_DISP Root Cause Analysis (display authorization)
SAP_RCA_EXE Root Cause Analysis (Delta Authorization to SAP_RCA_DISP for Application)
SAP_SMWORK_MYHOME Work Center My Home Page
Figure A: Minimum authorization requirement
Especially in the area of Solution Manager Diagnostic (managed system setup) the screenshot below (figure
B) points to a lack of authorization
9
To setup the BW content the minimum requirements for authorizations are the following three profiles:
• S_RS_ADMWB_A
• S_RS_ADW_A
• S_RS_EXPL_A
10
3.2 SMSY Connectivity

The setup of the Data Volume Mangement Cockpit (DVMC) always comprises at least two
systems: The SAP Solution Manager 7.0 (SolMan) and at least one managed system (e.g. your
current productive ERP system). As such, standard SMSY (transaction code SMSY) configuration
to the Managed System should be among the first steps, to be technically connected to the
platform of SAP Solution Manager. Especially the Business Process Monitoring (BPM) Framework
requires the related monitoring connections (RFCs to ABAP systems) for data exchange such as
configuration data and alert information. In the context of the DVM Cockpit the BPM Setup session
is used as part of the alerting as well as for the configuration of the „Saving Potential‟ scenario.
Figure 3: Check existing RFC connections in SMSY
11
We recommend using the SMSY wizards to connect new systems and to check the SMSY status
of all systems before you continue with the subsequent setup procedure.
12
3.3 Technical Readiness Check - SAP Notes (RTCCTOOL)

Please be aware that as of ST-A/PI 01L* the SAP delivered report RTCCTOOL (Service
Preparation Check) is capable of automatically checking the status of the SAP Solution Manager
as well as the managed system in regards to the successful implementation of all DVM specific
SAP Notes.
During execution RTCCTOOL will start downloading the recommended set of SAP Notes from
SAP OSS via the standard SAPOSS RFC connection which is also used for downloading SAP
Notes. The content at SAP is always up to date and reflects the best practice recommendation of a
minimum set of SAP notes which should be implemented before a specific tool is used or if a
specific service is going to be delivered. In any case we highly recommend to implement all of
these notes.
During execution RTCCTOOL considers the local systems environment and filters the SAP Notes
correspondingly. For example, database version specific SAP Notes are already filtered, which
means that Oracle specific SAP Notes are not shown if the underlying DB of a system is MSSQL
etc.
Please be aware that RTCCTOOL does not analyze all technical details of a SAP Note. Especially
support package relations are often not reflected by RTCCTOOL. This means that the list of notes
might contain SAP notes which are already implemented via a specific support package of the
affected software layer (e.g. SAP_BASIS). Finally during the standard note implementation
procedure of transaction SNOTE, it will always analyze all necessary dependencies (e.g. a SAP
Note requires another SAP Note to be implemented etc.).
To double check if all mandatory SAP Notes have been implemented correctly, proceed as follows:
13
Run program
RTCCTOOL in SE38.
Next, click the

“Settings” button on the
Service Preparation
Check screen
Check the “Prepare for

DVM” box and click
Save:
14
Typical results of the

RTCCTOOL / DVM
report
Note: SAP OSS Note 1295328 cannot be implemented with transaction SNOTE. Manual activity is required.
15
4 Installation & Configuration

4.1 SAP Solution Manager System
The following chapters describe the main steps to be performed on your SAP Solution Manager
7.0 EhP1 system as well as the SAP Netweaver Business Warehouse system on top of it.
4.1.1 Diagnostics Setup - SMD Agent Setup

Following SMSY connectivity, the Solution Manager Diagnostics (SMD) Agent must be installed on
each Managed System. The Agent is required to establish the connection between the Solution
Manager Diagnostic and the target system. The SMD Agent runs on operating system and is the
most essential part of the whole SAP Solution Manager infrastructure. Among others the data
extractors and the resource management of the target system is controlled by the SMD.
For more information on the SMD Agent installation including mass-deployment (install the SMD
Agent on multiple systems using and unattended mode), please visit the service marketplace (alias
„diagnostics‟).
Without the SMD Agent, the extractors necessary for DVMC functionality will not be available.
Once the SMD Agent is installed, go through the Diagnostics Agent Setup Wizard for both, the
Diagnostics System and the Managed Systems. The SAP Solution Manager Diagnostics needs to
be fully configured and upgraded to EhP1 at least (remember to perform upgrade related steps
after implementing EhPs in the SAP Solution Manager)
If you haven‟t done the Diagnostics Setup before it can be best reached via the Solution Manager
Work Centers, such as Root Cause Analysis.
Note that the tabs within the Solution Manager Workcenters Transaction
(SOLMAN_WORKCENTER) show up according to the Roles you have been assigned. Pay
particular attention to the Roles beginning with the following text: SAP_SMWORK*
An example would be:
SAP_SMWORK_DIAG
which is the role for
“Work Center: Root
Cause Analysis.”To run
the Solution Manager
Diagnostics Agent
Setup Wizard, select
“Root Cause Analysis”
tab after starting
transaction
„SOLMAN_WORKCEN
TER‟
In the left pane under

Common Tasks / Setup
and Check, select
Diagnostics Setup.
16
Following this, select

Diagnostics System
Then click on Setup

Wizard
Select the Diagnostics

Server Setup Wizard
option
Provide all relevant

information and click
Next
The jobs that run as a result require a few moments. Hit the “Refresh” button on the next screen
until all of the indicators are green.
Following this, return to

Diagnostics Setup and
select Managed
Systems
Then click on Setup

Wizard
17
Then locate the system

to be set up. In this
case, we‟re selecting
SMT
Note that both the

ABAP and Java Stacks
associated with SMT
initially display as “NOT
DIAGNOSTICS
RELEVANT.” This, of
course, must be
changed as follows.
Expand the
selection[NOT
DIAGNOSTICS
RELEVANT] under
Managed Products,
and uncheck the “Not
Diagnostics Relevant”
check box
18
Then select the

Product to be
managed. Note that
multiple selections are
possible
Finally, hit the Set

button to validate
assignment of
Managed Products
Hint: The most common issue with the managed system setup is data inconsistency with SMSY.
Please pay special attention to the SMSY product and product version assignment of a system and
check that the same product has been selected in the managed system setup as well. If there is a
data inconstency the DVM specific extractors might not show up in the list of available extractors
for the selected system in the next setup step.
4.2 SAP Netweaver Business Warehouse Preparation

Before the extractors will be setup the SAP Netweaver Business Warehouse 7.0, which runs on
top of your SAP Solution Manager system, has to be prepared.
The most important pre-check is to have a look at the allowed characters to be uploaded to BW.
Please see SAP Note 173241 for more details. During the future data extraction processes we
also extract table names, index names and related master data such as descriptions etc. As a best
practice we usually setup the permitted characters (transaction code RSKC in your SAP Solution
Manager system) to ‘ALL_CAPITAL’.
Note: Please be aware that the procedure described below is also valid for any upcoming update
of the BW content, e.g. if a new BI_CONT release or SP is being implemented.
19
Transaction Code
RSA1.
“BI Content” button on
left navigation pane.
Look for the SAP

Solution Manager
section
Select the Data
Volume Management
entry.
Choose “Grouping / In
Dataflow Before &
Afterwards.” This is to
ensure that all related
sub-objects will be
considered by the
installation / activation.
The default selection

on this screen is as
follows
20
The BI Content for

Data Volume
Management Info
providers needs to be
dragged & dropped to
the outer right part of
the screen
Following this, choose

“Install.”
Queries need to be
activated seperately in
order to get the actual
content
An alternative would be
to Install in
Background, in case
the installation process
becomes
temperamental, takes a
long time and
subsequently exceeds
the run time tolerance
for a Dialog Work
Process.
In the above case, the

process completed
successfully
21
4.3 Extractor Framework Setup

The above mentioned procedure was particularly important for the data extractor setup. Now the SAP
Solution Manager system is able to determine all availabe extractors which are released for the product and
product version of the system for which you want to activate the DVM extractors.
To start the DVM extractors proceed as follows:
In the Solution Manager

system go to
SOLMAN_WORKCENTERS,
then access Root Cause
Analysis.
Click on Extractor FWK

Administration on the left
navigation pane
Then select the Managed

Systems tab in the UI that
follows
Select the relevant system

i.e. system to be analyzed
Use the option and

restrict the display of the
extractors to the DVM
relevant ones.
22
Multiple selections are

possible.
Click Activate.
Be sure to activate all DVM

Extractors. There may be
some on the following page.
There should be twelve (12)
in total.
23
4.3.1 Technical Information on DVM Cockpit Extractors
The following table provides an overview about the DVM related extractors and their technical backgrounds
e.g. purpose, expected data growth and frequency.
Extractor Name Purpose Frequency Extraction Volume Data Growth

(default)
DVM DB OBJECT SIZES Extraction of DB weekly One record for each medium
statistics (sizes, table and index
entries) for tables available in SAP
and indexes dictionary
DVM SAVING POTENTIAL Extraction of Saving hourly One record for each low - medium
Potential Analysis result set of a saving (depends on
results and potential analysis configuration of
histogram data from and histogram set the relevant
target system scenarios)
DVM ARCHIVING RUNS Extraction of hourly One record for each low (depends on
Archiving Job executed archiving archiving
information run within the last 60 frequency)
min.
DVM ARCHIVING Extraction of hourly One record for each low (depends on
STATISTICS Archive File archive file created archiving
statistics (details on within the last 60 frequency)
archived, deleted min.
objects and related
file sizes)
DVM ARCHIVING OBJECT Master Data Loader weekly One record for each no data growth
(DESCRIPTION) for descriptions of archiving object in besides the
Archiving Objects the managed system initial load for
each system
(data is
overwritten)
DVM DEVCLASS Master Data Loader weekly One record for each no data growth
(DESCRIPTION) for descriptions of development besides the
Development class/package initial load for
Classes/packages each system
(data is
overwritten)
DVM TABLE HIERARCHY Creates and weekly One record for each no data growth
(DEVCLASS) updates a Hierarchy development besides the
for application class/package initial load for
component each system
assignement (data is
overwritten)
DVM TABLE MASTER DATA Master Data Loader weekly One record for each no data growth
(DESCRIPTION) for descriptions of table besides the
tables initial load for
each system
(data is
overwritten)
DVM TABLE NAV Attribute Loader weekly One record for each no data growth
ATTRIBUTES (Assignment of table in the besides the
tables to Document managed system initial load for
24
Type, Application each system

Area, Development (data is
Class etc.) overwritten)
DVM AOBJ HIERARCHY Creates and every 24 One record for each no data growth
(TABLE - AOBJ) updates a Hierarchy hrs archiving object – besides the
for the linkage table assignment initial load for
between Archiving combination each system
Object and Tables (data is
overwritten)
DVM ARCHIVE FILE STATUS Master Data Loader weekly One record for each no data growth
(DESCRIPTION) for descriptions of file status besides the
archive file status initial load for
each system
(data is
overwritten)
DVM ARCHIVE STORAGE Master Data Loader weekly One record for each no data growth
(DESCRIPTION) for descriptions of file status besides the
archive storage initial load for
status each system
(data is
overwritten)
25
4.3.2 Technical Restrictions for specific Extractors

Some of the DVM extractors have a specific inbuilt logic of how to handle the delta update of already
extracted data to keep the BI reporting in sync, see below the brief overview of the design of those
extractors:
1. Archive File Statistics, DVM ARCHIVING STATISTICS:

The extractor considers the archiving procedure as completed only if all archiving and deletion steps have
been performed successfully. For those archiving runs for which only the archiving steps have been
completed, but the deletion step is still missing, the statistics are re-evaluated each time the extractor is
executed as long as the archive file status (STATUS_OPT) equals 3.
The performance impact of re-evaluating those archive files is absolutely minimal and even for a high
amount of file status to be re-read the total runtime for the delta handling is within a range of several
seconds.
Due to the above mentioned design of the extractor please be aware that for queries using the archive file
information we highly recommend to use the calculated key figures indicated with 'last value' when creating
new queries. All SAP standard queries are using the same approach.
4.4 Business Process Monitoring Setup Session

The Business Process Monitoring Setup Session is required for two configuration steps as part of the DVM
Cockpit: Saving Potential Analysis and DVM Alerting. To ease the overall configuration handling we re-
use the session environment of the Business Process Monitoring Setup session.
NOTE: Only productive systems in productive solutions are supported by the BPM setup.
4.4.1 Entering Business Process Monitoring Setup Session

There are mainly two ways to reach the “Business Process Monitoring Setup Session” in your Solution, i.e. in
the Solution that contains all relevant systems.
4.4.1.1 Transaction DSWP
Call transaction DSWP
26
Choose the solution in which you

want to configure the saving potential
analysis
4.4.1.2 WorkCenter Business Process Operations
Call transaction
SOLMAN_WORKCENTERS
Business Process Operations
Common Tasks  Setup

Business Process Monitoring
For DVMC purposes a Solution

titled “DVM Demo Solution” was
created
27
4.4.2 Saving Potential Analysis Configuration
Select a Logical
Component
In this case, we‟re

selecting a Logical
Component pointing to
the Solution Manager
instance.
Next, select the Logical

Component reflecting
your system for the
potential analyses
Z_SOLMAN_ITSELF
and under Monitoring
Types check the
Application Monitor box
This creates a new

subcheck called
“Application Monitor.”
Under Application
Monitor, specify “DV
Cockpit: Table
Analysis” in the
Monitoring Object
Name space.
Select Node “DV

Cockpit: Table
Analysis,” then check
“Age of Records” and
“Archiving Potential”
under Key Figures. The
“Age of Records” Key
Figure is where all the
table data will be
28
stored. The “Archiving

Potential” Key Figure
is, at this point, a
workaround for a
technical glitch that
prevents the “DVMON:
Collective Analysis” job
from being visible.
Click the Detail

Information tab, then
double click on Counter
001
Click Yes
Fill in the Counter

detail, and then click
Execute.
Next, fill in the detail for
the “Archiving
Potential” Key Figure.
Click “Save + next

open check,”
then double click on

Archiving Potential
Counter 001
29
Here, we select only

the Field Name value,
typically MANDT
Do not provide any
other detail here.
Remember, this is
simply a workaround.
If the Field Name drop
down list in the
Archiving Potential
Counter doesn‟t return
any values, it is likely
that the table in
question doesn‟t exist
on the Managed
System being
configured. In this
case, simply move to
the next step.
Click Execute to save

the information.
Under the Monitoring

Schedule tab, Specify
a timeframe for the
collectors to run
Several considerations are important here:

 Select a Weekly Schedule Type. Typically, it is sufficient to run the collectors on a Sunday.
 Select the day of the week for the job to run.
 Specify a Start Time.
 Do not check the “DC in Background” check box.
 Hit the Save + Next Open Check icon when complete.
 The resulting job will show up in SM37 as “DVMON: Collective Analysis.”
 It will not be visible until it has been kicked off. If something happens to cancel or abort the job, it is
likely that it will not automatically reschedule.
 You can test this process by creating a simple Business Process Monitoring session containing one
table specification. Schedule the job for a period that is a few moments in the future, activate and
generate the customizing. Then monitor via SM37.
 Important: Please do not set a frequency lower than 60 mins as this will lead to the situation that no
records will ever be extracted into the BW.
30
The final step in the BPM Setup process is Generation / Activation / Deactivation.
Depending on the current activation status, additional pushbuttons are displayed:
 If monitoring is active, there is a pushbutton for deactivation and a pushbutton to execute the
generation, deactivation, and activation at once.
 If monitoring is inactive, there is a pushbutton for activation.
If monitoring is already active, it is always necessary to deactivate and reactivate it to activate the latest
configuration.
4.4.3 Setting up Data Volume Management specific Alerting

4.4.3.1 Available standard Queries for Alerting
The actual BW content contains the following standard Queries especially configured for alerting purposes.
Please refer to the table below for the available BW Queries
Info Cube Query Name Tech. Name Description

DVM Age of DVM Alerting Saving 0SM_DVM_ALERTING_SAVINGS_PERC Alerting on savings
Records & Potential (%) calculated in
Potential percent in relation
to the figures of the
last analysis
DVM Alerting Saving 0SM_DVM_ALERTING_SAVINGS_MB Alerting on savings
Potential (MB) calculated in MB in
relation to the
figures of the last
analysis
DVM Object DVM Alerting Current 0SM_DVM_ALERTING_SIZE_CURRENT Alerting based on
Sizes Object Size the current object
size in MB
DVM Alerting Growth - 0SM_DVM_ALERTING_GROWTH_M Alerting based on
Month the monthly object
growth in MB
DVM Alerting Growth - 0SM_DVM_ALERTING_GROWTH_W Alerting based on
Week the weekly object
growth in MB
31
4.4.3.2 Example Query Configuration
The sections in red are the most crucial areas of a BW Query. Please find the explanations below.
1) Free Characteristics - Having all the object information in this section enables you to drilldown to
each of the selected characteristics.
2) Columns - The results will be calculated on the monthly object growth figures in MB
3) Rows – The results are provided per system ID
32
4.4.3.3 Configuration Steps

Start Transaction
“DSWP” and open your
solution
Click on
Choose
Select Business
Scenario and define a
scenario title.
Select Business
Processes and create
a process under your
own naming
convention.
Status needs to be set
to “Productive” and
Process availability to
“7x24”
33
Different alerting steps

need to be created now
based on the type of
alerting which should
be set up
Include “logical
component”.
Recommendation is
to run it locally on the
Solution Manager
which means to choose
the logical component
of the solution manager
itself.
For documentation
reasons set the
processing to “Dialog”
Display your settings
with the “Graphic”
button
Go back to transaction
DSWP, Business
Process Monitoring
and select DVM
Alerting infrastructure
34
Select one of your

previously created
alerts and choose
“Application Monitor”
In order to have the

monitors available via
F4 Help you first need
to load them using the
refresh push-button
Select the BI Query
Alert Collector
(BOBIQUAC)
Define a Monitoring
object name and
“Save”
This leads to the

screen opposite where
a type of key figure
supporting your alerting
requirements should be
selected.
KPI in BI Query (single

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

Keyfigure will select all
values returned by the
BI Query, then sort
those values in
descending order and
return the first x values
(similar to a Top-N-
Query). The value for x
can be specified via a
parameter.
KPI in BI Query (# of
values): This Alert
Keyfigure will count the
number of values
returned by the BI
Query that exceed
either the green or the
yellow threshold
specified.
Click on detailed
information and
double-click the
counter field to bring
you to the next pop-up
Choose the RFC

destination (select
“NONE” if you intend to
run the alerting locally
on the Solution
manager -
recommended)
otherwise you have to
maintain the relevant
RFC destination.
Choose the BI Info

Provider (0SM_SIZES)
Select one of the

standard DVM alerting
Queries (select via F4
Help) and provide a
description.
36
As a last parameter the

different thresholds‟ to
categorize the alerts
must be set.
4.5 Managed System related Steps

The following actions need to be executed on your target system (e.g. your SAP ERP system)
which you are planning to connect to the DVM Cockpit. If you plan to connect your SAP Solution
Manager system as well to the DVM Cockpit (which is technically on the SAP Solution Manager
system) you have to perform these steps on the SolMan system as well.
4.5.1 Generation of TAANA – Virtual Fields (managed system)

As part of the subsequent system and scenario specific setup of a „Saving Potential Analysis‟ the
DVM Cockpit uses a basis functionality called TAANA (table analysis, also available via transaction
TAANA). To create a histogram of data and to finally calculate the saving potential on records
basis the TAANA uses virtual fields, which extract the month or year information out of a date field
of a table.
There are already some virtual fields shipped via the software layer SAP_BASIS, but for
application specific analysis many more fields are required, especially virtual fields for the
extraction of the „month‟ out of a date field that are not available per default.
The manual way of creating virtual fields is to use the transaction TAANA_VF in your development
system (see the application help within this transaction for more information). Using that approach
you need to define your own virtual fields, record them via a transport and import them in all
systems in the transport layer until you can finally use them in your production environment. Please
be aware that virtual fields need to be created in each of you managed systems BEFORE you can
use them in the saving potential configuration.
The semi-automatic approach is to use another expert tool which is mainly used in an SAP Active
Global Support Service delivery in the context of Data Volume Management. The expert tools can
be called via a launchpad, which is transaction code ST13. The DVM_SETUP tool provides you
with the possibility to generate SAP AGS approved and recommeded virtual fields on demand.
There exists a set of several hundred virtual fields. SAP Support uses these in their every day
service delivery. With the following steps you can simply generate these virtual fields as well, which
usually contain all fields to setup the saving potential scenario for well know top tables and
document types.
37
In the managed System

go into transaction
ST13. Select the
DVM_SETUP tool and
execute.
The DVM content is

updated on a regular
basis from SAP‟s best
practice definitions
Click on “Ok”
Click on “YES”
Go to “Virtual fields”
Click on “Start creation”
38
The result is the

following screen
The warning “Table does

not exist on DB!” is
expected. Scroll further
down in the results and
you will see that Virtual
Fields have been
successfully created.
Background Information: The DVM Content, which contains the definition of virtual fields is not
application specific. Hence the DVM_SETUP tool always has hundreds of virtual field definitions
for ERP, CRM, BW, SRM, APO etc. systems. During the creation of the virtual fields for each of the
field definitions the corresponding database table is checked for existence as well as for technical
structure, to finally check if the creation of the specific virtual field is technically supported. Hence
39
the log output will always indicate a lot of fields not being created, e.g. a CRM virtual field is not
created on an ERP system etc.
5 Integration into Work Center of Solution Manager

As the concept of
accessing work centers
within the Solution
Manager is role-based
and not authorization
based you should
update your roles as
shown in the example
on the right, even if you
have “SAP_ALL” you
still need to assign the
specific *SMWORK*
roles.
Choose the transaction

SOLMAN_WORKCEN
TER
Work Centers are

displayed for the roles
you have been
assigned
Of interest here is the

DVM section. You can
see the DVM alerts
from the alerting setup
(if you have decided to
activate and customize
alerting)
40
The prerequisite for

that is the
categorization of your
alerting as “DVM
relevant” as shown on
the screenshot.
The alerting display

functionality within the
work Center is very
much the same as in
the traditional way but
more convenient
Don‟t get confused with

the DVM button shown
here. This will be used
to integrate delivered
DVM services and the
service reports. These
reports can be taken as
a starting point for the
DVM Cockpit setup.
41
The MyHome Work

Center can also be
used to integrate your
dashboards directly.
Therefore you have to
follow the steps below
Figure 4
Select Business
Process Operations
within the
“SOLMAN_WORKCEN
TER” transaction
Select “Reports” from

the selection panel
Add the following

information
Hint: the requested

Server / Server port
can be determined by
executing your
dashboard manually
and using the
information from the
internet explorer
42
Choose the MyHome

Work Center and select
Personalize
For implementing the

DVM Cockpit deselect
everything except the
DVM section
Please be aware that

only those alerts which
are already generated
in the system will be
displayed (i.e. if no
yellow or green alerts
are available, then
there will be no display
in the MyHome work
Center personalization)
Choose the Layout of

Overview button of
your personalization
screen to define the
areas where the
different information
should be displayed
When doing this please
consider the future
layout of your MyHome
Work Center.
43
The different areas

represent the physical
location of the items
you assign.
Some dashboards
may need a longer time
to be loaded and
displayed. If the work
center refreshes too
frequently you never
get a display result. To
avoid permanent
refreshing of the work
center MyHome the
asynchronous refresh
settings should be
adjusted at least to
1800 – 3600 sec.
44
6 Troubleshooting
The following section is intended to provide some tips and tricks for common issues which happen during the
setup procedure or simply to provide some background on root cause analysis.
6.1 Inconsistent PPMS Modeling / No DVM Extractors avail. in EFWK Admin UI

The most important information for the setup of the DVM extractors is a consistent modeling of product and
product version assignments in your SAP Solution Manager system. Mainly there are two areas to be
checked in your SAP Solution Manager system which have to consistently reflect the product and product
version assignment, SMSY and the Solution Manager Diagnostics Landscape repository.
Often the symptom of not having any DVM extractors available in the Extractor Framework Administration UI
is related to an inconsistent modeling of products.
Independent of the design of your landscape repository (e.g. single SLD, cascading SLD scenario etc.) there
is an easy way of checking any inconsistent modeling:
There are two `tools` required: transaction SMSY and the System Browser. The following screenshots will
show how to double check if the product assignment is consistent.
Logon to your solution

manager diagnostic an
select the system
browsing tab on the left
hand side of the screen
Type in your system

name and select
“Search”. On the
results select the
ABAP-related entries
Compare this result

with the product
information in
transaction SMSY
45
Select the same

system as done in the
Solution Manager
Diagnostic screen.
Both product versions
have to match
In case there are different products assigned in SMSY and in the results of the landscape browser, the
solution is mainly to either change the product in SMSY or to re-run the SMD managed system setup wizard
again, in which you are chosing the corresponding product.
6.2 How to support product EHP x FOR SAP ERP 6.0

6.2.1 Solution Manager version  EhP1 SP5
As of Solution Manager version EhP1 SP5 (“SP21”) we do not require a manual configuration step in SMSY.
EHP x FOR SAP ERP 6.0 should be recognized as product version. In the Managed System Setup, EHP x
FOR SAP ERP 6.0 must be marked as “relevant for Diagnostics” and the setup must include the main
instances you want to manage with your SAP Solution Manager scenarios, such as the DVM Cockpit.
6.2.2 Solution Manager version < EhP1 SP5

EHP x FOR SAP ERP 6.0 is not directly supported by most SAP Solution manager applications but requires
a manual configuration step in SMSY: You need to assign SAP ERP 6.0 as an additional product version to
your EHP x FOR SAP ERP 6.0 system.
1. In SMSY, navigate to your EHP x FOR SAP ERP 6.0 system.

2. On the “Header Data” tab click “Installed Product Versions” and add product version SAP ERP 6.0.
Note that none of the product versions should be marked as “Leading product version”.
46
In the Managed System Setup, SAP ERP 6.0 must be marked as “relevant for Diagnostics” and the setup
must include the main instances of SAP ERP 6.0 which you want to manage with SAP Solution Manager
scenarios, such as the DVM Cockpit.
Additionally, for EHP 4 FOR SAP ERP 6.0/NW 7.01, EHP 5 FOR SAP ERP 6.0 or higher:
 In SMSY, select at least one main instance of EHP x FOR SAP ERP 6.0 that uses software
component SAP BASIS (for example ”ABAP Technology for ERP EHP4”).
 In the Managed System Setup, EHP x FOR SAP ERP 6.0 must be marked as “relevant for
Diagnostics” and the setup must include the main instance selected in SMSY as described in the
previous step (for example ”ABAP Technology for ERP EHP4”).
6.2.3 Additional information

E2E Root Cause Analysis applications like Change Analysis, Error Analysis or Workload Analysis are based
on main instances. For SAP ERP 6.0 the following main instances are supported meaning that content is
delivered with Solution Manager to manage these main instances with RCA applications:
 SAP ECC Server
 SAP SEM
 SAP SRM – Server
 SRM-MDM Catalog
 SAP NW – Business Intelligence
 SAP NW – Enterprise Portal
 SAP NW – Process Integration
 SAP NW – Adapter Engine J2EE
 SAP NW – Search and Classif. (TREX)
 SAP NW – Application Server Java
 SAP NW – BI Java
For a SAP ERP 6.0 system no manual configuration step in SMSY is required.
47
6.3 Manual Restarting of Extractors

In certain cases extractors fail due to technical reasons, such as RFC connection issues (user, password,
authorization etc.) or system parameterization (time out). Usually the extractor framework takes care of
triggering the extractor again, but this usually happens in the extractor specific frequency. Especially the
DVM extractors are often scheduled in a weekly or even monthly frequency. In the worst case the EFWK
would trigger a failed extractor a week or a month later.
For some of the DVM extractors there is a manual SE16 based expert approach available how to force the
EFWK to trigger a specific extractor again.
Important: The manual restart is not available for ALL kinds of extractors. There are different kinds of
extractors available using different concepts of data loading. One 'family' of extractors always performs a full
data load (e.g. the DB statistics for tables and indexes) others do a time slice dependent data selection and
hence follow a delta logic. The EFWK controls and records all time slices for which these extractors have
been scheduled and have delivered data already. Restarting these extractors manually would cause data
inconsitencies as it will lead to loading the same records multiple times into the BW infocubes, hence we
HIGHLY recommend to only perform these steps for extractors that do a full data selection. These
extractorsall have the same MAINEXTRACTOR interface (see below) which is called
E2E_ME_ST_API_ASYNC_NO_RR.
6.3.1 Determine failed extractor

You can determine which extractor is failing via the EFWK Administration UI (please refer to chapter
'Extractor Framework Setup'). Alternatively you can use the SE16 approach below. Please know that you
need to have SE16 and table change authorization in the SAP Solution Manager system.
 Call SE16 and check table E2E_EFWK_STATUS
 Restrict your search to the DVM extractors (field EXTRACTOR = *DVM*) that have a full data load
interface (hence they are not time slice and delta logic relevant -> only those extractors should be re-
triggered manually). Set the field MAINEXTRACTOR to E2E_ME_ST_API_ASYNC_NO_RR
 In the result list you will see the status overview of all DVM specific extractors
 The field message and RC are the most important ones to check for possible issues
 As an example we will now re-trigger the extractor DVM_EXTRACTOR_SIZES which loads the DB
statistics of tables and indexes
 Double click in the SE16 on the row containing the extractor DVM_EXTRACTOR_SIZES to see the
details of these data records
48
 Copy the WLI ID which is the unique ID for a specific extractor

 Open another SE16 screen and choose table E2E_ACTIVE_WLI
 Enter the WLI ID you have copied in the step before the last step and execute
 As a result you will see all the technical details of this single extractor instance
 Mark the single line and click on the EDIT button in SE16
 We will simply change the frequency of the extractor so that the EFWK will take care of triggering
this extractor in a higher frequency. The frequency is defined in the field DTRUN, the unit of this field
is in minutes. For the selected extractor the settings look as follows
49
 In our example the frequency is set to 10.080 minutes which is equivalent to a "one week"
frequency. Simply change the value to a lower one, such as 60 and save the new value. This will
force the EFWK to trigger the extractor in an hourly frequency. The first run is again calculated from
the last timestamp of the last execution of this extractor. This timestamp can be found in the table
E2E_EFWK_STATUS, fields TIMESTART and TIMESTOP.
 You should now have the chance to test the next executions of this extractor more often. If the
testing is completed, simply change the value of DTRUN for the relevant extractor back to the default
setting, the extractor framework will immediately consider the new value after you have saved it.
Please do not change any other value in this record as it can lead to data inconsistency or issues in the
EFWK
6.4 Identifying authorization issues (Alerting & saving potential

calculation)
A comfortable way to identify potential authorization issues and allocate those to the affected user is the
following 2-step approach-
The first step is to identify the system and the scheduled runtime of the DVM extractors. Therefore the table
DSWP_BPM_TIMESCH (on SAP Solution Manager) will be restricted to the relevant system and the DVM
related monitoring object for the saving potential analysis (BODVMANA) or the object name for the alerting
50
on BW queries (BOBIQUAC).
Note: Depending on your setup it might be that for searching the details for alerting on BW queries you need
to enter the system ID of the local SAP Solution Manager system.
The next runtime of the specifc collector in question is taken to restrict the selection of the following step
(SLG1).
The extractor runtime information in used to limit the selection of the application log data. Therefore call
trasnacation SLG1
51
In this example the external ID “DCOL” hints to a potential BW authorization problem of user “SM_BPMO”.
This is in that case the starting point for a further root cause analysis.
There are 3 more external ID‟s of interest for the setup of the DVM Cockpit:
• GENM: Configuration Generation
• DCTM: Configuration Deactivation
• ACTM: Configuration Activation
You will find further detailed information if problems with activation /deactivation have occurred.
7 Appendix 1: Example Queries and Dashboards

The following example Queries and Dashboards were created to give customers with less BW experience an
idea of the powerful capabilities the DVM Cockpit can provide. The selection is not meant to be complete and
can be expanded to cover the specific customer future needs.
The above mentioned BW Queries are restricted to the specific customer area in order to comply with the
demand of having specific Queries for specific organizational areas. This restriction is done via the
Characteristic “System ID” and the limitation to the customer – specific systems as they were connected to
the Solution manager in our example.
52
For other customer areas the suggestion is to modify the specific BW Queries and copy them a) into the
relevant name space and b) restrict the systems to the relevant area.
Nevertheless a concept should be created before any further activities in order to avoid unnecessary work
and to tailor the solution to the specific needs.
After the responsible person (DVM Champion) becomes familiar with the more generic DVM Cockpit
installation the next steps are to provide a customer specific training where customers have to provide
specific key figures, KPI‟s in terms of certain system thresholds. This information will be used to create
concept templates on the one hand and to configure the existing Cockpit installation to the specific needs on
the other hand.
The concept template could then be used to roll out the DVM Cockpit to other areas as mentioned above.
The same considerations need to be taken into account for the dashboards. As long as there is no working
concept the dashboard configuration made by SAP could only count as examples.
It is essential to gather information on how the customer intends to setup role and responsibilities. The major
question in this regards is “Who needs to see which content?”. The same approach as mentioned above is
relevant for the BW Query topic as well. The generic Dashboards can be used as a template to be adjusted
and rolled out to the different organizational areas.
7.1 Example queries per infoprovoder

In the following pages one Query per infoprovider is introduced and explained in detail including the
visualization of the output.
The naming convention for description and technical naming follow the concept of identifying the area where
the query is used for (e.g. DVM Saving Potential Archiving (0SM_TABLE_SAVING_POTENTIAL_ARC)).
7.1.1 DVM Age of Records & Potential (0SM_DVPOT)

DVM Saving Potential Archiving (0SM_TABLE_SAVING_POTENTIAL_ARC)
53
As you can see in the coloured boxes the information is used to construct the layout of the query. The circles
represen variables to pre-select the information. This will be visible when executing the query.
After execution the structure of the query builder will be filled with data and displayed in the same way as
shown above (refer to the coloured boxes)
Fields defined in “Free characteristics” are used to drill down to the specified information within the same
Query (refer to the fields listed in the red box above and below). This information is available when doing a
right-click in the executed query and selecting “Filter and drilldown according to”
54
7.1.2 DVM Archive Job Information (0SM_ARCHJ)

DVM Archive Job information (0SM_ARCH_JOB_INFO_Q0001)
As you can see in the coloured boxes the information is used to cunstruct the layout of the query. The circles
represent variables to pre-select the information. This will be visible when executing the query.
55
Query (refer to the fields listed in the red box aove and below). This information is available when doing a
56
7.1.3 DVM Archiving History (0SM_ARCHH)

Data Archiving Statistics per Object (0SM_ARCH_STAT_AOBJ)
As you can see in the coloured boxes the information is used to cunstruct the layout of the query. The circles
represent variables to pre-select the information. This will be visible when executing the query.
57
7.1.4 DVM Object Sizes (0SM_ SIZES)
DVM Top 10 DocType Growth – Monthly (0SM_DVM_TOP10_DOCTY_GROWTH_MON)
58
As you can see in the coloured boxes the information is used to cunstruct the layout of the query.
Top „n‟ condition are used to limit display of data to the relevant figure. This helps to improve performance
and to concentrate on the necessary information.
There are various posibilities to restrict a query by defining a condition. In the example below the “Top „N‟
limitation is being used.
59
60
8 Appendix 2: Linking Queries to Queries

Linking one Query to another could be helpful if you want to drilldown into further details based on a very
generic Query.
The example below provides the technical configuration steps. The used Queries are standard Queries and
available in BI Content 7.04.
The main transaction to link queries is RSBBS. The example is based on the “Top 30 Table Growths –
Monthly” Query. Based on this Query other Queries will be linked to the “Top 30 Table Growth – Monthly”
Query in order to provide further drill down possibilities within the MyHome Dashboard.
Entry point is transaction RSBBS. As a first task the “Header Query” needs to be assigned. In the example
here it is the “Top 30 Table Growth – Monthly”.
Queries can be selected via F4 Help
61
The report type needs to be set to “BW BEx Query” and the first Query you want to link to the “Header
Query” needs to be selected via the F4 Help of section
Select the relevant Query and click on This step has to be repeated for each Query you want
to link to your “Header Query”.
Also for each of the assigned Queries you have to complete the following steps: Mark the relevant Query and
click on
Identify the relevant info objects and assign as Type “Info Object”, choose the relevant fieldname out of the
F4 Help list. Assign as “Selection Type” Single Value” and flag the field “Required”.
62
After you have saved the settings the result can be seen in your DVM Dashboard as follows:
With a right mouse – click on the table name the detailed menu opens. Navigating via “Goto” will show the
linked Queries
Clicking on one of the queries shown in the menu opens another (separate) explorer window
63
64

DVM Cockpit Juni2010

Hochgeladen von

Dokumentinformationen

Originalbeschreibung:

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

DVM Cockpit Juni2010

Hochgeladen von

Copyright:

Verfügbare Formate

.

Data Volume Management Cockpit

Establish a Centralized Information Cockpit for

Get Transparency on Landscape’s Data

Detect biggest ‚Consumer‘ of data

Reveal Potential for Creating / Optimizing

‘Simulate’ different Data Volume Scenarios

Enable automatic Compliance Checks of

© SAP AG 2009. All rights reserved. / Page 5

Figure 1: DVM Cockpit Use Cases

1.1 Architecture Overview

Data Volume Management Cockpit

SAP Solution Manager

Extractors SCM CRM ERP …

Figure 2: Architecture Overview

From an integration perspective the DVM Cockpit is to be considered as a „Cross Application‟

Data Volume Management Cockpit

Managed Systems Solution Manager Persistence Layer Applications

Figure 3: Extractor Framework

2.1 Technical Prerequisites

1. SAP Note 1159758 - Data Volume Management: Central Preparation Note

2. Note 1233709 - Prerequisites for Data Volume Cockpit (DVM Cockpit)

3. SAP Note 521820 - Availability of BusinessProcessMonitoring

4. SAP Note 784752 - BPMon in SAP Solution Manager - Prerequisites

5. SAP Note 1172948 - SAP Solution Manager - Basic functions

6. SAP Note 1365123 - SMD Agent Strategy

7. SAP Note 1234387 - SMD Agent Installation

8. General SMD documentation

2.2 Organizational Readiness

Role name Description

3.2 SMSY Connectivity

Figure 3: Check existing RFC connections in SMSY

3.3 Technical Readiness Check - SAP Notes (RTCCTOOL)

Next, click the

Check the “Prepare for

Typical results of the

4 Installation & Configuration

4.1.1 Diagnostics Setup - SMD Agent Setup

In the left pane under

Following this, select

Then click on Setup

Select the Diagnostics

Provide all relevant

Following this, return to

Then click on Setup

Then locate the system

Note that both the

Then select the

Finally, hit the Set

4.2 SAP Netweaver Business Warehouse Preparation

Look for the SAP

The default selection

The BI Content for

Following this, choose

In the above case, the

4.3 Extractor Framework Setup

In the Solution Manager

Click on Extractor FWK

Then select the Managed

Select the relevant system

Use the option and

Multiple selections are

Be sure to activate all DVM