Insights and lessons learned on moving to S/4HANA

Insights and lessons learned on moving to S/4HANA

Insights and lessons learned while converting to S/4HANA


Some practicals : Voting app

It is still a long time to 2025 2027.



It is still a long time to 2025 2027

End of compatibility scope support

End of mainstream maintenance business suite 7.0

Guaranteed support of S/4HANA

End of optional extended mainstream maintenance business suite 7.0

2025 2027 2030 2040


It is still a long time to 2025 2027

In February 4, 2020, SAP has announced an innovation commitment for SAP S/4HANA until the end of 2040. This means that until 2040, there will be always at least one release of SAP S/4HANA in maintenance.

At the same time, SAP will provide mainstream maintenance for SAP Business Suite 7 core applications until end of 2027. This offboarding phase will be followed by optional extended maintenance until end of 2030.

SAP will provide mainstream maintenance until the end of 2027 for SAP Business Suite 7 core applications, which are also core applications of SAP Business All-in-One, including:

• SAP ERP 6.0,

• SAP Customer Relationship Management 7.0,

• SAP Supply Chain Management 7.0,

• SAP Supplier Relationship Management 7.0 applications,

• SAP Business Suite powered by SAP HANA.

After years of customization I believe my system is not convertible.



After years of customization I believe my system is not convertible.

Is it technically possible?

• From a technical perspective usually only unsupported industry solutions are really technically preventing a conversion

• A lot of custom code will result in a lot of work, but it doesn’t imply it is impossible

Is it smart to convert your ECC box?

• If you developed Z-processes you will not grasp the benefits of S/4HANA after a conversion• Where do you need to land and what is the best way to get there?

• Are you aware of area’s to improve vs area’s to consolidate?

• What are the good things you want to take along?• Standard in your system doesn’t mean necessarily SAP standard (small things making big differences)…


S/4HANA Transformation option that suits you the best

Brownfield

Smart Brownfield

Hybrid

Greenfield

Time

Co

st

Upgrade live systems & reuse existing elements

Upgrade live systems & new setup with selective data transfer

New system with existing & new setup with selective data transfer

New system with new setup

Process transformation

New Finance Concepts

Facilitate M&A Activities

Reduce system complexity

Generate innovation

Hardware change

Reasons to go for Brownfield or Greenfield:


S/4HANA Transformation option Architectures

Brownfield Smart Brownfield Hybrid Greenfield

So

urc

eTa

rget

ERP 6.0 EHP7

S/4HANA EM

SAP HANA DB

Any DB

Tran

sfo

rmat

ion

S/4HANA EM

SAP HANA DB

SUM&DMO

Pre-requisites

Custom Code & Simplifications

ERP 6.0 EHP7

Any DB

S/4HANA EM

SAP HANA DB

S/4HANA EM

SAP HANA DB

SUM&DMO

Custom Code & Simplifications

Sel

ecti

ve d

ata

tran

sfer

New

Set

up

ERP X

Any DB

ERP Y

Any DB

S/4HANA EM

SAP HANA DB

S/4HANA EM

SAP HANA DB

Sel

ecti

ve d

ata

tran

sfer

Sel

ecti

ve d

ata

tran

sfer

New system with existing setup

New setup

ERP X

Any DB

S/4HANA EM

SAP HANA DB

S/4HANA EM

SAP HANA DB

Dat

a co

nve

rsio

n New system

New setup

The road to SAP S/4HANAGreenfield, Brownfield or Hybrid?

Copyright © 2018 Accenture. All rights reserved.

Chose Greenfield Chose Brownfield

Ability to change• Top-down decision making capabilities exist

• Ability to integrate an acquisition in parallel to Greenfield is given

2

External factors• Significant changes are required due to M&A activities

• Significant changes in regulatory environment / customer industries

/ market shifts require client to transform significantly

3

Business Case

• A solid business case for the implementation exists

• Benefits can be clearly attributed to individual concurrent projects

• Speed is not a key requirement for the approach

4

Internal drivers

• A burning platform mandates an immediate and fundamental change

• Current systems doesn’t allow for required changes

• Past choices limit scope of future changes

• Significant corporate restructuring is on the agenda

• Global business process governance is established

• The organization can handle a significant, global amount of change

1

Hybrid Greenfield

Strongly Agree Strongly Disagree

?

?

?

?

?

?

?

?

?

?

?

?

?


Moving to S/4HANA is a technical project.



Moving to S/4HANA is a technical project

Well actually, it could be or at least part of it could be => it is a clear choice you can make....BUT

If you consider doing a technical migration don’t forget the following key points:

• Authorisations

• The better you test the smoother you will go live

• Special attention to interfaces and side applications

• Get familiar with embedded analytics and CDS views

• Get a functional understanding of what Fiori apps can do

Being successful starts with a methodology that takes all aspects of a project into account: Alphabet X


Alphabet X MethodologyOverviewOur methodology is based on 4 valuable pillars, used as basis for a tailored project approach

Accelerators

• SAP Activate accelerators

• Expertum internal & customer

training (material)

• Expertum authorizations approach

• Expertum books on the topic

SAP Activate

• SAP’s current S/4Hana

methodology

• Fast Business driven set-up

• Based on SAP’s

accumulated experience

Toolset

• Enable automation

• Pre-defined

• Better quality and control

Project Experience

• Leverage previous client

projects

• Tailor to cultural country

specifics/differences

Methodology

Prepare Explore Realize Deploy

SAP Activate

Tailor solution in short time-boxed

sprints

Cutover and begin productive phase

Verify solution scenarios meet business needs, capture

backlog

Jump start project with ready-to-run

best practices

There are 4 major project phases in the SAP Activate methodologyEach Phase defines major milestones, tasks and deliverables



SAP Activate - Execution Tracks

On top of the execution track, we define

▪ Project management

▪ Change Management

The high-level approach is translated into 5 execution tracks that will perform specific tasks in each phase

Each execution track represents a workstreamfocusing on specific topics

The tasks to be performed in each execution track is different in each project phase (see next slides)

Testing

Training

Authorizations

Data Manage

ment

Application design &

configuration• Functional and technical Team to define solution,

customizing, define and execute developments, architecture* and interfaces

* Architecture can be defined as a separate execution track if needed

• Master data and transactional data approach, cleansing and migration

• Security and authorization definition and execution

• Training planning, documentation and execution for key users and endd-users

• Planning, preparing and execution of User Acceptance test scenarios, including functional and E2E tests

Execution Tracks – Explore tasksDuring this important phase, the design of the solution is prepared that will be the foundation for the entire project ad solution build

Project Management is preparing the detailed planning for the key next steps of the project execution

Project & Change Management

• Activate solution (including UX)• Fit-to-standard Analysis / Design• Gap validation• Design review: workflow, reports, interfaces, conversions, enhancements and forms (WRICEF)• Technical Architecture and infrastructure definition

Application design&

configuration

Testing

Training

• Detailed project planning• Change Management planning• Execution follow- up and monitoring

Explore

Data Management

• Data migration strategy & design

Authorizations• Security Design• Fiori Authorizations concept• Definition of roles


EXAMPLE

I will move to S/4HANA once my users ask for it.




Based on experience we see new possibilities being opened

User Experience Functionality and Innovation



Without additional effort, S/4HANA unlocks additional capabilities for existing functionalities

Examples

• Rebates and commissions with condition contract management• Flexible workflow with mobile approval app

• Embedded analytics and online operational reports

• Fiori app’s in all functional area’s• API business hub: standard API’s compared to old school integration possibilities


Customer Example: Plant Maintenance

Out of the box Fiori app’s for maintenance scheduling covering gap requirements


I will move to S/4HANA once my users ask for it

But let’s also talk about innovations relevant for your specific context

• S/4HANA Inspiration Sessions and Workshops to understand the value of S/4HANA▪ Topical content workshops with the different Lines of Business

▪ Show & Tell key SAP innovations, led by the Expertum S/4HANA experts

• Test Migration with Proof of Concept on set of topics


Design Functional Innovations (Example)


Inspired by SAP Tools

Process Discovery for SAP S/4HANA Transformation: Spotlight by SAP

• Insights into current business process performance, system usage, and industry benchmarks

• Recommendations for SAP S/4HANA functionalities, SAP Fiori apps and automation for six lines of business and across end-to-end processes

• No additional charge for customers on SAP Maintenance


Inspired by SAP Tools

Transformation Navigator

• Based on▪ The current landscape and usage information

▪ Future business/solution needs

▪ IT Strategy (on premise/cloud)

• Overview of▪ Recommended products and capabilities

▪ Value drivers & related business value

▪ Required Licenses

▪ Relevant tools, etc.

Cloud is not an option for me.



Cloud is not an option for me.

Historical concerns about the cloud:

• Availability

• Connectivity

• Security • Functionality

But the world is changing rapidly…

RISE with SAP


Cloud is not an option for me.RISE with SAP: 1 SAP offering with various components

I don’t plan to move shortly so I don't bother now.



I don’t plan to move shortly so I don't bother now.

Strategic• C-level buy in• Roadmap definition• Migration approach

Tactical• Management buy in• Pre-study • Sandbox conversion• Program definition

Operation• Functional preparations• Technical preparations

Preparation is key on all levels.

Our teams can assist you on the different levels.

35


36


BOOK LAUNCH

09/1206:00 PM

Van der Valk Hotel Brussels Airport

www.Expertum.net/event

Insights and lessons learned on moving to S/4HANA

Documents

Transcript of Insights and lessons learned on moving to S/4HANA