Binoy JamesVP, Application DeliveryProtera Technologiesb.james@protera.biz@ProteraTech

Migrating to SAP Business Suite on SAP HANA

Protera Technologies

•

• SAP Centric IT Services Organization• Created by former SAP executives in 1998• Pioneer in AMS for SAP• Combined customer base of 150K SAP users• 60 + Live hosting customers across all industries • Completed 100+ SAP projects; migrations, carve-out• Strong Partnership with market leaders, SAP Ecosystem, Verizon, and AWS

On-Demand hosting and AMS

from SAP deployment to 24/7 support and SaaS delivery

On-Demand Service Offerings

SAP & Third Party Apps, MS SP/Exchange, Citrix, EDI/Fax, IT Outsourcing

SAP-Certified

Cloud, Hosting , AMS, HANA and Mobile Operations

SAP Solution Provider

Full Suite of SAP services and solutions on the Cloud

Global IT outsourcing services organization

Presence in the US, Europe and AsiaLeader in Global on-demand IT platform

services

Snapshot

Protera Technologies

Founded in 1998

Focus on SAP AMS & Hosting

SAP is our ONLY ERP application

Combined customer base of 150K SAP users

60+ Live hosting customers across all industries

Completed 100+ SAP projects; migrations, carve-outs

International Presence

Global Offices, Data Centers and Customers

Strong SAP Application Expertise

FIVE SAP Certifications, Including HANA Operations & Installation Proven Procedures, Tools and Automation, ITIL Framework

Strong Partnership Based Approach To Conducting Business

SAP TechEd 2014 Update

Options for Migration to SAP HANA

Classical Migration

DMO Migration

Classical vs DMO Migration

Best Practices & Optimizations

Q&A

APPENDIX:

Further Information

Agenda

SAP TechEd 2014 – SAP BSoH Roadmap

SAP TechEd 2014 – SAP BSoH Adoption Rates

SAP TechEd 2014 – SAP BSoH Migration Projects

SAP TechEd 2014 – SAP BSoH Cost Evolution

SAP TechEd 2014 – SAP HANA SPS09 11/2014

Migration to SAP HANA – Planning Considerations

Data Cleansing - Run SAP DVM project in Solution Manager

Check supported platforms, releases, add-ons & restrictions

Perform Sizing exercise of SAP HANA Define overall target system landscape Appliance, TDI or Cloud? Provision SAP HANA and associated systems in time Plan transition and optimization of custom code

Migration to SAP HANA – Options

Classical Migration to SAP HANA – Overview

Benefits: Results in nearly identical system Minimal impact on functional teams Both ABAP and Java-based systems can be migrated Pure migration without intermediate steps or HANA optimization (only if

source release supported on HANA)

Disadvantages:x Typically implies extended downtime and several downtime windows

depending on size of DB and required scope (Unicode conversion, SAP System upgrade, DB Upgrade, Migration)

x With inclusion of upgrade, fallback to original state only possible via restore

Classical Migration to SAP HANA – Process

Classical Migration to SAP HANA – Prerequisites

Following should be considered before performing a classical migration:

• Perform system sizing• As HANA appliance delivery may take time, order hardware in advance• Install latest version of HANA DB, client and Management Studio• Make sure your system is based on Unicode• Use latest versions of migration tools (SWPM, R3load, R3ldctl, R3szchk,

R3ta)• Use latest kernel versions/patches both on source and target system• Check and implement OSS Notes for SMIGR_CREATE_DDL report,

especially those relevant to HANA

Classical Migration to SAP HANA – Prerequisites

Following should be considered before performing a classical migration:

• Perform system housekeeping – delete/archive obsolete data from tables• Collect/Update DB statistics after data cleansing, prior to Migration• Consider table and package splitting to optimize migration runtime.

Perform test migration and analyze its results using Migtime tool• Download latest version of OSS notes specific to migration to HANA• Perform consistency check for pool and cluster tables. In large production

environment this step can take days to complete, so plan to run it in advance

• Generate the migration key

Classical Migration to SAP HANA – Export/Import

Following should be considered while performing a classical migration:

• Avoid creating export directory on NFS drives – this can slow exports and potentially corrupt export dump files

• Update database statistics in source system before performing export• Before starting import, set DB log mode to ‘Overwrite’ to avoid disk full

situations• Use HANA mass import feature to drastically improve import time

Classical Migration to SAP HANA – Post Processing

For SAP Business Suite systems, no additional steps apart from standard activities are required.

For SAP BW systems:Implement latest OSS Notes for report RSDU_TABLE_CONSISTENCY, then run it to identify problems which may occur in migrated system• Run report RS_BW_POST_MIGRATION• Perform repair of inconsistent PSA tables, check consistency for all

external HANA views, correct missing views for selected master data• Execute task list SAP_BW_AFTER_MIGRATION via transaction STC01 • Review OSS Note 1846493 “Important SAP Notes for SAP BW powered by

HANA” prior to production use of migrated system.

DMO Migration to SAP HANA – Overview

Benefits: Reduced complexity – one step upgrade/migration/Unicode conversion Manual effort and errors reduced, only intermediate fallback effort Downtime optimized (depending on scenario), only one downtime window NW 7.X based systems (for BW)/SAP ECC 5.0 as start release - for more

information, refer to OSS Note 1813548.

Disadvantages:x Only ABAP systems are currently supportedx Migrations as part of upgrade only (before SUM SP12), as of SUM SP 12

migration can be done directly to HANA as long as migrated system supports HANA

x Platform change with additional steps only

DMO Migration to SAP HANA – Process

DMO Migration to SAP HANA – Prerequisites

Following should be considered before performing a DMO migration:

• Perform system sizing (SAP Quicksizer)• As HANA appliance delivery and installation may take time, order

hardware and schedule resources well in advance• Download and check latest version of OSS notes specific to migration to

HANA using DMO• Install latest version of HANA DB, client and Management Studio• Perform dual-stack split as DMO supports only ABAP systems• Use latest kernel versions/patches both on source and target system• Check pool/cluster tables; as this step may take long time in large

environments, should be executed in advance• For non-Unicode systems, execute report UMG_ADD_PREP_STEP and

transaction SPUMG

DMO Migration to SAP HANA – Prerequisites

Following should be considered before performing a DMO migration:

• Oracle-based systems: implement measures suppressing long running migration phases

• Download and install latest versions of migration tools (SUM, SAP Host Agent)

• When running Maintenance Optimizer, generate upgrade queue which contains kernel files of the target software release for both the existing and the SAP HANA databases

• Check and implement OSS Notes for SMIGR_CREATE_DDL report, especially those relevant to HANA

• Start working with the Application-Specific Upgrade (ASU) toolbox in the original system. Check for the latest XML file in SAP Note 1000009

• Specifically for SAP BW upgrade, execute task list SAP_BW_BEFORE_UPGRADE via transaction STC01

DMO Migration to SAP HANA – Export/Import

Following should be considered while performing a DMO migration:

• Migration is done together with system upgrade and/or Unicode migration• Provide HANA connection details and logon information• Install HANA DB client• BW system – provide parameters for cleanup tasks• Provide number of R3load processes; note it an be changed dynamically

later on• It is now possible to move the ABAP CI to the HANA appliance to

dramatically increase the overall performance due to massive parallelization.

DMO Migration to SAP HANA – Downtime Optimization

By integration of SLT technology (SAP LT Replication Server, part of DMIS 2011 Add-On), selected large application tables can be migrated during DMO uptime processing, therefore decreasing system downtime.

Specific considerations compared to standard DMO:• Customer has to register migration project with SAP to receive support• DMIS 2011 (SLT 2.0) Add-On has to be selected in MOPZ while generating

stack.xml file• Target SAP release must be based on Netweaver 7.40 SPS 5 or higher• Text file has to be created containing list of migrated application tables.

Tables can’t be of pool/cluster type, have /BI in the name or belong to SAP_BASIS, SAP_GWFND or SAP_UI components

• Unicode conversion is not yet supported

DMO Migration to SAP HANA – Post Processing

For SAP Business Suite systems, no additional steps apart from standard post-upgrade activities are required.

For SAP BW systems:• Implement latest OSS Notes for report RSDU_TABLE_CONSISTENCY, then

run it to identify problems which may occur in migrated system• Run report RS_BW_POST_MIGRATION• Perform repair of inconsistent PSA tables, check consistency for all

external HANA views, correct missing views for selected master data• Execute task list SAP_BW_AFTER_MIGRATION via transaction STC01 • Review OSS Note 1846493 “Important SAP Notes for SAP BW powered by

HANA” prior to production use of migrated system.

Classical vs DMO Migration – Which one for me?

Classical vs DMO Migration – Decision Tree

Classical vs DMO Migration – Scenario 1

Classical vs DMO Migration – Scenario 2

Classical vs DMO Migration – General Best Practices

Always use the latest tool versions

Test Key Performance Indicators beforehand:• Network Bandwidth• Source DB read performance• Perform SAP HANA performance check with Hardware configuration

check tool• Test Disk I/O performance of Source DB and Primary Application server

After migration, analyze runtimes, identify bottlenecks + optimization options• R3load jobs• Adapt table splitting• Consider to adapt table comparision with SUM

Plan several test runs to optimize procedure, performance and downtimes

Additional Best Practices for Classical Migration

For Performance Optimization:• Consider parallel export/import• Consider to use additional app servers for export• Consider to use SAP HANA standby node for import - also option for DMO

Refer to Best Practice Guide for classical migration of SAP Netweaver AS ABAP to SAP HANA:

• Further information on involved tools• Provides further best practices about performance, table splitting, package

splitting etc…• Includes examples for optimizing runtime• Target group: Migration experts• Part of SAP HANA system copy guide (see Appendix)

Classical vs DMO Migration – Minimizing Downtime

Classical Migrations:• Combine Unicode Conversion & DB migration• For upgrade – use downtime minized capabilities of SUM

DMO:• Use Downtime-minimized DMO via migration of big tables during uptime• Available on request – not available for SAP BW

Near Zero Downtime:• In case of special requirements • Clones source system + performs changes on cloned systems• Intermediate changes in source system handled with record & replay

technique (Available as of SUM 1.0 SP7)

SAP BW - Automated delta-queue cloning:• Created parallel shadow system (using BW Post Copy Automation – PCA) +

performs changes on shadow system• Intermediate changes handled with delta queues

Migrating Business Suite to SAP HANA – Q&A

Appendix

SAP DVMhttp://service.sap.com/dvm

Custom ABAP code migration to SAP HANAhttp://service.sap.com/dvm

KPI MeasurementsSource DB – SAP Note 1875778SAP HANA performance check – SAP Note 1943937

SAP HANA System Copy Guidehttp://scn.sap.com/docs/DOC-47657

Downtime Minimized capabilities of SUMSAP Note 1678565

SAP HANA System Copy Guidehttp://scn.sap.com/docs/DOC-32414

End-to-End Implementation Roadmap for SAP Netweaver AShttp://help.sap.com/nw74/#section7

Appendix

SAP NotesSAP Note 1799545 DMO for SAP NetWeaver BW systemsSAP Note 1875197 DMO SAP Business Suite systemsSAP Note 1813548 Database Migration Option  DMO DocumentationUse the quicklink /sltoolset in SAP Service Marketplace, choose "SL Toolset 1.0",scroll down to the table of documentation, open section "system maintenance"SAP First Guidance - Migration BW on HANA using the DMO option in SUM Blogs on DMOMigration to SAP HANA: Overview Video of Database Migration Option DMODMO: introducing the new UIDMO: technical backgroundDMO: comparing pipe and file mode for R3load Blogs on related topicsMigration of SAP Systems to SAP HANAA better way to migrate your SAP NetWeaver BW from any database to SAP HANADecision Matrix to Choose Best Migration Option of ABAP Systems to SAP HANASoftware Update Manager (SUM): introducing the tool for software maintenanceBest Practice Guide - Classical Migration of SAP NetWeaver AS ABAP to SAP HANAhttp://wiki.scn.sap.com/wiki/display/SLGB/Strategy+beyond+SAP+Business+Suite+7+Innovations+2011

SAP Education offeringHA250: "Migration to SAP HANA using DMO" - two days classroom training

Protera Technologies – Binoy James, Application Delivery Contact Info:

B.james@protera.biz 630-303-7919

Protera Technologies – Sam Arra, Business Development

Contact Info: sam@protera.biz 877-707-7683 @ProteraTech

THANK YOU FOR PARTICIPATING

For ongoing education on this area of focus,visit ASUG.com