WIXLIB

Migrating SAP & Solution Managerto a HyperscalerMatthew HarmonSolution Manager (SOLMAN) Leader – S/4HANA Cloud EnvironmentW.L.GoreCraig BrownChief Transformation ArchitectXceleon

Key Outcomes/ObjectivesLearn About:1. Developing a migration playbook for your SAP Solution Manager toexpedite your migration2. Helpful planning suggestions from SME's who have lived through amigration and can give you real world examples and lessons learned3. Areas to watch out for in the planning and migration process to ensuresuccess4. How to prepare if you are planning an SAP S/4HANA migration in parallel2 2022 ASUG

Agenda Developing a migration playbook for your SAP Solution Manager Helpful planning suggestions from SME's who have lived through amigration Areas to watch out for in the planning and migration process How attendees found success and what resources they utilized to attain it SAP Tools to help if you are planning a transition to SAP S/4HANA Open discussion3 2022 ASUG

Matthew Harmon15 years of IT experience with varying roles and responsibilities including SAP Project and Program Management.Co-chair ASUG Solution Manager Influence Council10 Years-experience with SAP Solution Manager7.2 Knowledge Areas ChaRM Solution Documentation Technical Monitoring Focused Insight Test ManagementBusiness Process MonitoringIncident ManagementFocused BuildCraig BrownCo-chair ASUG Solution Manager Influence Council & Think Tank15 years of IT experience to include Chief Consultant and S/4HANA Migration Architect12 Years-experience with SAP Solution Manager & ALM Operations7.2 Knowledge Areas & ALM Value Streams Focused Build Solution Documentation Test Management & Test Automation ChaRM 4 2022 ASUGMigration Assessment and PlanningThird Party Tool IntegrationAgile Program and Project OperationsStandard and Custom Dashboards

Migrating SAP & SolutionManager to a Hyperscaler5 2022 ASUG

Engagement Be an active participant in the planning Each customer is different, there is no ‘one size fits all’ There are strategies for success and planning is critical Understand your environment, business requirements and utilization6 2022 ASUG

Solution ManagerUtilization Organizer7 2022 ASUG

KeySolution Manager Usage lementationScenarioNot Heavily Used, but configuredUsed by two of four regionsUsed by All Regions, highly configuredDetails of ImplementationAdoptionProcess Management# process diagrams, # transactions/programs documented, used for Solution DocumentationHighTest SuiteRegionally for test management, primarily manual test casesHighBusiness Process Operations# of Business Process monitors set up across four landscapes (SIDs), EEM scripts runningHighChange Control Management# of SAP landscapes are managed by ChaRM. (Types of Change: Normal, Urgent, Standard, Admin andGeneral)Very HighCustom Code ManagementConfigured to most major landscapes, not heavily utilizedLowApplication OperationsBaseline technical monitoring is set up for all landscapes connected to Solution ManagerHighIT Service ManagementInterface to 3rd party external Service Desk, ServiceNow to incidents passed between systems (Start inSNOW)HighLandscape ManagementLeveraged by Global Basis team to manage # of SAP SIDsHighData Volume ManagementConfigured to most major landscapes, not heavily utilizedLowInterfacesServiceNow for Incident, SharePoint, MF ALM for Testing, TREXHigh 2022 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLICSP ##8

Solution ManagerMigration Approach9 2022 ASUG

ChaRM General Approach SAP Solution Manager should go last – but takes careful planning for those other systems being migrated If you have cycles that contain multiple SAP systems, before migration they need to be pulled out of all opencycles and put into their own dedicated cycle: If something goes wrong, you do not want to stop daily operations which can happen – cycles aredesigned to protect themselves and will lock For example if user/saptrans is not reachable, the entire cycle stops working Be sure to check all cycles: If continual cycles are open, this can take some time Do not underestimate the amount of open documents Leverage report: https:// server :port/sap/bc/webdynpro/sap/ai crm cm com wd esh ui# Have this done even before your first sandbox system moves10 2022 ASUG

Establish a Playbook11 2022 ASUG

Phase 1 – Project DEV MigrationExistingSTMSRouteProj DevProj TestMaint DevMaint DevMaint TestProdSystem beingmigratedMain TestProdBeforeDuring Migration (downtime)After Migration (duringdowntime) Send comms to users to complete alldocuments and what new cycle touseRemove from all cycles (Except Q2)Open status switches for all systemsCommunicate new HEC specific cycleto be used for all other changesSet LMDB as inactiveValidate TMS Domain Controller isDevelopmentRunhttps:// server :port/sap/bc/webdynpro/sap/ai crm cm com wd eshui#Extract iBase Numbers before anymigrations start for reference12 2022 ASUG DEV will not be available. Need toassess where the team in in therelease cycle and give direction. Forexample, Sandbox or projectconsolidation, etc Consider changes through themaintenance landscape would needto be retrofitted. If project work isdecided to and happening inmaintenance path, would need towait for Dev system to be back to beable to auto-retrofit. Formaintenance changes while devsystems is down, will need to retrofitmanually (Depends on timing) Week of Mon DCycle phase: [Phase]System migratedCycle Name: To be NamedMonth D – Month D SCOPEMonth D – Month D BUILDMonth D – Month D TESTMonth D-D GO LIVEAfter Migration (systemreleased to users)Execute post migration Basis tasks Set LMBD Active RFC Connections Managed systemconfiguration Review transport route Validate TMS DomainController is Project Dev Use RZ70 to push data Check SLD information Check new IP and hostnameof HEC system Check LMDB information,make sure LMDB has correctinformationLandscape should be redefined toidentify if any issues exist in thecycle ChaRM team needs tovalidate cycles are usefulFollow previously agreedretrofit plan

Phase 2 – Project Consolidation MigrationExistingSTMSRouteProj DevProj TestMaint DevMaint DevMaint TestProdSystem beingmigratedMaint TestProdSystem migratedWeek of Mon DCycle phase: [Phase]BeforeDuring Migration(downtime)After Migration (duringdowntime)Cycle Name: To be NamedMonth D – Month D SCOPEMonth D – Month D BUILDMonth D – Month D TESTMonth D-D GO LIVEAfter Migration (system released tousers) Confirm with userswhat to do at thisphase of migrationSet LMDB as inactiveRunhttps:// server :port/sap/bc/webdynpro/sap/ai crm cm com wd esh ui#Extract iBase Numbersbefore any migrationsstart for reference 13 2022 ASUGDEV will be available. Need toassess where the team is in therelease cycle and give directionEx (What to do/not do withdocuments (i.e. BPP Approval,Confirm Test Success, etc.)Consider changes through theupper landscape would need tobe retrofitted. If project work isdecided to and happening inmaintenance path, would need toadvise on auto-retrofitFor maintenance changes, willneed to advise on outstandingretrofits (Depends on timing) Execute post migration Basis tasks Set LMBD Active RFC Connections Managed systemconfiguration Review transport route Use RZ70 to push data Check SLD information Check new IP and hostnameof HEC system Check LMDB information,make sure LMDB has correctinformationLandscape should be redefined toidentify if any issues exist in thecycle ChaRM team needs to validate cycles areusefulFollow previously agreed retrofit plan

Phase 3 – Production MigrationExistingSTMSRouteProj DevProj TestMaint DevMaint DevMaint TestProdSystem beingmigratedMaint TestSystem migratedProdWeek of Mon DCycle phase: [Phase]Cycle Name: To be NamedMonth D – Month D SCOPEMonth D – Month D BUILDMonth D – Month D TESTMonth D-D GO LIVEBeforeDuring Migration(downtime)After Migration (during downtime)After Migration (systemreleased to users) Confirm with users whatto do at this phase ofmigrationSet LMDB as inactiveValidate TMS DomainController is NOTProductionRunhttps:// server :port/sap/bc/webdynpro/sap/ai crm cm com wd esh ui#Extract iBase Numbersbefore any migrationsstart for reference14 2022 ASUG DEV will be available. Need toassess where the team is in therelease cycle and give directionEx (What to do/not do withdocuments (i.e. Confirm TestSuccess.)Consider changes through theupper landscape would need tobe retrofitted. If project workis decided to and happening inmaintenance path, would needto advise on auto-retrofitFor maintenance changes, willneed to advise on outstandingretrofits (Depends on timing) Execute post migration Basis tasks Set LMBD Active RFC Connections Managed system configuration Review transport route Use RZ70 to push data Check SLD information Check new IP and hostname of HECsystem Check LMDB information, make sureLMDB has correct information Validate TMS Domain Controller isProject DevLandscape should be redefined to identifyif any issues exist in the cycle ChaRM team needs to validatecycles are usefulFollow previously agreed retrofitplan

Phase 4 – Remaining System MigrationExistingSTMSRouteProj DevProj TestMaint DevMaint DevMaint TestProdMaint TestSystem beingmigratedSystem migratedProdBeforeDuring Migration(downtime)After Migration (during downtime) Confirm with users what todo at this phase of migrationSet LMDB as inactiveValidate TMS DomainController is NOT ProductionRunhttps:// server :port/sap/bc/webdynpro/sap/ai crm cm com wd esh ui#Extract iBase Numbersbefore any migrations startfor reference DEV will be available. Needto assess where the team isin the release cycle and givedirectionEx (Manual release steps tomove transports)Need to assess how to moveurgent changes 15 2022 ASUGExecute post migration Basis tasks Set LMBD Active RFC Connections Managed system configuration Review transport route Use RZ70 to push data Check SLD information Check new IP and hostname of HECsystem Check LMDB information, make sureLMDB has correct information Validate TMS Domain Controller isProject DevLandscape should be redefined to identify ifany issues exist in the cycleUpdate documents to reflect the new IBASE /Configuration item of MGPWeek of Mon DCycle phase: [Phase]Cycle Name: To be NamedMonth D – Month D SCOPEMonth D – Month D BUILDMonth D – Month D TESTMonth D-D GO LIVEAfter Migration (systemreleased to users) ChaRM team needs to validatecycles are usefulFollow previously agreedretrofit planConfiguration item in changedocument needs to be updated AI MODIFY IBASE IN DOCIf DB migrated, need to redomanaged system setup – DBconnection – Deactivate in onprem environment

Migration Lessons Learned16 2022 ASUG