MIGRATION TO S/4HANA What will your story be?€¦ · G3G Migration Migration from ECC 6.0 EHP 5 to...

© Copyright 2019 G3G Limited. All rights reserved

MIGRATION TO S/4HANA – What wi l l your story be?A n d r e w B o r r e s e n - A p r i l 2 0 1 9

#EIMSAPSIG #SIGEIMSAP #AFSUG


Overview of G3G and Aberdare Cables S/4HANA Stories

A Practical guide for conversion to S/4HANA

Introductions and ObjectivesNameAndrew Borresen (CTO @G3G)

• 20 years global SAP experience • Key focus – SAP Architecture and

Roadmap Advisory• G3G is a SAP customer and partner

(running SAP since 2010)

Questions

Speaker Brief Agenda


S/4HANA Migration Options

New Implementation

System Conversion

Landscape Transformation

On-Premise

Cloud

On-Premise

Cloud

On-Premise

S/4HANA

ERP System

Non-SAP System

ERP System

ERP System- Region A -

ERP System- Region B -

ERP System- Region C -

New Implementation

System Conversion

Landscape Transformation

▪ Longer timeline▪ Large investment for existing SAP customer▪ Faster adoption of innovations and best

practices (move away from customisation)▪ Opportunity to clean data

▪ Quicker migration realisation▪ Suitable for most customers who have a

single SAP instance▪ Transaction history is retained ▪ Minimal Change Management▪ Custom remediation effort could be high▪ Slower adoption of new innovations


G3G MigrationMigration from ECC 6.0 EHP 5 to S/4HANA Finance 1503Go-live: January 2016 (6 months)

Drivers▪ Become early adoption SAP Partner▪ Build confidence in HANA product▪ More efficient planning process (BPC embedded)

Takeaways▪ Low risk approach for new software is possible▪ Suitable for multiple short innovation cycles

EHP5

EHP7 on SQL

EHP7 on HANA (SoH)

S/4HANA Finance 1503

Continuous Improvement

1

2

3

4

5


Aberdare Cables MigrationConversion from ECC 6.0 EHP 7 to S/4 HANA 1709 Estimated Go-live: Nov 2019

Carve out

DB6/Linux SuseECC 6.0 EHP5No Unicode

ECC 6.0 EHP7 (SOH)Unicode

1709 HANA 2.0

Continuous Improvement

1

2

3

4

5

Infrastructure changeHANA custom code

adaptations

Platform change

Unicode change

Software Upgrade

Mandatory features

Configuration of optional features

More Fiori apps

Best Practices


Methodology Overview

Start with POC rehearsal (s)▪ Determine S/4HANA conversion compatibility and

approach, determine likely effort and ‘play book’ for production landscape.

▪ Mandatory functional adaptations only (Technical conversion)

▪ Iterate until success achieved

Migration approach decision point:▪ Conversion▪ New implementation with migration (S/4 Best

Practice Solution)

POC rehearsal(s) Technical Conversion (Production Landscape) Continuous Improvement


Prepare PhaseReadiness Check

▪ Which adds on are supported/conflicting?

▪ Which Business Functions are supported/conflicting?

▪ What Custom code needs to be checked / changed?

▪ What data needs to be migrated?

▪ What functional changes are mandatory?

▪ Simplification items (Principle of 1)

▪ What infrastructure sizing requirements will I have?

▪ Which Fiori apps are recommended?


Prepare PhaseLogistics

▪ Business Partner approach

▪ Customer/Vendor integration(CVI)

▪ MRP areas (Principle of 1)

▪ MATNR extension


Prepare Phase

GL to Sub Ledger

Ledger Comparison

Inventory to GL

Asset Period Closed

New Assets Activate

Finance

▪ Financial configuration and data consistency checks

▪ Reconciliation

▪ Period-end closing activities

▪ Document posting data (‘Before’ recon reports)


Realization PhaseTechnical Conversion with SUM (DMO)

▪ Complete uptime phases

▪ Execute full down time

▪ Post activities


Realization PhaseFinance Conversion

▪ Customizing migration

▪ Credit management, General Ledger, Material Ledger, House Banks

▪ Finance data migration

▪ Universal Journal

Analyse errors, clean in production, perform 2nd iteration of conversion POC


Realization PhasePost Conversion Activities

▪ Output Management

▪ PP/DS

▪ SAP Fiori activation (embedded versus hub)

▪ SAP Fiori Launchpad & application configuration

▪ Expose system to internet


Summary

▪ Establish a low risk plan by executing a POC

▪ Establish technical feasibility of conversion (approach decision point)

▪ Identify and resolve issues

▪ Establish well documented repeatable process - ‘Play Book’

▪ Identify change management considerations

▪ Reduce time to value

▪ Technical Conversion

▪ Mandatory functional adaptations

▪ Continuous improvement later (code optimization and functional enhancement)

Write your S/4 Story now…


UK Head OfficeQuatro HouseFrimley RoadCamberleySurrey GU16 7ER

+44 (0)370 620 1111

South Africa Head OfficeBuilding 1Ashlea Gardens Office ParkCnr. Garstfontein Rdand Matroosberg StreetPretoria 0081

+27 (0)12 947 9620

UK Daresbury OfficeTechspace TwoSci TechKeckwick LaneDaresbury WA4 4FS

+44 (0)370 620 1112

company/g3g

@G3Gnews

www.g3g.com

Follow us

Contact us

+27 (0)60 757 8635

Andrew. [email protected]

Andrew BorresenCTO

MIGRATION TO S/4HANA What will your story be?€¦ · G3G Migration Migration from ECC 6.0 EHP 5 to...

Documents

Transcript of MIGRATION TO S/4HANA What will your story be?€¦ · G3G Migration Migration from ECC 6.0 EHP 5 to...