22
10(ish) Golden Rules for a S/4HANA Migration John Appleby GM, Bluefin Solutions Inc.

10 Golden Rules for S/4 HANA Migrations

Embed Size (px)

Citation preview

Page 1: 10 Golden Rules for S/4 HANA Migrations

10(ish) Golden Rules for aS/4HANA MigrationJohn Appleby

GM, Bluefin Solutions Inc.

Page 2: 10 Golden Rules for S/4 HANA Migrations

2

• S/4HANA Introduction Differences between Suite on HANA and S/4HANA Deployment Options

• Preparing for your S/4HANA Migration Building an integrated schedule Sandboxing and prototypying Housekeeping & Solution Manager Change Management & Test Management Sizing, Architecture, HA, DR, Backup & Recovery

What you will learn today

Page 3: 10 Golden Rules for S/4 HANA Migrations

S/4HANA Introduction

Page 4: 10 Golden Rules for S/4 HANA Migrations

4

• The next version of SAP Business Suite

• New SKU and Code Fork Only supported with the SAP HANA DB

• S/4HANA themes: Renewed interface with Fiori UX Simplified structure with SAP HANA Cloud deployment first

What is S/4HANA

Page 5: 10 Golden Rules for S/4 HANA Migrations

5

S/4HANA Deployment Options

Public Cloud• Shared HANA multi-

tenant DB• HANA Cloud Platform

Extensions• Quarterly Release

Schedule• 100% Managed by SAP• Automatic Updates

Managed Cloud• Managed HANA DB and

network• HANA Cloud Platform

Extensions• ABAP Customization• Quarterly Release

Schedule• 100% Managed by SAP• Scheduled Updates

On-Premises• On-Premises or Hosted• ABAP Customization• Yearly Release Schedule• Managed by

Customer/Partner• Update schedule

defined by customer

Page 8: 10 Golden Rules for S/4 HANA Migrations

Planning for your migration

Page 9: 10 Golden Rules for S/4 HANA Migrations

9

• Most Customers look for a technical migration first To S/4HANA or Suite on HANA

• Out of Scope: HANA Live / Analytics Simple Finance (i.e. S/4HANA)

• Suite on HANA is the stepping stone to S/4HANA Then perform code changes, activate S/4HANA extensions

• S/4HANA direct migration expected late 2015 N.B. Migrating to SoH is a great first step to S/4HANA!

1) Define Project Scope

Page 10: 10 Golden Rules for S/4 HANA Migrations

10

• Cover all Technical Migration activities Upgrade to ECC 6.0 EhP7 (if necessary) Unicode Conversion (if necessary) HANA Migration

• Restitution “As fast, faster, or much faster” ABAP code optimization (some things will be slower)

2 Define Technical Scope

ECC EHP 7 UpgradeUnicode

ECC to HANA MIgration

New GLSFIN

S/4HANA

ECC on HANA

Page 11: 10 Golden Rules for S/4 HANA Migrations

11

• Build one Integrated Schedule Weekly goals

• Include all teams above And partners! Assign ownership

• Agree schedule with all teams Takes time (1-2 weeks) Aligns with project prep phase

3) Build the Integrated Schedule

Page 12: 10 Golden Rules for S/4 HANA Migrations

12

4) Define Stakeholders & Comms Plan

Functional

PMOBasis

ReleaseManagement

BW/Analytics

Integration

ChangeManagement

Test Management

Business Owners

Sponsors

ABAP

Infrastructure

EnterpriseSecurity

SAPSecurity

Page 13: 10 Golden Rules for S/4 HANA Migrations

13

• Build first sandbox immediately Recent production copy Production sized! Include integration environment (if possible)

• Build it for real! Full migration with documentation All functional work

• Include test cycle Unit testing Integration testing Performance/Stress testing

5) Sandbox & Prototype

Page 14: 10 Golden Rules for S/4 HANA Migrations

14

• Business Suite systems often venerable Housekeeping is not always done A clean system is #1 way to de-risk your project!

• DRAM is expensive! Basis tables alone cost ~150GB of DRAM below Multiplied by N production sized systems! TB!

• Run HANA sizing guide SAP Note 1736976 (BW) SAP Note 1793345 (ECC) Look for Big Basis Tables SAP Note 706478

• Include in Schedule

6) Focus on Housekeeping

Page 15: 10 Golden Rules for S/4 HANA Migrations

15

• Disk Databases are inexpensive Data Reduction rarely considered

• Top 100 tables usually 90% of DB space Run HANA sizing guide SAP Note 1736976 (BW) SAP Note 1793345 (ECC)

• Analyze Top 100 tables Create action plan PSA, DSO Change Log deletion (BW) IDOC, Old Functional Areas, Data Archiving (ECC)

• Remember every GB saved is 10-20GB stored!

7) Data Reduction Program

Page 16: 10 Golden Rules for S/4 HANA Migrations

• Test Management is critical Some customers have a mature strategy Some do not

• Revise your test management strategy Test Automation Test Coverage Test Prioritization

• Reduce your time to complete testing! How long does it take to complete regression test?

8) Change & Test Management

Page 17: 10 Golden Rules for S/4 HANA Migrations

17

• Make sure you are on the latest latest SP! http://scn.sap.com/community/abap/custom-code-management

• Custom Code Management Tools (CCMT) Custom Code Management Cockpit (CDMC) Usage & Procedure Logging (UPL) CloneFinder

• Use these tools in combination with: Testing Process prioritization by business users

9) Solution Manager is your friend!

TestStrategy

Priority

Testing

Clones CDMCUPL

Page 18: 10 Golden Rules for S/4 HANA Migrations

• Complete Sizing Sandbox system is a great way to size accurately Sizing tools are good alternative

• Consider technical architecture HANA supports database multi-tenancy

10) Architect for S/4HANA

Page 19: 10 Golden Rules for S/4 HANA Migrations

• HANA supports system replication Active/Passive Synchronous (HA) Multi-tier Asynchronous (DR) SUSE Linux supports automated host failover

• Very low cost to implement As compares to e.g. RAC Most HANA systems are HA

• Even lower cost options Share QA & DR

11) Architect for HA/DR

Page 20: 10 Golden Rules for S/4 HANA Migrations

• HANA Advisory Council https://blogs.saphana.com/2015/01/12/now-time-plug-sap-hana-customer-communities

• HANA Ambassador Program North America only Ask your SAP Account Executive

• Max Attention / Active Embedded Various services provided Some useful (going live services, custom code)

• Active Global Support Going live services

12) Get Support from SAP

Page 21: 10 Golden Rules for S/4 HANA Migrations

• Cutover plan touches many teams But most teams build “MY PLAN”

• Build an integrated plan All teams, all activities Number the plan Align the numbers with the cutover doc

• Track forecast and actual Tool doesn’t matter (Project, Excel etc.)

13) Build an integrated cutover plan

Page 22: 10 Golden Rules for S/4 HANA Migrations

John [email protected]@applebyjbluefinsolutions.com/johnappleby