Simple Upgrade | Clear Value | Profound Opportunity
MOVE/Global Upgrade Office
Accelerating the Adoption of SAP Business Suite, SAP ERP 6.0, SAP Enhancement Packages, and Enterprise Services
SAP Business Suite 7
Technical Considerations in the Context of Release Upgrades
May 2009Business Process Platform (BPP)
SAP NetWeaver
SAP Business Suite
SAP ERP 6.0
Service-oriented Architecture
SAP Enhancement Packages
SRM SCM CRM PLM
Legal Disclaimer
© SAP 2009
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 maybe changed by SAP at any time for any reason without notice. This document is provided without a warranty of any kind, either expressor implied, including but not limited to, the implied warranties of merchantability, fitnessfor 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.
Focusing on technology, this session provides an overview on: Upgrading existing SAP Business Suite applications. Technical considerations of SAP Business Suite 7.
This E-BookBackground and Objectives
SAP Business Suite software is a comprehensive, fully integrated and modular suite of applications that drives:
End-to-end industry processes. End-to-end process scenarios across multiple applications.
It is a collection of SAP applications containing the go-to releases of software for SAP customers that want a stable core and continuous, minimally disruptive innovation:
SAP ERP 6.0 with SAP enhancement package 4 for SAP ERP.SAP CRM 7.0. SAP SRM 7.0.SAP SCM 7.0.SAP PLM 7.0.Industry Applications and Supplementary Applications.
SAP Business Suite offers companies the opportunity to transform business processes efficiently and integrate business with minimal disruptive innovation.
© SAP 2009
Business Suite Upgrades
SAP Business Suite 7 - Overview: End-to-End Processes 1
SAP Business Suite 7 - Landscape Upgrade Drivers2
© SAP 2009
Benefits of the New SAP Business Suite -Addressing New Customer Expectations
SAP Business Suite 7No more stovepipesFlexible end-to-end processes
Deploy as you goStepwise projects and installation
No more upgradesSAP enhancement packages = innovation packages
DynamicRe-usable enterprise services
Industry-focusedDelivers integrated industry solutions
ExtensibleEasy expansion beyond SAP ERP 6.0
SAP Business Suite
NetWeaverIntegration
NetWeaverComposition
EHP
EHP
SAP ERP SAP CRM SAP SCM SAP PLMSAP SRM
Industry Applications
Supplementary Applications
SAP Business Suite SAP Business Suite
NetWeaverIntegration
NetWeaverComposition
EHP
EHP
EHP
SAP ERP SAP CRM SAP SCM SAP PLMSAP SRM
Industry Applications
Supplementary Applications
© SAP 2009
Flexible End-to-End Scenarios -Expands Support for Lines of Business
Flexible End-to-end ScenariosFinance: Financial closeHuman Resources: Talent managementSales: Territory managementMarketing: Loyalty programsService: High-volume call centersProcurement: Service contract managementProduct Design: Process engineering integrationSupply Chain: Warehouse & transportation managementManufacturing: Collaborative supply chain planning
© SAP 2009
Accelerating “Lead to Cash” is an End-to-End, Cross-Functional Process
[2] Bridge to Value Scenario “Logistics and Fulfillment Management”
[1] Bridge to Value Scenario “Collaborative Demand & Supply Planning”
© SAP 2009
Accelerating Lead to Cash: Implementable Step “Sales and Marketing Planning”
SAP ERP SAP CRMSAP Price & Margin Mgmt by VendavoSAP Netweaver Business Warehouse
SAP Business Suite 7 Applications
© SAP 2009
EXAMPLE
Implementation Content: Value Scenarios
Implementation content includes SAP Solution Manager content and scenario & process component list.
Value scenarios can be found in the new folder “cross-application implementation packages”.
SAP Solution Manager Content Scenario & Process Component list: http://service.sap.com/scl
SAP Solution Manager Content and Scenario Component List
© SAP 2009
Business Suite Upgrades
SAP Business Suite 7 - Overview: End-to-End Processes 1
Transition to SAP Business Suite 7 2
Technology Considerations Overview
Upgrade per Application
Deploy further Applications
A
B
© SAP 2009
Key Technology Considerations
Source: MOVE/GUO
Target Business Suite 7Current
Upgrade per application
Upgrade Paths
Complexity Drivers
SAP Enhancement Packages
UnicodeA
Business scenarios in ONE application
Upgrade the respective application.Activate new functionality.
Deploy further applications
Deployment Options
Upgrade DependenciesB
Mandatory Components
Business scenarios ACROSS applications
Upgrade the respective applications.Deploy required additional applications. SAP NetWeaver Scenarios
SAP Appl. BS 7 Appl.Upgradee.g. SAP
R3 4.Xe.g. EHP 4 for SAP ERP 6.0
Upgrade & Deploy
SAP Appl.e.g. SAP R3 4.X
1
2
3
4
1
2
3
4
SAP Business Suite
NetWeaverIntegration
NetWeaverComposition
EHP
EHP
SAP ERP SAP CRM SAP SCM SAP PLMSAP SRM
Industry Applications
Supplementary Applications
SAP Business Suite SAP Business Suite
NetWeaverIntegration
NetWeaverComposition
EHP
EHP
EHP
SAP ERP SAP CRM SAP SCM SAP PLMSAP SRM
Industry Applications
Supplementary Applications
© SAP 2009
Transition to SAP Business Suite: Business Scenarios Determine the Transition Path
Business Suite Upgrades
SAP Business Suite 7 - Overview: End-to-End Processes 1
Transition to SAP Business Suite 72
Technology Considerations
Upgrade per Application Deploy further Applications
AB
© SAP 2009
1
Number of add-ons / industry solutions
Number of modifiedobjects
Required downtime
Source release
Number of codepages
Code freeze strategy
Testing requirements
OS / DB migration requirements
Type of upgrade (technical/functional)
Upgrade Project Complexity
Drivers
Dependencies to connected systems1
1 SAP and Non-SAP2 Other factors influencing the upgrade effort (i.e. organizational complexity, knowledge) are considered in a later stageSource: MOVE/GUO
Duration/effort of an upgrade can mainly be determined based on system scope/system complexity2. Different upgrade complexity drivers per application to be considered.
© SAP 2009
Complexity DriversUpgrade Complexity Classification
Unicode -Upgrade Paths to Unicode
1 If No. of Code Pages in old system > 1 then the Unicode Conversion MUST be done IMMEDIATELY after upgrade2 If MDMP is used (i.e. systems contains multiple code pages) then Unicode conversion can be done first, or with an upgrade
R/3 4.6c
R/3 4.5b
R/3 4.6b
R/3 4.0b
Directupgrade
SAP ERP 6.0non-Unicode1
SAP ERP 6.0including
SAP enhance-ment package 4
Unicode
Con-version
First upgrade, then conversion to Unicode2
As-is ReleaseExample: SAP R/3 to SAP ERP 6.0
including SAP enhancement package 4
Other, more recent releases
2
© SAP 2009
3
© SAP 2009
SAP Enhancement Packages - AvailableAnd Synchronized For The Entire Suite
The roles mentioned on this slide refer to the SAP Standards for E2E Solution Operations.
3
© SAP 2009
Enhancement Packages - Lifecycle
¹ Direct upgrade from these source releases to the go-to releases of SAP Business Suite 7 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) have to be migrated separately.³ Besides the core applications, the SAP Business Suite provides also industry-specific applications (e.g. SAP Dealer Business Management, SAP Reinsurance Management) and cross-industry supplementary applications (e.g. SAP Portfolio and Project Management, SAP E-Sourcing). For these applications, the usual upgrade procedures apply. For an overview on the currently available and planned industry and supplementary applications, please refer to "SAP Release Strategy for Large Enterprises" on http://www.service.sap.com/releasestrategy
Install SAP enhancement package 4 for SAP ERP
SAP R/3 4.0B¹and above
SAP CRM 4.0¹,²and above
SAP SRM 3.0¹and above
SAP SCM 4.1¹and above
SAP PLM 4.0¹and above
Upgrade to SAP ERP 6.0 and include SAP enhancement package 4 for SAP ERP
SAP ERP 6.0 plus SAP enhancement
package 4 for SAP ERP
(including SAP PLM 7.0)
SAP CRM 7.0
SAP SRM 7.0
SAP SCM 7.0
SAP PLM 7.0
Upgrade
Upgrade
Upgrade
SAP ERP 6.0
Core A
pplications of SAP B
usiness Suite 7³4
© SAP 2009
Upgrade Paths - How to Get to SAP Business Suite 7 if You’re Running on...
Business Suite Upgrades
SAP Business Suite 7 - Overview: End-to-End Processes 1
Transition to SAP Business Suite 72
Technology Considerations
Upgrade per Application Deploy further Applications
AB
© SAP 2009
http://service.sap.com/scl
1
© SAP 2009
Mandatory Components -Scenario & Process Component List
1. Install SAP Solution Manager 7.0.
2. Upgrade existing system landscape:- SAP R/3 4.6 C to SAP ECC 6.04.- SAP BW 3.5 to SAP Netweaver
Business Warehouse (BW) 7.01.
3. Install and implement new components- SAP CRM 7.0 / NW7.01 - CRM
Application Server ABAP.- SAP CRM 7.0 / NW7.01.- SAP SCM 7.0 - SCM Server.
Selected ScenarioGoal: Customer implements value scenario “Lead to Cash”
Required Steps
2
Current system landscape
Target system landscape
Portal 7.0*
R/3 4.6C Server
SAP R/3
ABAP
Portal 7.0*
ABAP
SAP BW
Portal 7.0*ECC Server
SAP ERP
ABAP
Portal 7.0*
ABAP
SAP BW
EXAMPLE
BW Server
BW Server
© SAP 2009
Upgrade Dependencies - Evolution Path Example: Implement “Lead to Cash”
SAP ERP/PLM
I: General Recommendation II: Reasonable Alternative
Single System Scenario Layered PLM Deployment
Use CaseSingle System Scenario with SAP PLM 7.0 (PLMWUI and EHP 4) with PPM 5.0 (CPRXRPM) as Add-On.Project and portfolio management, design collaboration.
BenefitsReduced TCO by shared use of infrastructure.Reduced administration and operation effort.
ConsiderationsPLM scenarios running in SAP ECC Server might impact:
stability & performance.downtime for patching.Security.
Use CaseProduct development with partners using external ("presentation only" mode) and internal ("data persistency" mode) layers.
BenefitsIncreased network security through separation of application servers.Intranet and extranet access controlled by authorizations inside internal application server.Better scalability and load balancing capabilities.
ConsiderationsComplex system landscape and higher TCO.
internal
external
3
© SAP 2009
Deployment Options -SAP ERP / PLM 7.0 Deployment
Use CaseCentrally governed SAP SRM Server integrated to 1-n SAP ERP systems.Centralized procurement.
BenefitsSupport different innovation cycles, individual availability.Separation of responsibilities (e.g. less alignment effort) .Independent scalability & performance.Flexibility to change landscape layout.
ConsiderationsHigher TCO.
Use CaseSingle System Scenario with SAP SRM 7.0 (with EHP4 and SRM_SERVER and SRM_EXT as Add On’s). Self-Service Procurement (classic Scenario), Temp. Labor Service Procurement, Supplier Self Service.
BenefitsReduced TCO by shared use of infrastructure and one organizational model.Master data distribution synchronously & bi-directional.
ConsiderationsFunctional Limitations, e.g. no extended classic scenario, no multi backend deployment.
SAP SRM
Single System Scenario SRM Server Deployment
SAP SRM
Server
3
I: General Recommendation II: Reasonable Alternative
© SAP 2009
Deployment Options -SAP SRM 7.0 Deployment
SAP SCM
Use CaseStandalone, centrally governed SAP SCM Server.
BenefitsSupport different innovation cycles, individual availability.Separation of responsibilities (e.g. less alignment effort). Independent scalability & performance.Flexibility to change landscape layout.Full functionality available.
ConsiderationsHigher TCO.
Use CaseSingle system scenario with EM and EWM Add-ons (with EHP3+ and SCM_BASIS, SCMEWM , SCEMSRV as Add On’s). Event Management, Extended Warehouse Management, planned: Transportation Management (SAP TM 8.0).
BenefitsReduced TCO by shared use of infrastructure.Reduced administration and operation effort.
ConsiderationsFunctional limitations, e.g. no Supply Network Collaboration (SAP SNC) or Advanced Planner & Optimizer (SAP APO).
SCM Server Deployment Single System Scenario
3
I: General Recommendation II: Reasonable Alternative
© SAP 2009
Deployment Options -SAP SCM 7.0 Deployment
SAP CRM3
© SAP 2009
Deployment Options -SAP CRM 7.0 Deployment
SAP NetWeaver Scenarios -Deployment of SAP NetWeaver Portal
General RecommendationShared usage of SAP NetWeaver Portal provides a central access to the SAP Business Suite application systems in the customer solution landscape.SAP NetWeaver Portal is deployed as a separate system to support different innovation speed and simplified landscape setups.Avoid embedded deployment of SAP NetWeaver Portal within the application system.
General RecommendationShared usage of SAP NetWeaver Portal provides a central access to the SAP Business Suite application systems in the customer solution landscape.SAP NetWeaver Portal is deployed as a separate system to support different innovation speed and simplified landscape setups.Avoid embedded deployment of SAP NetWeaver Portal within the application system.
Use CasesCentral role-based access to different backend applications.Sharing central portal infrastructure for portal based applications.
BenefitsCentrally governed and administrated portal.Shared use of central SAP NetWeaver system to reduce administration effort.
ConsiderationsInteroperability to connected application systems have to be checked.Applications running in the portal might impact.
stability & performance.downtime for patching.
4
Central portalSRM Server
CRM Server
© SAP 2009
General RecommendationIntegrate, store, and manage company data from multiple connected data sources in acentral data warehouse system including central definition of all queries, web templates andenterprise reports. Comprehensive set of planning and simulation capabilities with a simplified landscape setup.Implement SAP Netweaver Business Warehouse and Business Explorer Web capabilities on separated systems.
General RecommendationIntegrate, store, and manage company data from multiple connected data sources in acentral data warehouse system including central definition of all queries, web templates andenterprise reports. Comprehensive set of planning and simulation capabilities with a simplified landscape setup.Implement SAP Netweaver Business Warehouse and Business Explorer Web capabilities on separated systems.
Use CasesIntegrate, store, and manage company data from multiple connected data sources in a central data warehouse system.Design and execute queries to analyze business information.Access analytic data based on web templates and enterprise reports.
BenefitsConsolidated view of company wide reporting data.Comprehensive Business Intelligence capabilities for planning and simulation.Reduced TCO by shared services and infrastructure.Highly scalable by separated technology stacks.
ConsiderationsRelease & SP stack dependency between SAP Netweaver Business Warehouse and BEx Web²
² current planning: remove support package stack dependency with SAP NetWeaver 7.0 EHP2
Central Data Warehouse
Central Bex Web
4
Portal 7.0*
ABAP
SAP BW
BW Server
SRM Server
SCM Server
© SAP 2009
SAP NetWeaver Scenarios - Deployment of SAP NetWeaver Business Warehouse
General RecommendationShared usage of SAP NetWeaver Process Integration for A2A or B2B scenarios as well as service enabling of the SAP Business Suite application systems. SAP NetWeaver Process Integration is deployed as a central, separate system to supportdifferent innovation speed and simplified landscape setups.Avoid embedded deployment of SAP NetWeaver Process Integration within the application system.
General RecommendationShared usage of SAP NetWeaver Process Integration for A2A or B2B scenarios as well as service enabling of the SAP Business Suite application systems. SAP NetWeaver Process Integration is deployed as a central, separate system to supportdifferent innovation speed and simplified landscape setups.Avoid embedded deployment of SAP NetWeaver Process Integration within the application system.
Use CasesIntegration of A2A or B2B processes between SAP and Non-SAP systems.Service enablement of SAP and Non-SAP systems.
BenefitsLess complexity of system landscape.Central governance for meta data.Less effort by central maintaining of data for routing,mapping, connectivity, ccBPM, etc.Central responsibility for monitoring of services and processes.Support of high volume scenarios, simplified modeling and configuration, enhanced standard support with SAP NetWeaver Process Integration 7.1.
Central PI
4
SCM Server
© SAP 2009
SAP NetWeaver Scenarios - Deployment of SAP NetWeaver Process Integration
Resources (1/2)
SAP Business Suite 7Homepage: http://service.sap.com/businesssuite
SAP CRM 7.0: http://service.sap.com/crm
SAP PLM 7.0: http://service.sap.com/plm
SAP SRM 7.0: http://service.sap.com/srm
SAP SCM 7.0: http://service.sap.com/scm
SAP ERP 6.0 – please see below
SAP ERPHomepage: 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
Scenario & process component list: http://service.sap.com/scl
SAP Enhancement Package Infocenter: http://service.sap.com/erp-ehp
© SAP 2009
SAP Upgrade Info CenterHomepage: http://service.sap.com/upgrade
SAP ERP 6.0 Upgrade: http://service.sap.com/upgrade-erp
SAP Upgrade Road Map: HTML Version
SAP Upgrade Tools Upgrade Tools: http://service.sap.com/upgradetools
System switch technology: http://service.sap.com/upgradetech
SAP Solution Manager: http://service.sap.com/solutionmanager
SAP Upgrade Services Overview and order information: http://service.sap.com/upgradeservices
SAP Consulting upgrade services : http://service.sap.com/ufg
SAP Netweaver Homepage: http://service.sap.com/netweaver
SAP Netweaver administrator: http://service.sap.com/nwa
System landscape directory: http://service.sap.com/sld
Software lifecycle manager: http://service.sap.com/slm
Resources (2/2)
© SAP 2009
Key Technology Considerations
Source: MOVE/GUO
Target Business Suite 7Current
Upgrade per application
Upgrade Paths
Complexity Drivers
SAP Enhancement Packages
UnicodeA
Business scenarios in ONE application
Upgrade the respective application.Activate new functionality.
Deploy further applications
Deployment Options
Upgrade DependenciesB
Mandatory Components
Business scenarios ACROSS applications
Upgrade the respective applications.Deploy required additional applications. SAP NetWeaver Scenarios
SAP Appl. BS 7 Appl.Upgradee.g. SAP
R3 4.Xe.g. EHP 4 for SAP ERP 6.0
Upgrade & Deploy
SAP Appl.e.g. SAP R3 4.X
1
2
3
4
1
2
3
4
SAP Business Suite
NetWeaverIntegration
NetWeaverComposition
EHP
EHP
SAP ERP SAP CRM SAP SCM SAP PLMSAP SRM
Industry Applications
Supplementary Applications
SAP Business Suite SAP Business Suite
NetWeaverIntegration
NetWeaverComposition
EHP
EHP
EHP
SAP ERP SAP CRM SAP SCM SAP PLMSAP SRM
Industry Applications
Supplementary Applications
© SAP 2009
Transition to SAP Business Suite - Summary