SAP ERP 6.0 UpgradeWelcome to the SAP ERP 6.0 Upgrade space. This is the SDN Wiki starting point for topics around the SAP ERP Upgrade. Feel free to create and correct entries. SAP had developed three different upgrade project approaches to move from SAP R/3 to my SAP ERP2005. Why Upgrade?The value proposition and related return on investment (ROI) highly depend on the motivation and selected approach for your upgrade project(s). The value proposition is specific to every customer because their system landscapes and SAP software in use is very unique. Furthermore, SAP customers have different needs to achieve further improvements in operational excellence or to become enabled for future business motivation. In any case, SAP's best-in-class guidance and portfolio of offerings help you master any potential challenges. Justifying the UpgradeA customer-specific justification for an SAP upgrade includes a combination of several arguments, including the following:
In the following decision framework, individual business needs are mapped to respective SAP enablers. The framework, which covers both business and IT requirements, summarizes the motivation and value drivers for SAP upgrades in four major categories.
Please find more details on: http://service.sap.com/upgrade Determining an Upgrade StrategyUpgrade strategy is determined by the factors which influence the upgrade project. It would determine the decisions on IT and business related factors as well as Unicode conversion and technical perspective.
Factors influencing the complexity of an upgrade :IT related complexity Drivers
Project Related complexity drivers
Business Related complexity Drivers
Upgrade ApproachesSuccessfully executing an upgrade to SAP ERP 6.0 requires a well-defined upgrade strategy encompassing an approach and project scope based on the circumstances and aims of your organization. The project 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. Step 1: Technical UpgradeThis initial phase involves a purely technological upgrade whose major goal is the implementation of the new software release as the foundation for all subsequent improvements. The impact of this phase on your business and business processes is very limited:
The technical upgrade simply creates the basis for functional and strategic enhancements. Step 2: Functional EnhancementsDirected toward business benefits, this phase focuses on increasing business value by implementing the most valuable functions of the new software and laying the foundation for future business 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 combined in a single project with the technical upgrade, statistics show that more than 80% of SAP customers approach this second phase as a separate project, to be conducted after a technical upgrade has been completed and overall stability has been reached. Step 3: Strategic EnhancementsPhase three involves implementing new and optimized business processes and scenarios that fully exploit new SAP ERP functions and enable enterprise SOA. It may include implementing other software systems or components and is very much dependent on the business needs of your organization. Enterprise SOA enables you to shorten application innovation life cycles and implement strategic business enhancements at your own speed. SAP Upgrade Road MapSAP has defined a roadmap for upgrade. You can access it in SAP Solution Manager or via SAP Service Marketplace (http://service.sap.com/upgraderoadmap).
SAP expects at least 2 to 3 months for an upgrade and this again depends on project scope and complexity and various other factors that depend on the upgrade project and on the individual organization.
|
Moderators of this WIKI section are Sriramachandra Murthy Parasuramuni and Anja Mueller |
Frequently Asked Questions
containing a collections of problems and questions around ERP2005 Upgrade. Learning Map
Upgrade Realization
This section contains the information about the standard landscape strategy to be followed for Upgrade.
|
Interesting References / Links
There are good articles, information and blogs on ERP2005 Upgrade in SAP and other online websites. Find here a collection of some of the most interesting. Migration Tasks / Check Lists
Find Important migration tasks & Key things to be taken care during Upgrade Bibliographyhttp://www.sap-press.de/katalog/buecher/titel/gp/titelID-2050 http://www.sap-press.de/katalog/buecher/titel/gp/titelID-2385 This section contains links to books related to ERP2005 Upgrade. How-to Guides |
Please review the Guidelines before contributing in this Wiki space.
DO NOT USE WIKI PAGES TO POST QUESTIONS AND ANSWERS. Use appropriate forums listed under links on right hand side of this page.