Effective SAP BW System Management - Webinar Webinar Powerpoint

Know-How Network: Effective
SAP BW System Management

Ron Silberstein
Technologist & Architect
SAP NetWeaver Regional Implementation Group
SAP Labs, LLC
Agenda
Overview
Process Chains
n Key Concepts
n Implementation
System Monitoring
Data Management
Capacity Planning
Summary
SAP AG 2004, SAP TechEd / BW 201 / 2
Learning Objectives
As a result of this workshop, you will

be able to:
n Understand key concepts of BW system management
n Develop enhanced strategies for effective BW system
management
n Incorporate best practices into BW system management
procedures
Agenda
Overview
Process Chains
n Key Concepts
n Implementation
System Monitoring
Data Management
Capacity Planning
Summary
Characteristics of Effective SAP BW System Management

Collaborative efforts: technical and functional
team members
Exploit all advantages of process chains:
automate all key system activities
Proactive monitoring: Utilize the available tools
to their potential, optimize accordingly
Data management: Consistently delete
temporary data, summarize, consolidate and
reduce data volume; minimize object sizes
Plan for growth: Sound capacity planning
ensures system sizing and resource
allocation is commensurate with user load
and data volume growth rates
Service excellence: Vigilance in providing
strong and performant SAP BW production
environment AND attentively support
ongoing development phases, ensuring
quality via change management process
Ongoing Maintenance and Optimization Efforts
Monitoring and System Management
Tactical Tuning
Resource Allocation
Track Concerns
Manage Data Volume
Evaluation
Identify Bottlenecks
Coordinate Effort
Scheduling
Performance Tuning and Optimization
Agenda
Overview
Process Chains
n Key Concepts
n Implementation
System Monitoring
Data Management
Capacity Planning
Summary
Process Chains Motivation & Key Functionality

Automation of key SAP BW operational activities: data load
and other tasks (ie compression, aggregate rollup, reporting agent)
These activities may require a significant administrator effort,
without using process chains, risks include:
Inefficient utilization of BW and basis teams time
Possibility of missed activities, , human error
Limited monitoring capabilities
Some Important Process Chains Features:

Graphical modelling: build a control flow of tasks to be executed
in a defined sequence
Central monitoring of SAP BW operational activities

Ability to Create and implement a custom process type:
powerful!
Openness: Interface for Job Scheduling for SAP BW (Integration
scenario to process chains for certified partners)
Process Chains Concepts: Typical Data Load Cycle

Other Monitors
Change Run (MD activation)
Data Load
Monitor
Load Master Data

Data loaded
into ODS
Object
Start
Activate ODS
Object data
Data Mining
Jobs
Reporting
Agent Jobs
Roll up
Aggregates
Data loaded into

InfoCube
Concept Example: Building a process control flow

Start
Load
Master Data
Failure Success
Perform change run
(master data activation)
Email
System
Admin
Activate
Master Data
Failure
Load 3 InfoPackages
concurrently into 1 InfoCube
Email
System
Admin
IC Data
Load 1
Failure
Email
System
Admin
Success
IC Data
Load 2
IC Data
Load 3
Success off all 3?
Rollup
Aggregates
Failure
Email
System
Admin
Process Chains Graphical Modeling and Monitoring

e rs
v
i
l
de
P
SA
ny
a
s!
m
e
p
ty
s
s
ce
o
r
p
Process Chains: Log View (aka Monitoring View) - RSPC
Process in Green shows a

successful completion
Processes in Red
indicate a failure
Processes in Grey have

yet to be executed
Note: CCMS has an overview
of process chain successes
and failures
Third-Party Scheduling & Monitoring Tools BW-Certified

Certified scheduling/monitoring tools
offering integration with process chains:
CA
BMC (Control-M)
CA (Unicenter job mgmt adapter)
TIDAL (Enterprise Scheduler)
UC4 (UC4 Global)
ORSYP (Dollar Universe)
Redwood (Europe) (Cronacle)
Agenda
Overview
Process Chains
n Key Concepts
n Implementation
System Monitoring
Data Management
Capacity Planning
Summary
Project planning and project organization

Project planning
Process chains should be designed after modelling data flows but
during the realization phase
Use the final preparation phase of your project to test your process
chains for performance, correctness and robustness
Project
Preparation
Business
Blueprint
Realization
Final
Preparation
Go Live &
Support
Continuous
Improvement
Project organization
Team members must be able to use process chains, but also need
knowledge about:
Data warehouse administration
Single process types used in process chains
If several project teams build process chains in the same system, a
central documentation process is critical
How to start process overview

Collect all processes that have to run before data can be released
to end user
Data Loading processes
Administration processes
?
t
ha
W
Reporting Agent processes
Define time windows for process chains

Requirements on data availability from business
?
n
e
h
W
Contact basis administration team for information on jobs in source

systems that have to run before data loading
?
Define dependencies and priorities
w
o
H
Define whether one or several predecessors processes have to run

before a single process can start
Define whether a single process has to run when the process chain is
executed or whether failures can be (temporarily) accepted
Example on process overview

Collect all relevant processes in a central document to prepare
modelling of process chains
*
Reporting
Scenario,
for example
Sales
statistics
possible additional fields:

* Not always necessary, sometimes needed as of different time zones or
different source data availability in one source system
Aspects of using process chain hierarchies

Complexity of a single chain (number of processes) should be
reasonable
One process chain for everything approach could create
(unwanted) cross dependencies between processes
Benefits on using process chain

hierarchies (sub chains)
Better visualization of dependencies
Enhanced administration capabilities
(e.g. Restarting of single sub chain)
Maximum number of process chain hierarchy levels: 2 3
(recommendation)
Common SAP BW Tasks: Process Chain Automation

Strongly Recommended
Highly Recommended
Data Load (all kinds)
Reporting Agent: OLAP Cache
ODS Object Activation
Reporting Agent: Pre-calculated

Templates
Aggregate Rollup
InfoCube Compression
Reporting Agent: Exceptions &

Conditions
DB statistics (RDBMS dependent)
Master Data Reorganization
Change Run
Local Process Chain
PSA Deletion
Other tasks, such as export of data
via Open Hub, should be utilized as
needed.
Agenda
Overview
Process Chains
n Key Concepts
n Implementation
System Monitoring
Data Management
Capacity Planning
Summary
Some Important Monitoring Tools
Scenario
n Generally slow query or data load performance (systemic)
n Look for CPU utilization bottlenecks
n If adequate CPU time is available, check other factors
What can you check?
n Operating system (ST06)
n Database Information (DB02)
n Database monitor (ST04)
n Analysis of BW objects (RSRV)
n Performance Analysis (ST03, BW Statistic Business Content)
n Computer Center Management System (BWCCMS)
n Memory Management (ST02)
Monitoring Tools: Operating System Monitor (ST06)
Useful Key Figures

n Current Values (snapshots) and history (previous hours)
u CPU
u Memory
u Swap
Check following parameter values:

n CPU utilization
n Free memory
n Also check SM50 for process bottlenecks
Monitoring Tools: Database Monitor (DB02)

Utilization
n General DB Monitor
n Check for missing indices
Useful Features
n Missing indices
n Table and Index extent growth (non-local
tablespaces, RDBMS dependent)
n Monitor tablespace allocation
Tools: Analysis and Repair of BW Objects (RSRV)

Utilization
Many various analyses of InfoCubes and master data
Useful Features
n Database
u DB
statistics for an InfoCube and its aggregates
u DB
indices for an InfoCube and its aggregates

u DB parameter settings check
u DB
Information about InfoProvider tables
l InfoCube: Relative size of dimension tables compared to fact table
n Repair feature
Check following parameter values:
n Ensure DB statistics are up-to-date for an InfoCube
n Ensure indices exist for InfoCube
n Check for unbalanced InfoCubes
u(dimension table size 10% or more compared to fact table size)
SAP BW Reporting Performance Analysis Tools
BW Statistics
Business Content
SAP BW Workload Analysis

ST03
Tip: Build a monitoring cockpit using BW statistics content,

custom query and BW web applications
Monitoring Tools: ST03 - Drill Down to Query

Highest contributor in
Total Run Time per
InfoCube
High % DB
Time
Double Click
No of
runs
Highest
DB time
Drill down check if there is any single query that could be the major
contributor. Where is the major contribution coming from?
Example shows an active query, high DB time, with low OLAP & frontend time.
Low
Front-end
time
System-wide monitoring with BWCCMS

The Computing Center Management System
is part of SAPs technolgy platform.
CCMS is SAPs open, integrated infrastructure
for:
n Centrally monitoring SAP landscapes
comprising:
u
Components based on SAP Web Application

Server, or SAP Basis Release as of 3.0
Other SAP components

u Non-SAP components
n Background and print processing

n New with BW Release 3.52:
n History data of the Central Performance
History (CPH) can be transferred to SAP
BW for efficient analysis
SAP Solution Manager: Central System Administration

Task
n Central administration of systems
in one SAP solution
Solution
n SAP Solution Manager, Central Monitoring
feature
Benefits
n Automated support of periodic and sporadic
administration tasks
n Time savings due to central access to
administered systems
n Automated logging of activities
n Reporting across the whole solution
SolMan System & Solution Monitoring Data Collection

SAP Solution
Manager
Detailed
Reporting
SAP
EarlyWatch
Alerts
System Monitoring
Satellite
Systems
Real-time Monitoring:
CCMS Monitoring
Infrastructure (RZ20)
Continous Monitoring:
Service Data Download
(SDCC)
Solution Manager System Monitoring Workflow

Alert graphics
n System monitoring of core components

to detect critical situations as early as
possible
n Support administrators working with
new SAP products
n System monitoring and Central System
Administration complement each other
System-related
tasks with
integrated and
automated log
Expert monitors
directly linked in
satellite systems
Solution Manager Monitoring: Integration of 3rd-Party Tools

Solution
Monitoring
SAP Solution Manager

Trigger console
in case of an alert
(SAPConnect;
SNMP; XML)
3rd-Party
System
Management
Console
Detailed Analysis
with 3rd-party tools
Monitoring
Infrastructure
CCMS Monitoring
Infrastructure (RZ20)
Report Alerts
Monitoring
Agent
Solution
Landscape
3rd-Party
Components
Agenda
Overview
Process Chains
n Key Concepts
n Implementation
System Monitoring
Data Management
Capacity Planning
Summary
What about your Data Volume growth?

700.00
Expected size
without Archiving
600.00
Allocated DB size
500.00
400.00
Allocated DB content
300.00
01.09.2003
01.08.2003
01.07.2003
01.06.2003
01.05.2003
01.04.2003
01.03.2003
01.12.2002
01.11.2002
01.10.2002
01.09.2002
DB growth: ~7 GB/month
01.08.2002
01.07.2002
01.06.2002
01.05.2002
01.04.2002
0.00
DB growth:
Reduction:
~15 GB/month
~60GB
01.03.2002
100.00
With regular archiving
01.02.2003
200.00
Initial
Archiving
01.01.2003
'Without'
Archiving
Distribution of the memory costs

Hard disk costs do not even represent a quarter of the memory costs
(Giga Information Group)
Misc
(Purchasing,
training)
10%
Personel
Hard disk
45%
23%
Environment
(Electricity, Space)
3%
StorageMangement
(Soft- & Hardware)
19%
Administrative expense for 1 Terabyte of memory are appropriate for five

to seven times more higher than the memory costs themselves
(Dataquest/Gartner)
Data Aging Strategy Implementation

Data aging is a strategy for managing data over time, balancing
data access requirements with TCO.
n Each data aging Strategy is uniquely determined by the customers
data and the business value of accessing the data.
Which tools should I consider to use when?

Online Database
Storage
Near line
Storage
Frequently read
/updated data
Infrequently
read data
Very rarely
read data
BW data
archiving
Data Volume Minimization Strategies

PSA Deletion: Temporary inbound data load layer, exists
for recovery or reload purposes.
l Retain daily loads 1 week, monthly retain 60 days
l Customer example: DB growing at 450 GB/month
without PSA deletion, 150 GB/month with deletion
ODS Object Change Log Deletion: Its like a PSA.

l Optimize ODS Object activation performance
Caution: Do not delete if ODS Object generates delta for

the next level!
Data Consolidation: Eliminate redundant data

l Merge data from similar data marts
l Optimize aggregates
l Consider carefully number of ODS Object and InfoCube
levels; aggressively archive and delete from Data
warehouse layer
l Summarize at the InfoCube and aggregate level (RRI)
Remote Access: Use RRI, Virtual InfoProviders, UDI, etc:

operational processing possibly might remain in OLTP
system
Agenda
Overview
Process Chains
n Key Concepts
n Implementation
System Monitoring
Data Management
Capacity Planning
Summary
Multi-Tier Architecture & System Landscape
Architecture of SAP basis system supports multi-user

environment: If number of concurrent users grows
significantly, you can add more application servers
Scalability via multiple

application servers
SAP BW CPU Sizing Approach (Quicksizer)
~ 10%
Authors &
Analysts
high
Assumptions and Findings:
Analytical
Complexity
One navigation in BW (drill-down, filter, etc.) =

~9 dialog steps
Author
~ 30%
A medium type query is1.5x the load on the DB

server as an easy query
Knowledge
Workers
Analyst
A heavy query exerts 5 times the load on the

DB server as an easy query
~ 70%
Information
Consumers
Low
Users of a specific category do not only run

queries of the corresponding category
Query Type: Distribution Assumptions

User category
Consumer
Easy
Medium
Heavy
Information
Consumers
90%
10%
0%
Knowledge
Workers
50%
50%
0%
Authors &
Analysts
0%
10%
90%
Sizing and Re-sizing: Preparing for New Project Phases
SAP recommends to work closely with the hardware

vendors to ensure your system is sized properly
Quicksizer: SAP-delivered tool for estimating hardware
sizing requirements
n Only useful in conjunction with HW vendor assistance
Estimates of concurrent user load and data volume, if

obtained at project startup, may not be sufficient for future
project phased implementations!
Recommendations: If project scope changes significantly
(in terms of expected data volume or number of concurrent
users), conduct a capacity planning session where sizing
estimates are revisited
n
n
n
n
Work with business owners to get realistic user numbers

Analyze to estimate potential data volume
Use the Quicksizer in re-sizing
Work with hardware vendors
Summary
n
Use process chains heavily to automate and monitor critical

and important system tasks
Build process chain development into project plan, organize

effort around comprehensive BW administration strategy
Good use of available tools for system monitoring can help

ensure a smooth running system and good performance
Best practices for data management entails deleting PSA data

regularly, active capacity planning, use of archiving and
consideration of near-line storage option
Effective collaboration between technical and functional team

members is necessary for successful BW system management
Further Information
Public Web:
http://www.sap.com > Solutions > NetWeaver
SAP Online Help:

http://help.sap.com > NetWeaver > BI
SAP Service Marketplace:

http://service.sap.com/bw
l BW InfoIndex Process Chains
l BW InfoIndex Archiving
l BW InfoIndex BW Statistics
l Partner Certified Software Partners
www.service.sap.com/education
l BW360 BW Administration & Performance (5 days)
SAP Developer Network

http://www.sdn.sap.com > Business
information Warehouse
Questions?
Q&A
Copyright 2004 SAP AG. All Rights Reserved

n No part of this publication may be reproduced or transmitted in any form or for any purpose without the express
permission of SAP AG. The information contained herein may be changed without prior notice.
n Some software products marketed by SAP AG and its distributors contain proprietary software components of other
software vendors.
n Microsoft, Windows, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation.
n IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iSeries,
pSeries, xSeries, zSeries, z/OS, AFP, Intelligent Miner, WebSphere, Netfinity, Tivoli, and Informix are trademarks or
registered trademarks of IBM Corporation in the United States and/or other countries.
n Oracle is a registered trademark of Oracle Corporation.
n UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.
n Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered
trademarks of Citrix Systems, Inc.

n HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C, World Wide Web Consortium,
Massachusetts Institute of Technology.

n Java is a registered trademark of Sun Microsystems, Inc.
n JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and
implemented by Netscape.
n MaxDB is a trademark of MySQL AB, Sweden.
n SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver and other SAP products and services mentioned herein
as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and in several other
countries all over the world. All other product and service names mentioned are the trademarks of their respective
companies. Data contained in this document serves informational purposes only. National product specifications may vary.
n These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated
companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP Group
shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and
services are those that are set forth in the express warranty statements accompanying such products and services, if any.
Nothing herein should be construed as constituting an additional warranty.

Effective SAP BW System Management - Webinar Webinar Powerpoint

Uploaded by

Copyright:

Available Formats

You might also like

Effective SAP BW System Management - Webinar Webinar Powerpoint

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Effective SAP BW System Management - Webinar Webinar Powerpoint

Uploaded by

Copyright:

Available Formats

Know-How Network: Effective

SAP BW System Management

SAP AG 2004, SAP TechEd / BW 201 / 2

As a result of this workshop, you will

SAP AG 2004, SAP TechEd / BW 201 / 3

SAP AG 2004, SAP TechEd / BW 201 / 4

Characteristics of Effective SAP BW System Management

Ongoing Maintenance and Optimization Efforts

Monitoring and System Management

Performance Tuning and Optimization

SAP AG 2004, SAP TechEd / BW 201 / 6

SAP AG 2004, SAP TechEd / BW 201 / 7

Process Chains Motivation & Key Functionality

Some Important Process Chains Features:

Central monitoring of SAP BW operational activities

Process Chains Concepts: Typical Data Load Cycle

Change Run (MD activation)

Load Master Data

Data loaded into

Concept Example: Building a process control flow

Success off all 3?

Process Chains Graphical Modeling and Monitoring

SAP AG 2004, SAP TechEd / BW 201 / 11

Process Chains: Log View (aka Monitoring View) - RSPC

Process in Green shows a

Processes in Grey have

Third-Party Scheduling & Monitoring Tools BW-Certified

SAP AG 2004, SAP TechEd / BW 201 / 14

Project planning and project organization

How to start process overview

Reporting Agent processes

Define time windows for process chains

Contact basis administration team for information on jobs in source

Define dependencies and priorities

Define whether one or several predecessors processes have to run

SAP AG 2004, SAP TechEd / BW 201 / 16

Example on process overview

possible additional fields:

Aspects of using process chain hierarchies

Benefits on using process chain

Maximum number of process chain hierarchy levels: 2 3

Common SAP BW Tasks: Process Chain Automation

Data Load (all kinds)

Reporting Agent: OLAP Cache

ODS Object Activation

Reporting Agent: Pre-calculated

Reporting Agent: Exceptions &

DB statistics (RDBMS dependent)

Master Data Reorganization

Local Process Chain

SAP AG 2004, SAP TechEd / BW 201 / 19

SAP AG 2004, SAP TechEd / BW 201 / 20

Some Important Monitoring Tools

Monitoring Tools: Operating System Monitor (ST06)

Useful Key Figures

Check following parameter values:

SAP AG 2004, SAP TechEd / BW 201 / 22

Monitoring Tools: Database Monitor (DB02)

SAP AG 2004, SAP TechEd / BW 201 / 23