© 2004 wellesley information services. all rights reserved. critical considerations for timing,...
TRANSCRIPT
© 2004 Wellesley Information Services. All rights reserved.
Critical considerations for timing, sizing and scoping your SAP BW upgrade
Dr. Bjarne BergLenoir-Rhyne College
Philippe TanguyIBM Global Services
2
What We’ll Cover …
•Why upgrade? What is new? Why should I care?
•Planning the upgradeThe business caseStaffing, duration and scope
•Creating an upgrade strategy for the futureContent upgradesTechnical upgradesLeveraging new featuresThe bigger picture –NetWeaver and Portals
•Questions and Answers
Technology
Integration
Bsuiness
Marketplace
Integrated Analytics
Systems
3
What is New?
One of the major reasons for upgrading your BW environment is the availability of new content and features in the next release.
Let us take a look at what is new in version 3.5:
Business Planning and Simulation Information Broadcaster Data warehousing and Business Intelligence Universal Data Integration Unicode Support BeX Portfolio in Enterprise Portals
We will now take a quick look at these
features
4
What is New - Business Planning and Simulation
You need no installation of SEM add-ons to use the planning functionality with BW 3.5, and you only one software installation.
You can also plan towards totals (i.e. total costs, total revenue) through pre-defined totals in rows or columns.
You can now remove outliers from the plan (unusual data points).
We can handle incomplete time-series with improved BPS functionality
BPS increases the functionality and statistical features
5
What is New - Information Broadcaster
In version 3.5 you can schedule delivery of reports through a variety of methods.
a) Users can schedule reports to be delivered to them through email, portal roles, web based reports (browser & handhelds), and zip files.
b) Reports can be mailed as pre-run or to allow people to execute on-demand.
c) We can trigger the reports to run at:Certain timesWhen data is loaded to the systemOr we can mail it to the users ad-hoc when we want to do it…
BW 3.5 can “push” data to the users, instead of forcing them to “pull” the data
Broadcaster can be run from the web
application designer, BeX Analyzer
and the BeX query designer!!!
6
What is New - Information Broadcaster
What to you need?
SAP NetWeaver Knowledge Manager to do content ratings, searches, feedback, subscriptions and discussions.
Java Repository Manger for pre-calculated KM services, templates and queries, as well as metadata.
Enterprise Portal 6.0
Broadcaster with NetWeaver can create a truly collaborative work environment with more data transparently
7
What is New - DW & Business Intelligence
The Web Application Designer has more features:
The navigational state can be stored in XML format
JavaScript can be used to customize web navigation
Corporate web templates can be reused
New truly advanced chart designer with cool charts and a development wizard (and you can actually read these cool charts!!)
Note
8
What is New - DW & Business Intelligence
New BeX features
Better search features in hierarchies
Improved masterdata display (long text and keys)
Better Analysis Process Designer for classifications, stratification and pre-processing for data mining
Multiple currency types support (i.e. bids middle-rate)
Process chains can call 3rd party load tools and vendors may be certified for open-hub compliance
9
What is New - Universal Data Integration
Universal Data Connect
SAP Non-SAP
BW
BI Java SDK SAP Query JDBC ODBO XML-A
Custom Applications
2. Java connect-
tors
1. Universal Data Connect
3. Java
BW becomes truly an open solution..
10
Universal Data Connect
Universal Data Connect
RFC, BAPI, API JDBC Driver ODBO provider URL/HTTP
SAP Query JDBC ODBO XML-A
R/3 3rd PartyBWRDBMS
Java 2 Enterprise Edition 6.4
BW 3.5
WAS 6.4
UD Connect is based on BI Java connectors
RELATIONAL DATABASES
1. Over 190 JDBC drivers for database connectivity
2. BI SAP Query connector for R/3, SAP CRM ad-hoc connectivity
OLAP
1. BI OLE connector a Microsoft standard
2. BI XMLA connector for web based OLAP sources
11
What is New - Unicode Support
Unicode support for SAP DB, Oracle 9.2, IBM DB2 AS400 UDB, and SQL Server:
BW 3.5 Supports multiple languages through a unicode enabled server (back-end) and a unicode enabled web front-end
For Microsoft based components the “log-on language” is supported
يآلإلقفغ
غяь
фдФ
њщ
Ệẁ תשרחפא ǻǼǽǿ
12
What is New – BeX Portfolio in Enterprise Portal
Business Explorer (BeX) can be used to publish queries to the Portal Content Catalog.
The BeX Portfolio consists of applications that include collaborative information such as:
Technical metadata (run times, descriptions, priority etc)Subscriptions of a reportFeedback of a report (i.e. comments)Rating of report (by users)Report details such as descriptions and use informationMailing of a report to others
The Portfolio is the entry point for BW reports
BeX Portfolio on Enterprise Portal (v.6.0) creates a collaborate way to distribute and work with information
NEWS: B
W w
eb applicatio
ns
are KM O
bjects
13
What is New – BW content in Enterprise Portal
We can publish a BW application in to the SAP Enterprise Portal as:
A Knowledge management object to a collaboration room
A Knowledge management (KM) object to a KM folder
An iView to the Portal Role
An iView to the Portal Content Directory
You don’t have to upload iView files anymore!!!
Source: SAP AG
14
End of support dates and upgrade paths
SAP BW End of standard maintenance
Can be upgraded to
2.0B Feb. 2004 2.1C, 3.0B, 3.1C, 3.50/3.51
2.1C Feb. 2004 3.0B, 3.1C, 3.50/3.51
3.0A Sep. 2002 3.0B, 3.1C, 3.50/3.51
3.0B May 2005 3.1C, 3.50/3.51
3.1C May 2005 3.2 and 3.3 must be applied before 3.5
3.2 ? 3.3 and 3.5
3.3 ? 3.5
3.5 ? 4.0
A direct release upgrade from 2.0B, 2.1C and 3.0B to 3.5 is possible. However an upgrade from 3.1C needs to apply 3.2 and 3.3 content add-ons before
upgrading to 3.5
Source: SAP & intelligence
#1 reason for upgrade:
“Because I had to!”
15
What We’ll Cover …
• Why upgrade? what is new? why should I care?
• Planning the upgrade The business case Staffing, duration and scope
• Creating an upgrade strategy for the future Content upgrades Technical upgrades The bigger picture –NetWeaver and Portals
• Questions and Answers
Technology
Integration
Bsuiness
Marketplace
Integrated Analytics
Systems
16
Planning Your Upgrade
• Determine the business caseUnderstand the content/features provided in the BI
Pack or Technical ReleaseCross reference content/features with your
organization’s “pain points” or needs
&*#@!
Not again!
Month Close
17
Planning Your Upgrade
• Determine the business case
Examples:o Performance issues?o System Admin/Support issues?o End of standard support?o Planning new content roll outs?o Planning new MySAP product roll outs?
Conduct user surveys or focus groups as neededTip
18
Planning Your Upgrade
• Determine the business case“Quantify” and Qualify the benefits of upgrading –
what’s the value (productivity/satisfaction/key measures/etc.)?
Show me the money!
Now (hrs)
New release
Number of objects
Cost per hour
Net Change ($)
Development time ODS 230 160 35 105 257,250$ Development time infocubes 270 190 55 105 462,000$ Development time web reports 40 15 120 105 315,000$ Maintenance time (yr) 3200 1800 1 55 77,000$ Retirement of old architecture 1 190,000$ Cost of new architecture 1 (150,000)$
… -$
… -$
… -$
… -$ Net benefits of upgrade 1,151,250$
Example:
19
Planning Your Upgrade
Examples:o Reduced support – IT Labor cost $avings?o Eliminate redundant work (Cost avoidance)?o Data availability – Time saved closing books/responding to
information requests?o Information “on demand” – Only spend time looking
at/analyzing problem areas (Reporting Agent/Alerts)?o New BI content – Legacy reporting systems consolidations
opportunity/transition expensive R/3 ABAP reports to BW/Implementation time to value?
o Operational necessity?
Quantify any improvements in business
metrics that are important in your company/industryTip
20
Planning Your Upgrade
• Determine the business caseBalance the technical requirement and associated
implementation cost with the derived business benefit
Is the upgrade justified?
$$Upgrade ?
Can you do more with a new release? (I.e. mobile)
21
Planning Your Upgrade
• Scope the projectBased on Business Case, determine and prioritize the
content of your upgrade project(s) o BI Packo Technical Releaseo Leveraging new features
??
22
Planning Your Upgrade
• Scope the projectDetermine your upgrade “readiness” & path
o Conduct a technical review of your existing landscape - Factors to consider…
Number of R/3 & BW Systems – Check Plug in and Support Pack Level requirements for your release of R/3 – multiple R/3s on different releases will drive pre-upgrade effort
MySAP apps – Compatibility/Content – Does an upgrade in one force an upgrade in the other? (e.g. BW 3.1C -> SEM 3.2, BW 3.0B -> CRM 3.0/3.1)
Non SAP Apps – Will custom interfaces/extracts need to be updated? (Benefits of moving to DB Connect?)
23
Planning Your Upgrade
• Scope the projectDetermine your upgrade “readiness” & path
o Conduct a technical review of your existing landscape - Factors to consider…
SAP GUI – New GUI roll out, Patches? (e.g. BW 3.0B/3.1C -> 6.20 BUT… BW 3.5 -> 6.20/6.40 – unless Unicode required)
PC Requirements – Need upgrade to take advantage of new features? BW 2.0/2.1/3.0 - Same PC requirements – but the devil is in the details (see OSS 161993, 66971)
DB/OS – Are they supported on the new release? Take the opportunity to apply patches as needed.
IGS – If need rendering of charts and graphs in BW 3.x Web Applications you need IGS…BUT only runs under NT and W2K. (BW 3.5 will support UNIX until IGS 6.40)
24
Planning your upgrade
•Scope the projectDetermining the requirements for resizing your
Hardware/Infrastructure:o ODS -> Parallel Load = more memory, ODS Layer =
more spaceo Crystal Reports -> new hardwareo IGS -> may require new hardwareo Archiving -> may reduce need for spaceo New content -> more users -> more app servers?
Rerun the SAP Quicksizer – work with HW provider
Tip
25
Planning Your Upgrade
Production
12 CPU
96GB RAM
AppServer
4 CPUs
32GB RAM
Test
4 CPUs
32GB RAM
Development
4 CPUs
32GB RAM
This company reallocated their Sun-6800 box and planned for gigabit connectivity to the AppServer….
More memory allowed them to take better advantage of the parallel load feature of 3.x
Example
26
Planning Your Upgrade
• Scope the projectEstimate your upgrade effort
o Determine your testing strategy
o Don’t forget about end-user training requirements!
o Review level of effort with Basis, Security, Infrastructure, Functional teams, etc.
Example: Basis tasks: allocation of memory, back ups, application of kernal patches, etc.
New licensing requirements/costs? (e.g. Open Hub, Crystal)
27
Planning Your Upgrade
•Scope the projectSample Timeline for a complete landscape with a 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 system and roll out of SAPGui
Upgrade Sandbox system
Test functionality and decide what to implement 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 test)
Note: The duration is driven also by:
1. the number of BW systems in your landscape.
2. The new functionality your are rolling out
3. The support technology needed (I.e. app servers, GUI etc).
28
Planning Your Upgrade
• Staff the projectResource requirements vary based on scope & approachTypical upgrade roles & responsibilities includes:
o 1 Project Sponsor (10%)o 1 Project Manager (50-100%)
Budgets/resources/timelineso 1 BW Architect (50-100%)
Determining strategies/impact analysis/features to be leveraged
o 1-2 BW Analysts (100%) Implementing new features Regression testing
One person may perform more than one role
29
Planning Your Upgrade
•Staff the projectTypical upgrade roles & responsibilities includes:
o 1 Training/Change Management Resource (50%) Updating/Creating Training Material Communications
o 1 SAP Basis (75%) Basis/DBA/OS/Security
o Other R/3 or MySAP Functional (25%) Regression testing
o 1+ Business Analysts (50-100%) Implementing new features
NoteEnsure assigned resources are trained on new release
Is it cheaper t
o
“outs
ource” t
he upgra
de?
30
Planning Your Upgrade
• Sell the Upgrade Project Internally!Compile detailed business case, work plans, budgetsDrum up interest in your business case with the
business/end usersLeverage SAP Service Marketplace for canned demos
of new features/”point of view” on benefits
Whereto
FIND itwww001.sap-ag.de/
31
Planning Your Upgrade
• Sell the Upgrade Project Internally!
Tip
“Use and abuse” SAP BW consultants to support your internal sale (demos, prototypes, expert sessions etc).
32
What We’ll Cover …
• Why upgrade? what is new? why should I care?
• Planning the upgrade The business case Staffing, duration and scope
• Creating an upgrade strategy for the future Content upgrades Technical upgrades The bigger picture –NetWeaver and Portals
• Questions and Answers
Technology
Integration
Bsuiness
Marketplace
Integrated Analytics
Systems
33
Types of Upgrades – BW add-ons
Apply content when you need it to the release you are running!!
Source: SAP & intelligence
The new upgrade strategy from SAP is to provide BW releases and BI content add-ons,
Content releases such as 3.2, 3.3 and 3.51 contains more business content and can be applied via delta upgrade.
The content upgrade can occur in as little as 1-2 hours (per system) and are shipped on supplement CDs.
You do not need to perform a technical upgrade to update the business content
34
Types of Upgrades – BW add-ons
Future upgrade strategies needs to include both content as well as release upgrade plans for BW
Source: SAP & intelligence
The content delivered in add-on 3.5.1 is the same as the content in Release 3.1 with version 3.3. content.
Don't Forget
35
Types of Upgrades – BW Releases
Plan a periodic review of new content before
you build custom solutions
Source: SAP & intelligence
The Technical upgrades are called BW releases.
This include changes and/or additions to technical capabilities such as improved ODSs (ver 2.x) and Process Chains (ver 3.x).
The release 3.5 is a technical release with initial 3.5.1 add-on (business content).
Additional add-ons include:
3.5.3
TBD
3.5.22nd week
of June
3.5.1Rampup
3.5.3
TBD
3.5.22nd week
of June
3.5.1Rampup
Warning
36
An Upgrade Strategy - Example
Aug Sept Oct Nov Dec Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov DecBW 3.5 4.0Content 3.5.1 3.5.2 3.5.3 4.0.1Portal 6.0 Service Packs as availableExchange 3.0 xxxWAS 6.4 xxx
2004 2005
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 also coordinate the patches in the interim periods (i.e. every 3 months or when needed for integration purposes).
Tip
37
The Bigger Picture
Stop looking at infrastructure and technology…
Start looking at the big picture…
How are you going to make it all work together?
And,.. how will you plan your upgrades to make sure it does so in the future?
Source: SAP, Léo Apotheker
38
The Bigger Picture – Why NetWeaver
Enterprises has realized that they cannot create the same “stove-pipe” solutions for their decision support systems as existed for transactions systems prior to the ERP revolution.
They have also realized that business is not data driven, but event driven
The question has been… “How do I integrate it all to my job role?”
Source: SAP AG
Role-basedUser Interfaces
ATPATPPricePrice
CompositeBusinessScenarios
FocusedOperational "Nodes"
Delivery delayDelivery delayService requestService request
39
The Bigger Picture – NetWeaver ??C
OM
PO
SIT
E A
PP
LIC
AT
ION
FR
AM
EW
OR
K
PEOPLE INTEGRATION
Multichannel access
Portal Collaboration
INFORMATION INTEGRATION
Bus. Intelligence
Master Data Management
Knowledge Mgmt
PROCESS INTEGRATION
Integration Broker
Bus. ProcessMgmt
APPLICATION PLATFORM
J2EE
DB and OS Abstraction
ABAPL
IFE
CY
CL
E M
AN
AG
EM
EN
T
...
CO
MP
OS
ITE
AP
PL
ICA
TIO
N F
RA
ME
WO
RK
PEOPLE INTEGRATION
Multichannel access
Portal Collaboration
INFORMATION INTEGRATION
Bus. Intelligence
Master Data Management
Knowledge Mgmt
PROCESS INTEGRATION
Integration Broker
Bus. ProcessMgmt
APPLICATION PLATFORM
J2EE
DB and OS Abstraction
ABAPL
IFE
CY
CL
E M
AN
AG
EM
EN
T
CO
MP
OS
ITE
AP
PL
ICA
TIO
N F
RA
ME
WO
RK
PEOPLE INTEGRATION
Multichannel access
Portal Collaboration
INFORMATION INTEGRATION
Bus. Intelligence
Master Data Management
Knowledge Mgmt
PROCESS INTEGRATION
Integration Broker
Bus. ProcessMgmt
APPLICATION PLATFORM
J2EE
DB and OS Abstraction
ABAPL
IFE
CY
CL
E M
AN
AG
EM
EN
T
...
NetWeaver consolidates the integration of processes, information and people.
NetWeaver is a set of solution components that provides a comprehensive architecture that actually works together!!!
Source: SAP AG
40
The Bigger Picture – How Do you get Access?
• Ramp-up is SAP’s way to bring new products to market (all SAP products).
• Ramp-up is really a “controlled release” of a new product. Once no longer restricted, a product can be acquired by anyone.
• You can apply to the ramp-up program through:
SAP Service Marketplace alias /nw04SAPnet alias /nw-ramp-up
Whereto
FIND it
41
The Bigger Picture – Ramp-up
• BW 3.5 is part of the NetWeaver 04 Ramp-up• 3.5 unrestricted access is scheduled for 3rd quarter-
04.
What is included in NetWeaver-04 ramp-up? BW 3.5 Portal 6.0 Service Pack 3 Exchange Infrastructure 3.0 MI 2.5 Web Application Server 6.4
Companies in Ramp-up can go-live with the product!!
42
Resources
Getting access:SAP Service Marketplace alias /nw04SAPnet alias /nw-ramp-up
Demos of new contentwww001.sap-ag.de/
Collaboration roomhttp://sap.ittoolbox.com
Resource
HiddenBonus
Good
Thing
43
7 Key Points to Take Home
• Look at new features and functionality. 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 must contain more then single NetWeaver components
• You upgrade strategy should include both release upgrades as well as content upgrades
• Cross reference new features & functionality with your organization’s pain points…and ensure the implementation costs do not exceed the business benefits
• Include any needed hardware/infrastructure upgrade costs in your estimates
• Your upgrade time is largely a function of scope, your regression test strategy and the amount of content in your BW