Following Jerry Janda blog tutorial, I am an ASUG Volunteer & an SAP Mentor (introducing myself).

This is a session from last week.  Fortunately I was able to attend it live.

You can access replay here

Source: SAP

End to end overview

General introduction, tools essential, aspects to consider

Source: SAP

Things in future are subject to change

Source: SAP

What kinds of system capable to be converted

Checks

Software update manager (SUM)

Source: SAP

3 ways towards S/4HANA

System conversion is one of 3 scenarios

Conversion, 1 SAP ERP to S/4HANA (on premise) – 1 to 1

New implementation – greenfield, selective data transition

Blog explaining 3 scenarios is here

Source: SAP

S/4HANA “family”

Left SAP ECC

On right you see S/4HANA

Conversion targets S/4HANA on-premise

1503/1605 are not valid targets

Numbers give hint on year of release

1909 SP00 is initial shipments and 2 feature pack stacks, then SP’s, in maintenance lines

Conversion – target latest stable releases

Source: SAP

Overview of requirements

Any database, for 1 step conversion

Source system has to be on Unicode; should be no surprise, NetWeaver 740 Unicode

ABAP single stack, no dual stacks allowed

If already on HANA, need to move to HANA 2.0, as SUM tool requires this

SUM tool does not upgrade database for you

Target system – 1909, ABAP platform, S/4HANA not based on NetWeaver, based on ABAP, now name ABAP platform

Different operating system coverage – App Server level – host, see link to SAP Note

Source: SAP

Left hand side, system requirements

Maintenance planner, SI checks

Simplification list – some things have changed, written in simplification list, foundation for checks

Realization – conversion happens with SUM

Source: SAP

Simplification List that collects all that has changed, replaced, removed

S/4HANA is not successor of ERP, new product line

Differences are in simplification list

Decisions, in “old world” similar features, target architecture

Check simplification list outlines impact of changes

Checks based on single source of truth

Catalog, browser page to open, filter

Also available for PDF, plus blogs to support you

Prominent examples – BP approach, CVI, mandatory in source system; SUM checks this as well

600 simplification items; not all are relevant for your system

Simplification item check, implemented on your source system, what is relevant

Start early, consider Fiori

Source: SAP

Consider Fiori – new User Interface experience

Target architecture

SAP GUI is still supported, with some exceptions, as some transactions not available.

Recommendations on Fiori, based on usage in system

Can switch to all Fiori apps (big bang) or do a pilot approach

FES – embedded or separate

See blog for recommendations (embedded deployment)

Important for planning

Preparation – based on Simplification List

Source: SAP

SAP Readiness check, version 2.0, improved

Incremental improvements

Umbrella covering other checks

Partially checking what maintenance planner, SI check, and custom code check

Important first overview for your project; recommend to run early

Notes in source system, create files, upload to browser page and receive analysis

Can repeat this later on

Source: SAP

Fiori interface with different areas, recommended Fiori apps

New – activities for simplification items

Source: SAP

Maintenance planner – successor of maintenance optimizer

Browser based tool, access to system data

Check on component level

Checks source system, components, add-ons, business functions

Can run early; obtain an understanding of the add-ons

Add-ons may be an influencing factor for project, especially those from partners

If check is green, then do planning

Define target level, “recipe” required by SUM

For those add-ons to be uninstall – can tell planner for that

Check 3rd party add-ons in time, to clarify, whether 3rd party can run on target level

MP – planning overview, specify source system, specify target version, and select front end server, then check is executed

Source: SAP

SI checks – execute in source system – e.g. whether BP approach implemented, shipped with TCI notes to ease process

Start early; determine which items are relevant

Some checks concerning components

Need to clear open issues as SUM will run same check and if SUM detects issue, it will stop as requirements are not fulfilled

Source: SAP

Custom code prep – S/4HANA is simplified on database, repository level

New and old objects are gone

ACDOCA – universal journal

Old tables are deprecated

Custom code scoping, S/4HANA checks

After conversion, do functional adaptation

Custom code scoping – which code to be adapted

Run statistics on usage of custom code; run over 1 year, to see what is used at all – tools listed

New Fiori app (green) – allows efficient custom code analysis

Performance tuning is a good idea

Source: SAP

3 possibilities, 3 columns

First possibility – separate ATC check, small install (can use CAL) – target source system, get the findings, SI items

2nd column – Fiori app to simplify – available – use converted sandbox system, enable app, 1809 (based on 753)

3rd column – run Fiori app in cloud, requires license for SCP

SolMan is not used

Source: SAP

Overview – SAP ECC, app level – readiness check

SI Checks

Maintenance planner checks component, business function level, add-ons

SUM – app server, OS, executes the conversion

Z objects – custom code, checks

Overview of checks

Execution – SUM and Data Conversion

Source: SAP

Data conversion – left hand side, business suite, on right in blue, simplified view on tables in S/4HANA

Simplify to speed up applications, impact on conversion

Tables have to be moved to new tables, universal journals – e.g. MATDOC

Happens during technical conversion

Conversion will copy from old to new table; old tables still there

Concept of obsolete data handling – after system converted to S/4HANA – which tables can be deleted – report start, and will tell you which can be deleted (see SAP Note)

Source: SAP

Tasks for SUM tool

Will partially do the conversion to new data model

App server – start update manager (if on HANA)

If not on HANA – 2 database hosts

Source: SAP

What is required before start SUM

Run maintenance planner – have to be green

SI Checks – executed – solve all issues

Then SUM will run

Source: SAP

DMO with system move – migration case, scenario only applies if system not on HANA, moving hosts

Source: SAP

Blocks of technical conversion

Green – up time, create shadow repository

Technical sum – migration, conversion (partial by SUM and partial afterwards) – FIN migration finishes after in IMG

Discuss down times – be specific – which down time. SUM downtime is only part

Source: SAP

Start with sandbox, iterate, get familiar, refine project plan

Development, adaptation, transport

Dual maintenance

Consider dress rehearsal

Timing is important – SUM is issued about every 4 months

Not switch in critical phase

Source: SAP

Need time to clear SI items

Workshops, training

Adapt authorizations

Time to check 3rd party add on

Consider archiving

Plan project with stakeholders

2-3 conversion runs in sandbox

____________________________

So if you are attending a future SAP TechEd (Barcelona, Bangalore), I hope this helps you