Date post: | 03-Apr-2018 |
Category: |
Documents |
Upload: | inderpreet-singh |
View: | 213 times |
Download: | 0 times |
of 61
7/28/2019 PM2008_UpgradeBI70
1/61
2008 Wellesley Information Services. All rights reserved.
Best practices for creatinga sound strategy and athorough plan for yourSAP NetWeaver BusinessIntelligence upgrade
Dr. Bjarne Berg
7/28/2019 PM2008_UpgradeBI70
2/61
2
What Well Cover
Why upgrade
End of supportNew support strategy & NetWeaver
New features and capabilities
Creating an upgrade strategy for the futureContent Vs. Technical upgrades
Upgrades with NetWeaver
Planning and Executing the upgradeThe upgrade plan
The business case
Staffing, duration and scope Examples
Wrap up
Bonus material: ideas for the business case
7/28/2019 PM2008_UpgradeBI70
3/61
3
Why Upgradeend of support
Many upgrades are driven by end of support for a certain release.
SAP has now created a 5-1-2 maintenance system that consists of:- mainstream maintenance
- extended maintenance
- customer-specific maintenance
BW
Version
Release
date
End o f mainstream
maintenance2.0B 8/14/00 12/31/2005
2.1C 12/18/00 12/31/2005
3.0A 11/15/01 12/31/2005
3.0B 5/13/02 12/31/2006
3.1C 11/11/02 12/31/2006
3.2 3/31/03 12/31/2006
3.3 8/30/03 12/31/2006
3.5 3/31/04 3/31/2010
7/28/2019 PM2008_UpgradeBI70
4/61
4
Going forward, SAP will provide five years of mainstream (standard)
maintenance, with the option to extend their maintenance coverage for aperiod of up to three years for small premiums over the standard
maintenance rate.
1. Five years of mainstream maintenance at the standard maintenance fee
2. One year of extended maintenance at an additional two percent maintenance fee*
3. Two more years of extended maintenance at an additional four percent maintenance
fee per year*. After these eight years, customer-specific maintenance begins, providing
a program of support and services uniquely tailored to individual customerrequirements.
The plan covers SAP solutions based on the SAP NetWeaver platform
including mySAP SCM, SRM, PLM, CRM, and industry add-ons.
The 5-1-2 maintenance strategy
*check with your account executive to see what your fee may be
7/28/2019 PM2008_UpgradeBI70
5/61
5
The Bigger Picture NetWeaver ??
NetWeaver is a set
of solutioncomponents that
provides a
comprehensive
architecture.
All components of NetWeaver can use the same operating system
release, and the same database release. All components can be run
within a single physical server if it is a small configuration, thereby
reducing the management of many systems & databases
VisualComposer BI
Kit
VisualComposer BI
Kit
UDI
XMLASAP
Query
JDBC ODBO
Business Explorer Suite (BEx)
BEx Query Designer
Information Broadcasting
Web
Analyzer
Web
Application
Designer
MS Excel
Add-in
Report
Designer
BEx Web
DB
Connect BAPI
Service
API File XML/A
BEx AnalyzerBI Pattern
BI Consumer Services
BI Platform
Data Warehouse
Enterprise Portal
Analytic Engine Meta Data Mgr
KM
7/28/2019 PM2008_UpgradeBI70
6/61
6
Why Upgrade to NW BI 7.x?
One of the major reasons for upgrading your BW environment is the
availability of new content and features in the next release. Let us takea look at some of the major new features of version BI 7.x:
Web Application Designer
BI Accellerator
BEx Broadcaster
BEx Query Designer
BEx Report Designer
ReModeling Toolbox
Security Changes
New ETL Interface
BPS Integrated Planning
PDF print
Real-time data warehousing
BEx Web Analyzer
We will now take a quicklook at these features
7/28/2019 PM2008_UpgradeBI70
7/617
Web Application Designer is improved
The Web Application Designer is improved with new chart types (Heat Map, GANTT &
Milestone Trend Analysis), as well as new layout elements such as tab strips.
WAD also has new step-
by-step wizards for maps,
command editing to
create Web API
Commands and charts, as
well as a simplified wizard
for layout elements such
as radio buttons, action
buttons etc.
This reduce the amount
of custom coding
required with the help of
Command wizards, Auto
complete and support for
HTML tags.
WAD is a key tool
for all SAP BI shops
and in BI 7.x the
tool is simplifiedand more powerful.
New: Integration with
NW BI 7.x BEx Report
Designer.
7/28/2019 PM2008_UpgradeBI70
8/618
Why upgrade? - BI Accellerator for BI 7.x
The SAP BI
accelerator makes
query response time50-10,000 faster.
You use process
chains to maintain
the HPA engine after
each data load
HP, Sun and IBM have standard solutions rangingfrom $32K to $250K+ that can be installed and
tested in as little as 2-4 weeks (+ SAP license fees)
SAP
BW
Any
tool
7/28/2019 PM2008_UpgradeBI70
9/619
New Object Types
You can broadcast BEx query views and
formatted reports (reports) in addition to Webapplications, queries and workbooks. Reports
are a new BEx object type developed within the
new BEx Report Designer tool.
New Output Formats
New output formats are based on the
distribution type you select. But, you now canbroadcast web documents as PDF files.
New Broadcaster features of BI 7.x
7/28/2019 PM2008_UpgradeBI70
10/6110
New Distribution Types
You can broadcast to any printer using
Adobes PDF, Printer Common Language(psl) or Post Script (ps). (hint: Set up the
printers under tools CCMS print).
You to broadcast user-specific information
based on attributes in the master data
attributes using a distribution list in BI
(bursting of emails). The information can be
controlled by the system so that users only
see data related to them.
New Broadcaster features of BI 7.x
7/28/2019 PM2008_UpgradeBI70
11/6111
New Broadcaster Features of BI 7.x (cont.)
Exception broadcasting is now available in the
Broadcaster. Create the exceptions in the querydesigner and select distribution type in the
broadcaster. You can also use additional
distributions types (subordinate) and create rules
for when the exception report is monitored/
executed. Exceptions can be based on singleevents or levels of any performance measure.
You can use multiple distribution types to create
a setting that broadcasts over many channels
(e.g., the printer and the portal).
NOTE: To manage all alerts and workflow tasks
from a single location, an alert is integrated with
the portals universal worklist in the central
alert framework of NW application server.
7/28/2019 PM2008_UpgradeBI70
12/6112
To increase the performance of key queries, you
can fill the OLAP Cache, or the MDX Cache. This isuseful if you have large numbers of users
accessing a query, or you have a query that
accesses a high volume of data.
The Fill Precalculation Store distribution typeallows you to precalculate Web templates, and the
Precalculate Value Set option allows you to fill
precalculated value set variables with values for
characteristic values. The precalculated value sets
are then available as variable values in BEx queries.
Old Reporting Agent scenarios still run in NetWeaver BI 7.x.
However, the Reporting Agent will not be developed any further and
is removed from the BI 7.x Workbench. You can now only reach the
Reporting Agent using transaction code REPORTING_AGENT
New Broadcaster Features of BI 7.x (cont.)
7/28/2019 PM2008_UpgradeBI70
13/61
13
Better web printing leveraging PDF and web controls
PDF based BEx Web printing now
include a variety of functionality,
such as:
1. Fit to page width
2. Repeat column headers
3. Fit to one page4. Wallpaper
5. Page margins
6. Export Themes (e.g. black &
white)
7. Format & Allignment
8. Additional Headers & Footers
9. Print graphics and tables
10.Batch Printing via Broadcaster
7/28/2019 PM2008_UpgradeBI70
14/61
14
BEx Query Designer gets a facelift
The 3.5x BExQuery Designer
Note:
The BI 7.x BExQuery Designer
This new property pane makes it
easier to format and controldisplays than in the past.
You can choose if
you want the old or
the new look after
the upgrade
7/28/2019 PM2008_UpgradeBI70
15/61
15
Why upgrade? - BEx Report Designer
This new 7.x tool was
created to simplifythe formatting of
reports and fix many
of the printing issues
in previous versions
of BW.
We now get color
control, header-
footer control and
many new features
such as locationcontrol of cells and
integration of
pictures, charts and
fixed text. For many, this tool may reduce the need for
3rd
party tools to address structured reports.
Source: SAP AG, 2008
7/28/2019 PM2008_UpgradeBI70
16/61
16
Why upgrade? The Remodeling Tool Box
In the first releases of BI 7, youcould not transport the newmodels, now you can. You canalso:
Remove, exchange, replace, add &fill dimension characteristics and keyfigures.
NOTE: during (dictionary-based)conversion process, queries are not
possible; aggregates will beautomatically deactivated and mustbe rebuilt afterwards
NW BI 7.x goes a long way to address the complaints that BW is a hard to maintainenvironment with forever fixed models.
Source: SAP AG, RichardBrown, Aug. 2008
In BI 7.x you get a new tool to add characteristics and key figures to your model.
In older BW versions, if you forgot to include a field in your infocube , the rework was
quite substantial and often involved reloading the infocube as well.
7/28/2019 PM2008_UpgradeBI70
17/61
17
Why upgrade? - Better security features
There are many new security features inNW BI 7.x, and a conversion is needed (all
or nothing).
Role menus are displayed in the portaland passwords becomes case sensitive.
Authorizations arefundamental building
blocks of the newreporting concept andsecurity contains both
the data value and
hierarchy restrictions.
The new security can bebuilt using newRSECADMIN
transaction
ASUG Security Upgrade by Eric Dwyer, Nike: http://www.asug.com/client_files/Calendar/Upload/EA1_upgrade_bw_security_2.ppt
Source: SAP AG
7/28/2019 PM2008_UpgradeBI70
18/61
18
Why upgrade? - More Authorization Objects
You get the ability touse much lower
security granularity fordevelopers and users!!
Source: SAP AG July 2008
Authorization objects for the Data Warehousing Workbench:S_RS_DS: For the DataSource or its sub objects (BI 7.x)S_RS_ISNEW: For new InfoSources or their sub objects (NW BI 7.x)
S_RS_DTP: For the data transfer process and its sub objectsS_RS_TR: For transformation rules and their sub objectsS_RS_CTT: For currency translation typesS_RS_UOM: For quantity conversion typesS_RS_THJT: For key date derivation typesS_RS_PLENQ: Authorizations for maintaining or displaying the lock settingsS_RS_RST: Authorization object for the RS trace toolS_RS_PC: For process chainsS_RS_OHDEST: Open Hub Destination
Authorization objects for the Business Explorer:S_RS_DAS: For Data Access ServicesS_RS_BTMP: For BEx Web templatesS_RS_BEXTX: Authorizations for the maintenance of BEx texts
Authorization objects for the Admin of analysis authorizations
S_RSEC: Authorization for assignment and administration of analysis authorizationsS_RS_AUTH: Authorization object to include analysis authorizations in roles
Changed Authorization Objects:S_RS_ADMWB (Data Warehousing Workbench: Objects):
New sub objects:
CONT_ACT
Installing Business Content; USE_DND - Drag & Drop to InfoAreas andapplication components; CNG_RUN - Attribute change run
7/28/2019 PM2008_UpgradeBI70
19/61
19
Upgrading to BI 7.x Security
More Great Details about
the Security Upgrade at :
http://csc-studentweb.lrc.edu/swp/Berg/Articles/ BI
7.x_Authorizations.pdf
(Source: Amelia Lo, SAP)
SAP has created an ABAP migration tool to help you upgrade security inNW BI 7.x. To access it, goto transaction code SA38, and execute
migration program RSEC_MIGRATION.
About 80% of you security setup is expected to make it using this tool.i.e. customer exit variables for the object 0TCTAUTHH does not migrate,and you will have to manually reassign all hierarchy nodes.
While you upgrade, the old security is left intact and you can switchback if absolutely needed (IMG setting). Plan to testtest..and test
7/28/2019 PM2008_UpgradeBI70
20/61
20
Why Upgrade? - Better interface for ETL Design
SAP NetWeaver BI
7.x has a new and
better GUI and
formula editors to
write complex
transfer rules,
update rules and
data mapping.
On a typical DW project, 40-60% of project effort will be spenton data integration, transformation and loads (used to be
higher when tools were more immature).
7/28/2019 PM2008_UpgradeBI70
21/61
21
Why upgrade? - BPS Integrated Planning (still supported)
You can now create planning templates using the web based planning wizard to createmodels using patterns in the data (tool: Road map Pattern). Queries based onaggregation levels can now also write back to the InfoProvider
1 2 3 4 5 6
InfoProvider Aggregation Level Planning SequencePlanning FunctionFilter Pattern
Source: SAP AG, 2008
7/28/2019 PM2008_UpgradeBI70
22/61
22
Why upgrade?PDF Print
You can also use the PDF to create
reports based on BEx webapplications, queries and reportsusing the Adobe DS (comes with BI7.x).
The only Gotchas.. Your users nowneed to install Acrobat Reader(free at http://www.adobe.com/products/acrobat/readstep2.html).
The PDF document can also beBroadcasted through BExBroadcaster
The PDF options allows companies to
protect reports from changes by
employees by taking a snapshot of the
data regardless of subsequent updates
to the data warehouse.
Risks: no link back to SAP BW is
needed and security is not validated.
7/28/2019 PM2008_UpgradeBI70
23/61
23
Why upgrade? - Real-time Data warehousing gets better
NW BI 7.x has more features for updates that does not follow thetypical asynchronomous (batch) updates. This include:
1. We can use XML to fill the PSA directly2. Daemon-based update from delta queue (BW API)3. Daemon-based update of the ODS and minimal logging
Note: XML documents
creates many tags that will
slow down large dataloads
due to the size of each XMLrecord (relatively large)
However, it works great for
smaller streams of data.
7/28/2019 PM2008_UpgradeBI70
24/61
24
Why upgrade? - BEx web Analyzer integrates Excel
The Excel integration in the BEx
analyzer is far better.
Unlike the old days of dynamicHTML, you can now use the BExanalyzer more like a realapplication without refreshing thewhole page every time you clickon something (this is due to theJava component in BI 7.x)
Source: SAP AG, 2008
News: BEx browser
went away in BI 7.x
7/28/2019 PM2008_UpgradeBI70
25/61
25
Why upgrade? - Drag-and Drop in BeX web Analyzer
You can drag acharacteristics into a filter
area and automatically filteron that value, and you canalso drag it into a columnheader or a a row.
Building conditions andactivating them was oftenconfusing in earlier versionsand exception basedreporting was sometimes noteasy to create for beginningusers. BI 7.x has nowsimplified this with morewizards that helps users to
build this step-by-step.
BEx web analyzer is a better user toolthan in the past. You now get the best
world of Java & the web instead ofthe more clunky user experience
related to Dynamic HTML
7/28/2019 PM2008_UpgradeBI70
26/61
26
What Well Cover
Why upgrade
End of supportNew support strategy & NetWeaver
New features and capabilities
Creating an upgrade strategy for the futureContent Vs. Technical upgrades
Upgrades with NetWeaver
Planning and Executing the upgradeThe upgrade plan
The business case
Staffing, duration and scope
Examples
Wrap up
Bonus material: ideas for the business case
7/28/2019 PM2008_UpgradeBI70
27/61
27
BW Content Upgrades
Apply content when you need it, to the technical release you have!!
The new upgrade strategy from SAP is to provide BW technicalreleases as part of NetWeaver and BI content add-ons,
You do not need to perform a technical upgrade to update the
business content.
We now have SAP BI 7.0 and the content releases 7.0.1 and 7.0.2 and
7.0.3 are now available. Planned upgrades should also include the
content release 7.0.3.
Details around each content release is available at http://help.sap.comThe current content (7.0.3) is available at: http://help.sap.com/saphelp_nw04s/helpdata/en/ 44/16e6f7a6f30d19e10000000a114a6b/RN_703_en_final.pdf
7/28/2019 PM2008_UpgradeBI70
28/61
28
How can you weigh the choices of Technical or Functional?
Technical Functional
Opportunity to Sunsetother BI solutions
Increased UserSatisfaction
Tons of NewFunctionality
Longer Project
Less Functionality
Less Risk
Less Money
Less Time
28
Source: SAP AG
7/28/2019 PM2008_UpgradeBI70
29/61
29
Technical Functional
Weighing Towards a Technical Upgrade
A technical upgrade is
the safest way toproceed
It is also the fastest and
the least expensive
Your user community will
notice little to no change
UNTIL you start rollingout the new functionality
Source: SAP AG
7/28/2019 PM2008_UpgradeBI70
30/61
30
Weighing Towards a Functional Upgrade
A functional upgrade (which
includes all the technicalactivities) will make the
biggest impression on your
user community
This will take longer
and cost more money
You will be able to sunset
other solutions sooner
You will get the most
benefits from usability and
management
Technical Functional
Source: SAP AG
7/28/2019 PM2008_UpgradeBI70
31/61
31
An Upgrade Strategy
Think bigger than BW..
Apply content as soon as feasible. Especially if you
have on-going development work. This way you can
avoid many work-arounds.
You should seriously consider having all NetWeavercomponents on the same upgrade strategy instead of
selecting each component for upgrade. This will help in
the shared extractors and also substantially simplify the
upgrade planning and landscape.
Look at SAPs release strategy for each component youare using and plan ahead,instead of last-minute must-do projects.
Tip
7/28/2019 PM2008_UpgradeBI70
32/61
32
Some hints on the upgrade client, engines and usage types
We are in a transition period,
when some items of BI 7.x areseparate engines, some are
clients, and other are usage
types.
Key question: is you
organization committed to java
and the new BI 7.x direction?
-- if so, go java all the way..
Source: SAP Installable
software units
Note: standard system copy and SAP
migration tools have no standard
support for splitting or merging
systems with different usage types
7/28/2019 PM2008_UpgradeBI70
33/61
33
Some upgrade choices the architecture
Note: Depending on your current installation of
SAP BW, you have different upgrade options
Upgrade Or
Source: SAP AG May 2006
Upgrade Or
Upgrade Or
1
2
3
7/28/2019 PM2008_UpgradeBI70
34/61
34
What Well Cover
Why upgradeEnd of support
New support strategy & NetWeaver
New features and capabilities
Creating an upgrade strategy for the futureContent Vs. Technical upgrades
Upgrades with NetWeaver
Planning and Executing the upgradeThe upgrade plan
The business case
Staffing, duration and scope
Examples
Wrap up
Bonus material: ideas for the business case
7/28/2019 PM2008_UpgradeBI70
35/61
35
Typical Training Requirements
Functional Upgrade
Development TeamDelta Training
(DBW70E)
Report / PresentationTeam Delta Training
(DBW70R)
Integrated PlanningTraining (DBW70P)
User Training for newtools
Technical UpgradeBasis Training on new solution, if necessary
Could also be handled via Knowledge Transfer fromIntegration Partner
Basic Mgmt of Netweaver Portal (if deploying)
35
7/28/2019 PM2008_UpgradeBI70
36/61
36
Upgrade Pre-planning
It is important to communicate the goals and timings to the technical
team to help them prioritize their research and activity or hardware setup
Communicate goal of having existing content continue to work to
functional test team, so they do not get hung up in testing new features
before the upgrade is in production.
You need to have the SAP solution Manager to generate the key during
the upgrade to NW2004 SR1, and you will need to be on Solution
Manager release 3.2 SP8 or higher to make it work (note: 805390).
7/28/2019 PM2008_UpgradeBI70
37/61
37
BW
Version
Release
date
End of mainstream
maintenance
Can be upgraded to
2.0B 8/14/00 12/31/2005 2.1C, 3.0B, 3.1C, 3.50/3.51
2.1C 12/18/00 12/31/2005 3.0B, 3.1C, 3.50/3.513.0A 11/15/01 12/31/2005 3.0B, 3.1C, 3.50/3.51
3.0B 5/13/02 12/31/2006 3.1C, 3.50/3.51
3.1C 11/11/02 12/31/2006 3.2 and 3.3 must be applied before 3.5
3.2 3/31/03 12/31/2006 3.3 must be applied before 3.5
3.3 8/30/03 12/31/2006 3.5
3.5 3/31/04 3/31/2010
NetWeaver BI 7.x Upgrade paths
Still supported
Current Release NW 2004s Release/support
BW 3.5 (min. SP04) and ABAP, any content release (3.5.x)
BW 3.1c (min. SP14) content 3.2 or 3.3
BW 3.0B (min SP20)
BW 2.1C (min. SP18)
BW 2.0B (min. SP26 & Basis SP29)
Other
SAP BI 3.5 Java components (i.e. UDI) on WAS-Java System with usage type SAP AS Java
NetWeaver 2004s usage type ABAP,
(usage BI java and EP can be add-ins or
separate systems.
Must be upgraded to SAP BW 3.5 first and
then BI7.0 (upgrade with NetWeaver 2004s
Support release 1)
7/28/2019 PM2008_UpgradeBI70
38/61
38
Some hints Upgrade programs SAPup and SAPjup
You will need to install the NetWeaver Application Server Java and the
specific user type, before you can use all the features of BI 7.x (i.e.Business planning and analysis services, Enterprise data
warehousing, Reporting and analysis scenarios etc). You can install
this as a separate system or as an add-in to the upgraded ABAP
server.
SAP provides a software program called SAPup to help you upgrade
the WAS (ABAP) and SAP BW. It is called a system switch upgrade.
Note: if you already have java installed, you can also use the upgradeprogram called SAPjup, to upgrade the WAS-java.
If the WAS-J ava was installed on the same system as the WAS-ABAP (as an add-in) you need to run both the SAPup and SAPjup
programs in parallel (see the Master upgrade guide for more details).
S hi t th d U i d i
7/28/2019 PM2008_UpgradeBI70
39/61
39
Some hints on the upgrade - Unicode conversion
Unicode has been available since BW version 3.5.1. and is now
highly recommended as part of the upgrade (hint web applicationdesigner is now also unicode compliant).
Some things to remember and plan for:
Area Recommended increased capacity
Memory 20%
Processing power 20-25%
Disk space 20-30%45-50%
Pl i Y U d H d E l
7/28/2019 PM2008_UpgradeBI70
40/61
40
Planning Your Upgrade a Hardware Example
Production
12 CPU
96GB RAM
Sandbox
4 CPUs
32GB RAM
Test
4 CPUs
32GB RAM
Development
4 CPUs
32GB RAM
This west coast company reallocatedtheir Sun-6900 box (on Oracle) and have
3 Appservers on the production box..
More memory allows them to take better
advantage of the parallel load of the BW
system as well as to cache many of the
frequently run queries (BEx Broadcaster)
The hardware also allows them to have a
system where performance between the
boxes are comparable.
Example
Key numbers: 3.1 Terabytes of data; 2810
named users and about 620 active users
R
7/28/2019 PM2008_UpgradeBI70
41/61
41
Resources
A Dedicated team with a technical team lead (100%), a Basis resource
(100%) and a technical reviewer (100% is required).
In addition, a dedicated go-to resource for technical issues isrecommended. This should be an individual that have solidknowledge about the upgrade and have done his before. SAP
resources should be considered, due to their contact network withinthe SAP organization.
Regression testing is required on behalf or the user community. Thisshould be coordinated with the Power Users or existing developers.
Team Lead
Basis
resource
Technical reviewer Upgrade Support
External
Regression Testers
Team Lead
Basis Technical reviewer
BW Developer
Upgrade Support
External
Regression Testers
S l Ti li l t l d f l BW i l t ti
7/28/2019 PM2008_UpgradeBI70
42/61
42
Sample Timeline - complete landscape for large BW implementation
W1 W2 W3 W4 W5 W6 W7 W8 W9 W10 W11 W12
Project startup and Team training
Preparation for upgrade of Sandbox systemand roll out of SAPGui
Upgrade Sandbox system
Test functionality and decide what toimplement in upgrade (What has the best ROI)
Plan upgrade of production landscape
And roll out of new functionality to users
Upgrade development system
Test and validate upgrade
Implement new functionality
Upgrade Test system
(Copy of production if possible)
Test and validate Test system and user training& roll out of SAPGui
Upgrade Production system
Test and validate Production system
The more content you have
the longer the upgrade
(the more you have to
regression test)
The duration is driven by:
1. The number of BW systems in your landscape.
2. The new functionality your are rolling out
3. The support technology needed
Mi i Ti li d B i t
7/28/2019 PM2008_UpgradeBI70
43/61
43
Minimum Timeline and Basic events:
Do initial upgrade guide and note research [1-2 days]
Upgrade BW sandbox and do cursory issues check [1-4 days]
Upgrade a copy of BW production have key development leads regression test all
live content (both systems must be connected to other landscape environments
testing extractors too!) [2-5 days (size/copy/hw depending)]
Once the initial regression test is complete, create any correctional transports. [3-5days?]
Post-fix, have full team in for Upgrade buy-in testing that all works properly [2-3
workdays]
KEY: now freeze development and release transports, upgrade development and atest system, incorporating the fix transports generated from the upgrade regression
test. This should be a clean 2-4 day process.
Plan for regression test glitches and production cut-over.
M i t L d
7/28/2019 PM2008_UpgradeBI70
44/61
44
Move into Landscape
At this point you have a temporary BW Dev to test patch, and
perhaps static training, production and production supportsystems.
Ideally, youd migrate the upgrade to these as soon as possible,but this is a stable point. You will have to decide, based on
content, whether copying a test box to training makes sense (canpreserve user master)
For production and production support, youve already done a dryrun just do production and copy back to production support
unless the size makes this impractical [~ >500GB]
Hardware requirements changed if you also did
unicode conversion (recommended)
Don't
Forget
7/28/2019 PM2008_UpgradeBI70
45/61
Step 1: Hardware install and BWS Copy
7/28/2019 PM2008_UpgradeBI70
46/61
46
Step -1: Hardware install and BWS Copy
BWX BWD BWQ BWP
BWS BWX BWX BWX
1
3
2 4
January Feb March April
21 28 4 11 18 25 3 10 17 24 31 7 14
Hardware install
Copy BWD to new BWS
Upgrade DB2 to latest version
Post processing of box
Rename/restore old BWS box
Download latest patches for upgrade
In this real example, we are also
installing new Hardware. This givesus lot of flexibility
First, we copy the old development
system to the new Sandbox (new HW)
46
Step 1: BWS Unicode conversion Java upgrade & test
7/28/2019 PM2008_UpgradeBI70
47/61
47
Step -1: BWS Unicode conversion, Java upgrade & test
BWX BWD BWQ BWP
BWS BWX BWX BWX
1 2
January Feb March April
21 28 4 11 18 25 3 10 17 24 31 7 14
Start upgrade BWS
Start shadow instance
SPDD start
ICNV startStart syst. downtime upgrade activity
Complete BWS upgrade
Post processing
Basis and functional testing
Unicode conversion
Java upgrade
3
4
At this stage you should document and
test all work that occurs. Some time
has to be set aside for notes researchand unforeseen issues.
We want to creating a repeatable
process, so no ad-hoc activities are
allowed.
Step 2: System copies
7/28/2019 PM2008_UpgradeBI70
48/61
48
Step -2: System copies
BWX BWX BWX BWP
BWS BWD BWQ BWX
1
3
2 4
January Feb March April
21 28 4 11 18 25 3 10 17 24 31 7 14
Copy BWD
Development freeze
Rename BWD
Copy BWQ
Rename BWQ
Copy PDW (no rename yet). It is
still the production system..
You now freeze the development and
can take copies of the BWD and BWQ
system and prepare for upgrades.
The old BWP is still running as the
productive system..
48
Step 3: BWD upgrade
7/28/2019 PM2008_UpgradeBI70
49/61
49
Step -3: BWD upgrade
BWX BWX BWX BWP
BWS BWD BWQ BWX
1
3
2 4
January Feb March April
21 28 4 11 18 25 3 10 17 24 31 7 14
Complete Prepare on BWD
Apply fixes
Start upgrade BWD
Start shadow instance
SPDD start
ICNV start
Start syst. downtime upgrade activity
Complete BWD upgrade
Post processing
Basis and functional testing
Unicode conversion
Java upgrade
We now repeat the process. Remember,
you have already upgraded BWD once
(in step-1) and should know the needfor any post processing.
Don't ignore the need for technical and
functional testing.
Step 4: The real test BWQ upgrade
7/28/2019 PM2008_UpgradeBI70
50/61
50
Step -4: The real test -- BWQ upgrade
BWX BWX BWX BWP
BWS BWD BWQ BWX
1
3
2 4
January Feb March April
21 28 4 11 18 25 3 10 17 24 31 7 14
Complete Prepare on BWQ
Apply fixes
Start upgrade BWQ
Start shadow instance
SPDD start
ICNV start
Start syst. downtime upgrade activity
Complete BWQ upgrade
Post processing
Basis and functional testing
Unicode conversion
Java upgrade
Functional test and go/no-go decision
Notice, we refreshed the new BWQ
from BWP, so this is really a BWP
upgrade
St 5 Th Bi O C t O k d
7/28/2019 PM2008_UpgradeBI70
51/61
51
Step -5: The Big One: Cut-Over weekend.
BWX BWX BWX BWX
BWS BWD BWQ BWP
1
3
2 4
January Feb March April
21 28 4 11 18 25 3 10 17 24 31 7 14 18 19 20 21
Java install
Remove data in new system
Rename BWP
Complete Prepare on BWP
Apply fixes
Start upgrade BWP
Start shadow instance
SPDD start
ICNV start
Start syst. downtime upgrade activity
Complete BWP upgrade
Post processing
Basis testing
Functional test
Unicode conversion (TBD)
Contingencies should be made. I.e. notice
that is any showstoppers occur on 20th, the
old BWP can be renamed back, or if thetime becomes too short the Unicode can be
done the next weekend.
Lessons learned
7/28/2019 PM2008_UpgradeBI70
52/61
52
Lessons learned
Mfg. Retail Government Finance Energy
Old version 3.1C 3.5.3 3.5.3 3.1C 3.5.3
Duration 10 weeks 9 weeks 10 weeks 12 weeks 14 weeks
Scope 3 Tb/900 users 6 Tb/300 users 1 Tb/80 users 7 Tb/1,200 users 4 Tb/500 users
Number of environments 9 5 4 4 4
Number of core team
members 4 3 4 5 3
Hardware switch No No Yes Yes No
Testing 2 weeks 2 weeks 3 weeks 4 weeks 2 weeksUnicode No Yes Yes Yes No
Hardware Sun IBM Sun Sun IBM
Lessons Learned
Have the right
people in place.
Wait until they
are available
and have a core
business team
for short bursts
of testing
Unicode took a
bit longer than
expected. Wait
with rollout of
new
functionality
until you have
a stable
environment
If possible,
reload the data
during Unicode
conversion
(faster).
Hardware
switch removed
a lot of risk and
made the
upgrade faster.
Could have done
this faster, if
business people
had been
scheduled for
testing earlier.
Otherwise
smooth process.
Did not have the
right technical
people involved.
This added 6
weeks to an
otherwise
straight-forward
upgrade.
What Well Cover
7/28/2019 PM2008_UpgradeBI70
53/61
53
What We ll Cover
Why upgradeEnd of support
New support strategy & NetWeaver
New features and capabilities
Creating an upgrade strategy for the futureContent Vs. Technical upgrades
Upgrades with NetWeaver
Planning and Executing the upgradeThe upgrade plan
The business case
Staffing, duration and scope
Examples
Wrap up
Bonus material: ideas for the business case
7 K P i t t T k H
7/28/2019 PM2008_UpgradeBI70
54/61
54
7 Key Points to Take Home
Is it cheaper to upgrade to new content or risk reinventing the wheel?
A BW architecture is part of a larger decision support landscape
An upgrade strategy should contain all NetWeaver components
You upgrade strategy must include both release and content upgrades
Your upgrade time is largely a function of scope, your regression test
strategy and the amount of content in your BW
The BI 7.x upgrade is an extensive one and you should treat it as so.
Cross reference new features & functionality with your organizations
pain pointsand ensure the upgrade costs do not exceed the business
benefits
Wh t i t?
7/28/2019 PM2008_UpgradeBI70
55/61
55
What is next?
do not exceed the business benefits
Resources
7/28/2019 PM2008_UpgradeBI70
56/61
56
COMERIT (presentations, articles, accellerators)
www.comerit.net
The document NW BI 7.x Upgrade master Guide is available at
https://websmp108.sap-ag.de/~sapidb/011000358700005412772005E.pdf
Business content and extractors SAP BI 7.0.3 available at
http://help.sap.com/saphelp_nw04s/helpdata/en/44/16e6f7a6f30d19e10000000a114a6b/
RN_703_en_final.pdf
Component upgrade guide SAP Netweaver BI 7.x ABAP available at
http://help.sap.com
Resources
Your Turn!
http://www.sap.com/index.epx7/28/2019 PM2008_UpgradeBI70
57/61
57
Your Turn!
How to contact me:
Dr. Bjarne Berg
Th B i C f di S id
7/28/2019 PM2008_UpgradeBI70
58/61
58
The Business Case for upgrading Some ideasStrategic:
Timing of releases - BI 7.x is a major BI release - better to absorb it and new technologies now
Technology like Java and EP usage type is mature and stable enough for productive use
All included technologies are the future of SAP software development - unicode, java and portal especially - itis better for the technical team to become experienced in installing and maintaining them in a non critical
application like reporting and data analysis before applying this know-how to mission critical applications like
mySAP ERP 2005/ECC 6.0 (R3)
While BI 7.x has a lot of new technology, much of which has been tested for over ten months, there is no
requirement to convert to newer features on upgrade - BW 3.x content can be migrated scenario by scenario.
Integrated Planning features are the best planning approach
Technical:
Better administration capability thru Netweaver Administrator - and BW load and query statistics have been
redesigned and a cockpit provided which includes better process chain support
Unicode support
The GUI component, used by developers even if end users are 100% web based, is in maintenance and SAP
supported past 2010. In addition, the Visual composer component can be used for development, which mayshorten KPI reporting request turnaround time.
BI capability is integrated into the new ECC - but will likely not be used as an integrated reporting component.
Utilizing the BI 7.x BI usage type allows early adoption and testing of enterprise services
BI Accelerator capable - indexes InfoCube data - acts as super fast aggregate to overcome bad modeling or
design or simply huge data volumes. (hardware based, provided separately)
New additional support for near-line storage of infrequently used data
Th B i C f di S id
7/28/2019 PM2008_UpgradeBI70
59/61
59
The Business Case for upgrading Some ideas
Functional:
Security changes - new model is provider oriented, not the old R3 transactional model - enables
better architecture of security solution for reporting, dashboarding and planning - new securityimplementation has enhanced monitoring, auditing and test tools.
Better linked extract performance - helps with larger volume extracts, consolidated data transfer
Better now before a larger volume of data, larger user community and more content requires
testing or is affected by downtime
Allows greater automation and self service capability, freeing business experts for more
strategic and less daily operational workload. (source SAP What's new in BI 7.x)
Migration towards single user interface (via EP usage type) in place, tested and scalable before
ERP upgrade
One BI Toolset - Report Design takes place in the new BEx Report Designer
Specific new components which may drive a component based business justification: (source: SAPNew Developments in SAP BI)
The Business Case for upgrading Some ideas
7/28/2019 PM2008_UpgradeBI70
60/61
60
The Business Case for upgrading Some ideas
Modeling new features:
remodeling toolbox - change InfoCubes without rebuilding them
enhanced datastore objects (ODS) - write optimized objects enhanced InfoSets (can integrate InfoCubes into join with time dependent Master data)
new, unified datasource definitions
enhanced remote capability - remote master data access without replication
better EDW transformation - graphic UI, simplification of transfer rules, new end and expert
routines
unit conversion - new capabilities during data load and reporting
streamlined Data Flow control definition and process chain build - includes better real-time
data acquisition
new Data Transfer Process (DTP) for better transparency, filtering and parallism in staging, and
delta management
Real time EDW push from XML to PSA vs delta queue
Completely redesigned Administration Cockpit and Statistics for BI runtime, Data load and newData load status stats.
redesigned BW "Warehousing Workbench"
Improved Business Content Analysis - overview, search and analysis capability
New process chain functionality and process types
Better Data quality thru improved error handling
Re-partitioning capability - removes drop and rebuild restriction
The Business Case for upgrading Some ideas
7/28/2019 PM2008_UpgradeBI70
61/61
The Business Case for upgrading Some ideas
Reporting new features: Redesigned Business Explorer Suite of tools... New Query Designer tool is VB, .NET based unicode compliant, and has enhanced UI features. New Query Designer supports multi-selected objects, and has options for BI Integrates planning New report designer tool for better formatted reporting BEx integrated Web Application Design - more model driven with new layout chart and map wizards New Web App designer -new layout elements, web items, chart types (GANTT) and is planning aware Improved intuitive ad-hoc design on the web with better drag and drop PDF based BEx web printing Excel based data entry capability New Information Broadcasting features (query views, formatted reports, data bursting, exception
broadcast, alerts etc) Visual Composer BI kit for modeling BI applications - can integrate heterogeneous DataSources
(OLAP/relational) Planning Improvements - speed of analysis, access to real-time data for forecasting, planning wizard
using roadmap pattern Planning capability built into Query designer - ie queries based on aggregation level can write back to
infoprovider Planning layouts can be done in Web Application designer - create-configure layout, bind data and
configure interaction