1 / 21

SAP R/3 upgrades

SAP R/3 upgrades. A Methodology overview. Overview. Why Upgrade ? What’s Effected ? What Can Be Reused ? What Will Be New or Changed ? What Does The Project Include ? What’s New With Upgrading to 4.x? Lessons Learned. Why Upgrade ?. Provide new capabilities Fix bugs

lynde
Download Presentation

SAP R/3 upgrades

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. SAP R/3 upgrades A Methodology overview

  2. Overview • Why Upgrade ? • What’s Effected ? • What Can Be Reused ? • What Will Be New or Changed ? • What Does The Project Include ? • What’s New With Upgrading to 4.x? • Lessons Learned

  3. Why Upgrade ? • Provide new capabilities • Fix bugs • Eliminate customization • Stay current (Address end of life issues) • Business process extension • mySAP.com • APO • CRM • BW • To upgrade other components • Database • Operating system • Corporate structure changes • Merger, acquisition, divestiture

  4. What’s Effected ? • Database servers • Application servers and workstation GUIs • Processes • Data • Interfaces • Customization • Reports • Training and documentation • People - users, IS, and project team

  5. What Can Be Reused ? • Processes that do not change between versions • Related documentation and training materials • Technical design/code potentially not effected by the upgrade • Interfaces • Customizations • Reports • Layout Sets • SAP terminology, knowledge, skills • Project team • Process knowledge of the end user community

  6. What Will be New or Changed? • New or changed processes, documentation, & training • Interfaces, reports, etc. impacted by changes in the target SAP table structures, coding syntax, and/or different screen flow • New customized functionality • To supplement new, changed, or existing processes • Customization that can be removed • User exits • Custom ABAPs

  7. SYSTEM DESIGN TEST & TRAINING SYSTEM CONSTRUCTION PROJECT PREPARATION GO-LIVE & SUPPORT What Does The Project Include?

  8. What Does The Project Include? • Project Preparation • Build the business case and justification • Define the scope • Prepare the project work plan • Review user requirements • What outstanding system change requests can be met by the upgrade? • What new functionality do we want from the upgrade? • Review organizational change impact • Develop other project management deliverables • Issue resolution plan • Risk analysis • Project standards • Software configuration management plan

  9. What Does The Project Include? • System Design • Review/Setup environments • Sandbox • Development • QA • Others • Process design and regression • As-Is flows • To-Be flows • Results in new and modified flows as needed

  10. What Does The Project Include? • System Design (continued) • Data design and regression • R/2 - R/3 ABAPs • Source to target table changes • Customization design and regression • Resulting in customization specifications for functionality gaps between the current and new version • Interface design and regression • Resulting in interface design for new and modified interfaces • Report design and regression • Resulting in report design for new and modified reports • Establish business scenarios • For new and modified business flows that will need to be tested

  11. What Does The Project Include? • System Construction • Develop upgrade execution plan • Develop training plan and training materials • For new and changed functionality • Develop system test plan • Individual business process tests • Fixes and rework • End-to-end test • Produce records

  12. What Does The Project Include? • System Construction (Continued) • Execute upgrade - iterate with testing • Perform first test upgrade • Move to first test cycle • Fix and rework problems found during test • Iterate until upgrade is successful • Configure changed and new processes • Conversion programs • Interfaces • Reports

  13. What Does The Project Include? • Test & Training • Conduct system test - iterate with conversion • Test the actual upgrade • Individual business process tests • Test ABAP customized code and changed SAP code • End-to-end test • Re-testing for time estimates and documentation verification • Produce records • Plan detailed organizational changes • For new or modified functionality • Conduct user training • For new and modified functionality

  14. What Does The Project Include? • Test & Training (Continued) • Conduct additional testing • Performance testing/tuning • User acceptance testing • Develop detailed cut-over plans • How long will it take? • What is the landscape path? • Who is responsible for what?

  15. What Does The Project Include? • Go-Live & Support • Finalize cut-over plan • Develop “Go Live” contingency plan • Develop system support plan • Install upgraded system • Use records produced during construction/test iteration • Implement organizational changes • Go Live • Support system

  16. Business Processes Development Basis Upgrade Components Configuration Authorizations Reports/Layout Sets Interfaces/EDI/Conversions Modifications/Enhancements Data Dictionary Objects Operating System/Database Upgrade (R3up/R3Setup) Preparation Post-Processing

  17. Upgrading to 4.x • R/3 Upgrade Assistant - Upgrade systems remotely via a web browser • PREPARE tool pre-loads data and helps reduce upgrade time • Modification conflicts can be identified via PREPARE - prior to actually upgrading

  18. Lessons Learned • The current functionality will still exist in the upgraded system • Make sure to look at: • Configuration that may have changed during the upgrade • New configuration that needs to be adjusted to fit the current process flows • Follow a structured methodology • Similar in many ways to a straight implementation

  19. Lessons Learned • Depending on situation, it may be less painful and expensive to do a new implementation • You get good reuse from process documentation and training materials • Plan organizational impact

  20. Lessons Learned • Even if it doesn’t appear to be affected, test to make sure • Schedule MANY dry run test upgrades • Upgrade project is very linear - plan accordingly and do not expect overlap • Pay attention to the version of everything involved • SAP • Database • Operating system • Interfacing systems

  21. Lessons Learned • Complexity of the upgrade is directly related to how well the systems have been maintained • Select team members carefully • Similar to the original implementation, they should have a strong understanding of the business process in their area • If not, some of the processes may be overlooked

More Related