Professional Documents
Culture Documents
Legal Disclaimer
This presentation is not subject to your license agreement or any other agreement with SAP. SAP has no obligation to pursue any course of business outlined in this presentation or to develop or release any functionality mentioned in this presentation. This presentation and SAP's strategy and possible future developments are subject to change and may be changed by SAP at any time for any reason without notice. This document is provided without a warranty of any kind, either express or implied, including but not limited to, the implied warranties of merchantability, fitness for a particular purpose, or non-infringement. SAP assumes no responsibility for errors or omissions in this document, except if such damages were caused by SAP intentionally or grossly negligent.
Agenda
1. Getting Started
1.1. 1.2. 1.3. 1.4. SAP ERP 6.0 Overview Functional Overview Architecture of SAP ERP Release & Maintenance Strategy
2. Upgrade Projects 3. ERP Technology Aspects 4. SAP Upgrade Tools and Services
Client/Server Architecture R/3 Basis Transactional user Data-centric Functional modules Process efficiency
Information-centric
Adaptable industry processes Analysis, decisions and actions
SAP ERP
Enhanced and Integrated Business Processes
Financials
Simplified reporting and CPM E-Invoicing, collections New General Ledger Support for SWIFT, SEPA
Integrated talent management Succession management Support for HR shared services Expanded roles and self-services
Corporate Services
Real-estate and property management End-to-end travel management Enterprise asset management
Simplified sales order entry Services procurement SAP xApps integration Additional roles: sales, buyers
Platform Solutions
Industry switch framework Enterprise services bundles Integrated business intelligence Eco-system of partner solutions
Business Client
Simplified user experience
Enterprise Search
Faster responses and action
Analytics
Action oriented and personalized information
SAPGUI
Easy Access
Duet
Integrated access from MS-Office
Adobe Forms
Easy form based processing
Bridging the gap between the users, their information and processes needs and their access needs
SAP 2008 / Transition & Upgrade to ERP 6.0 / Page 6
Agenda
1. Getting Started
1.1. 1.2. 1.3. 1.4. SAP ERP 6.0 Overview Functional Overview Architecture of SAP ERP Release & Maintenance Strategy
2. Upgrade Projects 3. ERP Technology Aspects 4. SAP Upgrade Tools and Services
Tangible Benefits
Reduced DSO Reduced bad debt Improved credit scoring efficiency Improved dispute mgmt. Improved Cash Forecasting and Reporting Faster financial close Enhanced GL processing
ANALYTICS
Tangible Benefits
ANALYTICS
Tangible Benefits
Improved utilization of idle/ un-utilized real estate Reduced time spend on real estate management
ANALYTICS
Project Management Reduce manual tasks through tighter integration and automation Improve on time project performance through coordinated project planning and execution Travel Management Lower costs by reducing manual tasks Minimize training and help desk costs through easy to use UI Lower travel costs through expanded options and increased leverage
Increased project management and execution efficiency Reduced costly project delays
Increased travel planning efficiency Lowered training costs Reduced help desk costs Decreased travel costs
Tangible Benefits
Reduced time spend on procurement activities Reduced indirect material and services spend Improved processing of inbound/outbound goods Reduced out-of-stock Increased R&D productivity Faster time to market Increased in new products revenue Improved product quality Reduced Asset maintenance costs
ANALYTICS
Increased customer service productivity Reduced order errors Lowered time spend on ICM activities Decreased incentive compensation costs
Tangible Benefits
ANALYTICS
Agenda
1. Getting Started
1.1. 1.2. 1.3. 1.4. SAP ERP 6.0 Overview Functional Overview Architecture of SAP ERP Release & Maintenance Strategy
2. Upgrade Projects 3. ERP Technology Aspects 4. SAP Upgrade Tools and Services
..
SAP R/3
up to 4.6C
and more
Switch Framework
Industry Sol.
Enterprise Extensions
Industry Extensions
Application
SAP Basis
INFORMATION INTEGRATION Bus. Intelligence Knowledge Mgmt Master Data Mgmt PROCESS INTEGRATION Business Integration Process Mgmt Broker APPLICATION SERVER (7.00) J2EE ABAP DB and OS Abstraction
Technology
ITS
SAP NetWeaver
BUSINESS SUITE - Stable Core
Launched in June 2006 Built on SAP NetWeaver 7.0 Platform upon SAP will deliver future software innovations via SAP enhancement packages SAP enhancement package 4 for SAP ERP 6.0 generally available since May 2009 High number of productive SAP enhancement package customers (6500+)
Optionally installed and activated software innovations for SAP ERP 6.0 Software innovations include
SAP enhancement packages are built on top of each other Enhancement packages are not support packages: Support Packages contain corrections and legal changes, SAP enhancement packages new functionality
EhP 1
Released 4. Q./2006 HCM Shared Services
EhP 2
Released 2. Q./2007 Order To Cash
EhP 3
Released 4. Q./2007 Procure To Pay
EhP 4
4. Q./2008
EhP 5
3. Q./2010
SIMPLIFICATION
Attract To Perform
Accounting To Reporting
ENTERPRISE SOA
Adaptive Manufacturing
Order To Cash
Procure To Pay
planned
New in ERP 6.0 SR3: Upgrade to SAP ECC 6.0 including SAP enhancement package 3 possible from..
Industry add-ons integrated into SAP ECC 6.0 (see SAP Note 838003)
SAP ECC DIMP 5.0
Non industry add-ons integrated into SAP ECC 6.0 (see SAP Note 838002)
SAP LEARNING SOLUTION 2.00 SAP VADM SAP IS-PS-FM 3.00 2.05 4.62 4.61 4.02 SAP EH&S 2.2B/2.7B/4.6C 2.2B/2.7B/4.6B 2.2B/2.7B/4.5B SAP IS-U/FERC
Target
SAP ECC 6.0 + EHP 5
SAP IS-CWM
2.0 SAP DI 4.6C2 SAP IS-EC 3.0B SAP IS-U/CCS 472 471 464 461
SAP JVA
4.6C 4.6B 4.5B 4.1B SAP HR-PS 4.62 4.61 4.52
3.0B 2.0B
SAP IS-HT 4.61
SAP PLM RECIPE MANAGEMENT 2.1 1.0 SAP BANKING 4.63 4.61 4.03 SAP R/3 ENTERPRISE 47X200 47X110 SAP CFM 2.0
SAP PUBLIC SECTOR PSCD 4.72 4.71 4.64 SAP IS-HER-CM 4.72 4.71 4.64
SAP PATIENT MANAGEMENT 4.72 4.63B SAP IS-OIL 4.72 4.6C 4.6B 4.0B SAP IS-MINE 4.6C 4.6B
SAP INSURANCE FS-CD 4.72 4.71 4.64 4.61 4.51 FS-CM 4.72 4.71 4.64 FS-CS 4.72 4.71 4.64
SAP ECC
SAP ERP 6.0: industry & enterprise extensions can be activated via the switch framework
SAP Switch Framework
Industry Business Function Sets SAP Discrete Industries Mill Products SAP Media SAP Telecommunication SAP Oil and Gas .. Generic Business Functions Financial Services Global Trade .. ..
SAP ECC
SAP ERP Central Component 6.00
Only ONE Industry Business Function Set can be activated via Switch
SEVERAL Generic Business Functions can be activated via Switch Switch Framework: Transaction SFW5
With SAP ERP 6.0, the majority of industry solutions are delivered within the standard release cycle
SAP 2008 / Transition & Upgrade to ERP 6.0 / Page 18
Agenda
1. Getting Started
1.1. 1.2. 1.3. 1.4. SAP ERP 6.0 Overview Functional Overview Architecture of SAP ERP Release & Maintenance Strategy
2. Upgrade Projects 3. ERP Technology Aspects 4. SAP Upgrade Tools and Services
Outlook
CE 7.1
SAP NetWeaver
PI 7.1
Continuous Innovation
EhP EhP EhP EhP CRM SRM SAP Business Suite EhP EhP SCM PLM EhP EhP
Non-SAP
ERP
Deploying business innovation with SAP enhancement packages across the SAP Business Suite
7-2 maintenance strategy for SAP Business Suite 7 core applications*: 7 years of mainstream maintenance, 2 years of extended maintenance
Long-term planning security and higher return on investment nine year maintenance horizon Additional time to deploy and benefit from innovation delivered via enhancement packages Less additional cost for extended maintenance
7 2
New
EHP** EHP**
EHP**
EHP** Extended Maint. (+ 2%)* EHP** Extended Maint. (+ 2%)* Cust.-Spec. Maintenance Cust.-Spec. Maintenance
RampUp EHP**
Mainstream Maintenance
EHP** EHP**
RampUp
Mainstream Maintenance
Nov Dec
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
Before
EHP** EHP** EHP** EHP** Ext. Maint. (+ 2%)* Ext. Maintenance (+ 4%)* Cust.-Spec. Maintenance
RampUp
Mainstream Maintenance
Mar
Mar
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
Mar
2016
2017
* Core applications of SAP Business Suite 7: SAP CRM 7.0, SAP SRM 7.0, SAP SCM 7.0, SAP PLM 7.0; plus SAP ERP 6.0 (EHP4) and SAP NetWeaver 7.0. Industry-specific add-on applications and SAP enhancement packages based on these core application releases will offer mainstream and extended maintenance in line with these releases. ** Enhancement Packages: Illustrative only; does not reflect exact shipment times and frequency.
SAP 2008 / Page 21 / EHP Technology Facts 3.0 / Christian Oehler
Dec
Agenda
Value proposition for the upgrade Target release fitting best the business and IT needs
and synchronization with other projects (e.g. rollouts) Awareness on SAPs product and maintenance strategy
Technical feasibility of the upgrade Handling the complexity of the existing landscape Sizing and/or potential of technical redesign
Identification of key cost drivers and risk factors Measurements to gain efficiency and save costs
Pure Technical
Functional1
North America
52% 42%
39%
34% 20%
Germany
N = 441
48%
N = 138
73%
Brazil
24% 14%
India
N = 353
57%
14% 8%
N =37
74%
13% 11%
China
Source: MOVE/GUO 1 Combined project
23% 10%
Australia
N = 52
N = 46
Why?
What benefits does an upgrade provide?
The business value is typically the key driver for an upgrade Not the technical upgrade, but the use of the new capabilities of the target release provides value of an upgrade To identify the key value drivers, an in-depth analysis with the business owners should be considered Project costs of a SAP ERP Upgrade are similar to an R/3 Enterprise Upgrade The system complexity, the upgrade-path and the project scope are key influencing factors for the potential project costs More than 70% start with a technical upgrade with the objective of risk mitigation, while additional enhancements are implemented in subsequent projects Test-Upgrades provide useful insight prior to the real execution of the upgrade For key challenges, it is reasonable to leverage external expertise
How much?
What are the cost of an upgrade costs?
How?
How to organize an upgrade project?
SAP Upgrade Road Map SAP Uprade Coaching Other SAP upgrade tools & services
Plan
Upgrade Discovery Upgrade Evaluation
Build
Upgrade Implementation
Run
Operations & Continuous Improvement
Define strategy
Upgrade Roadmap
Project Preparation Document current solution and set-up project Blueprint Realization Final Preparation for Cutover Perform integration and system tests and plan cutover Production Cutover & Support Execute production system Upgrade & Support
Plan
Upgrade Discovery Upgrade Evaluation
Key User
Champs
Define Define Business Business Requirements Requirements
PMO
Plan Upgrade Program
Tech Op/ IT
Define IT IT Requirements Requirements
Plan and Update Infrastructure Adjust Application Manage Upgrade Project Test Technical Upgrade
Document current status of business solution Identify impact of corporate business strategy on current business solution Identify existing gaps and issues Define future business needs Understand new functions and features of SAP target solution Map requirements to possible target solution(s)
Define Business and Test KPIs Test Core Business Processes Sign-off Upgrade
Define IT Requirements
Test Change
Document current solution landscape Identify impact of corporate IT strategy on current solution, e.g. including provider model and data center, hardware and platform strategies Define maintenance strategy for solution Understand new technology features of possible SAP target solutions
Plan
Upgrade Discovery Upgrade Evaluation
Key User
Champs
Define Business Requirements
PMO
Plan Plan Upgrade Upgrade Program Program
Tech Op/ IT
Define IT Requirements
Plan and Update Infrastructure Adjust Application Manage Upgrade Project Test Technical Upgrade
Identify and design possible target solution landscapes (releases and software components) that meet business and IT requirements Perform high-level analysis how changes impact the complete solution landscape (including technical platform, SAP and non-SAP software) Evaluate migration paths to possible target landscape and determine best option
Define Business and Test KPIs Test Core Business Processes Sign-off Upgrade
Test Change
Identify TCO of the as-is solution and costs for adaptation to business requirements in existing landscape Estimate TCO of planned target landscape Estimate upgrade project costs and general change costs Formulate business value proposition Create business case
Agenda
Project Management
PM
Time planning: Relations to other implementations or roll-out activities, Project runtime Budgeting: IT-Costs; External and internal Resources Resource planning: project members; skills; roles responsibilities; number of external resources Project standards & procedures: e.g. coordinating the parallel change streams of production and upgrade landscape, define and manage the code freeze period
Business Aspects
Release customizing: Upgrade Customizing / Delta Customizing Identification and elimination of unused modifications and custom developments Adjust and test customer developments, interfaces, forms; authorizations End-User training: only if significant user interface changes and redesign were required Test core business processes efficiently (incl. user acceptance test)
Technical Aspects
IT infrastructure adjustments / Sizing of new release: Server, Frontend; Network Planning and execution of technical upgrade process: SAP application but also operating system and database - Recommendation: Split OS, DB and SAP Upgrade into different maintenance slots ! Planning Backup Strategy: during and after the technical upgrade Post upgrade activities: Performance analysis, reorganizational actions
Calender week 11 12 13 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 2 3
Project preparation Blueprint Realization Final preparation for cutover Go-Live & Support
2 w.
Upgrade strategy Application Complexity Downtime requirements Project portfolio IT capacity and skills available Testing requirements, e.g. GXP, SOX, FDA End user involvement and availability Application landscape and dependencies
Example
Production Cutover & Support
Legend = new release = old release
Project work
Project Management:
System landscape
Upgrade project system
= Transport route
Create detailed project plan Nominate project team Order temporary hardware Business Experts:
UPS 4.6C
Study material on new release (Development News, SAP ERP Solution Browser, ) Perform upgrade impact analysis for solution landscape
Temporary landscape
Productive landscape
DEV 4.6C
QAS 4.6C
PRD 4.6c
3W May
5W 8W Jun Jul
3W
2W Aug
Timeline
Example
Production Cutover & Support
Legend = new release = old release
Blueprint
Realization
Project work
Technical Team:
System landscape
Upgrade project system
= Transport route
Developers:
UPS ECC
Perform SPDD and SPAU adjustment Adjust & test customer reports and transactions (total: 3 weeks) Business Experts: Upgrade Customizing Test of business processes (Cycle I 2 weeks) Deliverables:
Temporary landscape
Productive landscape
DEV 4.6C
QAS 4.6C
PRD 4.6C
3W May
SAP 2008 / Transition & Upgrade to ERP 6.0 / Page 34
5W 5W Jun Jul
3W
2W Aug
Timeline
Modification
Definition: any change to an SAP-owned workbench object
Custom Objects
Definition: any development in the y* or z* namespace
Types of modifications
Modifications made due to OSS notes Customer modifications
Who owns the modification? What is the business justification for retaining the modification? E.g.: user exits - these are generally not issues in upgrades (Unicode 553110)
Enhancements
Cloned objects
SAP-standard objects copied into the customer namespace
Cloned objects present unique challenges possible approach: re-clone them on the new release.
Customizing
Study release notes; generate Upgrade IMG (transaction: spro_admin)
Custom Objects
Further Information
Authorizations
The SAP_NEW profile contains the authorizations for new checks in functions that have already been delivered.
After the upgrade:
To copy the latest SAP default values while retaining your own modifications, call transaction SU25 (steps 2 and 3) Delete all the individual profiles from SAP_NEW that refer to releases that are lower than the source release for the upgrade. Go through the profile SAP_NEW and decide for each authorization object, into which customer profile the authorizations need to be copied.
Please read SAP notes: 367676 4.6 to 6.10 452229 6.10 to 6.20 689951 6.20 to 6.40 857904 6.40 to 7.0
e.g. ABAP and Unicode, ABAP objects, Internal tables, Open SQL and update, ABAP Compiler, ABAP runtime
Queries
Please read note: 672784
Batch Input
Please read note: 311440
Example
Final prep. for Cutover
Production Cutover & Support
Legend = new release = old release
Realization
Project work
Technical Team:
System landscape
Upgrade project system
= Transport route
Setup a temporary development system for maintenance (DEV) Upgrade of development system (DEV) Redo manually SPDD and SPAU adjustment Redo manually adjustment of customer reports Short unit testing in development system Redo customizing adjustments Unit testing in development system Dual maintenance period starts Customer programs are unit tested in development system
UPS ECC
Developers:
Temporary landscape
Double maintenance
DEV 4.6C
1. Copy 2. Upgrade
Business Experts:
Productive landscape
DEV ECC
QAS 4.6C
PRD 4.6C
Deliverables:
3W May
5W Jun
3W Jul
3W
2W Aug
Timeline
Example
Production Cutover & Support
Legend = new release = old release
Project work
Technical Team:
System landscape
Upgrade project system
= Transport route
UPS ECC
Transport project work to QAS system Business Experts: Final Integration tests in QA system (Test cycle II 1 week) Developers: Error corrections Deliverables:
Temporary landscape
Double maintenance
DEV 4.6C
QAS 4.6C
1. Copy 2. Upgrade
Productive landscape
DEV ECC
Transfer changes
QAS ECC
PRD 4.6C
Timeline
Define business requirements and KPIs for a successful go-live Define suitable test scope: Find right balance between level of risk mitigation and testing effort Set-up efficient test procedures and test KPIs Identify appropriate training scope and efficient training methods
Testing Effort
???
High Availability
No testing
effort-risk
e.g. iterative testing balance
Risk
Phase
Regression Tests User Accept. Tests Technical System Tests Integration Tests
Functional Tests
Realization
Realization
Example
Legend = new release = old release
Project work
Technical Team:
System landscape
= Transport route
Upgrade of the production system (PRD) -> Downtime Performance of post processing Activities
Business Experts: Signing Off of the Solution in the New Release Deliverables:
Removal of Temporary Enhancements from the System Landscape Support for the Go-Live Date
Productive landscape
DEV ECC
QAS ECC
Transfer changes
PRD ECC
Project Closure
3W May
5W 8W Jun Jul
3W
2W Aug
Timeline
Agenda
* 10% of outer values were cut off to provide a representative benchmark for your planning, please see distribution of values (upper part of the grapghic) for minimum/maximum values
PM
Reduce Dual Maintenance Period Do add. effort work in upgrade project system before upgrade of system landscape Reduce time window between upgrade of DEV and PRD system Test Output Programs Most companies focus on the business process testing and forget about print programs and forms Involvement and Commitment Early Involvement of key users and management commitment are key success factors
95 % of our customers who upgraded to ERP 6.0 were satisfied or even gave a better rating
Based on 212 upgrades
Very satisified More than satisfied Satisfied Less satisified Not satisfied
Excellent documentation
Qualified Support
Simple Upgrade
Easy transition - Smooth upgrade for users - No training necessary Kabel Deutschland
After a very smooth upgrade, we are now up and running with stable applications and technology.
Bitburger Brauerei Th. Simon GmbH
The SAP upgrade tasks were completed quickly compared to previous upgrades was a simple technical upgrade Petro Canada ... the transition from our existing solution was fast, smooth, and hassle free with minimal downtime and no business disruption.
Mineralbrunnen berkingen-Teinach AG
Agenda
Business Requirements
ERP Upgrade
Time
ECC 6.0
EHP 4
Upgrade as a major business activity every 5-6 years to fulfill business requirements.
Permanently decrease functional gap With SAP enhancement packages for SAP ERP continuous provisioning of new functionality is possible.
Cost
Upgrade
Upgrade
Support Package Support Package Support Package
SAP System
Time
Release Upgrade
Legal/Tax Changes, Corrections, Mandatory Technically a set of Support Packages and patches
Optional, new Software Components Activate new functionality in Switch Framework via Business Function
Install SAP enhancement packages combined with Support Pack Stack as a maintenance activity with only minor additional effort (ABAP).
Quick Facts
Installation of new functionality separated from activation via Switch Framework
Preamble
SAP enhancement packages are shipped as a delta shipment to SAP ERP 6.0
Enhancement Packages
Each SAP enhancement package contains new versions of existing software components You only update software components, which are related to the functionality you want to use. After installation:
No UI or process change until a Business Function is activated (ABAP) However SAP enhancement packages require defined ERP Support Package Stack
Selective Activation
Support Packages
New functionality must be explicitly switched on to become active in the system. If activated:
Changes are predictable, only well described changes in the activated areas. Testing is simplified with templates, provided for every Business Function
Mandatory Mandatory
SAP 2008 / Transition & Upgrade to ERP 6.0 / Page 52
Plan
PLANUNG
Discover Business Process Champions, Technical Operations Test & Go Live Key Users, Business Process Champions Evaluate & Decide Champions, Technical Operations, Project Mgmt. Office
Combine Upgrade, EhP and Support Package implementation Installation of all core components recommended SPAU and SPDD is obligatory Short functional check of customer developments necessary Regression tests Installation non-reversible
Build
The roles mentioned on this slide refer to the SAP Standards for E2E Solution Operations.
SAP 2008 / Transition & Upgrade to ERP 6.0 / Page 53
Documentation
Release notes Dependencies Test catalogue Learning Maps
http://service.sap.com/erp-ehp
Documentation at deep level of granularity Great ability to analyze new software functionality Easily identify needed Business Function(s)
Step 3: Prepare & Install SAP enhancement package 2 for SAP ERP
4. Automated download of required installation files for selected technical usage with Solution Manager Maintenance Optimizer
Queue of installable packages & stack XML
605
SAP_APPL 605 Basis
702
Business Function
Technical Usage
RE_GEN_CI_1
(Real Estate)
Central Applications
SAP_APPL 605
HCM_ASR_CI_1
EA_HR 605
Prerequisites
3
1.
Up-to-date SAP Solution Manager 7.0 (SP23). Your system landscape has to be maintained in the Solution Manager system.
In general there is no minimal Support Packages Level required in the system where the SAP enhancement package will be installed. But you have to make sure that a valid and consistent queue incl. Support Packages is defined (step 2c). If you have an add-on installed in your system, ask your add-on provider whether it is compatible with the SAP enhancement package for SAP ERP 6.0. Read the documentation and check all relevant SAP notes.
2.
3.
4.
Call transaction SPRO Activate ECC Extensions Enterprise Business Functions Tab Set Planned Status
Acceptance test for selected business functions Use standard test case templates Train end-users Go live, transport switch activities to production system
Benefits
Faster test preparation due to test case templates Smaller test scope because changes in objects are documented for each business function
Smaller training effort due to limited and documented effect on user interfaces
Shorter downtime than in full releaseupgrade
Agenda
Data
Function Modules
Documentation Modules
Messages
Views
Dynpros
Adapt applications
Adjust modifications of SAP-owned workbench and DDIC objects Identify necessary adjustments in custom programs using SAP standard objects Understand needs for customizing adoptions and adjustments of business processes Check and adopt interfaces
Modifications
Customer Development
Extension
SAP 2008 / Transition & Upgrade to ERP 6.0 / Page 63
Provided for ABAP Stack via Add-on ST-PI Further Information: SAP Note 1000009 Starting from ERP 6.0 SR3 integrated into the upgrade as mandatory step
RELIABLE Provides a detailed task overview of steps which have to be performed before and after the technical upgrade Shows a description of each step, links to the related SAP notes and gives the possibility to insert comments regarding this step Gives the chance to plan and organize pre and post upgrade tasks to own needs Enables to transport the once generated task list within the whole upgrade landscape Helps to get the system quickly and with a minimum of effort and cost into a stable condition
In-place upgrade without moving customer mass data Java upgrade is generic procedure that is applicable for all SAP products (SAP Business Suite, ) Upgrade of SAP NetWeaver systems with AS Java and applications Standalone Java installation Dual-stack installation Detection of components to be upgraded and additional components to be installed Available for upgrade from SAP NetWeaver 04 to 7.0 Synchronization of ABAP and Java upgrade for dual stack systems Inclusion of Support Package Stack in the upgrade up-to-date upgrade to the latest SP stack in one step Modifications and customer developments on start release Customer developments remain unchanged after the upgrade Modifications on SAP standard must be included in the upgrade after the migration to the target release with SAP NetWeaver Development Infrastructure (NWDI) Error and restart handling at any point
System switch upgrade technology (optimized) Synchronization of ABAP and Java upgrade for dual stack systems Tool enhancements:
New GUI Improved usability for including additional packages into upgrade (wizard)
Reduced downtime through parallel import of software packages (shadow import and main import)
Improved fixpack concept
Support for system conversion from Multi-Display, Multi-Processing Code Page (MDMP) to Unicode from releases 4.6C and higher Support for switch framework Installation/upgrade of Internet Graphics Server
Agenda
Start-Release:
SAP Note:
Hardware Sizing
Sizing verification and proactively optimize configuration SAP Going Live Functional Upgrade Check
Analysis Session Load based Analysis Parameterization of future Landscape Verification Session provides corrective measures for avoiding potential bottlenecks
Aspect 2: Extensive changes on business processes or numbers of users after the upgrade
Quick Sizer
for user / throughput based sizing Additional Services to improve the performance of the system
Solution Management Optimization Services
SAP 2008 / Transition & Upgrade to ERP 6.0 / Page 68
Understand the dependencies and compatibility issues within a system, e.g. released DB, OS and UI combinations in target release (vertical stack) Understand dependencies between different SAP products and software components (horizontal stack) Identify compatibility issues with other software and hardware products, e.g. 3rd party software, SAP partner add-ons or printers (horizontal stack)
Check the Product Availability Matrix (PAM) to determine if any upgrade are required to the OS/ DB via Service Marketplace Quicklink: /pam Oracle customers: SAP NetWeaver 7.0 (and thus ECC 6.0) only run on Oracle 10 For new installations 64bit OS-/DB releases are since SAP NetWeaver 7.0 mandatory For upgrades to SAP NetWeaver 7.0 64bit OS-/DB releases are recommended
SAP Enterprise Portal is not required unless portal-specific applications are used (e.g. Employee Self-Service)
SAPGUI 7.10 is the recommended GUI for use with SAP ECC 6.0
SAPGUI 6.40 also supports SAP ECC 6.0, check dependencies during planning of SAPGUI Rollout SAP GUI for Java still offered for Macintosh, Linux, etc. SAP GUI for HTML still supported via Integrated ITS
Check the Product Availability Matrix (PAM) for technical prerequisites about your SAP GUI via Service Marketplace Quicklink: /pam
Supported SAP BC releases 4.6 and 4.7 Supported JDK versions 1.3 and 1.2 (with limitations) only Supported operating systems Windows NT and 2000 Linux Sun Solaris 8 and higher (32-bit only) IBM AIX 4.3 and higher (32-bit only) HP-UX 11.0 and higher (32-bit only)
SAP BC 4.6 and 4.7 based on webMethods Integration Server 4.6 SAP XI based on open standards (e. g. BPEL4WS for business processes)
The end-of-maintenance dates for the two Business Connector versions are defined as follows: - BC 4.6: December 31, 2008.
Any custom programming done on the basis of SAP BC will likely not be reusable in the SAP Exchange Infrastructure context
Customers still starting new projects with SAP BC should consider XSLT for mappings
SAP BC to SAP XI Migration Guide
ITS 6.20 is long term supported for SAP products based on SAP Netweaver 2004 and below as long as these products are supported ITS 6.20 standalone cannot be used with SAP Netweaver 7.0 (SAP Kernel 7.00). ITS services which use Flowlogic and WebRFC are no longer supported in system based on SAP Netweaver 7.0 Note 709038 Because SAP integrated ITS is part of the SAP kernel, the maintenance is as long as the maintenance for the SAP kernel For detailed information please check Platform Availability Matrix (PAM) to get up to date information (http://service.sap.com/pam)
SAP will no longer maintain the most ESS standard services based on Standalone ITS Technology as of SAP ERP 6.0. Note 870126. The functional scope of ESS will be ensured by SAP. SAP recommends using ESS based on Web Dynpro (Java). For the implemented ESS-Scenarios several SAP components have to work together (Business Package, XSS, EP, Backend). The combination and dependencies of them is dependent on the implemented scenarios and could be different in the individual releases.
SLD
CIM Model NW Web AS Java
Web Dynpro
http
SAP ESS 600 SAP MSS 600 SAP PCUI 600 NW Web AS Java
JCo RFC
RDBMS RDBMS
RFC
Agenda
Support Packs
Modification Adjustment
Activation Distribution
Add-Ons
Inst.
Uptime
PREPARE Upgrade
Upgrade
Backup
ICNV
downtime-minimized
New Rel.
Imp.
Backup
Downtime
Backup
resource-minimized
post Upgrade
Upgrade technical runtime (SAPup) not all of this is production downtime! Post-upgrade transports & manual adjustments Business validation & acceptance testing Pre- and post-upgrade system backups
up down
SAPup: PREPARE & repository import rampbackup down Basis SAPup: conversion, XPRAS, etc.
up down
go/no-go decision
Functional/ business
backup
Operations
Number of modifications
Number of installed languages Number of clients Productive applications/ Add-Ons or industry solutions
Use test Upgrade on production mirror to get estimations of runtime and downtime
SAP 2008 / Transition & Upgrade to ERP 6.0 / Page 78
Technical perspective
Prepare
Upgrade Uptime
Upgrade Downtime
Follow-up activities
SAP reduced technical downtime by ~50 % due to incremental tuning of Upgrade tools. Further reductions via improved Customer Based Upgrade (CBU) possible.
SR = Service Release
Upgrade Tuning (in Addition to Standard) In Which Extent can Downtime be Minimized?
Hardware
Tools
Upgrade Coach2
Parallelize tasks
(10-50%)
2 Gives
Agenda
Globalization requirements
Companies running global business processes like Global HR Systems Companies offering Web Services to their customers: Global Master Data containing multiple local language characters! Companies using Open Standards: J2EE and .NET integration
Chinese Korean
English
Thai Croatian Czech Hungarian Polish Rumanian Slovakian Slovene
Afar Abkhazian Avestan Afrikaans Amharic Arabic Assamese Aymara Azerbaijani Bashkir Belarusian Bulgarian Bihari Bislama Bengali Tibetan Breton Bosnian Catalan Chechen Chamorro Corsican Czech Church Slavic Chuvash Welsh Danish German
Danish Dutch, German Finnish French, Italian Norwegian Portuguese Spanish Swedish Turkish
Telugu Tajik Thai Tigrinya Turkmen Tagalog Tswana Tonga Turkish Tsonga Tatar Twi Tahitian Uighur Ukrainian Urdu
Uzbek Vietnamese Volapk Wolof Xhosa Yiddish Yoruba Reserved- cust. Zhuang Chinese trad. Chinese Zulu
R/3 3.1i R/3 4.0b R/3 4.5b R/3 4.6b R/3 4.6c Direct upgrade SAP ERP 6.0 non-Unicode Conversion SAP ERP 6.0 Unicode
First Upgrade, then conversion to Unicode (*1) One step (Upgrade and Unicode Conversion) options:
(*1)
If No. of Code Pages in old system > 1 then the Unicode Conversion MUST be done IMMEDIATELY after upgrade or dislaimer must be signed.
Prerequisites: You must first ensure that you employ Unicode-based SAP components and a Unicode-enabled database, as detailed in the following SAP Notes 379940 and 79991 Phases High Level Description
During preparation, topics such as additional hardware requirements, downtime issues, Unicode-enabling of customer developments, and the special treatment of MDMP systems have to be taken into consideration.
Preparation
Conversion
The Unicode conversion process is based on a system copy, and during this process, the database conversion and system shutdown/restart are as automated as possible. For small to mid-size databases (< 1 TB), this is based on an SAP Unload/Reload of the complete database; minimum downtime tools will be used for larger databases. Once the Unicode system is up and running, you need to verify data consistency on a scenario basis, as well as carry out general integration testing. For systems that support multiple languages, special emphasis needs to be placed on cross-language handling during the test phase. Correction tools are provided by SAP, which can be used in the case that conversion did not run properly.
Post-Conversion
Note: For details and conversion guides see SAP Service Marketplace http://sercive.sap.com/unicode
Yes
No
Yes
Unicode conversion before or after the upgrade or Combined Upgrade & Unicode Conversion
>90% of customers
CPU
+ 5% 30% depending on existing scenario (MDMP, double byte) and type of CPU
RAM
+ 40% 50% Application Servers are based on UTF-16 internally
Database size
Network Load
UTF-8*: up to +10%
ORACLE, DB/2 (AIX)
UTF-16:
+ 30 ... 60%
*35% is the observed maximum in growth for small systems (db size < 200 GB). * 10% is the observed maximum for bigger systems (db size > 200 GB).
SAP 2008 / Transition & Upgrade to ERP 6.0 / Page 86
1800
2800
3800
4800
5800
6800
7800
8800
DB size in GB
Net Runtimes on PRD systems: Time needed from begin of Export until end of Import (w/o e.g. Prepare Jobs, Back-up, Tests after the conversion etc)
Most of the shown examples used two Servers (Export on Server 1 and Import on Server 2 in parallel). Experiences show that the reduction can be significantly high when using the Two Servers Scenario (e.g. from 50 h to 28 h for the runtimes).
Downtime: dependencies
MDMP requires more preconversion tasks and postconversion handling in the Unicode system
Biggest Tables Optimize parallelization of Export/Import processes (splitting of R3load packages) Processing of Cluster Tables
Hardware
medium
Asian Codepage SAP ERP
difficult
Multiple Codepages (MDMP) SAP CRM with Mobile Sales
ABAP Enabling
Small Amount of Objects Easy objects (CS, ) Standard Table Splitting SAP Single codepage Latin-1 Single Codepage Latin-1 SAP MDMP + TABLES
Large Amount of Objects Difficult Objects (Offset) Combined Upgrade & Conversion SAP MDMP + ALE (Container) Single Codepage Asian
SAP Notes
551344 Unicode Conversion 548016 Conversion to Unicode 79991 Multi-Language and Unicode support of SAP solutions 928729 Combined Upgrade & Unicode Conversion FAQ 959698 Twin Upgrade & Unicode Conversion FAQ
Agenda
1. 2. 3. 4.
Getting Started Upgrade Projects ERP Technology Aspects SAP Upgrade Tools and Services
Planning
Execution
64 % 38 % 17 %
Efficient testing Modification Adjustments Downtime Minimization IT-Infrastructure/ Sizing Enduser trainings
75 %
62 %
43 %
31 % 21 %
Impact on the system landscape Search & find upgrade related information Interoperability
39 % 25 % 17 %
Projectmanagement Others
21 %
21 %
Source: DSAG-360-Customer Feedback Program: Upgrade (March 2008 138 participants 138 companies)
BUILD
Minimize project costs and risk of business disruption
RUN
Run and incrementally improve total cost and value
Strategic advice on SAP ERP transition Value proposition / business case definition
Complete Execution
Expert Guidance
SAP Accelerated Value Assessment for SAP ERP SAP Value Assessment
SAP Enterprise SOA Road Map for SAP ERP SAP Work Center Assessment SAP System Landscape Selection SAP Technology Workshop SAP System Sizing
Quality Management
Enabling
SAP Upgrade Training Solution Architect & Solution Overview Training SAP Customer & Project Team Training
SAP ERP Solution Browser SAP Business Maps Statement of Direction Value of Upgrade Document
SAP ERP Upgrade Aspects SAP Upgrade Road Map SAP ERP Course Finder
RUN
Run and incrementally improve total cost and value
Technical deployment
Testing
SAP Client Transition SAP System Landscape Operation Support SAP Unicode Conversion
Enabling
SAP End User Training SAP Customer & Project Team Training
SAP Tutor eCATT RWD Info Pak SAP Test Data Migration SAP Learning Solution Server SAP ERP Course Finder
Plan
Discover Evaluate & Decide
Benefits
Single point of access to all capabilities of SAP ERP and key functionalities
Fast identification of capabilities that respond to user requirements
Availability
SAP ERP Solution Browser: http://solutionbrowser.erp.sap.fmpmedia.com/ Further information at SAP Upgrade Info Center: http://service.sap.com/upgrade-erp
Description:
Upgrade Dependency Analyzer displays known dependencies Accessible via http://service.sap.com/uda Available: Since July 25th 2008 Integrated with SAP Solution Manager (with ST400 SP17)
DESCRIPTION
The SAP Upgrade Experience Database provides experiences/statistics of completed upgrade projects
The SAP Upgrade Experience Database includes the following upgrade aspects:
Median: 22,0
Min: 10,2 Max: 34,2
Range of values
Additional hardware requirements Project duration Business Downtime Reasons for upgrade, etc.
BENEFITS
Benchmark data to plan your upgrade Customers planning an upgrade to SAP ERP can participate in the upgrade experiences gathered in similar upgrade projects.
Register NOW: Data on SAP ERP 6.0 is available at: http://service.sap.com/upgraded b http://service.sap.com/upgradedb
Documentation
General information provided (mapping to new building blocks systems with usage types, standalone engines, clients) and planning information (landscape-related topics SAP NetWeaver Administrator, SAP Solution Manager, SLD, SLM, ) One section for every IT scenario providing information of its system landscape and implementation/upgrade sequence
For the installation of a system with usage types, only one Installation Guide SAP NetWeaver required
Comprises the information for your platform/database and all usage types No longer separate guides required for BI, EP, etc. OS Dependencies included/no longer required due to Prerequisite Checker
Description:
Documentation provides information required to understand and perform software life-cycle tasks Planning Guides ([Upgrade] Master Guide, )
Installation Guides Upgrade Guides Support Package Stack Guide SAP Library documentation Tool documentation (F1 help, )
Profiling prepared in the future, it is planned that more specific guides can be created on demand that only contain information for required usage types and operating systems
DESCRIPTION
SAP's standard methodology to plan and execute the upgrade of an SAP solution Content: Best practices and templates for project management, functional and technical aspects facilitating key tasks of the entire project team Formats:
Target Release
SAP ECC 6.0 SAP Learning Solution 6.0 SAP SEM 6.0 FSCM 6.0 SAP E-Recruting 6.0 SAP cProjects 4.0 XECO 5.0 SAP XSS 6.0
Accelerators
134 (22 unique) 54 (19 unique) 48 (17 unique) 63 (22 unique) 48 (17 unique) 57 (14 unique) 42 (15 unique) 45 (16 unique)
HTML version on SAP Upgrade Info Center at: http://service.sap.com/upgraderoadmap SAP Solution Manager format: starting with ST-ICO140, latest updates in ST-ICO150(SP4) Since 06/2004, latest update (V3.1) in 07/2006 Languages: English, German
Availability:
BENEFITS
Repeatable approach that helps to mitigate risks, attack key time consumers and reduce costs and effort Central point of access to upgrade project information and integrated use with SAP Solution Manager
SAP
Test Workbench
SAP Service Marketplace
SAP Customer
Upgrade Roadmap E-learning mgmt. Change Management
SAP Experts
DESCRIPTION
The Scenario & Process Component List allows to flexibly illustrate possible technical realization alternatives for key business scenarios or processes.
AVAILABILITY
The Scenario & Process Component List is accessible on SAP Service Marketplace at http://service.sap.com/scl
BENEFITS
Easy identification of the components needed to realize a new business scenario Quick access and easy to use Central access point across SAP solutions Customers starting an upgrade can find out which components can - or cannot - be combined for certain business scenarios
Planning an Upgrade Projects Step by Step Executing an Upgrade Technology Tips and Tricks Further Information and Resources
Target Group
Availability
Download
Upgrade Info Center http://service.sap.com/upgrade-erp Direct Link: Getting Started with an upgrade
Information Sources
SAP ERP
Homepage: http://service.sap.com/erp Development News: http://service.sap.com/developmentnews Release Notes: http://service.sap.com/releasenotes Release Strategy: http://service.sap.com/releasestrategy Maintenance Strategy: http://service.sap.com/maintenance
SAP Netweaver:
Homepage: http://service.sap.com/upgrade SAP ERP : http://service.sap.com/upgrade-erp SAP Upgrade Road Map: HTML Version SAP Upgrade News: http://service.sap.com/upgrade-news
Overview and order information: http://service.sap.com/upgradeservices Upgrade Services SAP Consulting: http://service.sap.com/ufg