An A-Z Guide to

Planning, Managing,
and Executing a Global
SAP NetWeaver BI
Project (Part 2)

Dr. Bjarne Berg

2007 Wellesley Information Services. All rights reserved.

What Weve Discussed So Far in Part 1

Writing your global SAP NetWeaver BI business case

Defining the global scope of your implementation
Writing a milestone plan
Developing your global staffing plan
Budgeting
Comprehensive on-boarding and training
Writing your work plan
Monitoring the progress and risks of your global project
Monitoring quality and instituting a formal approval process
Why you need an SAP NetWeaver BI user acceptance
group

2
What Well Discuss in Part 2

Final preparatory steps

Methodology details
SAP NetWeaver BI global lessons learned
Requirements and approvals
The Blueprinting phase
The Realization phase
The Implementation phase

Source: SAP

3
What Well Cover

Final preparatory steps

Blueprinting phase
Realization phase
Implementation phase
Wrap-up

4
Final Preparatory Steps

Methodology details
SAP NetWeaver BI global lessons learned
Requirements and approvals

5
 Project Preparation: Some Key Observations

Project
Projectcharter:
charter:Represents
Representsananagreement
agreement
on,
on,and
andcommitment
commitmentto,
to,the
thedeliverables
deliverablesofofthe
the
project,
project,as
aswell
wellas
asproject
projecttime
timeconstraints,
constraints,
resources,
resources,standards,
standards,and
andbudget.
budget.

Project
Projectplan:
plan:This
Thisis
isthe
thefirst
firstcut.
cut.ItIt
focuses
focusesononmilestones
milestonesand
andwork
work
Source: SAP
packages.
packages.
Scope:
Scope:Sets
Setsthe
theinitial
initialdefinition
definitionofofthe
theproject.
project.
Core Activities
1.1 Initial Project Planning Project
Projectteam
teamorganization:
organization:Sets
Setsthe
thewho
whoofof
1.2 Project Procedures the
theproject.
project.This
Thisdecides
decideswho
whowill
willbe
beinvolved,
involved,
and
andwhat
whattheir
theirgoal
goalis.
is.
1.3 Training Preparation
1.4 Project Kickoff
Standards
Standardsand andprocedures:
procedures:Sets
Setsthe
thewhy
why
1.5 Technical Requirements Planning and
andhow
howofofthe
theproject.
project.Standardizes
Standardizeshow
how
1.6 Quality Check Project meetings
meetingsarearerun,
run,how
howdocuments
documentsarearehandled,
handled,
Preparation etc.,
etc.,so
soeveryone
everyoneunderstands
understandswhat
whatisis
going
goingon.
on.
Source: Pauline Woods-Wilson
This is what we covered in Part 1.
6
Note
What is ASAP?

Examples for Accelerators:

Project Plan, Estimating
Fill
Fillin
inthe
theBlank
Blank
Design Strategies, Scope Definition vs.
Versus
Documentation, Issues DB Start
Start fromScratch
from Scratch
Workshop Agenda
Questionnaires
End-User Procedures
Test Plans
Technical Procedures
Made Easy guidebooks (printout, data transfer, system
administration)

Source: SAP 7
The ASAP Approach (from Part 1)

Integration
Testing
Create Technical
Specs
Create Functional No

Specs System Testing

Complete?
No
Yes

Complete? Unit Testing

Yes

Yes Configuration
Peer Review
No
Approved? Peer Review
Yes

No
Approved?

Yes Structured
Complete?
Walk-through
No
No Yes Structured
Complete?
Walk-through 8
Alternative Approach for Smaller Projects (Such As First Go-
Live)
Keep the scope focused and use a simple approach

Activate Request for Make

In-
standard modifications Yes enhancements
scope?
content
No

User
Load InfoCube acceptance Test
In-future
session
scope?

No

Review data Create 2 - 3 Deploy

quality issues sample queries

Rejection

No functional or technical specs are used in this approach.

The user acceptance session is used to refine requirements. 9
 Critical Success Factors for Global SAP NetWeaver BI Projects

Individual Organizational Technological Methodology

The best people End users on the team Platform sizing Proper scope

Backfilling Communication with Testing tools Leadership and

users commitment

Few locations
Documentation and Integration testing Budget for
(keep it focused and
training internal before releasing consulting and
have many rollouts) changes training

Good SAP Breadth and depth Do not modify code Overseas contacts
consultants of training

Source: Lee Schlenker

These are lessons learned the hard way.

Dont re-invent the wheel learn from others.
Note
10
 SAP Solution Manager

Upgrade Projects New in Change Request

Management
2004
e-Learning Landscape Reporting

Test Organizer Support Desk

Customizing
Synchronization Tool Solution Monitoring

Implementation Service Level

Platform Reporting

Implementation
Content Services
Content
Best Practice
Roadmaps
Documents

Service Delivery Gateway to SAP SAP Support

Platform

Added in 2004
Source: SAP AG
11
 SAP NetWeaver BI Best Practices Some Hints
This tool is still being
enhanced, but has
several SAP
NetWeaver BI-
specific project
accelerators that you
wont find in SAP
Solution Manager.
It has been available
since March 2003.
The current release
is as of August
2007 (v1.7).

You can access SAP Best Practices for BI at

http://help.sap.com/bp_biv170/index.htm 12
Option Work Plans Based on Deliverables

The best practice documents are organized around

scenarios, which simplify the collection of tools

Source: SAP Aug, 2007

13
 SAP Best Practices for BI What Versions Does It Support?
SAP NetWeaver BI 7.0

The SAP Best

Practices tool was
developed for SAP BW
3.5, and later updated for
SAP NetWeaver BI 7.0
SAP BW 3.5

Source: SAP Jan, 2007

While
Whileinstall
installrecommendations
recommendationsarearebased
basedononSAP
SAPBW
BW3.5
3.5ororSAP
SAPNetWeaver
NetWeaverBI BI7.0,
7.0,
most
mostmanagement
managementtools,
tools,accelerators,
accelerators,and
andthe
thesample
samplework
workplan
planare
arenot
notversion-
version- 14
Rapid Application Development (RAD)

Be flexible and consider using a RAD approach for the

initial information requirements gathering task. Typical ways
to conduct this include:
Ask for one to two days of uninterrupted time at each location, and
provide lunch on-site (global requirements gathering takes two to
three times longer plan for it).
Invite power users, casual users, todays report writers,
and managers.
Remove cell phones, PDAs, pagers, and email access.

Keep a rapid pace and a manageable group size (no more than
20).
Focus on shared information needs, and conduct multiple sessions
if needed.
Don't get trapped in details; give people a chance to provide

Youfeedback in writing
can use the sessionand follow-up
as an latersharing
information with individuals.
event, and give
a brief overview of what you are attempting to do. 15
What Well Cover

Final preparatory steps

Blueprinting phase
Realization phase
Implementation phase
Wrap-up

16
Blueprinting Phase

Global case studies

Leveraging the standard content
Modeling your solution
Deliverables

17
Lets Look at a Global BI Project Example

A case study

Fortune 100 company with operations around the world

230 systems identified as mission critical
23 installations of SAP R/3 on six continents
Other ERP systems:
JD Edwards
Custom-developed Oracle systems

18
 Global Data Warehouse Initiatives

A case study

These were the data warehouse

initiatives that corporate HQ knew about 19
 Rationale for a Bottom-Up Global SAP NetWeaver BI Approach

Improved Project Improved Cost Secured Commonality Leveraged SAP

Management Efficiency across Company Decision Support

Enables future Minimizes local invest- Ensures use of Provides users with a
migration of ments through a common definitions. fast way to integrate
standardized data consolidated hardware ERP reporting to
architecture to a Global environment. advanced stand-
Ensures uniformity
DSS architecture ardized decision
through eliminating
through standard local support systems
Leverages buying options to develop
solutions. through simplifying the
power in front of regional, functional or
vendors through pro- non-standard roll-out of SAP BW
Ensures higher quality vision of guidelines solutions. Enables the inclusion
of local deliveries and and corporate of future SAP-based
projects through agreements. standard decision
Provides centralized support modules
increasing focus on
testing of vendor
providing local (SEM, EC and others).
solutions. Enables lower software
development costs
through centralized Reduces delivery time
Establishes a better user documentation of decision support for
Using ONE SAP R/3 through
working environment and training.
methodology - one
between local units and usage of a
way of working. standardized
central project
management through Substantially reduces application.
the positioning as a ABAP report
Ensure reusability.
Competency Center for programming costs
Local Needs. through providing Creates a
support for an efficient Reusability will ensure Competence Center
A case study SAP BW roll-out. commonality! for SAP BW.
20
 Global SAP BI Activities, Priorities, and Architecture

4. Migrate existing solutions into company

3. After local solutions are implemented and architecture
standardized, consolidation to a Global
Data Warehouse (DW) is simplified
5. Install SAP BW-based
and faster
solutions (SEM, EC & consolidated BW)
2. Coordinate development Global DW for business and financial
efforts and activities: management together with
- Tool selection Shared Financial Services
- Methodology
- Organization DW
SAP
SAP SAP
SAP
DW BW BW
BW
- Deliverables BW

- Data standards 1. Test, productify

- Training SAP BW and
- Documentation install standard
solution(s) locally:
Local Local Loca SAP SAP SAP - Software
DW DW l
DW BW BW BW
- Hardware
- Testing
- Training
Oracle Oracle Oracle
Sybase Sybase Sybase SAP SAP SAP - Documentation
MVS MVS MVS R/3 R/3 R/3
Others Others Others
A case study
21
 An Approach to BI Global Architecture Development

Business Information Supply Chain

SAP
SAP NetWeaver
Business Warehouse
BI
(BISC) Responsibilities
BISC would take the responsibility for product -
fying and installing SAP NetWeaver BI standard
solutions locally, including software, hardware,
testing, training and documentation.

BISC could support SAP NetWeaver BI-based

Global DW
solutions for business & financial management
SEM, EC, and consolidated BI together with
Shared Financial Service Center etc).
SAP SAP
DW
BW BW Local Data Warehouses

BISC coordinates development efforts and

activities within the Data Warehousing field at
company. This includes guidelines on tool
Local
Local
DW
Local
DW DW
SAP
BW
SAP
BW
SAP
BW
selection, methodology, organization,
deliverables, data standards, training and
documentation.
Oracle Oracle Oracle
Sybase Sybase Sybase SAP SAP SAP
MVS MVS MVS R/3 R/3 R/3 Global Data Warehouse
Others Others Others

BISC has the overall responsibility to establish

the Global DW within company, which is
achieved through prioritizing development of
consistent local DW solutions enabling our long22
term goals.
 SAP NetWeaver BI Global Rollout Approach

The project delivered local SAP

Bottom-Up NetWeaver BI solutions and
HANGE
CHANGE

Fixed Departure packaged solutions for decision

Departure I - 3 months
Departure II - 3 months
A fixed departure approach
Departure III - 3 months
Departure IV - 3 months
A case study
support as a first priority,
and the global DW as a
second priority
was applied with focus on
delivering solutions rather than
projects and software
Specific BI solutions were
developed according to a pre-
defined schedule where local
business units were invited or
encouraged to participate
23
 A Global Rollout Different European Example

UK

North West (Den Haag)

Local
Local BW
Ireland others
AMC/Dev
AMC/Dev
Spiridon
Spiridon
Spiridon CRM
CRM (one client)
/CRM
/CRM Others
Switzerland

Netherland Global
s Development Mid South (Wien)
Spiridon/CRM
Local BW
AMC/Dev
e.p@ss
e.p@ss CRM
BW
Others /CRM

Austria Turkey
South West (Madrid)

Local BW
Belgium
Portugal AMC/Dev
Spiridon
Spiridon CRM
/CRM

Spain
Source: Siemens Corp information 2004

In this case, the company created both a local

and global BI system for CRM data 24
Some Lessons Learned from Other Global Implementations

Very large Global oil co. Global oil co. Fortune-500

global telecom co. retailer
BW version 3.1c 3.1c 3.0b 3.2
5 - 20 million Largest cubes have 18.8 35 million rows 120 million records in
transactional records million, 18.4 million, and sales, and 230 GB in
Largest
in FI cubes 11.2 million records sales and finance
volume
each.
Keep scope and Should not have gone Data movement is Custom coding cannot
development effort live on 1.2a, should the most complex overcome the BW
focused, use more have used more than part of BW. The extractors. Integration
Lessons than one one presentation tool. project would not with non-SAP R/3 data
presentation tool, The extract and load have accepted as was technically easy, but
learned
dont underestimate process is the most many enhancements conceptually hard.
the extract and load complex, strong BW if done again. The team members must
effort experience is essential You need a really have solid BI skills
strong BI architect
Standardized global Creation of corporate SAP R/3 was being Custom global reporting
reporting enterprise-wide data installed, and SAP has a too-high cost
Business warehouse BW is the reporting of ownership and is too
drivers strategy for all key hard to manage. Want
performance content and features.
indicators
Very happy with Overall happy. Have Is being rolled out to Very happy with the
implementation accomplished in six more subsidiaries speed of delivery and
Success
added three more months what would and management is user satisfaction
countries last year have taken five years. pleased with results

The major findings highlight the need for specialized

Note BW skills and very strong scope control. 25
Global Examples Summary

A conceptual architecture is the first

step, of which the physical architecture
is
a product
It should be driven by the user needs and
the types of interfaces needed not by an
internal IT exercise
You can now use SAP NetWeaver BI as
an enterprise data warehouse and
accomplish a global rollout
The two core ways to succeed require
both strong central control and support

26
 A Process Look at Getting Functional Specifications

Create a contact Create a tool to Gather Disposition Consolidate Build storage Construct
group and contact collect info information the info. requirements objects and reports and
list for business requests and using the requests to and write load programs navigation
input and business input tool & plan BI or SAP functional features
requirements traveling R/3 specs
Name Organization Phone Number
JoeJones MYORG Ltd 918-123-1234
JosephJones YourORG Ltd 918-123-1234
JoeJones MYORG Ltd 123-123-1234
JoeJones MYORG Ltd 918-123-1234
JoeJones MYORG Ltd 918-123-1238
JosephJones YourORG Ltd 918-123-1239
JoeJones MYORG Ltd 918-123-1234
JoeJones MYORG Ltd 918-123-1234
JoeJones MYORG Ltd 918-123-1234
JosephJones YourORG Ltd 918-123-1234
JoeJones MYORG Ltd 918-123-1234
JosephJones YourORG Ltd 918-123-1234
JoeJones MYORG Ltd 123-123-1234

More than one way is available to collect this information. However, a

Don't formal process should exist to capture requirements and communicate what
Forget is
being developed.

We will now examine the most common form of RAD.

27
 Getting the Global Functional Specifications

Avoid taking a total inventory of all reports in the global

organization.
The top-5 (most used) sales, distribution, inventory, etc. reports
from each geographical location will cover the vast majority of the
reporting needs.

A single SAP NetWeaver BI report may satisfy dozens of

todays static reports. Therefore, its impossible to map each
individual legacy report to a single SAP NetWeaver BI report.

Note

Avoid attempting to replicate each local

Best report based on what you might have in
place today. Accept new ways of
Practice
accessing data.
28
Getting the Global Functional Specifications (cont.)

Create a form that captures the business core

requirements in a structured format
Create a simple Information Request form, and use it to gather the
Tip
core relevant information about each report being requested by
the business community
The form should include at least the following fields:
Contact info about the requestor
Data currency (yesterday/today)
Department
Name of report
Description of report
Purpose of report
Type of users (mgr./analyst/casual)
Number of users expected
Frequency of report (daily/monthly)
Security requirements
How is this reporting done today
Comments 29
Sample Information Request Form

Document requirements in
a standardized format and
allow for a large
comment section
Prioritize requirements
Consolidate requirements
Support follow-up
discussions and reviews

Tool

P1 30
of 2
Sample Information Request Form (cont.)

Other uses
Post the form on the
intranet, thereby giving
stakeholders an easy way
to communicate with the
project team
Use the Comment section
for language and security
requirements, or add a
separate section for this
Note the section for
dispositioning the
requirement
Tool

P2 31
of 2
Sample Information Request Form (cont.)

An
Example

32
Sample Information Request Form (cont.)

An
Example

33
Consider Multiple Country Views of Displaying the Same Data!

Deliver reports in a consistent manner to

users (one version of the truth), but use KPI & Scorecard
Formatted
different mechanisms to do so Simple
Easy to view
Limited nav
Aggregates
Managers and executives tend to prefer
simple and directed interfaces Flat Reporting
Formatted
Print
Form based
Casual users tend to prefer predictable Static
Predictable access
structured access to data
OLAP Reporting
Drill Down
Slice and Dice
Analysts and power users tend to prefer high Analyse
flexibility and unstructured access to data Data Mining
Search and discover

Don't underestimate different users in various countries and their need

to access the information in various ways one size does not fit all!
34
 Blueprinting Phase: Some Key Observations

Getting
Gettingthe
theright
rightrequirements:
requirements:
Finding
Findingout
outthe
thedetailed
detailedfunctional
functional
specs
specsofofwhat
whatusers
usersreally
reallyneed
needand
and
not
notjust
justwhat
whatthey
theywant.
want.

Deciding
Decidingwhat whatwill
willbe
be
developed
developedin inSAP
SAPNetWeaver
NetWeaver
BI
BIand
andwhat
whatwill
willbe
be
maintained
maintainedas asSAP
SAPR/3R/3
Map
Map the functional requirementstotothe
the
reports.
reports. functional requirements the
standard
standardcontent,
content,and
andsee
seewhat
whatcancan
Core Activities be
beleveraged
leveragedandandwhat
whatneeds
needstoto
2.1 Project Management Business Blueprint be
beextended.
extended.
2.2 Organizational Change Management
Create
Createdetailed
detailedtechnical
technical
2.3 Project Team Training Business specifications
specificationsand
anddesigns
designsofof
Blueprint InfoCubes,
InfoCubes,master
masterdata,
data,ODSs,
ODSs,andand
2.4 Develop System Environment high-level
high-levelarchitectural
architecturaldesigns.
designs.
2.5 Organizational Structure Definition Create
Createuser
useracceptance
acceptancegroup(s),
group(s),and
and
2.6 Business Process Definition have
havethem
themreview
reviewandandgivegivefeedback
feedback
on
onthe
thesystem
systemasasititisisdeveloped.
developed.
2.7 Quality Check Business Blueprint
35
 Report Dispositioning: What Goes in BI and What Stays in
SAP R/3?
Many tools exist that can report on SAP R/3 data
You might have static reports that truly belong in SAP R/3,
which would not be cost effective to move to SAP NetWeaver
BI
Make cost-effective decisions
Just because the report is not in SAP NetWeaver BI does not
mean it cannot be added to a Portal or viewed on the Web
Warning Not all reports belong in SAP NetWeaver BI
Avoid using SAP NetWeaver BI as a dumping group
You need to make conscious decisions on what reporting
needs you are going to meet, and how you will
accomplish this
We will now take a look at an approach to formal report
dispositioning that has been used by a few companies.
36
Key Questions for Report Dispositioning

Is this really a reporting need or is it a want?

Is the data going to be in SAP NetWeaver BI at a frequency
that solves the users request (e.g., intraday reporting)?
Is the data needed for this report already in our SAP
NetWeaver BI scope?
Is there a report already available in SAP R/3?
Does standard BI content exist?
Is it less expensive to create the report in SAP R/3?
Are there a significant number of users?
Is the reporting need resource-intensive?
Is SAP NetWeaver BI cost effective in the long run
(ownership)?

37
 Team starts by reviewing documentation tool for

An example of how to decide

documentation completeness

cu Review requirements and identify

corresponding Data Model (InfoCube/ODS) Tool which reports should be in SAP
R/3 or the legacy system
D1 D1a
Communicate to
(refer to printed version)
Is report Is this a true No
Yes bus. leader
documentation reporting
complete? need

Yes

No D4
D2 D2.5 D3
Is the report
Is this Does data exist Significant
No No No system
an Intraday in "in-scope" models number
resource
Request additional report? Infocube/ODS of users? No
intensive?
input from Business
Team member
Yes Yes
Yes R/3 is selected as
Reporting Tool
R/3 is selected as and documented
Reporting Tool A2
Total Cost of in doc. tool
and documented
Responsible Ownership
Team member Analysis
acquires/documents
additional information R/3 is selected as
Communicate final Reporting Tool
disposition D8 No and documented
Is BI cost in doc. tool
Yes effective?

D5 BI is selected as
Reporting Tool Communicate final
Does Yes
No and documented disposition
Yes Standard R/3
content in the documentation tool
exist? D9
BI is selected as R/3 Tool
D6 D7 reporting tool and Change Selection
Does Is it less Communicate final Request is submitted if Process
Standard BW No expensive to disposition the scope changed
content create in
exist? No
R/3?
Standard Report
Yes Yes R/3 Writer

BI is selected as R/3 is selected as BI is selected as Communicate final ABAP/

Query Other
Reporting Tool and Reporting Tool and disposition Custom
Reporting Tool
documented in doc. and documented documented in doc.
tool in doc. tool tool
A3
Sub-Process Report Consolidation &
Communicate final Communicate final Communicate final eliminate if appropriate (winnowing)
disposition disposition disposition
R/3 team make final disposition

BI Team to forward completed detailed report specifications

based on selected Reporting Tool - BI or R/3 A4
Baseline reports
38
 Now That You Have Identified the In-Scope Reports, Whats
Next?
Obtain a copy of each of the current reports that are in-
scope (not all report across your organization)
Legacy reports are often a great way to document the data needs
They can be used to illustrate how data is currently being
summarized and viewed
Consolidate the requirements, and look for low-hanging fruit
Create a physical folder with paper copies of these legacy reports
Make sure the development team has access to them this

will reduce the time spent in meetings with the business

community

Great Many requirements

+ + = can be met by a
single SAP
Feature NetWeaver
BI report
39
 Where Do I Start?

All functional areas are not equally supported by strong

standard SAP NetWeaver BI business content
Some areas have much you can leverage, others will require
significant enhancement to meet your requirements
The differences are often due to customization on the SAP R/3-
side by companies and/or industry solutions
Approximate Usage of Standard Content BW 3.5 Focus on an area that
(percentage of overall development effort)
solves a problem instead
100
of becoming a
80 replacement project.

60 Gradually, using a
prioritized phased
40
approach, solve other
20 business problems.

0
A good way to think of a
BI rollout is in terms of
business problems. 40
* Rapidly improving content
 The Blueprinting Phase: Leveraging Standard Content
Mostly standard storage objects
As a guiding principle, Some customization
Highly customized storage objects
map requirements to
standard content before 31% 36%

customizing
However, you may also
have external data An example from a large

sources that require 33% manufacturing company

custom ODSs and

InfoCubes (3.5.1):
BW Content available (3.5.1)
Customizing lower level
objects cause higher

Cockpits
Workbooks
???
1,979
level standard objects Queries 3,299
Roles 861
not to work, unless you MultiCubes 121

also customize these InfoCube 605

ODS objects 349
InfoObjects 11,772
41
 The Blueprinting Phase: Model Your Solution
1. Create a model based on pre-delivered SAP NetWeaver BI content
2. Map your data requirements to the delivered content.
3. Identify where the data gaps are going to be sourced from
Unit
Logistics
Material
Currency Key Billing information
Plant Unit of Measure
Material number
Shipping/receiving point Base unit of measure
Material entered Billing document
Material group Sales unit of measure
Billing item
Item category Volume unit of measure
Billing type
Product hierarchy Weight unit of measure
Billing category

Storage EAN/UPC Billing Billing date

Creation date

Requirements
Cancel indicator
Number of billing documents Output medium
Customer Number biling line items ~ Batch billing indicator
Billed item quantity Debit/credit reason code
Sold-to Net weight Biling category
Ship-to Subtotal 1 Reference document
Bill-to Subtotal 2 Payment terms
Payer Subtotal 3 Cancelled billing document
Customer class Subtotal 4 Divison for the order header
Subtotal 5 Pricing procedure

+
Customer group
~ Customer country Subtotal 6
~ Customer region Subtotal A Document details
~ Customer postal code Net value
~ Customer industry code 1 Cost
End user Tax amount Sales order document type
Volume Sales deal
Sales docuement
Organization

Company code
Division
Distribution channel
Personnel Accounting
Time Storage
Standard Content Sales organization
Sales group
Sales rep number Cost center
Profit center Calendar
Calendar
year
month
Objects
Controlling area
Account assignment group Calendar week
Calendar day
LEGEND
Map functional requirements to
the standard content before you Delivered in standard extractors
Delivered in LO extractor
make enhancements Not in delivered Content -but in R-3 42
What Well Cover

Final preparatory steps

Blueprinting phase
Realization phase
Implementation phase
Wrap-up

43
Realization Phase

Building ODSs and InfoCubes

Planning, managing, and executing system test
Planning, managing, and executing integration and
performance test
Issue resolution, logs, sign-off, and approvals

44
 Realization Phase: Some Key Observations
Core Activities
3.1 Project Management Realization
3.2 Organizational Change Management
3.3 Training Realization
3.4 Baseline Configuration and Reviews
3.5 System Management
3.6 Final Configuration and Confirmation
3.7 Prepare & Coordinate Interface Development
DevelopmentPrograms:
Programs:Provide
Provide
Development details of added programming
details of added programming
structures
structures
3.8 Develop Data Conversion Programs (if any)
3.9 Develop Queries
End
EndUser:
User:Training
TrainingMaterial
Material
3.10 Develop User Interface Enhancements
3.11 Determine Additional Reporting Configuration
Configurationand
andTesting
TestingPlans:
Plans:
Requirements Define
Define how the configuration willbe
how the configuration will be
implemented and how it will be tested
implemented and how it will be tested
3.12 Create Structured Reports
3.13 Establish Authorization Concept Source: Pauline Woods-Wilson

3.14 Establish Data Archiving plan (if applicable)

3.15 Final Integration Test
3.16 Quality Check Realization 45
Building ODSs and InfoCubes

TIPS
1 Review the functional requirements and 6 Do not allow exceptions to your naming
technical design. conventions.
2 Make sure you have established Data 7 Make sure that putting out fires does not
Stewards for master data, and assign take precedence, becoming the
master data to specific developers. default architecture and standard.

3 Have your ETL developers work 8 Try new ideas in a Sandbox environment,
for the individual who is responsible and dont contaminate the development
for creating process chains (organizationally). environment.
4 Avoid nested ODS layers, and keep the 9 Keep details for multi-use in the ODS and
architecture as pristine as possible. do not design the ODS based on the needs
of a single InfoCube.
5 Make your transformations part of 10 Developers must unit test all of their
update rules into InfoCubes if you need work and personally sign-off on their
to be able to reconcile to the source storage object.
system. Keep the details in the ODS.

46
 Consider Upgrading to SAP NetWeaver BI 7.0

On a typical SAP NetWeaver BI project, 40 - 60% of project

effort will be spent on data integration, transformation,
and loads

BI in SAP
NetWeaver
2004s has a
new GUI to help
you write
transformations,
potentially
saving you a lot
of time!

Source SAP AG

47
The SAP NetWeaver BI Test Methodology

Methodology used for system and integration tests

Test Strategy

Test Plan

Test Execution

Problem Resolution

SAP R/3 and BI testing is not different from a

methodology standpoint, but the global execution
is different.
48
 SAP NetWeaver BI Test: Planning
Tasks\Dates December 2003 January 2004 February 2004 1-Mar 8-Mar 15-Mar 22-Mar 29-Mar 5-Apr

Identify People for Testing

i m e to s top for
s n o t
late.
Schedule Facilities
Ther e' a l r e a dy
'r e
Prioritize Test Areas (Queries)
gas, we
Send out Meeting Notice

Execute System Test

Document Results

Problem Resolution

Activities
Tasks
1 Create test script 6 Identify key contacts
2 Identify roles to be used 7 Communicate about transports
3 Documentation on using test tools 8 Arrange time for progress control
4 Procedure for documenting test results 9 Schedule facilities
5 Training sessions for using test scripts
Business analysts are responsible for planning, 10
11
12
1
2

coordinating, and executing the system testing of

9 3
8 4
7 5
6

queries. Timing
Plan for more than one test location and early 49
 SAP NetWeaver BI Test Scheduling: Example

3/10

3/12
3/13
3/14

3/16
3/17
3/18
3/19
3/20
3/21
3/22
3/23
3/24
3/25
3/26
3/27
3/28
3/29
3/30
3/31
3/15
3/11
3/1
3/2
3/3
3/4
3/5
3/6
3/7
3/8
3/9

4/1
4/2
Deliver
Cost and Profitability
Resolving
Order
Environment outstanding
Manufacturing
preparation issues and re-
Plan and scheduling
testing
Demand planning
Source

= Morning session 8:30 - noon

= Evening session 12:30 - 5:00

Each team should have dedicated time in the test room in each
country
If needed, rent your own training/test room
Provide food and snacks
At least two testers (preferably three) should be assigned to test
each query
All test results must be logged

50
SAP NetWeaver BI Test: Checklist

Preparations
Data source/cubes/ODS/queries prioritized for testing
Queries developed and available in the SAP NetWeaver BI
test environment
Track specific test plans created using test template
Test cases written
People
Individuals (testers) perform the identified tests
Testers invited to complete SAP NetWeaver BI on-line training
Availability of testers confirmed
Security roles tested and user IDs for testers have been created
Logistics
Testers familiarized with test results recording tools
Identify test location and verify resources
Rooms, computers, SAPGUI, network connections, phone, etc.
Plan for problem resolution

51
Performance Testing

Performance test execution

Identify queries to be performance tuned, and determine cutoff
load for load test (e.g., 40% of actual users not named)
Schedule queries to run in background, and execute each query
while load scripts are running to simulate real users
Monitor your system continuously, and attempt tuning at the
query level
Perform analysis based on benchmarks, and build aggregates
and/or indexes
Record findings in a formal tracking tool available to everyone
Meet with developers daily to discuss issues
Problem resolution

Look at the new BI Accelerator in SAP

NetWeaver 7.0 for improved performance
! Source: Alexander
Peter, SAP AG
52
 Test Signoffs

Signoff procedure
Document test feedback and update logs
Review open issues
Prioritize outstanding issues
Agree on scope decisions and resolutions
Obtain approvals from business representatives in each country
and the overall steering committee

53
What Well Cover

Final preparatory steps

Blueprinting phase
Realization phase
Implementation phase
Wrap-up

54
Implementation Phase

Executing cut-over to production

Conducting end-user and power user training
Establishing end-user support organization
Post implementation review and next steps

55
 Final Preparation Phase: Some Key Observations

The
TheCutover
CutoverPlan
Planand
andthe
theTechnical
Technical
Operations
Operations Manual: Describethe
Manual: Describe the
details
detailson
onhow
howtotomove
movetotothe
the
production
production environment andgo
environment and golive
live

Stress
Stressand
andVolume
VolumeTests:
Tests:Confirm
Confirmthe
the
production hardwares capabilities
production hardwares capabilities

End-User
End-UserTraining
TrainingDocument:
Document:
Describes
Describes the deliveryofofthe
the delivery thenecessary
necessary
levels
levelsofofSAP
SAPtraining
trainingprior
priortotogoing
goinglive
live
Core Activities Source: Pauline Woods-Wilson

4.1 Project Management Final Preparation

4.2 Training Final Preparation
4.3 Acceptance Testing
4.4 System Management
4.5 Detailed Project Planning
4.6 Cutover
4.7 Quality Check Final Preparation
Source: SAP

56
Conducting End-User and Power User Training

Web-based
All users 1) Create, or buy, an on-line
Training help and training system.
Tutorials Make sure you use many
images and links.
Instructor-led
On-site 2) Consider using
Power users animations to demonstrate
Executives complicated tasks as well.
Vendor-based 3) Consider multi language
Developers versions of the help and
Support staff training system

57
Establishing Local and Global End-User Support Organization

Getting power users involved early is important to the

overall success of a data warehousing project
To help support countries and regional businesses that
have already gone live, a strong local community of
ambassadors is needed
Without them, ongoing projects can get
bogged down with basic report support
and enhancement requests

Source: SAP
58
Go-Live: Some Key Observations

The
Thelast
lastdeliverable
deliverablefor
forthe
theimplementation
implementation
ensures
ensures high system performancethrough
high system performance through
monitoring and feedback
monitoring and feedback

Source: Pauline Woods-Wilson

We
Weneed
needtotoexecute
executeissue
issueresolution
resolutionplans
plans
and contingency plans
and contingency plans

AAlessons
lessonslearned
learnedsession
sessionshould
shouldbe
beheld
held
atatthe end of the project to assure
the end of the project to assure
organizational
organizationalawareness
awarenessandandeducation
education
Core Activities
5.1 Production Support The
Thesupport
supportorganization
organizationwill
willtake
takeover
overthe
the
system after a pre-determined time period.
system after a pre-determined time period.
5.2 Project End Some
Someteam
teammembers
membersmaymaytransition
transitioninto
intotheir
their
new roles as support staff
new roles as support staff

This
Thisisisaacritical
criticaltime
timewhen
whenaaSWAT
SWATteam
team
that
thatquickly
quicklyaddresses
addressesuseruserconcerns
concernscan
can
make
make all the difference in how the systemisis
all the difference in how the system
received
receivedamong
amongthe theusers
users

59
 Tracking Load Performance

During the first six weeks after each go-live, you should
formally track the load performance by process chain to see
if you have any systematic issues
Load Performance Rate
100%

90%

80%

70%

60%

50%

40%

30%

20%

10%

0%
4/ 05
4/ 005
4/ 05

4/ 05

4/ 05

5/ 05

5/ 05

5/ 05
05
3/ 005
3/ 005

3/ 005

3/ 005

3/ 005

4/ 05

4/ 005

4/ 005

4/ 005

4/ 005

4/ 005

4/ 005

4/ 005

4/ 005

4/ 005

5/ 05
20
20

20

20

20

20

20

20
0

0
2
/2
/2

/2

/2

/2

/2

/2

/2

/2

/2

/2

/2

/2

/2

/2
/2
1/

3/

5/

7/

9/

1/

3/

5/

7/
20

22

24

26

28

30

13

15

17

19

21

23

25

27

29
11
3/

This is also a great way to document your

success!! 60
 Tracking Load Performance (cont.)

A stabilization period after each go-live is normal, until the

new process chain has been tuned in the production box
This is a time when active monitoring of process chains
should occur Areas of BI Data Load Issues Production
Performance
Nov. 1st through Dec. 15th Demand
7 Planning

Transaction -
global
6
Source -
Purchase
5 Orders
Roughcut
Number of Issues

4 Material
Movements

MD - Bev.
3 Packaging

Master data
2
Hierarchies
1
Greycon

12/10/04

12/12/04
12/13/04
12/14/04
12/15/04
12/1/04
12/2/04
12/3/04
12/4/04
12/5/04
12/6/04
12/7/04
12/8/04
12/9/04
11/29/04
11/30/04

12/11/04
11/15/04

11/23/04
11/10/04

11/12/04
11/13/04
11/14/04

11/16/04
11/17/04
11/18/04
11/19/04
11/20/04
11/21/04
11/22/04

11/24/04
11/25/04
11/26/04
11/27/04
11/28/04
11/1/04
11/2/04
11/3/04
11/4/04
11/5/04
11/6/04
11/7/04
11/8/04
11/9/04

11/11/04

CO -line items

61
 Go-live: Post-Implementation Review

Alignment Benefits
Are we doing Are we getting
the right the benefits?
things?

Are we doing Are we getting

them the right way? them done well?

The Information Paradox: John Thorp

Integration Capability/Efficiency
Conduct a formal post-mortem after go-live before starting the next
phase of the project. Not everyone will tell you if they dislike the system,
but you need to give them a chance. Learn from your mistakes and
make continuous improvements. 62
What Well Cover

Final preparatory steps

Blueprinting phase
Realization phase
Implementation phase
Wrap-up

63
Resources

Steve McConnell, Rapid Development

(Microsoft Press 1996, ISBN: 1556159005)

Jeremy Kadlec, Start to Finish Guide to IT Project

Management (NetImpress 2003, ISBN: B0000W86H2)
Digital PDF, 109 pages
Download at: amazon.com

COMERIT.NET (presentations, tools and accellerators)

http://www.comerit.net

64
7 Key Points to Take Home

Keep the team relatively small and focused

Size your project based on your teams experience and skills,
in addition to scope
Make the implementations interactive instead of big bang
Follow a proven methodology
Dont cram all of your reports into SAP NetWeaver BI (some
belong in SAP R/3)
Track quality, and create a formal approval process
Involve power users and ambassadors in the development
project

65
Your Turn!

How to contact me:

Dr. Bjarne Berg
bberg@comerit.net
66