Sie sind auf Seite 1von 73

2004 Wellesley Information Services. All rights reserved.

Gary Elwick
Deloitte Consulting
A Technical Guide to
Planning Your R/3
Upgrade Project
2
What Well Cover
People
! Who gets involved, when, and how do they help
! What training is required and how to identify needs
Process
! Understanding the total scope
! Understanding technical upgrade approach
! General guiding principles for upgrade planning
Technology
! Aligning technology with the business requirements
! Impact assessment, landscape inventory
! Accelerators
! Key upgrade considerations
Project management
! Upgrade planning and challenges
Wrap-up
3
What Well Cover
People
! Who gets involved, when, and how do they help
! What training is required and how to identify needs
Process
! Understanding the total scope
! Understanding technical upgrade approach
! General guiding principles for upgrade planning
Technology
! Aligning technology with the business requirements
! Impact assessment, landscape inventory
! Accelerators
! Key upgrade considerations
Project management
! Upgrade planning and challenges
Wrap-up
4
Skills Required
Technical business champion
! Who CIO/CTO
! Role Ensure that project meets business and technical
requirements. Can also ensure that resources are backfilled and
dedicated to the project.
Technical project manager/team lead
! Role manage schedule and enable interactions with various teams
! Build and manage the technical project plan
Hosting partner
! Role provide contracted support
!OS administration
!Database administration
! Must be involved early in planning
5
Skills Required (cont.)
Basis
! Role work with hosting partner and technical teams to build
and execute detailed cutover cookbook
IT support
! Role work with the technical team lead to ensure that
infrastructure-related tasks are defined and completed
according to the plan
!Networking
!Job scheduling
!Technical infrastructure
!Disaster recovery
!ABAP programming
6
Technical Team Management
Dedicated team
! Make sure key resources are dedicated full time to the project
! Ensure that they are backfilled
Location of team
! Co-locate team with functional teams at each location
! Utilize existing help desk procedures to manage issues and
transports
! Global implementation
!Follow-the-sun support
o Multiple Basis teams to support global
development/testing
! Single country
!Ensure that Basis team is split among time zones to
ensure coverage
7
What Well Cover
People
! Who gets involved, when, and how do they help
! What training is required and how to identify needs
Process
! Understanding the total scope
! Understanding technical upgrade approach
! General guiding principles for upgrade planning
Technology
! Aligning technology with the business requirements
! Impact assessment, landscape inventory
! Accelerators
! Key upgrade considerations
Project management
! Upgrade planning and challenges
Wrap-up
8
What Types of Training Are Required?
The magnitude of the upgrade will greatly influence the
types and amount of training required
3.1 to ERP:
! New menus replace the standard reporting tree
! New transactions and processes
! Modified transaction codes and screens
! A complete change in basic navigation
4.5 to Enterprise:
! New transactions
! Modified transaction codes and screens
! Modified folders and menu paths
4.6C to Enterprise:
! Minimal changes to screens and architecture
9
Focus on High-Impact Areas for Training
Three key factors will help you identify the impact of a process:
Frequency of execution
! A key consideration in the timing of your training
! May indicate a need for reference materials
Complexity of the process
! May drive the need for interactive or instructor-led training
! Could indicate a need for repetition and follow-up to ensure the process is
fully understood
Risk of performing the process incorrectly
! Drives the importance of the training
! Indicates the need to reinforce the training and possibly use multiple delivery
methods
10
Curriculum Training Development and Delivery Options
Transaction scenarios via Web-based
performance support tool
Communication (go-live manual)
Low impact
Quick Reference Cards
Transaction scenarios
Communication and workshops pre-
training
Medium
Impact
Simulations
Quick Reference Cards
Transaction scenarios
Communication and expert led
Workshops pre-training
Labs post-go-live
Delta basic navigation
High impact
High impact = 50% change in data entry experiences/steps or processes
Medium impact = 20% to 50% change in data entry experience/steps or process
Low impact = Under 20% change in data entry experience/steps or process
# of users
! Greater than or less
than 100?
Location of users
! Users all in one region?
! Global users?
Complexity
! Is the transaction
complex or standard?
Risk
! What is the risk of
incorrect execution?
Weighting Factors
11
Curriculum and Content Development
Key to developing upgrade course curriculum
! Ensure high-impact transactions are identified:
!High-impact transactions are the basis for an upgrade
curriculum
! Identify and document roles by work steps
! Group training content into modular units
! Combine modular units into courses
! Determine appropriate delivery method
Delta training course content includes
! System navigation
! Changes to existing functionality
! New functionality (if any)
! Summary of improvements
12
What Well Cover
People
! Who gets involved, when, and how do they help
! What training is required and how to identify needs
Process
! Understanding the total scope
! Understanding technical upgrade approach
! General guiding principles for upgrade planning
Technology
! Aligning technology with the business requirements
! Impact assessment, landscape inventory
! Accelerators
! Key upgrade considerations
Project management
! Upgrade planning and challenges
Wrap-up
13
SAP Component Inventory
R/3
Bolt-ons
Vertex
Faxing
EDI
Shop floor
LIMS
EAI tools
SRM
CRM
Company
Web site
APO
BW
Supplier
Portal
All components related to R/3 must be investigated
! Release dependencies
!SAP certification
! New business functionality
! Product upgrade sequencing
!Do they have to be upgraded in a specific sequence?
!Can some bolt-ons/components be upgraded before the upgrade?
Customer
Portal
SAP GUI
14
System Objects Within Each Component
Each component needs to be evaluated for business as well
as system components that will change
! Custom developments now replaced by core SAP functionality
! Changes in business process, based on improved capabilities
15
What Else Do I Need to Look Out for?
Archiving
!Poorly maintained system tables (APQD, ARFC, etc.)
!Major impact on downtime processing
Changes to architecture
!Database upgrades
!Hardware refresh or upgrade
!Operating system upgrades/patches
Upgrade and cutover considerations
!Operating system/database changes to support 64-bit architecture
!Timing of these changes is critical to success
!How much can be prestaged?
!What must happen during the upgrade?
!Detailed procedures must be included in the upgrade cookbook
!Ensure that these changes are accounted for in the cutover plan
16
What Well Cover
People
! Who gets involved, when, and how do they help
! What training is required and how to identify needs
Process
! Understanding the total scope
! Understanding technical upgrade approach
! General guiding principles for upgrade planning
Technology
! Aligning technology with the business requirements
! Impact assessment, landscape inventory
! Accelerators
! Key upgrade considerations
Project management
! Upgrade planning and challenges
Wrap-up
17
Traditional Projects vs. SAP Upgrades
Traditional projects
Heavy analysis and design
Testing does not start until the realization phase
New user community
New user training
Estimating model is based on longer development hours
18
Traditional Projects vs. SAP Upgrades (cont.)
SAP upgrade projects
Limited or no design activities
Testing starts immediately
No data conversations
Limited impact to configurations
Delta training
Limited or no new users
SAP-savvy team
Estimating model is based on fixing objects typically shorter
duration
19
Evaluate Your Options and Decide on an Approach and Strategy
Starting
position
Starting Starting
position position
" Making the new release
work
Pure technical Pure technical
upgrade upgrade
" New release along with
significant functionality
and process improvements
Technical and Technical and
functional functional
" New release along with
significant release
functionality, process
improvements, and some
new modules or component
additions
Technical functional Technical functional
and enhancements and enhancements
O
P
T
I
O
N
S
" Technical upgrade with the
replacement of
workarounds by new
release functionality
Technical and basic Technical and basic
functions functions
2
1
3
4
20
Project Time/Effort Drivers
" Breadth of functionality implemented
" Number of SAP modifications
" Number of custom programs
" Number of interfaces
" Number of bolt-ons
" Geographic scope
" Number of users
" Breadth of functionality implemented
" Number of SAP modifications
" Number of custom programs
" Number of interfaces
" Number of bolt-ons
" Geographic scope
" Number of users
F
A
C
T
O
R
S
F
A
C
T
O
R
S
#Several factors have an
impact on the complexity of
the upgrade project and the
length of time required to
perform it
LEVEL OF COMPLEXITY
LEVEL OF COMPLEXITY
LOW
MEDIUM
HIGH
Upgrade estimates (months)
Medium complexity (~4+ months)
Low complexity (~2.5+ months)
High complexity (~7+ months)
21
What Drives Complexity and Risk for an Upgrade Project?
Factors influencing complexity and risk:
Technical complexity (SAP and others)
SAP functionality
Resources (constraints, skill levels)
Upgrade strategy employed
Stability of current environment
Level of knowledge in user community
Business case
Project funding
Organization burn-out (too many projects, too
fast)
Organization changes/other initiatives
Level of support required for other key and
competing business events
Project
complexity
and Risk
Low
complexity
Medium
complexity
High
complexity
Drives
22
What Well Cover
People
Process
! Understanding the total scope
! Understanding technical upgrade approach
! General guiding principles for upgrade planning
Technology
! Aligning technology with the business requirements
! Impact assessment, landscape inventory
! Accelerators
! Key upgrade considerations
Project management
! Upgrade planning and challenges
Wrap-up
23
Focus in Five Areas Will Help to Ensure Success
# ASAP upgrade methodology
# Tools and techniques
# Upgrade training
# Leadership and project planning
# Education and training
# Roles and responsibilities/accountability
# Expertise and skills in new release
# Sponsorship/leadership
# Justification and benefits
# Transition plan/
change management
# Communication plan
# Client landscapes
# Networks/telecom
# Technical standards
# Change control
# Interfaces, enhancements,
and reports
Organization
and staffing
Methods
and tools
Technology
infrastructure
Change
imperative
$A $B $C
Project
Integration
Implementation
process
# Deliverable
specifications/templates
# Project management
# Progress to plan
measurement
# Quality assurance
# Testing strategy
24
What Key Things Must the Technical Team Understand?
Key business constraints
! Drives upgrade timeline
! Drives downtime window
! Drives recovery approach and alternatives
Training requirements and schedules for end users
! Drives sizing for training instance
! Drives refresh schedule and approach
Approach for business ramp-down/ramp-up
Ancillary system upgrade requirements
! Drives team size
! Drives cutover coordination
25
What Key Things Must the Technical Team Understand? (cont.)
Technology baseline
! Drives hardware upgrade decisions
! Drives software upgrade decisions
! Drives lease vs. purchase decision for interim hardware
requirements
Current system performance characteristics
! Drives transaction watchlist
! Drives end-user expectations
Functionality baseline
! Drives scope of the upgrade
! Drives interface touch points and timing
26
Impact on Industry Solutions
Review product availability matrix for your industry
! Match business requirements to product availability
! May impact timing of the upgrade
! May impact which new release is targeted
Review release notes for your industry
! Determine which new functionality is relevant
! What core business processes have changed
Review installation and master guides for your industry
! Determine product relevance
! Determine product update sequencing
! Identify relevant upgrade notes
27
What Well Cover
People
! Who gets involved, when, and how do they help
! What training is required and how to identify needs
Process
! Understanding the total scope
! Understanding technical upgrade approach
! General guiding principles for upgrade planning
Technology
! Aligning technology with the business requirements
! Impact assessment, landscape inventory
! Accelerators
! Key upgrade considerations
Project management
! Upgrade planning and challenges
Wrap-up
28
Match Upgrade Approach to Business Drivers
Downtime minimized vs. resources minimized
! Downtime minimized tradeoffs
!Creates shadow instance
!Requires additional disk and CPU during the upgrade
o Approximately 40% additional disk for the shadow image
o Additional CPU to minimize the effect on uptime
processing
!Reduced downtime for the business
! Resources minimized tradeoffs
!Minimal hardware changes
!Increased business downtime
Involve the business senior leadership in this decision
! Be upfront about the tradeoffs
! Set realistic expectations
29
Functional Impact Analysis
Business Business
Requirements Requirements
SD SD MM MM FI FI CO CO WM WM QM QM PP PP
SD SDMM MM FI FI CO COWM WMQM QMPP PP
Pr oc ess Fi l t er i ng
Pr oc ess Fi l t er i ng
Test scripts and Test scripts and
business processes business processes
SAP 3.x SAP 3.x- -4.6 4.6
SAP 4.7 SAP 4.7
Business requirements
! How can I upgrade faster and be
cost effective?
! How big will the upgrade be?
! How many changes have we
made and to what modules?
! How will the upgrade impact our
environment?
! How can I reduce my risks?
New SAP functionality
! Old custom code replaced by
new SAP core functionality
! SAP business process change
! Change in screen flow
30
Technical Object Inventory
What needs to be considered
! Objects active and not released
!Data Dictionary objects and structures
!Programming objects and structures
! Central address management
! Function groups
! Function modules
! Message classes
! Program includes
! Reports
! SAPscript
! Structures
! Transactions
! Repair objects
31
Landscape Inventory
AS-IS landscape
! Hardware inventory
! Instance inventory
!Current maintenance/refresh strategy
!Current client/transport strategy
! OS releases and patch levels
! Database releases and patch levels
! Basis Support Package levels
! SAP kernel patch levels
32
What Well Cover
People
! Who gets involved, when, and how do they help
! What training is required and how to identify needs
Process
! Understanding the total scope
! Understanding technical upgrade approach
! General guiding principles for upgrade planning
Technology
! Aligning technology with the business requirements
! Impact assessment, landscape inventory
! Accelerators
! Key upgrade considerations
Project management
! Upgrade planning and challenges
Wrap-up
33
Technical Impact Analysis
Basis Basis Modifications Modifications
Security Security Training Training
Technical Technical
Requirements Requirements
Security Profiles, ABAP Security Profiles, ABAP
programs and training approach programs and training approach
Tec hni c al Ac t i vi t y Fi l t er i ng
Tec hni c al Ac t i vi t y Fi l t er i ng
Capacity/
Performance
User exit
points
Different in
4.5/4.6/4.7
Where
change
occurred
Basis Basis Modifications Modifications Security Security Re Re- -Training Training
The challenge
! Incomplete inventory of
system modifications
! Dependence on tribal
knowledge
How do I reduce the risk
! Upgrade pre-assessment
! Reliable and comprehensive
prediction of which objects
will impact the upgrade
Now lets see how this works!
34
What to Look for in a Pre-Assessment Tool
It helps achieve a faster and better upgrade by:
! Detecting potential failure points in custom programs
! Recommending corrective actions for the potential failure points
! Providing data regarding SAP repairs
! Providing work-in-progress data of custom programs
! Facilitating implementation of code-freeze strategy during the
upgrade
! Providing data for effort estimation
! Aiding in resource planning and project scheduling, thus
minimizing downtime
35
SETUP INVENTORY ANALYSIS REPORTS
Custom Program Inventory to Determine Scope and Complexity
36
SETUP INVENTORY ANALYSIS REPORTS
Extensive Reporting with Drill-Down Capabilities
37
INVENTORY CAMS WIP CORE MOD UPGRADE VERSION
Determine Work-In-Progress for Implementing Code-Freeze Strategy
38
INVENTORY CAMS WIP CORE MOD UPGRADE VERSION
SAP Modifications List
39
Pre-Assessment Tool Features
Version independence: Accelerates upgrades for any given
choice of source and target versions
Product independence: Addresses upgrades for SAP new
dimension products such as APO, BW, and CRM over and
above R/3
Upgrade scope: Upgrades any product developed on SAPs
ABAP Workbench
Deployment: Deploy with minimal resources (people,
hardware, software); least invasive on the SAP system
40
More Tool Features
Easy interface: Easy-to-use user interface and online
help
Accurate estimation: Analysis data to generate effort
estimates and project schedules for the upgrade
Continuous defect tracking: Defect tracking over the life
cycle of an upgrade
Statistical analysis: Data for Pareto and cause-and-effect
analysis
41
Technical Impact Analysis
Basis
! Identify OS/DB upgrades required
! 64-bit impact (if coming from 32-
bit)
! Hardware sizing
! Perform SAP functional upgrade
check
! Upgrade procedures or cookbook
!Start from initial upgrade
!Should be detailed enough to
allow any Basis team member
to perform any step
!Need to be integrated into the
cutover plan
! Gather performance baseline from
current system
Basis Basis Mods Mods Security Security Training Training
Technical Technical
Requirements Requirements
Security Profiles, ABAP programs Security Profiles, ABAP programs
and training approach and training approach
Tec hni c al Ac t i vi t y Fi l t er i ng
Tec hni c al Ac t i vi t y Fi l t er i ng
Capacity/
Performance
User
exit
points
Different in
4.5/4.6/4.7
Where
change
occurred
Basis Basis Mods Mods Security Security Re Re- -Training Training
42
Sample Project Timeline 20 Weeks
Prep
Go-Live
Fit/gap
Unit test
Integration
Test Cycle 1
Integration
Test Cycle 2
End-user
training
Prod
cutover
Cutover
rehearsal
5
wks
2
wks
4 wks 3
wks
3 wks
Integration
Test Cycle 3
3
wks
Week 0 Week 2 Week 7
Week11 Week 14
Week 17 Week 20 System Live
43
What Well Cover
People
! Who gets involved, when, and how do they help
! What training is required and how to identify needs
Process
! Understanding the total scope
! Understanding technical upgrade approach
! General guiding principles for upgrade planning
Technology
! Aligning technology with the business requirements
! Impact assessment, landscape inventory
! Accelerators
! Key upgrade considerations
Project management
! Upgrade planning and challenges
Wrap-up
44
Solution Manager
http://service.sap.com/roadmaps
45
Solution Manager Whats Available with SAP Upgrade Roadmap
46
Rapid SAP Upgrade Approach
Upgrade project pre-planning
! Address technical and environment requirements
! Conduct the assessment process
! Identify any high-level business process improvements
! Assess short-term and long-term directions
! Environment requirements and necessary hardware and software
! High-level scope and plan
! Completed upgrade assessment document
! Impact on people, their jobs, roles, and responsibilities
XD I ndi a Del oi t t e
Consul t i ng
Sui t e of
Mul t i -Di mensi onal
Anal ysi s &
Resol ut i on
Tool set
Sui t e of
Mul t i -Di mensi onal
Anal ysi s &
Resol ut i on
Tool set
-Satbir Kohli
47
Rapid SAP Upgrade Approach (cont.)
Project preparation
! Define the upgrade scope and project plan
! Establish the project organization and standards
! Define new roles and responsibilities for all team members
! Perform technical and security requirements planning
! Analyze the present environment contents
! Perform the necessary upgrade preparations
! Decide on tools, templates, and documentation standards for the project
48
Rapid SAP Upgrade Approach (cont.)
Business blueprint
! Inventory a list of interfaces, reports, data conversions, and third-party
tools
! Inventory a list of security profiles and activity groups
! Revisit business processes and determine which processes are within
the scope of the project
! Review new functionality and document new functionality impacts
! Locate all test scripts and update as needed
! Identify all new, changed, and deleted transactions as a result of new
release functionality
! Finalize the upgrade project scope
49
Rapid SAP Upgrade Approach (cont.)
Realization of DEV and QA
! Upgrade the DEV and QA environments
! Perform configuration and technical changes
! Conduct functional and technical integration tests
! Delta training preparation and delivery
! GUI rollout/desktop deployment
! Implement security strategy
! Prepare production support
! Create end-user documentation and training materials
50
Rapid SAP Upgrade Approach (cont.)
Realization of production
! Finalize documentation and training
! Revise/create documentation and training materials
! Perform end-user training focused on change areas
! Conduct stress tests
! Apply hot packages, OSS notes, and configuration changes
! Communicate the plan to end users
! Execute the production cutover plan
51
Rapid SAP Upgrade Approach (cont.)
Go-live and support
! Upgrade the production system
! Maintain a support organization for the short and long term
! Create policies and procedures for handling support calls
! Manage the roles and responsibilities of your support team
! Educate end users on the support process
! Obtain written signoff for the productive system
52
What Well Cover
People
! Who gets involved, when, and how do they help
! What training is required and how to identify needs
Process
! Understanding the total scope
! Understanding technical upgrade approach
! General guiding principles for upgrade planning
Technology
! Aligning technology with the business requirements
! Impact assessment, landscape inventory
! Accelerators
! Key upgrade considerations
Project management
! Upgrade planning and challenges
Wrap-up
53
Which Functionality Changes Are Important
What changed from release to release
! Review release notes at http://service.sap.com
! Review the Enterprise functional deltas spreadsheet
!http://service.sap.com/developmentnews
54
Technical Upgrade with Delivered Functional Changes
LEVEL OF COMPLEXITY
LEVEL OF COMPLEXITY
LOW (~2.5 mths)
MEDIUM (~4 months)
HIGH (~8 months)
Upgrade Estimates (Months)
Drivers:
! SAP support is expiring soon
! Limited resources required for upgrade
! Low risk of failure
! Limited funding
! Provide the minimum platform for future projects and functionality
Delta functionality focus
! Core business processes
! Technology changes (SAPGUI, 64-bit vs. 32-bit, development changes)
55
Drivers:
! Replace enhancements and work arounds with newly available
functionality
! Leverage new SAP functionality to meet additional business
requirements
! Gain efficiencies by consolidating the upgrade and functionality
improvements into a single project
Delta functionality focus
! Core business functionality
! Changes in key business processes
! Technology changes (SAPGUI, 64-bit vs. 32-bit, development changes)
LEVEL OF COMPLEXITY
LEVEL OF COMPLEXITY
LOW (~2.5 mths)
MEDIUM (~4 months)
HIGH (~8 months)
Upgrade Estimates (Months)
Technical and Functional
56
Technical, Functional, and New Components
Drivers:
! Implement grand vision
! Industry-driven new business requirements
! Combine initiatives into a single funding request
Delta functionality focus
! Core business functionality
! Updates to business blueprint
! Technology changes (SAPGUI, 64-bit vs. 32-bit, development changes,
additional components, replacement, or enhancement of portals)
LEVEL OF COMPLEXITY
LEVEL OF COMPLEXITY
LOW (~3 mths)
MEDIUM (~6 months)
HIGH (~8 months)
Upgrade Estimates (Months)
57
What Well Cover
People
! Who gets involved, when, and how do they help
! What training is required and how to identify needs
Process
! Understanding the total scope
! Understanding technical upgrade approach
! General guiding principles for upgrade planning
Technology
! Aligning technology with the business requirements
! Impact assessment, landscape inventory
! Accelerators
! Key upgrade considerations
Project management
! Upgrade planning and challenges
Wrap-up
58
Inputs for Improving the Planning Process
Inventory the following
! Interfaces between various system components (SAP-legacy,
Internal-external)
! Enhancements
! Modifications (repairs) to standard SAP-delivered code
Data conversion requirements (if any) as a result of upgrade
Dependencies between components, special requirements
(e.g., application of certain Support Package, Conflict
Resolution Transports (CRTs) for industry solutions, etc.)
Sequence/order of upgrading in case of multiple SAP
components (e.g., does Supply Chain Management and/or
Customer Relationship Management need to be upgraded at
the same time or can be done with a time gap)
59
Inputs for Improving the Planning Process (cont.)
Evaluate training needed for the support team as a result of
upgrade changes
Determine if any architectural changes would be required as a
result of upgrade
Additional technology and tools that would help in reducing the
system downtime
! (e.g., SAN copy and snapshot tools, capacity on lease/demand, etc.)
Size of database and additional space requirements
! Potential increased/additional hardware capacity for maintaining
production performance
Additional licensing requirements as a result of upgrade
software or hardware capacity changes
! (e.g., adding CPUs to database system can require additional database
licenses to be procured)
60
Keys to Success: Project Management
Early executive and user sponsorship is essential
Allow turnaround time for SAP issues to be resolved
Determine early in the project the tolerance for
downtime. This will help establish targets and determine
which approach is required.
Frequent end-user and business sponsor
communications
Manage the production cutover and the effect on the
production environments (interfaces, business
processes, and users)
61
Keys to Success: Development
Leverage pre-assessment tools to identify the impact of
the development objects
Manage production support changes against the
upgrade project (synchronize changes)
Experienced developers must be dedicated to the project
to resolve issues
! Ensure that they are backfilled by the business
Test interfaces, Data Dictionary changes, and user exits
62
Keys to Success: Testing
Thorough testing is required at all levels (technical,
training, functional, security)
Ensure that business process scripts are updated and
represent accurate testing actions
Retest interfaces, reports, batch schedule, printers,
electronic output, printing, faxing, and other interface
software
Remember, upgrade testing is no different than a normal
project test cycle
At least one rehearsal upgrade using a copy of
production will be needed between integration testing
and go-live
63
Keys to Success: Functional Approach
Retire SAP repairs where possible (resort back to standard
SAP)
Review SAP release notes
Clearly identify impact of new functionality (conduct fit/gap
analysis)
Prepare scenarios to regression test the upgraded version
Identify functionality workarounds early in the upgrade
process
Ensure functional team members available to unit test when
objects have been reconciled with changes
64
Keys to Success: Basis
Do not underestimate the impact of Support Packages or
support stacks
Plan the system landscape and transport path
Ensure transports are synchronized with the production
support system
Plan and communicate the new GUI rollout and desktop
deployment strategy
Leverage additional technology and tools that would help
reduce the system downtime (e.g., SAN copy and snapshot
tools, capacity on lease/demand, etc.)
65
Keys to Success: Security Team
Consider new functionality (Profile Generator)
Analyze release notes for new transaction codes
Test the security and authorizations during the testing
phase of the upgrade
Leverage the security team to control Business Ramp-
Down/Ramp-Up
66
Keys to Success: Training
Revise/create documentation and training materials
Perform end-user training before the production upgrade
Develop a strategy for delta training for each degree of
change
Define a process by which business (super users,
functional teams) reviews and tests both business
scripts and training materials
67
Upfront Planning to Maximize Technology
Create plan for evaluating new 64-bit technology
! Memory management in the DB server
!Leverage the additional memory available with 64-bit DB
!Reduce physical reads to the DB
! Memory management in the application servers
!Use SAPPFPAR to take maximum advantage of available
memory (64-bit kernel)
! Enhanced DB capabilities
!Dynamic SGA (Oracle)
!Cost-based optimizer (Oracle)
!Split mirror backups to reduce the impact of backups
68
Archiving Considerations
Archiving data prior to the upgrade can have a major
effect on both the downtime and uptime durations
Refer to Archive Quick Wins for Upgrades on
http://service.sap.com/upgrades
! Authors: Claudia Huber, Karl Lang, Egon Muller
Other tables to look for:
! APQD If this table has not been maintained properly it will
have a large impact on the upgrade during the downtime
phase
! Must be cleaned up before you begin the uptime phase of the
upgrade
69
What Well Cover
People
! Who gets involved, when, and how do they help
! What training is required and how to identify needs
Process
! Understanding the total scope
! Understanding technical upgrade approach
! General guiding principles for upgrade planning
Technology
! Aligning technology with the business requirements
! Impact assessment, landscape inventory
! Accelerators
! Key upgrade considerations
Project management
! Upgrade planning and challenges
Wrap-up
70
Resources
SAP
! http://service.sap.com/upgrade
! http://service.sap.com/roadmaps
! http://service.sap.com/solutionmanager
! http://service.sap.com/developmentnews
! SAP Master Guides
Deloitte
! http://www.deloitte.com/us
71
7 Key Points to Take Home
Get senior executive and management support
Staffing the right type, the right number, at the right time, with
right skills
! Ensure that key staff members are dedicated to the
upgrade and backfilled by the business
! Competing initiatives can increase the complexity of the
upgrade project and introduce resource contentions
Upgrades involve a high degree of task interdependence with
high front-end load of critical activities
You can never test too much
72
7 Key Points to Take Home (cont.)
Dont underestimate the effort required to handle
modifications, enhancements, and interfaces
At least one rehearsal upgrade using a copy of production will
be needed between integration testing and go-live
Create a repetitive process from the start. Timing and
synchronization is critical. Upgrade each environment exactly
they way you would upgrade production
73
Your Turn!
Questions?
How to contact me:
gelwick@deloitte.com