2 Project Aim: Why: ECC6 Upgrade Technical Upgrade to MySAP ERP 2005 ( ECC6 )Why:To prepare the foundation for NetWeaver / SOA ImplementationTo enable new SAP Functionality .To keep up-to-date – Mainstream Maintenance over.
3 Sub Projects along the Way: ECC6 UpgradeSub Projects along the Way:BIDI MigrationGUI Deployment / Citrix Deployment .Keter’s AS400 Data Warehouse Replication from SAP.64 Bit Windows / SQL implementation.Unicode enabling of our SAP Systems.
4 Business Background: ECC6 Upgrade The Keter Group has 22 SBU's dispersed globally in Israel, Europe, and the USA, connected to our central SAP System in Israel, working 24 hours a day, 7 Days a week.
5 Technical: ECC6 Upgrade Before: Operating System is Windows 2003 Enterprise.Our 46C DataBase was SQL 2000 – Advanced- 900 GB.After:Operating System is Windows 2003 Enterprise 32 Bit.With x64 – we will only require Windows 2003 Standard.Our new ECC6 Database is SQL 2005 – Enterprise 32 Bit and already 980 GB.The Upgrade to ECC6 added 45 GB to the Database.
6 Upgrade Project: Management: Technical Aspects: Functionality: Defines the scope of the Project – Planning.Kick Off - Project beginning and end.Support, Redefinition if required. Keeping to Deadlines.Technical Aspects:Infrastructure sizing – Servers, Communication, Desk Top.Functionality:Modifications and Custom Development.Mapping of Delta Functionality.Testing of functionality and Modifications .Training
8 Special Issues/Decisions: ECC6 UpgradeSpecial Issues/Decisions:BIDI Conversion with new SAP GUI Deployment – Before or at the same time as the Upgrade.To Build a new Dev System from the Production System or upgrade both systems independently.Down Time or Resource minimized Scenarios."In House" or "Fixed Price" Bid for the Project .To Unicode enable all customer programs or leave it as a post-upgrade project.SPAU – Clean the SPAU in the original 4.6C system or only in the Final System.
9 Pre-Upgrade Analysis: ECC6 UpgradePre-Upgrade Analysis:Hardware Sizing:From the Hardware Vendor – in our case HP.SAP Functional Upgrade Check:SAP Service that checks Hardware and performance capabilities before and after Upgrade.Application Specific Upgrade ( ASU ) tools from SAP:Includes application specific documents that outline problems with corresponding solutions including relevant SAP Notes.For each application area – CO , PP , MM, FI and SD.Tools to correct known problems – Variants etc – These tools were mostly built in to the ECC6 Upgrade Package already.Solution Manager:Upgrade RoadmapSolution Browser:Release Notes:Was not available at the time
10 Pre-Upgrade Analysis: ECC6 UpgradePre-Upgrade Analysis:Internal Interface analysis:ECC6 To/From external Systems – "Real Time" machine monitoring system , Time Clocks , VAT etc.Interfaces between BW , APO and ECC6.IntelliCorp Assessor Upgrade Edition:Both for Functionality and Project ScopeRequired a live ECC6 System to compare to.We used an Upgraded to ECC6 Dev system and the 4.6C Production System as reference.
11 Intellicorp Assessor Upgrade Edition: ECC6 UpgradeIntellicorp Assessor Upgrade Edition:Executive Summary:Project Scope.Excel Lists containing:All SAP programs according to SAP User and their index of modification in ECC6 according to Application Area.New SAP transactions in ECC6.Replaced Transactions in ECC6.Used/Unused Customer programs with Usage statistics .Customer Batch Input Programs and used BAPI's with code placement that would probably need to be changed in ECC6.
12 AUE Highlights: ECC6 Upgrade The Application Area was not always clear – We manually changed the Area where there were problems – a day's work.This is a SAP Issue because it is not always accurate.We sorted the Lists according to Application Areas and the lists were given to the relevant "Top Users"There was no indication of the last Programmer who did a change in the Program list.Consequently – we merged the Programmer Name into the Excels.This allowed us to sort the Program Changes and give the Program Change List to relevant Programmers.We also had a list of Customer programs that were not in use ,but they were called by other programsEstimation of required resources - manpower.The Excel sheets were passed onto the Keter Top Users and Programmers as a preparation and guide for functional and application Testing.This is a SAP Issue because it is not always accurate.We sorted the Lists according to Application Areas and the lists were given to the relevant "Top Users"
13 Our Upgrade Plan : ECC6 Upgrade Upgrade a copy of the Development System as a trial run.To see if we were missing anything – Software CD's , Notes etc.CookBook entries.Upgrade a copy of the Production System as a Upgrade Sandbox System:Used to test functionality – correct bugs .Created a separate transport for each program.We saved the transports and ported them to the next stage.Final Upgrade of the Development System and Interim Test System.Simultaneous upgrade of a copy of the Production System as an Interim Test SystemCode Freeze on the R3 Landscape.Porting of Transports from the Sandbox System to both the Final Dev System and the Interim Test System.SBU testing and training was done on the Interim Test System.Rehearsal Upgrade of the Production System.Testing and Final System Verification and acceptance was done on this System.Final Upgrade of the Production System.
14 Testing and Training Scenarios: ECC6 UpgradeTesting and Training Scenarios:Application and Functionality:Performed by Top Users and Implementation Consultants in the Keter Headquarters.Used the Lists derived from the Intellicorp Upgrade Assessment.Was done on our Upgrade Sandbox System first.Corrections / modifications were done on this system – the Transports were ported to the Final Dev system.Then testing was done on the Interim Test System.2nd Level testing was done by the Top Users in the SBU's.They concentrating on their most complex procedures.They were also responsible for local training.This testing and training was done on the Interim Test System.
15 Testing and Training Scenarios: ECC6 UpgradeTesting and Training Scenarios:Modifications and Customer Development:Checked and tested by the relevant Programmers / Top Users.Used the Intellicorp Upgrade Assessment derived Lists.
17 Upgrade Trial Run: ECC6 Upgrade Copy of Development System R3 ECC6 DEV Test/QAPRDR3To check if anything is missing.Notes, Downloads, etc.Ran Intellicorp Upgrade AssessmentECC6DEVTrial
18 Upgrade PRD to Sandbox: ECC6 UpgradeUpgrade PRD to Sandbox:Copy of Production SystemDEVTest/QAPRDR3TestingSPAUCorrectionsSave TransportsECC6SandBox
19 Upgrade Final DEV and PRD (Test): ECC6 UpgradeUpgrade Final DEV and PRD (Test):Copy of Development and Production SystemDEVTest/QAPRDR3R3 Code Freeze.SPAU again.Transports from SandboxTesting and Training in SBU’sECC6DEVFinalTest/QATransports
20 Testing and Final System Verification and Acceptance ECC6 UpgradePRD Rehearsal:Copy of Production SystemDEVTest/QAPRDR3Testing and Final System Verification and AcceptanceECC6DEVFinalPRDRehearsalTransports
21 Final PRD – Go Live: ECC6 Upgrade Copy of Production System R3 ECC6 DEVTest/QAPRDR3Contingency Plan for Roll BackOriginal PRD system existsIP and Server Name change only.ECC6DEVFinalPRDFinalTransports
22 Test/QA from PRD: ECC6 Upgrade DB Copy of Production System R3 ECC6 DEVTest/QAPRDR3ECC6DEVFinalTest/QAPRDFinalDB Copy
23 Glitches during the Upgrade Project: ECC6 UpgradeGlitches during the Upgrade Project:Localization CD at the last moment from NESS.HR SPAU entries.
24 Post Upgrade: Go-Live Problems/Issues and Lessons: ECC6 Upgrade Application ProblemsCitrix/GUI Deployment ProblemsBasis Problems.
25 Application Problems: ECC6 UpgradeApplication Problems:1st Week Problems:EDI did not fully work – very serious .SAPEVT did not work.HR Master data program did not work as before.COHV changed - no CO13.Changes to CS01/2/3.Replacement of MRHR with MIRO - Traumatic2nd Week Problems:3rd Week Problems:
26 GUI and Citrix Deployment: ECC6 UpgradeGUI and Citrix Deployment:Hebrew GUI Problems:6.40 GUI icons are different from 46DField Painting in Hebrew.Citrix Problems:Local DeskTop and Network Mapping.Printing through LOCL.Requires better quality communication lines.
27 Basis : ECC6 Upgrade SAP Functional Upgrade Verification. Performance tuning.Database tuning.Memory Tuning.SQL 2005 Service Pack 2 – waiting ….SAP ABAP and Basis Support Packs.Waiting for COP 11.
28 ECC6 UpgradeSummary:The SAP Technical Upgrade Process worked like a "Charm"Requires a thorough preparation and analyses of Application functionality.Mapping - Assessment for Upgrade Tool( Intellicorp ) .Requires Thorough Testing and User Training.
29 Lessons Learned: ECC6 Upgrade Keep the project simple - do not implement any new functionality.Do not try to mix too many projects together.It was problematic to Deploy Citrix and the new SAP GUI at the same time.The Upgrade project must be known to Localization at Ness .Localization CD at the last moment.Do not strive for too much Perfection – Know the Business Risks and Limits.Constantly Update Management and all Project People.Have a Contingency Plan for Roll Back.