SAP Business Suite

Getting Started with an Upgrade

Value Potential, Best Practices,
and SAP Recommendations
CONTENT
^ 4 Why Upgrade Your SAP
Software?
4 Upgrade As an Opportunity
^ 6 Identifying the Value
Proposition and Justifying
the Upgrade
6 Discovery Process
8 Essentials of an Upgrade
Justification
9 Reasons for Upgrading
9 Risk of Postponing an Upgrade
10 Operational Excellence
16 Business Strategy
19 Sustainability
20 Total Cost of Ownership
^21 Planning an Upgrade
21 Assessing the Impact of the
Upgrade on Your Existing
­Solution
22 Technical Prerequisites and
Limitations
22 Upgrade Paths for SAP
Business Suite Applications
24 Upgrade Paths for Unicode
26 Scheduling an Upgrade
26 Determining an Upgrade
­Strategy
26 Phase 1: Technical Upgrade
27 Phase 2: Functional Enhance-
ments (New Functionality)
27 Phase 3: Enterprise Services
(Strategic Enhancements)
27 Cost and Effort Estimation
28 Project and Risk Management
28 Success Factors
28 Standards and Procedures ^37 Tomorrow’s Solution Today
28 Project Duration and 37 Key Messages for IT Decision
­Sequencing Makers
29 Upgrade Management Tools 37 Key Messages for Project
and Assistance Managers and Technical Project
29 SAP Solution Manager Leaders
30 SAP Upgrade Road Map 38 Further Information
31 External Assistance 38 Upgrade Information Center
38 Community Network
^32 Executing an Upgrade 38 Help Portal
32 IT Infrastructure Adjustments 38 Upgrade Competency Centers
32 Resizing the Application Server 39 Identifying the Value Proposition
32 Deploying New SAP Front-End and Justifying the Upgrade
Components 40 Planning an Upgrade
33 Making Network Adjustments to 42 Executing an Upgrade
Maintain System Performance 45 Public Information Sources
33 Upgrading or Migrating Your
Operating System and Data- ^46 Index
base Platform
33 Converting to Unicode
33 Technical Deployment
33 Benefits of System Switch
Technology
33 Enhancement Package Installer
33 Minimizing Downtime
34 Application and Modification
Adjustments
35 Adjustments to SAP Software
Modifications
35 Adjustments to Custom
­Developments
35 Upgrade Customizing for
­Existing Business Processes
35 Adjustments to Interfaces or
Connected Applications
35 Testing
36 User Training
Why Upgrade Your SAP® Software?
An Opportunity to Maximize the Value
of Your SAP Investment
As the business world changes, SAP
develops new releases of its software
to accommodate your organization’s
evolving business needs and help you
remain competitive. In line with this
strategy, SAP has introduced the
SAP® Business Suite 7 software. SAP
Business Suite provides better insight
and visibility across organizations,
improves operational efficiency and
effectiveness, and increases the flexi-
bility to address business change.
SAP Business Suite 7 is a set of SAP
applications supporting a wide range
of industry and business support pro-
cesses for large enterprises, with a
stable core and the infrastructure for
continuous, minimally disruptive innova-
tion. The applications include these
go-to releases:
• SAP ERP 6.0 with SAP enhancement
package 4
• SAP Customer Relationship
Management (SAP CRM) 7.0
• SAP Supplier Relationship
Management (SAP SRM) 7.0
• SAP Supply Chain Management
(SAP SCM) 7.0
• SAP Product Lifecycle Management
(SAP PLM) 7.0
• Industry applications and supplemen-
tary applications
*This document contains the most current information on SAP’s release strategy for the product portfolio for large enterprises. Corresponding
documents for the product release strategy for small businesses and midsize companies can also be found at www.service.sap.com/releasestrategy.
In addition, a release strategy brochure is provided that focuses on the SAP® BusinessObjects™ portfolio of solutions. All three brochures are designed
to give SAP customers, salespeople, consultants, and partners a comprehensive view of the SAP portfolio, its release and maintenance strategy, and
the corresponding release plans.
4 Getting Started with an Upgrade
SAP Business Suite 7 synchronizes
all applications into one united release
strategy and schedule that is docu-
mented in SAP’s Release Strategy
for Large Enterprises
(www.service.sap.com
/releasestrategy).*
SAP will use enhancement packages –
introduced with SAP ERP 6.0 – to deliv-
er minimally disruptive innovation for all
core applications. SAP enhancement
package 5 for SAP ERP 6.0 and SAP
enhancement package 1 for each of
the other SAP Business Suite core
applications are planned to be in unre-
stricted shipment in 2010. In addition,
SAP will continue to deliver new and
improved functionalities through new
releases of the industry applications
and supplementary applications. With
SAP enhancement packages, you can
deploy SAP Business Suite software in
a stepwise manner to address specific
business challenges along your own
timelines and without costly upgrades.
SAP ERP 6.0 with SAP enhancement
package 4 is part of SAP Business
Suite 7. An upgrade to SAP ERP 6.0 is
the natural first step to create the foun-
dation for leveraging the benefits of
SAP Business Suite, including in partic-
ular SAP enhancement packages, sup-
port for end-to-end business process-
es, and service-oriented architecture
(SOA) enabling the use of enterprise
services.
“SAP Business Suite 7 provides
another incentive for customers
to upgrade and to expand their
footprint of SAP solutions.”
Paul D. Hamerman and R. “Ray” Wang, “SAP
Harmonizes Portfolio with Business Suite 7,”
Forrester Research (March 2009)
Upgrade As an Opportunity
Upgrading applications is an important
issue for many SAP customers, but an
upgrade to any of the latest releases of
the applications in SAP Business Suite
should not be perceived as a neces-
sary evil. Rather, it is a valuable oppor-
tunity to maximize the value of your
SAP investment. To take advantage of
this opportunity, all that’s required is
appropriate planning and management.
Upgrades must be well integrated with-
in an organization’s overall IT strategy
and planning, which is why release and
upgrade management for SAP soft-
ware has become a topic of strategic
importance, having high visibility among
senior managers.
 Given the inherent volatility of informa-
tion technology, an upgrade can be
seen as a normal business activity – an
investment necessary for maintaining a
stable IT environment. An upgrade can
also bring significant benefits to your
organization by extending the function-
Prompted by the importance of the
upgrade topic and the widely divergent
understanding of it within the SAP com-
munity, SAP has compiled this “getting
started” guide. Directed to IT decision
makers and project leaders, the guide
is designed to help you assess the val-
This guide answers the following
questions:
• How can my organization evaluate
and justify an upgrade?
• How can my organization plan an
upgrade?
• How can my organization execute
an upgrade?

“Companies need to plan for periodic updates just to ensure the At the end of this document, the
reliability of mission-critical applications. Perhaps even more im- “Further Information” section lists
useful resources that detail specific
portant is the role that upgrades play in adding new functionality aspects of an upgrade, such as
[and] improving business processes.” upgrade guides and the SAP Notes
service.
Jim Shepherd, “Reduce the Pain of ERP Upgrades with Better Planning,” AMR Research (June 2007)

ality and improving the performance of ue potential of upgrading to the latest

your SAP software. Far from purely a
technical issue that can be left entirely
in the hands of IT departments, an SAP
software upgrade is vital to the daily
business operations of your organiza-
tion and can bring about significant
improvements in business efficiency.
SAP Business Suite applications. It
also summarizes best practices, SAP
recommendations, and a range of
SAP tools and services that can assist
you with the upgrade project across
its entire life cycle – from discovery
to evaluation to implementation (see
Figure 1).

Plan Build

Upgrade Discovery Upgrade Evaluation Upgrade Implementation

Figure 1: Three-Phase Upgrade Life Cycle

Getting Started with an Upgrade 5

 Identifying the Value Proposition
and Justifying the Upgrade
Combine Bottom-Up and Top-Down
Approaches for Best Results
SAP Business Suite 7 provides SAP
customers with a wealth of opportuni-
ties for improving their businesses. The
latest releases of the SAP Business
Suite applications lay a stable techno-
logical foundation that covers legal and
compliance requirements while giving
“The software helps us to achieve
cost savings through easier
release management and to
further broaden the functional
support in areas like treasury,
talent management, and supply
chain control.”
Jennifer Allerton, CIO, Roche
you the flexibility to innovate. With SAP
Business Suite 7, you can meet your
particular business needs and imple-
ment new functions at your own pace.
Combining an upgrade with other IT
initiatives – for example, replacing lega-
cy systems, consolidating the system
landscape, or reducing the level of soft-
ware modification and customization –
can also help you lower the total cost
of ownership.
When justifying an upgrade to the lat-
est releases of the applications in SAP
Business Suite 7, you need to weigh
the potential benefits and risks in light
of your organization’s specific circum-
stances. Each SAP customer faces a
unique situation in terms of the cover-
6 Getting Started with an Upgrade
age and maturity of its SAP software.
Customers use SAP solutions in very
different ways. And each has different
needs, goals, and priorities as it works
to achieve improvements in operational
excellence or equip itself for future
business innovation. A good upgrade
justification does not usually depend
upon a single decisive factor or “killer
feature” but rather on a combination of
interrelated factors that can benefit a
wide range of business areas and
improve processes across the
business.
When determining the value of an
upgrade, SAP recommends combining
two approaches: bottom-up and
top-down:
• Bottom-up approach (technology
inspired): This is initiated by the IT
department, which investigates new
technology or functionality and cre-
ates a case for how it can be used
for business improvements. New
technology or functionality is the key
driver. The focus is on developing
use cases for opportunities identified
in the available technology. This
approach leverages IT’s insights into
technology and its unique end-to-end
view of processes.
• Top-down approach (business
requirement driven): This occurs
when resolving a key business prob-
lem leads to requirements for a
changing level of IT-based process
automation. The business value of
an upgrade can be derived from
responding to the many real-world
issues (for example, demographic
changes, business network risks, and
environmental and sustainability chal-
lenges) that have an impact on your
business and can require you to
change your organization, business
rules, and processes. This approach
is typically triggered by business
challenges and can include organiza-
tional, process, and IT changes.
Discovery Process
Because of the intricacy of an upgrade
justification, it is worthwhile assessing
the value potential of the latest releas-
es of SAP Business Suite applications
using a clear procedure and methodolo-
gy, as described here.
The following six-step approach is con-
sidered best practice among SAP cus-
tomers and takes into account both a
bottom-up and a top-down methodolo-
gy for upgrade value determination.
1. Gathering preliminary information –
The IT department gathers product
information from a variety of sources
such as SAP Web sites, release
notes, and white papers. It should
also participate in SAP events to get
a basic understanding of new SAP
products. This step should focus on
investigating what new functionality is
available and what has technically
changed since you last upgraded to,
or implemented, your current system.
2. Involving stakeholders – The IT
department and representatives of
the various business units cooperate
to assess the value proposition of an
upgrade and build consensus.
This step involves determining who
within the business can benefit from
an upgrade. You should ensure busi-
ness executive sponsorship and user
involvement to secure commitment
and support for the upgrade project.
Since an upgrade justification is
unique to each customer situation,
SAP has developed tools and
services to help in this process.
For example, SAP has developed a
solution browser tool for SAP ERP
that enables IT organizations to
include respective business units in
these discussions. For other SAP
Business Suite applications, you
should compare older releases with
the respective latest release using
delta information that can be found
in the release notes
(www.service.sap.com/releasenotes).
Solution Browser Tool for SAP® ERP
This tool allows you to identify new
features and functions and their
business benefits in a given release
of the SAP® ERP application and
enhancement packages. It gives
business process experts the
opportunity to map current busi-
ness requirements with the latest
functions available in SAP ERP.
You can access the tool directly at
http://erp.fmpmedia.com or from
www.service.sap.com/upgrade.
3. Determining the business value of
new functions – Business units gath-
er in-depth information about the spe-
cific features of SAP Business Suite
applications that could be useful to
them. This is a crucial step during
which the business case is made for
implementing new functionality. It
requires thorough understanding both
of the benefits of the features and of
the requirements of the business that
can be satisfied by implementing the
features. You should analyze the
environment in which you do busi-
ness and determine whether unavoid-
able business reasons for an upgrade
exist. Business units must determine
the availability of the required func-
tionality to realize their requirements.
Value comes from the potential for
innovation and business transforma-
tion. The SAP upgrade value assess-
ment service can help you determine
the detailed value proposition and
business case for an SAP upgrade.
Upgrade Value Assessment
Service
The upgrade value assessment
service enables IT and business
users to collaborate on assessing
the business value of an upgrade
to the SAP ERP 6.0 application and
adoption of SAP Business Suite 7
software components, along with
estimating the ROI of the project.
It also helps in the creation and
updating of a value-based road map
around SAP solutions. The service
provides a methodology, tools, con-
tent, benchmarks, and references
to enable customer self-service for
value assessment.
4. Organizing delta workshops –
IT departments organize workshops
showing the difference, or delta,
between releases with SAP software
experts, who come from either SAP
itself or from a partner organization.
These focused delta workshops allow
business process experts to assess
the value potential of new SAP soft-
ware functions in more detail and
also help them understand the possi-
ble implications of these functions
on business operations.
5. “Test-driving” new functions – To
become familiar with new functions in
an upgraded system, the IT depart-
ment sets up a demo or “sandbox”
system for trying out new functions.
This sandbox system has many uses
throughout the upgrade project, but
its initial purpose is to provide the
first opportunity for IT and business
users to try out new functionality in
the context of their own organization.
You can set up the environment to
mirror the processes and require-
ments of the production system, pos-
sibly using a copy of production data.
This is an ideal way to determine the
value of an upgrade in relation to
implementing new functions and fea-
tures. It gives you hands-on experi-
ence with new functionality intro-
duced through the upgrade. You can
use the sandbox system to review
current business processes and how
they will be affected by the upgrade.
7
6. Finalizing a justification – The busi-
ness units and the IT department
discuss the merits, costs, and risks
of an upgrade and produce a justifica-
tion for the upgrade. Here you should
combine the bottom-up approach –
where IT identifies functional improve-
ments in the software – with the top-
down approach – where the business
units identify new business process-
es that require changes in the soft-
ware. As part of the upgrade justifica-
tion process, you should develop an
initial cost estimate. This is an impor-
tant input to the business case and
is the initial step in determining the
upgrade project budget. The quick
upgrade analysis service for SAP
ERP and for SAP CRM help you
determine high-level costs for, and
benefits of, an upgrade for each of
these applications.
Quick Upgrade Analysis Services
Designed to get you started with an
upgrade assessment, these SAP®
services for the SAP ERP and the
SAP Customer Relationship Manage-
ment applications provide a high-
level savings estimate as well as an
estimate of the project’s ROI, an
assessment of the upgrade complexi-
ty (giving specific information on the
level of modifications in your solu-
tion), an effort estimate for each
phase of the upgrade project, and a
sample project plan.
1. At the time of publication of this document, this service was in the global pilot phase.
8
This six-step approach helps to quantify
in concrete terms the potential gains of
upgrading to SAP ERP 6.0 or any other
SAP Business Suite 7 application. It
also identifies areas in the business
where process change or improvement
is required.
Quick Upgrade Analysis Service
for SAP Business Suite1
The new quick upgrade analysis ser-
vice for the SAP Business Suite
applications helps current SAP cus-
tomers running two or more SAP
Business Suite software compo-
nents to plan an SAP software land-
scape upgrade and estimate poten-
tial effort involved in an upgrade. For
example, you will get information
about the specific impact of an SAP
software landscape upgrade, depen-
dencies between software compo-
nents when upgrading, transparency
of software system landscape com-
plexity, and the upgrade sequence of
SAP software components based on
their technical dependencies.
Essentials of an Upgrade
Justification
For an efficient and accurate justifica-
tion of an upgrade, you should ensure
that:
• You have assessed core business
processes supported by the existing
SAP software landscape.
• Complementary and competing proj-
ects that might affect the core busi-
ness processes and connected SAP
software systems are transparent.
• You have identified the key value
drivers for the company’s business
model and key improvement opportu-
nities in current business operations.
• You are familiar with the functionality
of the latest releases of the SAP
Business Suite applications, including
the functionality available in SAP
enhancement packages.
• You have identified and mapped
business requirements to the func-
tions of the new SAP Business Suite
applications. (Note: this establishes
what tangible benefits can be gained
from an upgrade and enables the
creation of a business case.)
 Reasons for Upgrading • Business user demand for new func- • Requirements from IT, such as
tionality to improve operational excel- planned infrastructure updates and
Each organization has different reasons lence, enable innovation, and support consolidation projects that can be
for considering an upgrade. For a well- new business models combined beneficially with an
oriented justification process, you and • Desire to increase process efficiency upgrade
other decision makers in your organiza- and thus reduce the total cost of • Vendor’s release schedule or support
tion should create a detailed summary ownership (TCO), particularly in policies
of what benefits you expect or would terms of the total cost of operations
like to derive from an upgrade. Some – for example, by returning SAP soft- Figure 2 gives the results of an SAP
of the most common reasons for con- ware modifications and custom devel- survey in which customers were asked
sidering an upgrade are: opments to SAP standard functions about what improvements they antici-
pated from an upgrade to SAP ERP
6.0. The figure shows the level of inter-
“We upgraded to SAP ERP to pursue our operational excellence. . . est (given as a percentage of those
But we have achieved much more. We have improved the overall surveyed) in specific benefits.

efficiency of company operations.” Risk of Postponing an Upgrade

Massimo Battaglioli, Director of Information Systems and Innovation Technology Department,
From another perspective, postponing
Manutencoop Facility Management SpA
upgrades may expose your company
to risk, such as failure to meet legal
and compliance requirements; techno-
logical obsolescence; or incompatibility
62% of your current hardware, operating
42% systems, and database versions. These
41% risks can be only partially covered by
32%
paying extended maintenance fees to
software vendors. Minimizing them is
24%
an important, though often underappre-
20% ciated, factor in justifying a software
20% upgrade. Ignoring the risks is unaccept-
17% able in the long term. So when consid-
ering an upgrade, the question you
13%
need to ask is not simply “Should I do
0% 10% 20% 30% 40% 50% 60% 70% it or should I not?” but rather “Should I
do it now or later?”
End of standard or extended maintenance
Use of latest technology enhancement packages
End of old hardware servers In the following sections, the benefits
Replacing custom development and modifications of upgrading are analyzed in detail from
Empowering new business (SOA) four perspectives:
Thorough implementation of function enhancements • Operational excellence
Achieve enhanced user experience
• Business strategy
Consolidation of system landscape
Legal compliance • Sustainability
• Total cost of ownership
Figure 2: Business Benefits SAP Customers Expect from an Upgrade

Getting Started with an Upgrade 9


With SAP enhancement
packages, you can
deploy SAP Business
Suite software in a
step-wise manner to ad-
dress specific business
challenges along your
own timelines and with-
out costly upgrades.
10 Getting Started with an Upgrade
Operational Excellence SAP ERP 6.0
All of the latest releases of SAP SAP ERP 6.0 with enhancement pack-
Business Suite applications deliver a age 4 provides many functional
large number of functional enhance- enhancements that can improve pro-
ments and benefit from an increased cess efficiency. In addition, it integrates
level of integration. Furthermore, the the functions of most SAP industry
new enhancement package technology solutions so that these solutions no
makes it easier to implement new longer must be installed and set up
features across SAP Business Suite separately. The new software also sim-
applications. plifies daily business tasks through
more appealing and integrated user-
Because every customer uses a differ- interface concepts that increase user
ent SAP software landscape, key value productivity and satisfaction – for
drivers and tangible benefits of the new example, by enabling the use of Duet™
SAP software must be identified and software for integrating Microsoft
mapped to business needs on an indi- applications.
vidual basis. You can use the summary
of enhancements shown in the follow-
ing tables to identify the relevance of
specific features and functions for your
organization and to drive an internal
discussion among business units.
Using the following lists to map the
specific business requirements and val-
ue drivers to the features and functions
of the SAP Business Suite applications
should help reveal the concrete bene-
fits that contribute significantly to an
upgrade justification.
Business Challenges
User productivity
Reporting and performance
management
Accounting and financial
­reporting compliance
Talent attraction and retention
Shared services for HR
Procurement and logistics
execution
Product life-cycle
management (PLM)
Sales and order management
SAP® ERP 6.0 Application with Enhancement Package 4: Features and Functions
Enhancements
• New application interfaces • Employee self-service
• Updated role-based access • Manager self-service
• Greater use of Adobe interactive forms • Employee interaction center
• Better planning and forecasting tools • Express planning
• Greater ability to account for investments • Business consolidation
• Improved product costing module • Product design cost estimate
• Automated allocations and balancing using multiple • New general ledger
dimensions • Financial accounting – closing cockpit
• Improved closing process and preparation; local close • Treasury – bank communication
across closing periods and subsidiaries management
• Smooth bank connection; ability to track the entire pay- • Financial supply chain management
ment life cycle and improve internal compliance
• Accelerated invoicing processes to reduce days sales
outstanding and improve integration between treasury
and accounting at lower total cost of ownership
• Improved support for recruiters • Recruiting
• Improved online learning resources • E-learning
• Enhanced performance management and objective- • Knowledge management
setting functions • Workforce performance management
• New e-learning portal role for training administrators – • Succession management
simplified training organization and delivery, and • Compensation management
improved training staff efficiency
• Enhanced compensation management
• Improved ability to operate an HR shared service center • HR administration
• Easier access to HR data and services such as perfor- • Time management
mance appraisals • Human capital management self-service
• Ability to standardize and automate business processes
• Improved purchasing self-service functions • E-procurement
• Enhanced services procurement • Project self-service
• Streamlined invoice management
• Ability to standardize and automate procure-to-pay
processes
• Ability to automate product labeling process • Recipe management
• Ability to collect, adjust, and finalize technical product • PLM integration
data to prepare exact product labels
• Integrated product and process engineering and CAD
integration
• Improved order-entry process • Order and quotation management
• Improved support for Internet sales • Selling via eBay
• Enhanced pricing and configuration • Internet pricing configurator
• Comprehensive support for supplier and
customer returns
• Sales order entry via the SAP® Customer
Relationship Management application
Getting Started with an Upgrade 11
SAP SCM 7.0
The following table highlights the main enhancements in each of the components
of SAP SCM 7.0: the SAP Advanced Planning & Optimization (SAP APO) compo-
nent and the SAP Extended Warehouse Management (SAP EWM), SAP Event
Management, and SAP Supply Network Collaboration (SAP SNC) applications.
Business Challenges
Globalization and outsourcing
Avoiding poor customer
service
Lack of visibility beyond the
four walls
Complex production planning
and scheduling for process
industries
Warehouse management
Managing storage and mate-
rial staging of products in con-
nection with production and
process orders
Warehouse and yard visibility
12 Getting Started with an Upgrade
SAP® Supply Chain Management Application: Features and Functions
Enhancements
SAP® Advanced Planning & Optimization (SAP APO) • Enablement of characteristic-based
component: capable-to-match planning
Cross-location planning with characteristics • Enhanced production planning and detail
scheduling (PP/DS) to simplify cross-
plant planning
SAP APO: • New forecasting algorithm for better use
Enhancements in demand planning of POS data
• Better recognition of structural changes
in the past
SAP APO: • Customer VMI (support for consignment
Improved demand collaboration through vendor-managed stock scenario, customer master data
inventory (VMI) and customer forecast management integration)
• New process: customer forecast
management
SAP APO: • Introduction of resource networks for
• Modeling restrictions of the flow of product through the precise modeling of resource
plant based on the physical abilities to connect resources connections
• Allowing process-oriented companies (such as chemi- • Enhanced PP/DS optimizer
cal, consumer products, pharmaceutical, oil, or mining) • Enhanced master data integration for tank
to model and plan for tank restrictions within their pro- planning via new-product storage definition
duction process
SAP Extended Warehouse Management (SAP EWM) • Opportunistic cross-docking and
application: merchandise distribution
• Production integration • Production supply
• Improvements in radio frequency execution • Graphical warehouse layout
• Graphical display of the warehouse
• Support for enhanced cross-docking scenarios
SAP EWM: Production supply
Integration of production supply into the processes of the
warehouse (with SAP EWM and the SAP ERP application )
SAP EWM: Graphical display of the warehouse and yard Graphical warehouse layout
Business Challenges
Reducing handling costs,
operating costs, and material
storage
Picking by customer, by line,
by article, or by product;
flexibly planning and control-
ling your flow of goods
User productivity
Supplier collaboration
Outsource manufacturing
Customer collaboration
Electronic Product Code
Information Services (EPCIS)
compliance
Unique item identification
SAP® Supply Chain Management Application: Features and Functions
Enhancements
SAP EWM: Opportunistic cross-docking and
Cross-docking merchandise distribution
SAP EWM: Merchandise distribution
Merchandise distribution and retail cross-docking
(with SAP EWM and SAP ERP)
SAP EWM: • Web access
New Web user interface coming with a broad set of • User productivity work list
built-in features
SAP Supply Network Collaboration (SAP SNC) • Purchase order collaboration
application: • Supplier-managed inventory
• Quick view (dashboard) • Dynamic replenishment
• Up- and download center for file exchange • Partner user management
(Microsoft Excel)
• Supplier self-service–enhanced PO work list functionality
• Improved SAP SNC and SAP ERP integration
• Extended partner user management
SAP SNC: • Work order collaboration
• Improved supply, demand, and inventory monitoring for • Supply network inventory
contract manufacturing
• Batch traceability
• Work-in-process integration with controlling (SAP ERP)
SAP SNC: Responsive replenishment
• Decision-support enhancement of responsive replenish-
ment overview monitor through additional key figures
• Additional mass maintenance of location products
• Additional rounding logic for replenishment orders and
transport load builder
• Additional selection criteria, safety stock calculations,
and improved promotion handling
Standard capture and query interface; improved master SAP Auto-ID Enterprise offering:
data, security, usability, and reporting SAP Auto-ID Infrastructure offering
and SAP object event repository
Support of unique item identifiers throughout: from SAP Auto-ID Enterprise: SAP Auto-ID
supply chain (using SAP Auto-ID Enterprise) to asset Infrastructure and SAP object event reposi-
management (SAP ERP) tory support for unique item identifiers
Getting Started with an Upgrade 13
SAP SRM 7.0
The following table highlights the main enhancements in SAP SRM 7.0.
Business Challenges
User productivity
Operational procurement
Self-service procurement
Plan-driven procurement
Services procurement
Catalog management
Centralized sourcing
Centralized contracts
Supplier collaboration
14 Getting Started with an Upgrade
SAP® Supplier Relationship Management (SAP SRM) Features and Functions
Application: Enhancements
• Personalized, intuitive user experience • Flexible user interface
• Greater user efficiency and faster task completion • Role-based access
• Upgraded, user-friendly work center • Portal business content
• Personal object work list
• Enhanced requisition handling through team purchasing • Requisition handling
and delivery date configuration • Purchase order processing
• Streamlined purchase orders
• Enhanced authorization concept, invoice accuracy, • Procure-to-pay cycle
and support for flexible integration scenarios • Purchase order and contract creation
• Automatic back-end enterprise resource planning
purchase order or contract creation based on an
accepted quote in SAP® SRM
• Better identification and automated handling of • Exception handling
exception situations • SAP ERP integration for purchase
• Enhanced integration with the SAP ERP application requirements, text transfers, revisions,
and PO transfer consistency checks
• Support for model specifications and service • Centralized repository of services
hierarchies functionality
• SAP SRM master data management (MDM) catalog • SAP SRM MDM catalog
access for purchaser and bidder as a repository for
service specifications
• Ability to import content (purchase information records • Catalog content management
and contracts) from SAP ERP • Web publishing
• Catalog interface for supplier-provided content
• Ability to publish catalog content on the Web
• Response modification within request-for-x (RFx) • RFx bid processing
documents • Auction management
• Enhanced analytics to support bid selection (bid com-
parison view and weighted sourcing)
• Real-time auction monitoring and bidding
• Single, central contract in SAP SRM shared via integra- • SAP ERP integration
tion with SAP ERP • Contract management
• Multiple alert thresholds, such as expiration date, target
value, and target quantity
• Ability to submit services procurement requisition Supplier self-service
responses, confirmations, and invoices
• Supplier-provided catalog content
SAP CRM 7.0
The following table highlights the main enhancements in SAP CRM 7.0.
Business Challenges
User productivity
Contract life cycle
Improving sales performance
Building stronger relationships
with consumers
Delivering service excellence
SAP® Customer Relationship Management (SAP CRM) Features and Functions
Application: Enhancements
• Enhanced user interface (UI) • A new Web client user interface in
• Improved user guide guidance, assistance, and SAP® CRM
navigation • Smart value help
• Visualizing table content in a pie or bar chart • Recent objects
• Table graphics
• Automation of contract activation processing Advanced contract management
• Enhanced package pricing and follow-ups creation
• Consolidated change processes for all contract types
• Ability to set revenue and units targets (overall, by • Pipeline performance management
product, and by product category) • Territory management
• Simulation of opportunity changes and what-if scenarios
for closing pipeline gaps
• Authorizations based on territory assignment
• Possibility to model and evaluate territory rules
• Improved segmentation scalability for high volumes of • Professional call center
customer data • High-volume marketing
• Lean high-volume campaign execution for e-mail and • Segmentation, campaign execution,
file export and address list handling
• Handling of temporary address data • Loyalty management
• Setup and maintenance of loyalty programs • Program management, rewards,
• Setup and maintenance of loyalty rules and conditions memberships, and processing
• SAP ERP application integration of functional locations • Communication-enabled business
and bill of materials processes
• Credit card payment in SAP CRM billing functionality • Advanced contract management
• Service transactions that inherit reference objects and • Shared service centers
categorizations to the item level • Information Technology Infrastructure
• Controlling and cost information displayed in Library–compliant IT service management
transactions • Resource optimization
• Improved serial number integration
• Enhanced authorizations for installed base
Getting Started with an Upgrade 15
SAP PLM 7.0
The following table highlights the main enhancements in SAP PLM 7.0.

Business Challenges SAP® Product Lifecycle Management (SAP PLM) Features and Functions
Application: Enhancements
User productivity • Easier-to-deploy and intuitive new user interface (UI) • Web UI
• UI for material master, bill of materials, document man- • UI support for existing objects
agement, and engineering change management • SAP® PLM object navigator
• Improved navigation • Search functionality
• Improved search usability and performance
Product intelligence Context-sensitive embedded analytics and supplemental Product-centric view
area in UI
Collaboration and access Increased security to protect intellectual property • Context-based authorization
control • Secure collaboration architecture
Document management • Simplified, intuitive handling of documents SAP Easy Document Management 7.0
• Group structures to facilitate team and group working application

Business Strategy
In an increasingly global economy, flexi-
bility has become a more important fac-
tor in business success. Organizations
seek to shorten product innovation
cycles, respond more quickly to dynam-
ic market conditions, and continuously
adjust their business model to stay
ahead of the competition. However,
many business applications are embed-
ded in complex software environments
that offer limited flexibility and little sup-
port for global business transformation.
SAP is constantly developing measures
to make it easier to manage SAP
Business Suite applications, to help
customers implement future functional
enhancements with little disruption and
effort, and to facilitate future business
innovation.
SAP Enhancement Packages
After you upgrade to the latest releas-
es of the SAP Business Suite applica-
tions, you can enhance the functionality
of your applications without performing
further upgrades thanks to a new
deployment technology: SAP enhance-
ment packages. These packages sim-
plify the way you manage and deploy
new software functions for SAP Busi-
ness Suite applications. They enable
you to take advantage of the latest
software innovations while minimizing
disruption to ongoing operations.
Currently four enhancement packages
have been delivered for SAP ERP 6.0,
and there has been one enhancement
package for the SAP NetWeaver® tech-
nology platform. In the future, enhance-
ment packages will be delivered for
SAP CRM 7.0, SAP SCM 7.0, and
SAP SRM 7.0 to build on the stable
underlying core of these applications.
SAP enhancement packages are cumu-
lative. This means when implementing
an enhancement package you will get
all the innovation delivered with the
previous enhancement packages. For
example, if you implement enhance-
ment package 4 for SAP ERP 6.0, you
get, and can activate, all innovation that
has been delivered with enhancement
packages 1 to 3 for SAP ERP 6.0 as
well.
Selective Installation and Activation
Using SAP enhancement packages,
you can implement selected software
innovations from SAP and then activate
selected functions and enhancements
on demand to meet your business
requirements.

16 Getting Started with an Upgrade

The key innovations of enhancement
packages are:
• Selective installation of business
functions – Install only the new and
improved business functions that you
require. After installation, no user
interface (UI) or process changes
take place.
• Selective activation of business func-
tions – Activate only the business
functions that you require. New func-
tionality must be explicitly switched
on to become active in the system,
with predictable changes restricted to
the activated areas.
This unique delivery and deployment
method for enterprise software,
enabled by the flexibility of SOA, lets
you access new functions while holding
on to your core functions. As a result,
you can isolate the impact of software
updates and quickly bring new func-
tions online through shortened testing
cycles without impeding core business
processes.
Figure 3 shows a road map for
enhancement packages for SAP ERP
6.0, outlining the most important areas
of innovation.
SAP ERP 6.0 with Enhancement
Package 4
An upgrade to SAP ERP 6.0 is the
first step to create the foundation for
leveraging the benefits of the SAP
enhancement package concept and
SAP Business Suite 7.
If you run the SAP R/3® 4.0B software
or above, you can directly upgrade to
SAP ERP 6.0. To benefit from SAP
Business Suite 7 and SAP enhance-
ment packages, you must upgrade to
SAP ERP 6.0 with SAP enhancement
package 4. Hence, when planning an
upgrade to SAP ERP 6.0, you should
include SAP enhancement package 4
(or the latest available SAP enhance-
ment package) for SAP ERP in your
upgrade project to minimize efforts and
maximize benefits. Customers already
running on SAP ERP 6.0 can leverage
available SAP enhancement packages.
You can start to update specific pro-
cesses instead of doing traditional
upgrades and continue to increase
your footprint in SAP Business Suite.

Figure 3: Road
Map of Enhancement
Packages for
Enhancement Packages* SAP® ERP 6.0
Q4 2006 Q3 2007 Q4 2007 Q4 2008 2010**
Enhancement Enhancement Enhancement Enhancement Enhancement
Package 1 Package 2 Package 3 Package 4 Package 5
Human Capital HR shared Talent Talent Talent Talent manage-
Management services management: management: management: ment: onboarding
learning e-recruiting new user and analytics
experience

Financials Credit and Bank Financial closing Treasury and risk Financial
collections communication management; shared services
management master data
governance

Operations Adaptive Order-to-cash Procure-to-pay Outsourced Global process

manufacturing simplification simplification manufacturing integration and
traceability

Corporate Travel Environmental Service sourcing Enterprise asset

Services management health and safety and recycling management
simplification simplification administration simplification

* Showing core content, without industry-specific content ** Planned enhancement package: subject to change

Getting Started with an Upgrade 17

“We anticipate that the enhance-
ment package strategy will
remove the upgrade barrier and
help us to more efficiently
deliver the innovation we need
for continued success. With all
components of SAP Business
Suite on the same release cycle,
the costs associated with
implementation and testing
of new functionality are greatly
reduced.”
Ed Toben, Senior VP, GIT and Business
Services, Colgate-Palmolive Company
Combined Installation
It is now possible to embed SAP
enhancement packages into the
upgrade. Combining the technical
upgrade with enhancement package
installation allows for one upgrade
downtime – that is, without separate
installation of the enhancement pack-
age after the upgrade (although this
is also possible). Including the imple-
mentation of an enhancement package
into an upgrade has no impact on
the technical downtime. (Beyond this,
enhancement packages can be
installed any time after application
installation or upgrade.) By embedding
enhancement packages, you are in an
advantageous position for activating
the relevant innovations at any later
point in time. If you install all parts of an
enhancement package, you can choose
from all business functions delivered.
If you install only some of the technical
18 Getting Started with an Upgrade
usages from an enhancement package,
the number of business functions is
reduced accordingly.
SAP Enhancement Packages and
Support Packages
The delivery of SAP enhancement
packages is synchronized with the
delivery of support packages. Support
packages deliver all legal changes and
corrections and can be installed inde-
pendently of enhancement packages.
This means that you can maintain core
applications by applying support pack-
ages and can optionally add functional-
ity through enhancement packages.
To minimize effort (especially regarding
potentially needed modification adjust-
ments and testing), you apply enhance-
ment packages within one installation
queue, together with the required sup-
port packages. Using this strategy,
enhancement packages can be installed
without causing disruption, as a normal
maintenance activity in one downtime.
The installation technology, now imple-
mented through a maintenance opti­
mizer (in the SAP Solution Manager
application management solution), and
the new SAP enhancement package
installer have improved the upgrade
and installation procedure.
Compatibility
As a rule, existing processes will
work with new SAP enhancement
packages and application releases.
In some cases, to use new processes
you may need to implement the new
application releases or enhancement
packages and activate new functional-
ity. For details on integration rules,
refer to SAP’s Release Strategy for
Large Enterprises.
Service-Oriented Architecture
SAP Business Suite 7 applications
are fully SOA-enabled. SOA helps you
shorten application innovation life
cycles and implement strategic busi-
ness innovations quickly and with mini-
mal effort by reusing components at
the macro level. SOA brings simplicity
and transparency to your SAP soft-
ware, enabling you to adapt it to suit
the business needs of your
organization.
“The support packages in our
productive SAP software system
are normally updated on an
annual basis. Now, with the in-
stallation of an enhancement
package, we can combine this
process without any additional
efforts. This means that the
latest SAP functionality and
technology is always on hand.
We simply need to activate
functionality on request from
our business community.”
Dr. Marco Lenck, CIO,
Rhein Chemie Rheinau GmbH
SOA improves the design, composi-
tion, and management of Web services
to address enterprise requirements.
An enterprise service can combine a
series of Web services with business
logic to be accessed and used repeat-
edly to support a particular business
process. Aggregating Web services in
this way facilitates the task of automat-
ing enterprise-scale business scenarios.
SAP publishes all enterprise services
that support SAP Business Suite func-
tionality at the Enterprise Services
Workplace site in the SAP Developer
Network (SDN) site. Every productized
enterprise service for SAP solutions
is available here for exploration, test-
driving, and consumption.
These are some of the potential bene-
fits you gain by using SOA:
• Ability to flexibly design a business
process such as an order-to-cash
process
• Potential to implement shared service
centers
• More reliable business insight
• Better integration of SAP Business
Suite applications with additional
applications from SAP partners
Although SOA is not currently consid-
ered a primary driver for upgrading,
the innovation and flexibility that SOA
enables should be considered a major
contribution to justifying an SAP soft-
ware upgrade.
Sustainability
SAP Business Suite applications inte-
grate operations with financial and HR
processes. They must cover regular
changes in legal requirements (such as
tax adjustments) as well as newer com-
pliance standards developed to meet
the needs of a global economy. Newer
standards include those issued by the
U.S. Food and Drug Administration and
those published in the Sarbanes-Oxley
Act and Basel II Accords.
Covering New Legal and Compliance
Requirements
SAP provides updates for legal changes
as part of the mainstream or extended
maintenance agreement for SAP Busi-
ness Suite 7 applications (as it does for
the previous releases of SAP software
replaced by later releases). With previ-
ous releases, the outdated underlying
software technology may impede the
implementation of effective solutions
for meeting current compliance
standards.
Ensuring Business and IT System
Stability
Running a productive business on an
SAP software landscape is a major IT
commitment. Any disturbance or insta-
bility in the landscape can affect the
performance of the entire company.
Furthermore, SAP software must
remain compliant with your company’s
underlying technology, including your
operating system, database version,
and hardware. Operating systems and
database versions usually have shorter
maintenance periods than SAP soft-
ware releases and require more regular
upgrades than SAP applications. Thus,
older releases of SAP software may
not be compatible with newer operating
systems and database versions or may
not be able to use the enhanced func-
tionality and performance of the newer
versions. By upgrading, you can stay
up-to-date with the underlying technolo-
gy and help ensure business continuity
and system stability.
Providing Continuous System Support
and Maintenance
SAP’s “7–2” maintenance strategy
applies to core application releases of
SAP Business Suite 7. In particular, for
SAP CRM 7.0, SAP SCM 7.0, SAP
SRM 7.0, and SAP PLM 7.0, SAP
will offer mainstream maintenance to
December 2015 and extended mainte-
nance for two additional years to
December 2017. In parallel, mainte-
nance for SAP ERP 6.0 and SAP
NetWeaver 7.0 has also been adapted
to this strategy. This means that main-
stream maintenance for these releases
is extended from March 2013 to
December 2015, and extended mainte-
nance will be offered to December 2017.
For other SAP Business Suite applica-
tions (for example, industry applica-
tions and supplementary applications),
the maintenance dates are aligned with
the maintenance dates for the core
application release or SAP NetWeaver
release they are based on. Details of
the 7–2 maintenance strategy for SAP
Business Suite 7 and the unchanged
maintenance strategy for SAP R/3
4.6C, the SAP R/3 Enterprise soft-
ware, and the mySAP™ ERP 2004 appli-
cation, can be found in SAP’s Release
Strategy for Large Enterprises and on
the SAP Service Marketplace extranet
(www.service.sap.com/maintenance).
The benefit of paying the extended
maintenance fees on previous releases
of SAP Business Suite applications –
perhaps to wait for the next major
release – is limited. Furthermore,
employing internal staff or hiring con-
sultants to maintain outdated releases
is very expensive. It’s important to con-
sider these potential cost savings – as
well as the operational benefits of the
latest SAP software – in your upgrade
business-case calculation.
Getting Started with an Upgrade 19

Licensing Aspects
The introduction of SAP Business Suite
7 does not influence the license model
and pricing. Customers will continue to
license SAP application users and
packages. Existing customers will get
access to relevant SAP Business Suite
7 innovation according to the extended
maintenance agreement. For further
details, contact your local account
executive.
Total Cost of Ownership
Market studies show that up to 80%
of IT budgets are spent as cost of
operations. One of the major contribu-
tors to the high cost of operations is a
software landscape that is unnecessar-
ily complex. An upgrade to the latest
releases of the SAP Business Suite
applications, when combined with other
IT initiatives, can reduce TCO, mainly
in terms of operations costs.
Reducing the Level of Modification
and Customization
Because the architecture and technolo-
gy of SAP software is very flexible,
some SAP customers invest heavily in
modifications of SAP code and in cus-
20 Getting Started with an Upgrade
tom developments (customization).
While it is possible to continuously
adjust your software system to meet
new business requirements, the life-
cycle management and maintenance
of highly modified SAP software sys-
tems becomes increasingly expensive
and difficult. SAP internal estimates
indicate that up to 60% of custom
developments are not even being used.
According to a customer survey con-
ducted by SAP in 2008, 32% of cus-
tomers take the opportunity of an
upgrade to clean up their software sys-
tems by eliminating unused modifica-
tions and custom developments. The
cost savings achieved by reducing
these modifications can make a con­
siderable contribution to the upgrade
business case.
Consolidating the Software
Landscape
Consolidation of your software land-
scape can provide a good opportunity
for upgrading your SAP software,
since both types of projects require a
detailed analysis of the landscape and
can be implemented simultaneously to
minimize disruption. Depending on your
IT strategy, you can run centralized or
decentralized SAP software systems.
While some multinational companies
run SAP software in a single-client
mode, others allow their decentralized
IT and business units to run individual
software systems. With the increasing
pressure to reduce IT expenditure,
there is a trend in the SAP community
to consolidate SAP software land-
scapes and replace legacy systems to
streamline hardware and server infra-
structure and reduce overhead costs.
Consolidation projects are usually
planned over several years, with the
goal of achieving a consolidated
landscape on a unified target, usually
the latest available release of SAP
software.
A more consolidated SAP software
landscape increases business efficien-
cy and flexibility and reduces the com-
plexity and expense of future imple-
mentation projects. Consolidating your
software landscape also makes future
upgrades considerably easier.
Lowering the Cost of Operations
Consolidating SAP software land-
scapes reduces the number of SAP
software systems and servers as well
as the number of modifications and
custom developments. This, in turn,
reduces the effort needed for ongoing
system administration tasks (such as
providing backups or applying new sup-
port packages). And using enhance-
ment packages to deploy enhanced
functionality reduces the need for
future upgrades and can also reduce
the cost of operations.
Beyond those cost savings, there are
additional opportunities to increase
the efficiency of IT operations by using
the synchronized tools and infrastruc-
ture available in SAP Business Suite 7.
For example, by using the software’s
robust and automated administration
features and functions or using inte-
grated functions such as root-cause
analysis, you can reduce manual sys-
tem maintenance tasks. And SAP
Solution Manager provides monitoring,
service delivery, and system adminis-
trator–related work centers that further
improve efficiency.
Planning an Upgrade
Strategy and Management to Make
the Project Run Smoothly
After the discovery and initial evalua-
tion phase, which produces a high-level
definition of business and IT require-
ments as well as a business case, you
enter a more detailed evaluation and
planning phase.
In a survey conducted by SAP in 2008,
69% of respondents said that cost
and effort estimates are the major chal-
lenges they face during the upgrade
planning phase, and 46% said that
project management factors are the
major challenges. The definition of an
upgrade strategy and development of a
schedule are also significant challenges
during planning and evaluation, espe-
cially in large organizations. This sec-
tion outlines challenges, best practices,
and SAP recommendations for these
and other important planning factors.
Upgrade Information Center
A single point of access for
upgrade-related information across
the entire upgrade life cycle –
general and solution specific – is
available at www.service.sap.com
/upgrade. This Web site contains
information for various target
groups (with technical and business
focus) in English and Japanese
and is updated regularly. Informa-
tion specific to the SAP® Business
Suite applications can be found at:
www.service.sap.com
/upgrade-erp
www.service.sap.com
/upgrade-crm
www.service.sap.com
/upgrade-scm
www.service.sap.com
/upgrade-srm
www.service.sap.com/plm
Assessing the Impact of the
Upgrade on Your Existing Solution
Even in the planning phase, you should
perform an early risk and impact
assessment to produce an accurate
picture of cost drivers for the
project(s). The risk, difficulty, and dura-
tion of upgrading to SAP Business
Suite applications vary greatly, depend-
ing on the source release and the sys-
tem landscape.
For example, upgrading from SAP R/3
4.6C or higher is considerably easier
and involves lower risk because it
requires only limited code changes to
the central component of your current
ERP software. For releases below
SAP R/3 4.6C, upgrades to SAP ERP
6.0 involve a higher risk and may
require more application adjustments,
testing, and user training.
Upgrade Dependency Analyzer
You can use the upgrade depen-
dency analyzer to check the exis-
tence of upgrade dependencies
between two separately installed
SAP software systems in your sys-
tem landscape. For details, see
www.service.sap.com/uda.
Typically, SAP Business Suite applica-
tions are part of an SAP software sys-
tem landscape that contains various
interconnected systems. Business
processes can run across the various
systems. When planning an upgrade
of the systems in your landscape, you
must know whether this will have an
impact on other systems in your land-
scape – that is, whether the upgrade
requires changes to other systems in
the landscape as well. In general there
are no dependencies – but if there are,
SAP can help with the right set of
tools.
The level of risk and the need for appli-
cation adjustments and user training
also increase with the complexity of the
software system landscape and your
levels of customization and modifica-
tion. Good IT housekeeping (archiving,
documentation, and regular system
maintenance) can also significantly
increase the efficiency of an upgrade.
And the use of SAP industry solutions
based on SAP R/3 may increase the
effort involved in the project.
SAP recommendation: To achieve a
detailed and reliable assessment of
the risk and complexity of an upgrade
project, you should carry out an impact
analysis for at least one typical soft-
ware system as a reference and as the
basis for an initial technical risk assess-
ment. Such a procedure is essential
for calculating required resources and
preparing your organization to deal with
challenges.
21
Technical Prerequisites and
Limitations
When upgrading to the latest release
of any of the SAP Business Suite appli-
cations, there are technical prerequi-
sites that you must take into account.
This section highlights some of the
important prerequisites and indicates
where to find more information for each
application.
Upgrade Paths for SAP Business Suite
Applications
Figure 4 gives an overview of the direct
upgrade paths to the latest releases of
the SAP Business Suite 7 applications.
To upgrade to the latest releases of
the SAP Business Suite applications,
you may need to:
• Upgrade to a source release from
which you can perform a direct
upgrade to the latest release
• Change your hardware, operating
system, or database platform
• Perform a Unicode conversion if
you use multiple-display, multiple-
processing (MDMP) technology or
blended code pages to display lan-
guages with different character sets
To minimize technical dependencies
between SAP NetWeaver, earlier
components of SAP Business Suite,
and SAP enhancement package 4 for
SAP ERP, SAP recommends installing
SAP enhancement package 4 for
SAP ERP and SAP enhancement pack-
age 1 for SAP NetWeaver, as well as
upgrading to the go-to releases of the
SAP Business Suite core applications.
The following table provides upgrade
and installation notes that contain
technical limitations and prerequisites
for each of the SAP Business Suite
applications.

SAP® Safeguarding for Upgrades SAP ERP 6.0 plus

Core applications of SAP Business Suite 73

SAP® ERP 6.0 Install SAP enhancement
With the SAP® Safeguarding for package 4 for SAP ERP enhancement package
4 for SAP ERP
Upgrades portfolio of services, (including SAP PLM)
SAP offers a holistic approach SAP R/3 4.0B1
for technical risk mitigation in Upgrade to SAP ERP 6.0
and above
and include enhancement
SAP software upgrades. It focuses
SAP PLM 4.01 package 4 for SAP ERP SAP PLM 7.0
particularly on the initial technical risk
and above
assessment and tailors this to your
specific situation
(see www.service.sap.com SAP CRM 4.01,2 Upgrade SAP CRM 7.0
/safeguardingupgrade). and above
SAP SRM 3.01 Upgrade SAP SRM 7.0
and above
SAP SCM 4.11 Upgrade SAP SCM 7.0
and above

¹ Direct upgrade from these source releases to the go-to releases of SAP Business Suite 7 applications is
supported by SAP.
² If you upgrade from SAP CRM 4.0 or 5.0 to SAP CRM 7.0, customer-specific UIs (including the underlying
UI-related coding) must be migrated separately.
³ Most industry and supplementary applications are shipped with the SAP Business Suite applications and
are included in the respective upgrade. For the versions of industry and supplementary applications that are
part of SAP Business Suite 7 but are not shipped as part of SAP ERP, SAP SCM, SAP PLM, SAP SRM, or
SAP CRM, refer to SAP’s Release Strategy for Large Enterprises at www.service.sap.com/releasestrategy.

Figure 4: Direct Upgrade Paths for SAP Business Suite Applications

Technical Upgrade Notes for SAP Business Suite Applications

SAP® Business Suite Application Notes

SAP® ERP 6.0 application If you run the mySAP™ ERP 2004 application or an older release, you must upgrade to
SAP ERP 6.0 before being able to use the SAP Business Suite 7 applications and SAP
enhancement packages.

If you are planning an upgrade to SAP ERP 6.0, you should include SAP enhancement
package 4 for SAP ERP into your upgrade project to minimize efforts and maximize benefits.

The former product SAP Internet Transaction Service (ITS) has been integrated into the
SAP NetWeaver® technology platform. The stand-alone ITS product is no longer support-
ed by SAP. If you have been using advanced features of this product and want to continue
using them, you need to perform a migration to the latest release of the SAP NetWeaver
Portal component. If you want to continue using the basic features of the ITS product,
you must perform a migration to the ITS software that is now part of SAP NetWeaver.
For details, see SAP Note 709038: “SAP Integrated ITS.”

For release restrictions, see SAP Note 852235.

SAP Customer Relationship Management SAP GUI is only supported for administrative tasks. The people-centric UI (PC UI) is
(SAP CRM) 7.0 application no longer supported. The new Web client user interface in SAP CRM was introduced
in SAP CRM 2007. For more information, see SAP Note 1118231.

If you upgrade from SAP CRM 4.0 or 5.0 to SAP CRM 7.0, a technical upgrade is
available, but an automatic UI migration of customer-specific UIs (including the underlying
UI-related coding) is not possible.

For details of UI migration, see the SAP CRM 7.0 Upgrade Master Guide.
SAP Product Lifecycle Management To use SAP PLM 7.0, you must install enhancement package 4 for SAP ERP 6.0, or
(SAP PLM) 7.0 application upgrade to SAP ERP 6.0 and include enhancement package 4 in the upgrade.

SAP PLM 7.0 also requires enhancement package 1 for SAP NetWeaver 7.0,
SAP NetWeaver Portal, and text retrieval and information extraction software.

The viewer used in the new SAP PLM UI must be installed on each front end, where
the viewer will be used. To do this, download the installation file from the SAP Service
Marketplace extranet and execute it locally. For details, see SAP Note 1179524:
“Installation Note for Viewer in SAP ERP EHP4.”

Getting Started with an Upgrade 23

SAP® Business Suite Application Notes
SAP Supplier Relationship Management In addition to being available as a stand-alone application, SAP SRM 7.0 is also available
(SAP SRM) 7.0 application as an add-on to SAP ERP 6.0 (SAP SRM on one client) with functional limitations.

SAP SRM 7.0 on one client in SAP ERP is available with SAP ERP 6.0 enhancement
package 4 with SAP NetWeaver 7.01.

If you have an existing SAP SRM 5.0 one-client installation on an SAP ERP 6.0 software
system, you can upgrade to SAP SRM 7.0 on one client after the installation of SAP ERP
6.0 enhancement package 4 (with SAP NetWeaver release 7.01).

For details of the limitations of SAP SRM 7.0 on one client, see SAP Note 963000:
“Usage and Release of SRM as Add-On to ECC in SAP ERP 6.0.”

SAP Supply Chain Management
(SAP SCM) 7.0 application
The following applications are components of SAP SCM 7.0 and are included in the
upgrade to SAP SCM 7.0:
• SAP Advanced Planning & Optimization (SAP APO) component
• SAP Extended Warehouse Management (SAP EWM) application
• SAP Event Management application
• SAP Supply Network Collaboration (SAP SNC) application

For release restrictions, see SAP Note 1284461: “Release Restrictions for SAP SCM 7.0.”

SAP EWM, SAP Event Management, and SAP SNC can also be installed as add-on
components to SAP ERP 6.0 with enhancement package 4 or SAP NetWeaver 7.0 with
enhancement package 1. For details, see SAP Note 1173386: “Installation/Upgrade from
SCM EWM 7.0 to ERP 6.0 EHP4”; SAP Note 1173567: “Installation/Upgrade SCEM-
SRV 700”; the SAP SNC 7.0 Upgrade Master Guide; and SAP Note 1173389: “Installa-
tion/Upgrade SCMSNC 700 on NW 7.0 EHP1.”

When upgrading, you may encounter
the following limitations:
• Limited availability of country ver-
sions or third-party products –
archiving tools, for example
• Compatibility problems with other
SAP applications or third-party
products (for example, those not
compatible with Unicode)
You can find comprehensive informa-
tion about the release restrictions and
technical limitations for each SAP Busi-
ness Suite application in SAP Notes.
SAP R/3 Plug-In
New and extended interfaces for inte-
gration between SAP ERP 6.0 and
other SAP Business Suite applications
are no longer delivered with their own
add-on – the SAP R/3 plug-in. The SAP
ERP Central Component 6.0 now
automatically contains all integration
interfaces that were previously
contained in the SAP R/3 plug-in.
Upgrade Paths for Unicode
For all SAP Business Suite applica-
tions, a Unicode conversion is only
necessary for those customers using
MDMP or blended code pages.
However, some organizations may

24 Getting Started with an Upgrade

want to perform a Unicode conversion
to provide future support for languages
with different code pages – for exam-
ple, for users in Asian or eastern
European countries.
Note: SAP recommends that you
perform a Unicode conversion for
all SAP Business Suite 7 applications.
The previous SAP technologies have
become obsolete for a variety of rea-
sons – for example, they do not enable
proper communication with Java-based
applications.
For details of the requirements to
convert to Unicode, see the following
SAP Notes:
• SAP Note 73606: “Supported
Languages and Code Pages”
• SAP Note 745030: “MDMP –
Unicode Interfaces: Solution
Overview”
• SAP Note 79991: “Multilanguage
and Unicode Support of SAP
Applications”
More details on procedures for per-
forming a Unicode conversion with an
upgrade to the newest SAP software
are given in the respective SAP Notes
listed at the end of this document (see
“Further Information”). And you can
find general information about Unicode
and SAP Business Suite applications
at www.service.sap.com/globalization.
The following table provides Unicode
conversion notes for each of the
SAP Business Suite 7 applications.
Unicode Conversion for SAP Business Suite Applications
SAP® Business Suite Application
SAP® ERP 6.0
SAP Customer Relationship
Management (SAP CRM) 7.0
SAP Product Lifecycle Management
(SAP PLM) 7.0
SAP Supply Chain Management
(SAP SCM) 7.0
SAP Supplier Relationship Management
(SAP SRM) 7.0
Notes
Customers running SAP R/3® software
with multiple-display, multiple-processing
(MDMP) technology or blended code pages
must combine their upgrade with a Unicode
conversion.
• Customers with single code page technology
who want to expand their business into
additional countries that require additional
code pages must switch to Unicode.
• Customers with MDMP or blended code
page technology must perform a Unicode
conversion.
• Note: if you want to perform a Unicode
conversion for SAP CRM, you have to do
it before or after the upgrade – the Unicode
conversion is independent from the SAP
CRM server upgrade.
As an add-on that is included in enhance-
ment package 4 for SAP ERP 6.0, SAP
PLM 7.0 is subject to the same Unicode
requirements as SAP ERP 6.0.
If you want to upgrade from a non-Unicode
SAP SCM software system to a Unicode
SAP SCM software system, you must
perform a special procedure called “com-
bined upgrade and Unicode conversion”
(CU&UC).
If you want to upgrade from a non-Unicode
SAP SRM software system to a Unicode
SAP SRM software system, you must
perform a CU&UC.
Getting Started with an Upgrade 25
Scheduling an Upgrade
There are many factors to be con­
sidered when you are developing a
detailed schedule to meet your specific
needs – a schedule with optimal timing
and sequencing of the individual
upgrade projects. A transition to the
latest SAP Business Suite applications
is rarely a single project. It is generally
a program that covers several produc-
tive SAP software systems over sever-
al months or even years. But regard-
less of the extent of the upgrade, the
timing of the upgrade is critical given
the effort and downtime it involves.
Therefore, an upgrade must be coordi-
nated with your IT planning group.
The following factors influence the
scheduling of an upgrade:
Managing SAP ERP 6.0 Upgrade
Projects
This book, published by SAP Press,
is the consultant’s and project team’s
guide to smooth and successful
SAP® upgrade projects. It covers:
• Upgrade planning: strategy,
scheduling, staffing, and cost
estimation
• Executing the upgrade: system
landscapes, Unicode, testing,
and training
• Upgrade tools: SAP Solution
Manager application management
solution, upgrade assistant, and
application-specific upgrade toolbox
Managing SAP ERP 6.0 Upgrade
Projects guides you through all
phases of the project and gives
insight on project management
approaches, best practices, possible
errors, resources, and tools.
Technical upgrade New functionality
Focus on currently
used functionality
• Get rid of unused modifications
• Move to SAP® standard functionality
• Create stable foundation for further
improvement
Figure 5: Upgrade Strategies
• Complexity of the existing IT land-
scape and the number of SAP
software systems to be upgraded
• Schedule and overlap with other
IT projects such as global rollouts,
ongoing innovation projects, or con-
solidation projects
• Upgrade strategy and project scope
If you have more than one SAP soft-
ware system, such as a production
system and a development system, you
must consider the entire system group.
It is recommended that you upgrade
your systems in the same sequence in
which you transport your modifications.
SAP recommendation: To identify
dependencies with other IT projects,
you should carry out an inventory on
all running projects and ensure that
the project timelines are compatible.
Schedule an upgrade for a period of
low business activity and look for favor-
able windows for the downtime phase.
Determining an Upgrade Strategy
Successfully executing an upgrade
requires a well-defined upgrade strategy
encompassing an approach and project
Enterprise services
Implement new functional requirements
from the business
• Implement new and enhanced
SAP standard functionality
• Implement enterprise services to
optimize business processes
• Innovate and be flexible to business
needs
scope based on the circumstances
and aims of your organization. The proj-
ect strategy has a great effect not only
on project duration and effort but also
on the immediate ROI of the upgrade.
The upgrade strategy usually consists
of several stages that progressively
expand functionality, increase business
value, and prepare the organization for
the transition to enterprise SOA while
minimizing risk. This process typically
lasts three to five years and consists
of three distinct phases: the technical
upgrade, functional enhancements,
and strategic enhancements.
Phase 1: Technical Upgrade
This initial phase involves a purely tech-
nological upgrade whose major goal is
the implementation of the new soft-
ware release as the foundation for all
subsequent improvements. The impact
of this phase on your business and
business processes is very limited:
• Previously used business functions
are retained.
• Modifications and custom develop-
ments are reduced (which reduces
cost of operations and system
complexity).
• Unicode conversion may take place.
The technical upgrade simply creates
the basis for functional and strategic
enhancements.
Note: For SAP CRM 7.0, a technical
upgrade from SAP CRM 4.0 or 5.0
must be combined with a functional
migration to the new Web client user
interface in SAP CRM. The upgrade
and migration processes are described
in the SAP CRM 7.0 Upgrade Master
Guide.
Phase 2: Functional Enhancements
(New Functionality)
Directed toward business benefits, this
phase focuses on increasing business
value by implementing the most valu-
able functions of the new software and
laying the foundation for future busi-
Upgrade Experience Database
SAP customers planning an
upgrade project often request
benchmarking data or project
statistics gathered from upgrades
completed by other customers.
SAP stores this data in a database
that includes information about:
• Project duration
• Business downtime
• Reasons for upgrade
• Satisfaction with the upgrade
To learn about the experiences
of other customers, see
www.service.sap.com/upgradedb.
ness innovation and improved process
automation. During this phase, SAP
software modifications and custom
developments are replaced with (new)
standard SAP software functions.
Operational excellence is improved by
picking and implementing “low-hanging
fruit” – functions that offer the greatest
business benefit with the least effort.
Even though this phase can be com-
bined in a single project with the techni-
cal upgrade, statistics show that more
than 80% of SAP customers approach
this second phase as a separate proj-
ect, to be conducted after a technical
upgrade has been completed and over-
all stability has been reached.
Phase 3: Enterprise Services
(Strategic Enhancements)
Phase three involves implementing
new and optimized business processes
and scenarios that fully exploit new
functions and enable SOA. It may
include implementing other software
systems or components and is very
much dependent on the business
needs of your organization. SOA
enables you to shorten application
innovation life cycles and implement
strategic business enhancements at
your own speed.
Cost and Effort Estimation
Large organizations running multiple
upgrade projects usually start with a
high-level cost and effort estimation for
a company-wide upgrade program. This
estimation is based on results from a
reference upgrade – usually performed
on a copy of a typical productive SAP
software system. SAP customers may
also use experience from previous
upgrade projects and benchmark data
from analysts or SAP to detail the
upgrade costs in major cost categories.
After the high-level estimate, cost and
effort factors should be considered
in detail. Assuming the project scope is
only a technical upgrade, these are
some of the indicators and examples
used in cost estimation:
• Costs of internal IT and business
staff
– General project and change man-
agement aspects (involves about
10% of the total project effort)
– Time for general project application
adjustments (for example, one
hour for each simple adjustment
of SAP software modifications or
custom developments)
– Testing effort (involves up to 40%
of total project effort, depending
on the degree of application adjust-
ments and the maturity of existing
test procedures)
– Training effort, if applicable –
depends on the number of users
affected, the training concept
used (classroom versus e-learn-
ing), and the extent of functional
enhancements
• Costs for external assistance
• Additional hardware costs, if applica-
ble (for example, server adjustments
– of the CPU, hard disk, or memory)
• Additional license costs for third-
party or SAP software, if applicable
(and if the costs are not yet covered
by contracts for SAP Business Suite
applications)
Getting Started with an Upgrade 27
The high-level cost estimation usually
results in a basic cost assumption
per business user affected. Analyst
reports, such as AMR and Forrester
studies, offer number ranges as a
guideline.
SAP recommendation: For a detailed
cost and effort estimation, the results
of a test upgrade and an in-depth sys-
tem analysis of the level of complexity
are recommended best practices. The
individual conditions of each system to
be upgraded, specific risk factors, and
technical limitations may become
potential cost drivers. Therefore, you
should establish assumptions for signif-
icant cost drivers and apply them to the
specific conditions of your existing
solution.
Project and Risk Management
Once the detailed project-specific cost
and effort estimation is completed and
approved, you need to determine a
Technical Upgrade Planning for
SAP® ERP
This SAP® service allows you to eval-
uate your upgrade project through
the combination of remote analysis
and a two-day on-site workshop that
covers a cost estimate, an estimate
of effort required, and a milestone
plan for executing your upgrade proj-
ect. The service results in a “deci-
sion document” that can serve as a
foundation for a fixed-price SAP pro-
posal for technical upgrade
execution.
governance structure and then allocate
the necessary resources. At the end of
this preparation phase, you can set up
a project kickoff meeting during which
the team can agree on other standards,
procedures, and milestones. In subse-
quent project phases, a project manag-
er should conduct progress tracking,
budget monitoring, capacity and
resource management, efficient escala-
tion management, and communication
and change management, as well as
coordinate the application and technical
teams.
Success Factors
These factors are critical to the suc-
cessful management of an upgrade:
• Appropriate governance structure
and top management commitment,
which ensure involvement of IT
and business units; fast escalation
and issue-resolution procedures;
alignment with other IT initiatives;
required resources; and so forth
• Sufficient capacity
Upgrade and Migration
Assessment for SAP CRM
If your organization intends to
upgrade your SAP Customer Rela-
tionship Management (SAP CRM)
3.1, 4.0, 5.0, or 2007 application to
the new release of SAP CRM, this
service will show the benefits or
value in upgrading and how the
upgrade will help you to meet busi-
ness objectives. The service is
designed to help SAP customers
prepare and plan for a successful
and optimal upgrade. By analyzing
the current SAP CRM application
to be upgraded, the service deliv-
ers various assets for planning your
upgrade.
• Project team with suitable skill set
• Adherence to project standards and
guidelines
• Clearly defined project scope and
reliable change management proce-
dures, especially for the handling of
the code-freeze period (Note: the
code freeze is the point in an upgrade
project from which the source code
cannot be changed until the produc-
tive system goes live.)
Standards and Procedures
To ensure the efficiency and transpar-
ency of the critical project tasks and
overall progress of the project, these
comprehensive standards and proce-
dures are necessary:
• Standards for project documentation,
problem solving, progress tracking,
and procedures for escalation
• Project approach and scope (for
example, technical upgrade only)
• Roles and responsibilities of the inter-
nal and external resources involved
• Setup of project landscape and
code-freeze procedures
• Guidelines and procedures for testing
and training strategy
SAP Solution Manager and the SAP
Upgrade Road Map content can help
you define standards and procedures
and help ensure they are adhered to.
Project Duration and Sequencing
As shown in SAP’s upgrade experience
database, the average duration of a
technical upgrade to SAP ERP 6.0 is
about three to five months. Figure 6
outlines SAP’s recommendation on
how to divide the upgrade effort into
different phases for a four-month
upgrade project.

April
Calendar week 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40
1 Project preparation
2 Blueprint
3 Realization
4 Final preparation for cutover
5 Going live and support
Overall project duration: About 4 months
Project characteristics: Assumed start release SAP® R/3® 4.6C; assumed target release: SAP ERP 6.0
SAP recommendation: There are
various strategies for sequencing the
activities involved in an upgrade. To
help ensure the best possible mainte-
nance (such as corrections and code
changes) of your productive SAP soft-
ware landscape, SAP recommends that
for each productive software system,
you perform a test upgrade by building
up a “project system” from a copy of
the software system. Working with a
project system allows you to test-drive
the majority of project tasks, such as
application adjustments and unit test-
ing, before the actual project landscape
(including development and quality
assurance systems) is upgraded.
This risk-minimized approach also
reduces the code-freeze period.
Upgrade Management Tools and
Assistance
To keep your upgrade on track, take
advantage of SAP Solution Manager,
May June July
5 weeks
8 weeks
3 weeks
Code freeze
SAP Upgrade Road Map, and – when
needed – expert outside assistance.
SAP Solution Manager
You can use SAP Solution Manager
to help with:
• Implementation and upgrade of
SAP solutions
• Implementation of SAP enhancement
packages
• Monitoring your solution
• Accessing services and support
• Managing project documentation
efficiently
• Documenting business processes
affected by the upgrade
• Accessing integrated testing
and user training functions
Using SAP Solution Manager through-
out the life cycle of your SAP applica-
tion leads to a faster implementation
and more efficient operation of the
SAP application by providing all imple-
mentation and upgrade content for
commonly used standard processes.
Figure 6: Milestone
August September Planning in a Techni-
cal Upgrade Project
2
weeks
In addition, projects become more
transparent, having up-to-date central
project documentation all in one place
at any point in time.
“With SAP Solution Manager we
can test system adjustments far
more quickly than we used to
be able to. Test distribution,
performance, checking, and
validation are also a lot more
transparent now.”
Detlev Voss, Test Manager,
Südwestfalen Energie und Wasser AG
For technical reasons, you require an
SAP Solution Manager software sys-
tem to upgrade your SAP application.
During the upgrade process you will
be prompted to enter an SAP Solution
Manager key. Without this key, the
Getting Started with an Upgrade 29
upgrade process cannot continue.
Therefore, you should install or upgrade Plan Build
to the latest release of SAP Solution
Upgrade Discovery Upgrade Evaluation Upgrade Implementation
Manager.

Maintenance Optimizer for SAP

Solution Manager SAP® Upgrade Road Map
The maintenance optimizer for SAP Project Blueprint Realization Final Production
Solution Manager is the central tool for Preparation Preparation Cutover and
planning, executing, and managing the for Cutover Support
installation of support packages and Document Specify imple- Implement and Perform Execute
patches across the entire SAP solution ­current solution mentation scope adjust solution inte­gration and production
landscape. and set up and solution ­system tests ­system ­upgrade
project ­adjustment and plan cutover and support
needs
During the installation of SAP enhance-
ment packages, the maintenance opti-
mizer also helps you to find and down- Figure 7: SAP Upgrade Road Map Content
load the necessary bundles of software
components and provides the informa- SAP Upgrade Road Map SAP Upgrade Road Map 3.2 includes
tion to the implementation tools. The SAP Upgrade Road Map content is upgrade content for the entire
When you combine the installation of delivered with SAP Solution Manager. SAP Business Suite, including
enhancement packages with the instal- It provides a standard methodology SAP NetWeaver.
lation of support packages (as recom- including best practices for all project
mended by SAP), there are mutual management, technical, and business For offline use, SAP Upgrade
dependencies to be taken into account. aspects of a technical upgrade project. Road Map is also available in
These dependencies are handled auto- With its checklists, templates, and HTML format. You can download
matically by the maintenance optimizer. how-to descriptions, the road map aims it from www.service.sap.com
to provide guidelines to the project /upgraderoadmap.
manager and the application and tech-
Usage Guide: Upgrade Projects with nical teams to help them accelerate and
the SAP Solution Manager optimize primary project activities.
This document (available at
www.service.sap.com The road map (see Figure 7) is struc-
/upgraderoadmap) helps you decide tured in five phases and provides
how the SAP® Solution Manager access to further tools, such as the
application management solution solution browser and the application-
can be beneficial during an upgrade specific upgrade toolbox from SAP.
of SAP software. The guide details
all functions that support upgrades.
External Assistance
If your internal resources are limited or
47%
your staff lacks the skills required for
an upgrade to any of the SAP Business 53%
Suite applications, there are coaching 59%
or specialized services available to 6%
help you avoid surprises and keep your 35%
project on time and within budget. 18%
SAP surveys indicate that most SAP
customers rely on some external assis- 0% 10% 20% 30% 40% 50% 60%
tance to help ensure the best outcome Yes – to provide project management for all project phases
for their upgrade projects. Figure 8 Yes – to provide migration services
shows the proportion of customers Yes – to assist in correcting development objects
who use external assistance in the vari- Yes – to assist in the project planning phase
Yes – to execute the technical upgrade
ous areas of an upgrade. No – covered with internal resources only

SAP supports its customers with tai-

lored expert services. It also provides Figure 8: Customer Use of External Assistance for an Upgrade
holistic engagement concepts such as
the SAP Safeguarding for Upgrades
portfolio of services or upgrade coach
services. With the coach services, an
SAP coach experienced in all aspects
of project management and technology
assists you with your upgrade.

Getting Started with an Upgrade 31

Executing an Upgrade
Meet the Challenges Successfully
with Tested Recommendations
The improved technology that SAP
introduced with the upgrade to SAP
R/3 Enterprise makes upgrading con-
siderably easier. This applies to all SAP
Business Suite applications. According
to recent results from SAP’s upgrade
experience database, current upgrade
procedures for the technical execution
meet or exceed customers’ expecta-
tions in 86% of the upgrades to SAP
ERP 6.0. Nevertheless, you and your
organization must be prepared for chal-
lenges in each project phase to help
ensure your upgrade runs smoothly.
A survey conducted by SAP in 2008
reveals which areas are perceived to
be major challenges during the upgrade
implementation phase and what per-
centage of survey participants found
them particularly challenging:
• IT infrastructure adjustment (39%)
• Downtime minimization (54%)
• Application and modification
adjustments (48%)
• Efficient testing (64%)
• User training (39%)
This section provides details, best
practices, and SAP recommendations
for each of these areas.
IT Infrastructure Adjustments
SAP’s upgrade experience database
shows that 40% of SAP customers do
not need to adjust their hardware con-
figuration for an upgrade. However, in
most cases they do find it necessary to
make adjustments to their IT infrastruc-
ture. These adjustments may include
resizing the application server, deploy-
ing new front-end components, making
network adjustments to maintain
32 Getting Started with an Upgrade
system performance, upgrading or
migrating your operating system and
database platform, and converting to
Unicode.
Resizing the Application Server
You should check whether you have
sufficient hardware resources, such as
CPU, main memory, disk space, and
swap space. For more information
about sizing, see SAP Service Market-
place at www.service.sap.com/sizing.
The sizing guidelines provide informa-
tion on how to perform a delta sizing
for technical upgrades (without func-
tional extensions).
For new releases of SAP Business
Suite applications, SAP provides
details of delta sizing requirements in
the SAP Notes. SAP also provides
Quick Sizer, a free tool to help you get
an initial sizing assessment.
As a rule of thumb, with each new
release of SAP ERP, the demands on
hardware for the application server
increase about 10%. Upgrading to SAP
ERP 6.0 from start release SAP R/3
4.6C increases the demands on appli-
cation server memory by 55% and on
the application server CPU by 22%.
SAP CRM 7.0 is a much-optimized
release and requires fewer resources,
compared to SAP CRM 2007, in sever-
al key processes. For example, in the
sales-order creation process, under
internal test conditions, database load
was 20% less. Application server and
memory requirements remain almost
constant.
Deploying New SAP Front-End
Components
SAP recommends you use and deploy
the latest release of its graphical user
interface (SAP GUI), which is down-
ward compatible with previous SAP
applications. To run the latest GUI, you
may need to upgrade hardware or the
operating system of user PCs. More
tips and tricks on the cost-efficient
deployment of the SAP front end are
contained in the SAP front-end deploy-
ment strategy document (see “Further
Information”).
With SAP Business Suite 7, the appli-
cations’ user interfaces have been har-
monized. A new visual design (“signa-
ture design”) provides a common look
and feel for the standard SAP clients,
which include:
• SAP NetWeaver Portal
• SAP NetWeaver Business Client
software
• A new Web client user interface in
SAP CRM
• SAP GUI for Windows
Web Dynpro development environment
ABAP™ programming language is the
standard UI technology for all new user
interfaces in SAP Business Suite 7
applications except SAP CRM, which
has its own Web client user interface
framework technology. As of SAP
CRM 2007, the SAP GUI is no longer
the client for accessing SAP functions
in SAP applications. It is replaced by
the new Web client user interface in
SAP CRM (although SAP GUI is still
required for system administration
functions and maintaining application
customizing).
For more details of user interfaces in
SAP Business Suite, see the Wiki at:
www.sdn.sap.com/irj/scn/wiki?path=
/display/Found/Simplified+User+
Experience+in+SAP+Business+Suite.
Making Network Adjustments to
Maintain System Performance
To avoid performance bottlenecks
after an upgrade to SAP Business
Suite applications and help ensure your
system performs the same as or better
than it did before, SAP offers the white
paper Front-End Network Require-
ments for SAP Business Solutions,
which summarizes key recommenda-
tions for an optimized network configu-
ration. The guide includes requirements
for all individual SAP applications such
as the Web client user interface in
SAP CRM, and SAP NetWeaver Por-
tal. However, it is strongly recommend-
ed that you conduct measurements
on your actual system to perform ade-
quate network sizing.
SAP® GoingLive™ Functional
Upgrade Check Service
This service can help you prevent
unforeseen costs before, during,
and after your upgrade:
• During the upgrade, it estimates
the need of IT infrastructure
adjustments and provides a ser-
vice plan with recommendations
– for example, how to minimize
cost-intensive system
downtimes.
• After the upgrade, you benefit
even further with optimal use of
your system resources.
Upgrading or Migrating Your Operating
System and Database Platform
This is a potential prerequisite for per-
forming a technical upgrade. Further-
more, some customers see the
upgrade project as an opportunity to
change their operating system or data-
base vendor to reduce their cost of
operations.
Converting to Unicode
If you are converting to Unicode with
the going-live phase of the upgrade
project, you need to consider additional
sizing requirements such as those
described in the dedicated SAP Notes
(see “Further Information”). The notes
also explain the reasons for a Unicode
conversion.
Technical Deployment
With the upgrade to SAP R/3 Enter-
prise software in 2003, SAP significant-
ly improved its upgrade procedures by
introducing system switch technology.
Today this technology is used consis-
tently for all SAP Business Suite appli-
cations based on the ABAP program-
ming language, as well as for
Java-based applications.
Benefits of System Switch Technology
With this technology, you can “switch”
one release of an SAP software sys-
tem (for example, an older release of
SAP R/3) to a target release level (for
example, SAP ERP 6.0) in a one-step
procedure. In contrast to migration
techniques, the switch technology
adjusts the new SAP software, the
underlying database, and related data
structure in an “in-place” procedure
without moving data outside the data-
base. Compared to the previous
upgrade technology, system switch
technology moves major activities from
the downtime to the uptime phase. For
example, for SAP ERP 6.0, this reduc-
es the average “technical downtime”
of an upgrade (which averages about
eight hours) by more than 50% com-
pared to previous upgrades from
releases of SAP R/3 to SAP R/3 4.6C.
Because the central component of
SAP ERP remains stable, the technical
upgrade is also much more predictable
and simpler than upgrades to previous
SAP R/3 releases.
Enhancement Package Installer
The new enhancement package install-
er tool is available as of enhancement
package 4 for SAP ERP 6.0. The install-
er aims to be reliable and intuitive by
building on the mature, stable, and
optimized system switch procedure. It
provides an improved user experience
due to its intuitive guided procedure.
This results in a streamlined installation
process. SAP recommends that you
always use the latest enhancement
package installer version that is avail-
able on SAP Service Marketplace.
To minimize the effort of installation
and testing, SAP recommends that you
should combine the application of both
enhancement packages and support
packages in one queue.
For more information on SAP
enhancement packages, visit
www.service.sap.com/erp-ehp.
Minimizing Downtime
Total downtime is divided into technical
downtime and business downtime.
Getting Started with an Upgrade 33
Technical downtime is time during
which the software system cannot be
used productively. It does not include
time for data backup, testing, and so
on. Business downtime is the time
(planned and unplanned) that the soft-
ware system or solution is not available
to users. It includes technical downtime
plus the time necessary for the data
backup and final tests.
You can reduce technical downtime by:
• Choosing a “downtime-minimized”
instead of the “resource-minimized”
strategy. (This is determined by the
preconfiguration mode during the
technical upgrade. For details, see
information on the upgrade guide for
each application.)
• Doing a preupgrade cleanup of data-
base tables affected by data conver-
sion activities during the downtime
• Using the SAP transaction code for
incremental table conversion, ICNV,
during uptime for tables with an
altered structure. The system switch
upgrade enables you to use transac-
tion ICNV for tables that have been
modified by support packages, add-
ons, or customer developments.
• Upgrading after hardware infrastruc-
ture has been reconfigured,
enhanced, or resized (if you are per-
forming any of these tasks), which
increases the speed of database-
related activities in particular
• Ensuring you always use the latest
patch of the upgrade tool
The size of the database has no direct
impact on the duration of technical
downtime.
34
Total business downtime can be influ-
enced by additional factors such as:
• Backup strategy – Depending on the
amount of time available, using an
online backup instead of an offline
backup strategy can further reduce
total downtime, while technologies
such as split-mirror backup can
reduce backup downtime to zero.
• Postupgrade activities – The time
required to prepare the system for
release to users can be increased
depending on the languages installed,
the other transports you want includ-
ed in the system, and the duration of
user acceptance testing. The
upgrade guide for each application
describes the follow-up activities that
you need to perform after you have
upgraded your SAP software system.
Application-Specific Upgrade
Toolbox
The application-specific upgrade
toolbox can also help you with all
postupgrade activities. When you
upgrade an SAP® software system,
in addition to the actual technical
upgrade, you often have to perform
additional application-specific steps
before and after the upgrade.
The toolbox enables you to recog-
nize the necessary steps and
perform them in the system in a
controlled manner. The toolbox is
integrated with the upgrade GUI
and can also be accessed from the
SAP Upgrade Road Map content
(www.service.sap.com
/upgraderoadmap).
Each SAP software system is highly
individual in terms of its configuration
and application data. Therefore, an
accurate forecast of total duration
of the upgrade and downtime is only
possible after you have analyzed the
results of a test upgrade with a repre-
sentative hardware configuration and a
volume of data.
Application and Modification
Adjustments
Using a project system (a test-drive
system), you can readily identify all
relevant SAP software modifications
and necessary adjustments. As a
result, you can minimize the time it
takes to make the actual adjustments
to the development system.
Application adjustments for a technical
upgrade involve four major areas:
adjustments to SAP software modifica-
tions; adjustments to custom develop-
ments; upgrade (delta) customizing
for existing business processes and
standard SAP software functions; and
adjustments to interfaces or connected
SAP applications and third-party
products.
In the future, SAP enhancement pack-
ages are expected to minimize the
need for application adjustments, since
new functions can be selectively acti-
vated with very limited impact on the
application in use. Building on a stable
core significantly reduces the need for
application adjustments.
Adjustments to SAP Software
Modifications
The upgrade process replaces modified
SAP objects with standard SAP objects.
Modifications that are still needed after
the upgrade must be adjusted. You can
readily identify and handle all relevant
SAP software modifications as well
as related database and data structure
changes by using the tools SAP pro-
vides for modification adjustment.
Adjustments to Custom Developments
In contrast to modified SAP objects,
custom software developments are
not directly affected by the technical
upgrade process. However, since these
custom developments are embedded
in other SAP objects and often refer-
ence standard objects that might have
changed during the upgrade, they also
require adjustment activities. SAP
release notes are the primary informa-
tion source for identifying if and how
much custom code must be changed
to remain compliant with the standard
functions provided in SAP Business
Suite applications. These adjustments
can be done using the standard
SAP development tools. Furthermore,
SAP offers a custom development
optimi­zation package to help you han-
dle custom developments effectively
during an upgrade and over the entire
solution life cycle.
SAP recommendation: If SAP software
modifications and custom develop-
ments are no longer in use, you should
eliminate them as part of the applica-
tion adjustment activities in the devel-
opment system to decrease future
maintenance costs. SAP statistics
show that many custom developments
and reports are not used in any case.
SAP uses standardized tools (as part
of the quick upgrade evaluation ser-
vice, for example) to analyze system-
specific conditions. This helps you
assess the impact of the upgrade and
provides a reliable foundation for a cost
and effort estimation.
Upgrade Customizing for Existing
Business Processes
In most cases, there is no need to
change customizing settings for
existing business processes after an
upgrade. However, in certain areas,
specific customizing adjustments may
need to be performed to help ensure
existing business processes and stan-
dard SAP functions are running proper-
ly. In this case, the necessary custom-
izing adjustments can be highlighted
in the implementation guide for upgrade
(delta) customizing (see the “Further
Information” section).
With the upgrade, some transactions
may become obsolete, replaced by
new functionality. Information about
further application adjustment require-
ments is collected and delivered to
SAP customers via the application-
specific upgrade toolbox.
Adjustments to Interfaces or
Connected Applications
Since certain business processes run
across systems or use third-party prod-
ucts, it is important to ensure that all
interfaces are documented properly prior
to the upgrade so they can be checked
effectively during the upgrade project.
For SAP CRM, SAP Note 1037748
describes how to display fields in the
new Web client user interface in SAP
CRM that have been enhanced in a
tool called the easy enhancement
workbench.
Testing
Thorough testing is critical to minimiz-
ing the risk of business disruption in
any SAP project, even in purely tech­
nical upgrade projects. Based on a sur-
vey conducted by SAP in 2007, 68%
of SAP customers claim testing is a
major cost driver and challenge in
upgrade projects.
The need for and the effort involved in
testing is determined by the level of
application adjustments and the func-
tional scope of the project. The effort
can be reduced through organization
and preparation. The focus of testing in
upgrade projects should be on core
business processes including interfac-
es, forms, authorizations, and develop-
ments. The manual effort and user
involvement in testing can be reduced
by developing comprehensive proce-
dures and ensuring the transparency of
existing business processes. However,
reducing by too much the time and
money spent on testing – or neglecting
to implement adequate testing stan-
dards and procedures – can jeopardize
critical business processes. Often,
insufficient transparency of critical pro-
cesses or an incomplete test catalog
prevents SAP customers from perform-
ing accurate testing.
Getting Started with an Upgrade 35
SAP provides tools for planning and
executing tests in a streamlined and
cost-efficient manner to help you strike
the balance between high-quality test-
ing and affordable effort. SAP Solution
Manager provides integrated access to
a test organizer and extended comput-
er-aided test tools. For example, it can
help organize test cases and provide
transparency on available manual or
automated test cases by documenting
the cases according to major business
processes. These test cases can be
used for unit tests and to define test
plans for regression and integration
testing in the upgrade project. SAP
Solution Manager can also reduce
manual testing effort considerably and
help guarantee high-quality testing
results and transparent test progress
even beyond the SAP software
upgrade. Test automation, especially
for regression testing (which is also
relevant when applying support pack-
ages for SAP applications), can be a
significant testing accelerator and con-
tributor, reducing manual testing effort
by up to 40%.
SAP recommendation: For SAP soft-
ware upgrade projects of about four
months’ duration, at least three weeks
should be dedicated to regression and
final integration testing.
If you need to build up test systems or
other nonproductive systems more
often, the SAP Test Data Migration
Server software can help ensure con-
sistent and high-quality test systems
by minimizing hardware investment. In
addition, partner tools and dedicated
36 Getting Started with an Upgrade
SAP service offerings can help process. If there are only limited user
optimize the entire test management interface changes but a high number of
process. (For details, see www.service. users across the globe who need train-
sap.com/upgradeservices.) ing, an e-learning approach could also
enable more streamlined training.
User Training
You can find details of the courses
As with testing, the user training effort offered for SAP Business Suite appli-
very much depends on the upgrade’s cations at www.sap.com/services
functional scope and the extent of /education/index.epx. For an upgrade
application adjustments. The effort to SAP ERP 6.0, the upgrade course
involved also depends on your com­ finder helps you locate courses that
pany’s organizational readiness to deal train your project team to introduce
with this topic (for example, by using employees to SAP ERP: www.sap.com
accurate and complete training /services/education/catalog/erp
material). /coursefinder.epx.
A purely technical upgrade has limited SAP also offers e-learning solutions
impact on the interfaces employees are and a documentation tool integrated
using. Where the source release is with SAP Solution Manager to provide
SAP R/3 4.6C or higher, an upgrade methodology support and expert
to SAP ERP 6.0 will barely affect users, guidance to suit your specific needs.
since SAP ERP 6.0 employs the same
user interface. For releases below SAP
R/3 4.6C, the impact could be consid-
erably higher, because some crucial
SAP transactions were redesigned in
SAP R/3 4.6C. With SAP CRM 7.0,
you may need to migrate to a new user
interface depending on the upgrade
source release; the new Web client
user interface in SAP CRM was intro-
duced with SAP CRM 2007.
SAP recommendation: For a cost-
effective execution of delta training
for users, SAP suggests investigating
alternatives to standard classroom
training – for example, employing a
train-the-trainer concept to multiply
knowledge provided to users via busi-
ness process experts in a cascading
Tomorrow’s Solution Today
Why Put Off the Advantages an Upgrade
Offers Your Organization?
SAP Business Suite 7 applications pro-
vide great potential for improving your
current business operations, expanding
your current functionality, and helping
you innovate to meet changing busi-
ness requirements. Current through
2015, the go-to releases of the SAP
Business Suite applications also help
ensure a stable, long-term IT platform
that minimizes risk and maintenance,
enabling your organization to keep up
in a dynamic and competitive business
world.
Satisfaction with SAP software
upgrades has increased significantly
over the past 10 years thanks to the
robustness and stability of the core
applications, improvements in SAP
upgrade technology, and the assistance
SAP provides in all areas of an upgrade.
Sensitivity to the potential challenges
of an SAP software upgrade and
knowledge of how to master these
challenges by using best practices and
establishing standards and procedures
should make the transition to SAP
Business Suite 7 smooth and straight-
forward. Thus, there is little reason to
postpone an upgrade. Now is the time
to start maximizing the benefits of your
SAP investment.
Key Messages for IT Decision
Makers
An upgrade to the latest release of an
SAP Business Suite application offers
significant advantages for your organi-
zation in several areas if you prepare
for it appropriately:
• Wide-ranging benefits – The new
software provides a stable, flexible
foundation with a wealth of new fea-
tures and functions that maximize
your existing SAP investment. How-
ever, do not expect to find a single
decisive factor to justify the upgrade.
Instead, take a holistic approach and
analyze the wide range of benefits
an upgrade can bring to various areas
of your organization.
• Business-driven justification –
Identify your crucial business require-
ments and the aspects of your
business model that could change
or be improved, and then map your
needs to the functions available in
SAP Business Suite 7 applications.
The tools and services offered by
SAP can help you identify the con-
crete benefits of the upgrade.
• Inclusive evaluation process –
There is potential for both business
units and IT departments to derive
great value from SAP Business Suite
7 applications. Ensure cooperation
and consultation between these
areas, and weigh opportunities
against potential risks.
• Coordination with IT strategy –
Executing SAP software upgrades
has become much more straightfor-
ward and predictable in recent years.
However, you should make sure an
upgrade fits your overall IT strategy
and does not conflict with other IT
projects.
Key Messages for Project Manag-
ers and Technical Project Leaders
The following are key messages for
project managers and technical project
leaders involved in an upgrade:
• Take upgrades seriously – Plan and
manage upgrades as carefully as you
do other SAP projects, such as by
establishing comprehensive project
standards and procedures. SAP
Solution Manager can help you plan
and manage an upgrade.
• Prepare your system(s) – Cleaning
up modifications and performing
selective archiving can reduce the
effort of an upgrade considerably.
• Test the upgrade – Get prepared
by doing at least one test upgrade in
the early planning phase to identify
potential risks, technical challenges
and limitations, and cost drivers.
• Take a multistep approach – Perform
a technical upgrade first, and then
implement new functions or business
innovations in subsequent projects.
• Leverage improved upgrade tech-
nology – Upgrading involves signifi-
cantly lower impact, less effort, and
shorter downtime than upgrades to
previous releases of SAP Business
Suite software.
• Plan comprehensive testing –
Do not underestimate the effort
involved in testing. Testing effort
will be determined mainly by the
need for application adjustment and
the functional scope of the upgrade.
• Train users – The need for user
training depends on how much new
functionality is implemented. Consider
using alternative training concepts
such as e-learning or a train-the-
trainer approach.
• Ask for expert help as needed –
Consider using external assistance
(including offerings from SAP) to
complement your internal resources
in specific areas (for example, for a
Unicode conversion) rather than
endanger the project.
Getting Started with an Upgrade 37
Further Information
The resources outlined in this section
provide more specific or detailed infor-
mation on upgrading to SAP Business
Suite 7 applications. In the following
tables, most of the online resources
listed take you to SAP Service Market-
place, which requires registration. SAP
Notes are also published on SAP Ser-
vice Marketplace, which can be
accessed at www.service.sap.com.
“Upgrading to SAP ERP 6.0 was
quick and painless, and the
functional enhancements have
provided significant business
value.”
LaBaugh Stansbury, Director IT, Pittsburgh
Water & Sewer Authority
Upgrade Information Center
The Upgrade Information Center desti-
nation on SAP Service Marketplace
(www.service.sap.com/upgrade) is the
location you should go to first to look
for more information on the upgrade
topic. The Upgrade Information Center
contains a variety of brochures, pre-
sentations, and dos and don’ts, as well
as region-specific sites.
38 Getting Started with an Upgrade
Community Network
The community network is an online
reference and collaboration resource
consisting of the SAP Developer
Network, the Business Process
Expert community, and the SAP
BusinessObjects™ community. You
can access these resources at
www.sdn.sap.com.
Help Portal
The help portal at http://help.sap.com
provides Web-based documentation for
all SAP solutions. It also has additional
information about documentation, edu-
cation services, and information design
at SAP.
Upgrade Competency Centers
The upgrade competency centers in
APJ, EMEA, and North and Latin
America are centers of expertise for
customer upgrades and strengthen the
upgrade support within the regions.
It is their mission to drive a coherent
set of upgrade-focused products, tools,
and services to support customers
and partners. The upgrade competency
centers in each region can assist in a
quick start on an SAP ERP 6.0 upgrade
and help with any SAP Business Suite
and SAP enhancement package topic.
Contact the upgrade competency
center closest to you:
• APJ: upgradeccapj@sap.com
• EMEA: upgradecc@sap.com
• Latin America: upgradeccla@sap.com
• North America: upgradeccna@sap.com
Identifying the Value Proposition
and Justifying the Upgrade
Understanding the Release Strategy for SAP® Business Suite
and Determining the Value Proposition
Topic
Maintenance timelines for the SAP®
Business Suite 7 applications
SAP release strategy
Overview of SAP Business Suite 7
applications and enhancement packages
Further Information Sources
SAP maintenance strategy:
www.service.sap.com/maintenance
SAP’s release strategy for large enterprises:
www.service.sap.com/releasestrategy
Overview of SAP Business Suite:
www.service.sap.com/businesssuite
• Application-specific overviews
– SAP ERP: www.service.sap.com/erp
– SAP Customer Relationship Management (SAP CRM): www.service.sap.com/crm
– SAP Supply Chain Management (SAP SCM): www.service.sap.com/scm
– – SAP Supplier Relationship Management (SAP SRM): www.service.sap.com/srm
– – SAP Product Lifecycle Management (SAP PLM): www.service.sap.com/plm
– – SAP NetWeaver® technology platform: www.service.sap.com/netweaver
• Enhancement packages for SAP ERP: www.service.sap.com/erp-ehp
• What IT Professionals Need to Know About SAP Enhancement Packages for SAP ERP:
www.service.sap.com/~sapidb/011000358700001166742007E
Getting Started with an Upgrade 39
Understanding the Release Strategy for SAP® Business Suite and Determining the Value Proposition
Topic
Services provided by SAP for all upgrade phases, address-
ing all business needs across SAP Business Suite
Delta functionality of latest SAP ERP
release
Application-specific upgrade information
Further Information Sources
SAP upgrade services:
www.service.sap.com/upgradeservices
Solution browser tool for SAP ERP:
http://erp.fmpmedia.com/
• SAP ERP: www.service.sap.com/upgrade-erp
• SAP CRM: www.service.sap.com/upgrade-crm
• SAP SCM: www.service.sap.com/upgrade-scm
• SAP SRM: www.service.sap.com/upgrade-srm
• SAP NetWeaver: www.service.sap.com/upgrade-nw

Defining a Business Case

Topic Further Information Sources
Value assessment services from SAP Upgrade value assessment:
Overview

Planning an Upgrade
Assessing the Impact on Your Existing SAP® Software and System Landscape
Topic Further Information Sources
Overview of technical aspects of the upgrade “Transition and Upgrade to SAP ERP”:
SAP standard presentation
SAP® tools that support your upgrade from a functional SAP upgrade tools:
and technical perspective, including testing www.service.sap.com/upgradetools
Technical prerequisites and limitations of SAP Business Product availability matrix:
Suite applications www.service.sap.com/pam
Need for Unicode conversion for SAP Business Suite Unicode:
applications www.service.sap.com/unicode
www.service.sap.com/unicode@sap
Availability of country versions Localization:
www.service.sap.com/localization
Compatibility issues with other SAP applications, SAP process component list:
supported business scenarios, and processes www.service.sap.com/scl
Limitations for the former product SAP Internet SAP Note 709038: “SAP Integrated ITS”
Transaction Server

40 Getting Started with an Upgrade

Assessing the Impact on Your Existing SAP® Software and System Landscape
Topic
SAP tools for the technical execution of an SAP upgrade
Assessing the impact on other systems in your landscape
Estimating Costs and Effort
Topic
Consider benchmark information for project duration,
project effort, and so forth in preparing for final cost and
effort estimation
Use the tailored value assessment service from SAP to
estimate cost and effort
Managing Upgrade Projects Successfully
Topic
Project plan, standards, and guidelines
SAP Solution Manager application management solution
as a project documentation tool and advanced life-cycle
management platform
External assistance (including SAP offerings) to cover need
for expert knowledge or to fill resource gaps
Further Information Sources
• SAP upgrade tool and GUI for the ABAP™ programming language:
SAPup/SAPjup
• Application-specific upgrade toolbox
SAP upgrade dependency analyzer: www.service.sap.com/uda
Further Information Sources
SAP’s upgrade experience database:
www.service.sap.com/upgradedb
• Technical upgrade planning for SAP® ERP application: Overview
• Upgrade and migration assessment for SAP Customer Relationship
Management application: Overview
Further Information Sources
SAP® Upgrade Road Map content:
www.service.sap.com/upgraderoadmap
Usage guide for SAP Solution Manager in upgrade projects
SAP global upgrade services portfolio:
www.service.sap.com/upgradeservices
Getting Started with an Upgrade 41
Executing an Upgrade
Determining the Need for IT Infrastructure Adjustments
Topic
Updating desktop PCs because of new SAP® GUI
Requirements for and impact on network bandwidth
Application server resizing for the SAP ERP application
Information on hardware sizing and the Quick Sizer for all
SAP Business Suite applications
Requirements for and impact on network bandwidth
Unicode conversion and related impact on sizing
Implications for operating system and database
Unicode hardware sizing
SAP GoingLive™ Functional Upgrade Check service
42 Getting Started with an Upgrade
Further Information Sources
SAP Front-End Deployment Strategy
Network sizing guide:
Front-End Network Requirements for SAP Business Solutions
As a rule of thumb, servers must be resized about 10% for each higher
release. See these SAP Notes on delta sizing for previous releases of
SAP ERP software:
• 89305 (source release 4.0B)
• 113795 (source release 4.5B)
• 178616 (source release 4.6B)
• 323263 (source release 4.6C)
• 517085 (source release Enterprise 1.10)
• 752532 (source release Enterprise 2.00)
• 778774 (source release ECC 5.00)
• 901070 (source release ECC 6.00)
• Sizing guidelines: www.service.sap.com/sizing
• Quick Sizer: www.service.sap.com/quicksizer
Network sizing guide:
Front-End Network Requirements for SAP Business Solutions
SAP Note 79991: “Multilanguage and Unicode Support of SAP Applications”
Product availability matrix: www.service.sap.com/pam
SAP Note 1139642: “Hardware Requirements in Unicode Systems”
SAP GoingLive Functional Upgrade Check:
www.service.sap.com/goinglive-fu
Performing the Technical Deployment
Topic
Upgrade guides, upgrade master guides, component up-
grade guides, and migration guides
Enhancement package installation
Handling Other Technical Considerations
Topic
Technical prerequisites for using the SAP® Solution
Manager application management solution for generating
the installation key for setting up an actual application
solution landscape
Upgrade and migration guide for the new Web client user
interface in SAP CRM
Unicode conversion and upgrade
Unicode-related downtime optimization
Identifying the required software components to be upgrad-
ed in order to use specific enhancements
Further Information Sources
Comprehensive technical documentation, including installation and upgrade
guides for all SAP® Business Suite applications and industry solutions:
www.service.sap.com/instguides
How to install enhancement package 4 for SAP ERP 6.0:
How to Install EHP4: A Practical Guide
Further Information Sources
SAP Note 805390: “SAP Solution Manager Is Required for SAP Software”
• SAP CRM 7.0 Upgrade Master Guide
• SAP Note 1118231: “Supported User Interfaces for SAP CRM”
• SAP Note 928729: “Combined Unicode Conversion and Upgrade”
• SAP Note 959698: “Twin Upgrade and Unicode Conversion”
SAP Note 857081: “Unicode Conversion: Downtime Estimate”
SAP Note 1165438: “Enhancement Package 4 for SAP ERP: Required
Software Components”
Getting Started with an Upgrade 43
Performing Efficient Application Adjustments, Testing, and User Training
Topic
Analyzing and adjusting SAP® software modifications and
custom developments
Application adjustments and upgrade customizing
Additional application adjustments
SAP testing tools to execute tests through the upgrade and
afterward
Using the SAP Solution Manager application management
solution to increase efficiency of business-related upgrade
aspects such as testing or user training
Details of courses and education offerings from SAP
44 Getting Started with an Upgrade
Further Information Sources
• Quick upgrade analysis service and technical upgrade planning service:
www.service.sap.com/upgradeservices
• SAP software release notes:
www.service.sap.com/releasenotes
Use the SAP implementation guide – upgrade customizing.
(Note: this is not a document but a system tool that is installed
and handled by the system administrator.)
• SAP Note 623723: “Upgrade: Application-Specific Problems”
• SAP Note 1000009: “Application-Specific Upgrade Toolbox 2008”
SAP testing tools: www.service.sap.com/upgradetools
Usage guide for SAP Solution Manager in upgrade projects
• Training catalog for SAP Business Suite applications:
www.sap.com/services/education/catalog/index.epx
• Course finder for upgrades and delta training for the SAP ERP
application:
www.sap.com/services/education/catalog/erp/coursefinder.epx
Public Information Sources

The analyst reports below are available

on the Internet, as is the article from
RAAD Studie. The SAP presentations
can be accessed online at SAP Service
Marketplace, www.service.sap.com.
This site requires registration.

Analyst reports:
• AMR Research: “Reduce the Pain of
ERP Upgrades with Better Planning,”
June 2007
• Forrester Research: “SAP Harmonizes
Portfolio with Business Suite 7,”
March 2009
• Forrester Research: “Enhancement
Packages Improve SAP Upgrade
Value,” May 2008
• RAAD Studie: “IT-Markt
Deutschland,” December 2008

SAP presentations:
• “SAP Upgrade Experience
Database,” March 2009
• “SAP Transition and Upgrade to
SAP ERP,” March 2009

SAP white paper:

SAP Standard for Upgrades, April 2007

SAP Press book:

Martin Riedel, Managing SAP ERP 6.0
Upgrade Projects, April 2009, ISBN:
978-1592292684, SAP Press

Getting Started with an Upgrade 45

Index
Note: SAP product and service names
are indexed under the first word
following “SAP” (for example,
SAP ERP 6.0 is listed as “ERP 6.0”).
A Enhancement packages, 16
Application server resizing, 42
Application-specific upgrade
toolbox, 34, 41, 44
C – Support packages, 18
Compliance, 19
Cost estimation, 27
Cost of operations, 20
CRM
– Easy enhancement
workbench, 35
– Field enhancements, 35
CRM 7.0, 15, 23, 25
CRM Web client user interface,
15, 23, 27, 32, 43
Custom developments, 35, 44
Customizing 35, 44
D
Discovery process, 6
Downtime
– Business downtime, 34
– Incremental table conversion, 34
– Minimizing, 33
– Technical downtime, 34
46 Getting Started with an Upgrade
E M
Effort estimation, 27, 41 Maintenance optimizer, 30
Enhancement package installation, Maintenance strategy, 4, 19, 39
18, 43 Modification, 20
Modification adjustment, 34
– Compatibility, 18
– Embedded installation, 18 P
– ERP 6.0 with enhancement
package 4, 10, 17 PLM 7.0, 16, 23, 25
– Installation, 16, 18, 34 Project
– Duration, 28
Enterprise services, 19, 27 – Procedures, 28
ERP 6.0, 10, 23, 25, 26 – Sequencing, 28
External assistance, 31, 41 – Standards, 28
– Success factors, 28
F Project duration, 28
Project sequencing, 28
Front-end deployment, 32, 42
Q
G
Quick upgrade analysis service, 8, 44
GoingLive Functional Upgrade Check,
33, 42 Quick upgrade analysis service for
SAP Business Suite, 8
I R
Incremental table conversion (ICNV), R/3 plug-in, 24
34 Release strategy, 4, 39
Interfaces, 33, 35
IT infrastructure adjustments, 32, 42
L
Legal requirements, 19
Licensing, 20
S U
Safeguarding for Upgrade, 22
SAP GUI, 23, 32
Scheduling an upgrade, 26
SCM 7.0, 12, 24, 25
Service-oriented architecture, 4, 18
Software landscape
– Consolidation, 20
Solution browser tool, 7, 40
Solution Manager, 29, 41, 43, 44
– Maintenance optimizer, 30
SRM 7.0, 14, 24, 25
Success factors, 28
Support packages, 18
System landscape
– Dependencies, 21
System performance, 33
System switch, 33
T for SAP CRM, 28, 41
Technical deployment, 33, 43
Technical limitations, 22
Technical prerequisites, 22, 40, 43
Technical upgrade planning and
implementation for
– SAP Business Suite, 40
Test data migration server, 36
Testing, 35
– Test data migration server, 36
Total cost of ownership (TCO), 9, 20
W
Unicode conversion, 25, 40, 42, 43 Web Dynpro ABAP, 32
Upgrade and migration assessment
for SAP CRM, 28, 41
Upgrade dependency
analyzer (UDA), 21, 41
Upgrade experience database, 27, 41
Upgrade Information Center, 21, 38
Upgrade paths, 22
Upgrade Road Map, 30, 41
Upgrade scheduling, 26
Upgrade services, 40
– GoingLive Functional Upgrade
Check, 33, 42
– Quick upgrade analysis, 8, 44
– Safeguarding for Upgrade, 22
– Technical upgrade planning
and implementation for
SAP Business Suite, 40
– Upgrade and migration assessment
– Upgrade value assessment, 7, 40
Upgrade strategy, 26
Upgrade tools, 26, 40
– Application-specific
upgrade toolbox, 34, 41, 44
– Solution browser tool
for SAP ERP, 7, 40
– Solution Manager, 29, 41, 43, 44
– Test data migration server, 36
– Upgrade dependency analyzer, 21, 41
– Upgrade Road Map, 30, 41
Upgrade value
– Determining, 6
Upgrade value
assessment service, 7
User training, 36, 44
Getting Started with an Upgrade 47
50 082 075 (07/09)
©2009 by SAP AG.
All rights reserved. SAP, R/3, SAP NetWeaver, Duet, PartnerEdge,
ByDesign, SAP Business ByDesign, and other SAP products and services
mentioned herein as well as their respective logos are trademarks or
registered trademarks of SAP AG in Germany and other countries.

Business Objects and the Business Objects logo, BusinessObjects,

Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius, and other
Business Objects products and services mentioned herein as well
as their respective logos are trademarks or registered trademarks of
Business Objects S.A. in the United States and in other countries.
Business Objects is an SAP company.

All other product and service names mentioned are the trademarks of their
respective companies. Data contained in this document serves informational
purposes only. National product specifications may vary.

These materials are subject to change without notice. These materials

are provided by SAP AG and its affiliated companies (“SAP Group”) for
informational purposes only, without representation or warranty of any kind,
and SAP Group shall not be liable for errors or omissions with r­ espect to
the materials. The only warranties for SAP Group products and services are
those that are set forth in the express warranty s­ tatements accompanying
such products and services, if any. Nothing herein should be construed as
constituting an additional warranty.

www.sap.com /contactsap