Benchmarking The Business Case For Sap S/4Hana: Pierce Owen Rizal Ahmed
Benchmarking The Business Case For Sap S/4Hana: Pierce Owen Rizal Ahmed
Benchmarking The Business Case For Sap S/4Hana: Pierce Owen Rizal Ahmed
Benchmarking the
Business Case for
SAP S/4HANA
Pierce Owen
Rizal Ahmed
August 2019
Research Partner
BENCHMARKING THE BUSINESS CASE
FOR SAP S/4HANA
Research Partner
The best-run businesses make the world run better. With courage,
perseverance, and breakthrough technology, SAP customers tackle some of the
world’s biggest challenges. Find out how they work with SAP to make a lasting
difference — and learn about the technology solutions that fuel their innovation.
Contents
Executive Summary ............................................................................................................. 1
Competitive Maturity Assessment ....................................................................... 1
Required Actions ............................................................................................................. 2
Chapter One: SAP S/4HANA Overview ................................................................... 3
What Do Leaders Do Differently with SAP S/4HANA? ........................... 6
How Are Industry Average Respondents and Laggards Planning
to Move Forward? ........................................................................................................... 7
What Holds Back Laggards? ................................................................................... 8
Key Takeaways .................................................................................................................. 9
Chapter Two: How Do Customers Approach the SAP S/4HANA
Business Case? ..................................................................................................................... 10
Top Requirements for Building the SAP S/4HANA Business
Case........................................................................................................................................ 10
How Will Respondents Use Technology to Support Their
Strategies and Accelerate Growth? ...................................................................13
Key Takeaways .................................................................................................................13
Chapter Three: Required Actions ..............................................................................15
Leader Steps to Success ............................................................................................15
Industry Average Steps to Success ................................................................... 16
Laggard Steps to Success ....................................................................................... 16
Key Takeaways ................................................................................................................ 17
Methodology ......................................................................................................................... 19
Appendix A: The DARTTM Methodology ............................................................... 20
Executive Summary
SAP S/4HANA is unlike any previous release of SAP ERP and must not be
looked at as a typical upgrade project. SAP S/4HANA offers organizations the
potential to deliver significant business value, but it also brings significant
deployment decisions and technical migration challenges. When building the The challenge we’re
business case for SAP S/4HANA, SAP customers should consider a variety of
seeing with customers
important factors and potential impacts on digital transformation, business
in terms of building the
processes, and technical landscapes.
business case is that
In August 2019, SAPinsider surveyed 338 members of our audience to sometimes they
understand the progress SAP customers have made in building the business struggle to fully
case for SAP S/4HANA. We found that the majority (77%) have at least started quantify the cost of
fact-finding and trying to understand SAP S/4HANA to begin building their inaction.
business case, while 17% have already succeeded in completing the business
case. This report takes an in-depth look at the data behind this finding,
including how and why companies undertake such projects, the outcomes ~ Amr El Meleegy,
they’ve seen thus far, and the actions they can take to ensure successful Value Advisory and
results going forward. Customer Success, SAP
• Leaders: These early adopters have already completed their business Laggards Leaders
cases. This group represents 17% of the survey respondents. 23% 17%
The survey results show that leaders in building the SAP S/4HANA business
case share several common characteristics:
• Form a committee with the CIO and high-level representatives from ~ Director,
International Agricultural
every major functional area or LoB (such as finance, operations, supply
Commodities Company
chain management, production, and HR). SAP S/4HANA requires an
immense investment, but it can also hold a massive payoff. To unlock
that payoff, every major LoB must not only identify siloed areas of
improvement but also exchange ideas and find synergies.
• Identify all processes that the SAP S/4HANA migration could affect.
This migration provides an opportunity to reinvent, restart, and
reengineer almost every business process according to best practices.
SAP customers will have to go through their systems and pick out each
process that can leverage SAP S/4HANA.
Chapter One:
SAP S/4HANA Overview
SAP customers must start building or at least assessing the business case for
SAP S/4HANA sooner rather than later. If they do not migrate soon, they will
Some existing SAP
run up against the deadline for maintenance support for SAP ERP Central
customers might be
Component (SAP ECC). At that point, they will either lose support for their ERP
system or have to implement SAP S/4HANA without a fleshed-out plan or
under the impression
business case. Fortunately, 77% of survey respondents have at least started that an SAP S/4HANA
their fact-finding missions to understand SAP S/4HANA (see Figure 1). project follows the same
traditional classical ERP
Figure 1: Organizations’ business case status project approach and
methodology that
34%
involves heavy blue
printing, custom
development, and
waterfall approach. That
20%
17% 17%
approach was
traditionally lengthy
and costly.
4% 5% 4%
~ Amr El Meleegy,
We are not Have not Early fact In the middle We are stuck Modifying Business case Value Advisory and
doing a started yet finding and of doing and having approach or is complete Customer Success, SAP
business case trying to analysis difficulty rejected
understand making the
SAP S/4HANA case
Leaders have examined the different deployment options for SAP S/4HANA
and how they will affect key performance indicators (KPIs) and business
processes such as mergers and acquisitions (M&As) in response to the drivers
for digital transformation and the pressure on their LoBs. This has also led
them to focus more on understanding the potential services and consulting There is widespread
costs and impact and invest earlier in technologies such as business process confusion about the
performance analysis solutions. Much of what the leaders do builds on
business case for SAP
commonalities between the three groups.
S/4HANA. Everyone
Figure 3 illustrates how capabilities build on each other for organizations knows that they have to
trying to build a business case for SAP S/4HANA. go there, but not
everyone is clear about
ROI. They are struggling
Figure 3: Building capabilities for the business case with having to think
about this project in a
completely different
way.
~ Winni Hesel,
SAP Expert and Partner,
Enowa LLC
of maintenance for SAP ECC” (cited by 41% of respondents overall) as the main
drivers for their SAP S/4HANA business cases.
A closer look at the top drivers by respondent group reveals that leaders
respond to business and executive pressure to rethink existing technical
architectures and deployment models (32%), while the industry average group
and laggards focus more on reducing the costs of customized environments From a technical
and older technologies (32% and 31%, respectively) rather than rethinking best standpoint, SAP
practices (see Figure 4). All three groups also responded at a relatively S/4HANA will benefit
significant rate (each greater than 25%) to the growing number of technology me. Product lifecycle
projects and investments that need to be considered and prioritized.
management (PLM)
Figure 4: Business drivers for the SAP S/4HANA business case by tools don’t run as
respondent group quickly as I would like.
That will be vastly
70% improved.
60%
50%
40%
30% ~ Director PLM/Engineering
20% Services, American Food &
10% Beverage Company
0%
Business focus on 2025 end of Business and Growing number Increasing cost of
digital maintenance for executive pressure of technology maintaining highly
transformation SAP ECC to rethink existing projects and customized
technical investments that environments and
architectures and need to be older technology
deployment considered and
models prioritized
examine the different options in detail. Going deeper still, leaders have
learned how SAP S/4HANA will affect specific KPIs and business processes
(such as M&As) in response to their business focus on digital transformation.
As shown in Figure 5, 47% of leaders — versus less than 31% of each of the
other groups — chose learning how SAP S/4HANA will affect specific
business processes and KPIs and understanding how SAP S/4HANA can SAP S/4HANA delivers
support current and future organizational change (such as M&As and
high-performance in-
divestitures) as top strategies.
memory technology.
Figure 5: Top strategies prioritized to address the top drivers of change The columnized SAP
HANA database
includes a certain level
50% of efficiency.
40%
30%
20% ~ Consultant,
10% Pakistani Chemicals
Company
0%
Understand how SAP Learn how SAP Examine deploying SAP Learn how SAP
S/4HANA can support S/4HANA will affect S/4HANA on cloud S/4HANA can
organizational change specific business environments consolidate and simplify
processes and KPIs ERP landscapes
Laggards remain at least one year behind the industry average group with
only 4% currently using business process performance analysis solutions, but
62% expect to do so within two years. Using this type of solution or tool, such
as SAP’s business scenario recommendations for SAP S/4HANA report, often
constitutes the first step in changing how an organization views SAP S/4HANA SAP has plugged many
from a necessary cost to an opportunity for digital transformation with new capabilities into the
measurable business impact and accelerated growth. new platform. This
These findings show that most of the industry average group and the
concept of the
laggards at least have an idea of the first steps they need to take to intelligent enterprise is
develop their business cases for SAP S/4HANA, but they do not yet feel intriguing, but few truly
the urgency to accelerate through these initial steps. Additionally, most understand what it
members of these groups have not yet aligned the rest of their means. Executives are
strategies with the right drivers in a way that will ultimately lead to a turning to IT saying,
successful business case for digital transformation with SAP S/4HANA. please help me connect
the dots, but IT isn’t
What Holds Back Laggards? used to advising on
Many organizations find it difficult to accurately estimate the total cost of an such a thing and
SAP S/4HANA implementation, but in general, it can require millions of dollars. creating the link
More than one third (34%) of laggards find it difficult to justify that cost (see between SAP and
Figure 6). Beyond that, more than a quarter (26%) of laggards find the amount business process
of information out there overwhelming and don’t understand the total
transformation; so, they
business impact or justification for SAP S/4HANA. The only way to develop this
are struggling.
understanding involves in-depth cross-functional internal meetings with
different LoBs and external meetings with partners and consultants because
every customer can leverage the capabilities differently. Again, the business
~ Winni Hesel,
scenario recommendations report provides a decent place to start.
SAP Expert and Partner,
Enowa LLC
Figure 6: Challenges preventing laggards from building a business case for
an SAP S/4HANA implementation
34%
30% 26%
19%
We are having trouble We don’t understand the Too much information We are having trouble
justifying the overall cost business impact of SAP and we’re trying to justifying why we should
and investment S/4HANA organize it all into a be doing this project now
compelling case
An additional 19% does not feel the urgency to build a business case for SAP
S/4HANA. Many of these companies have undergone an ERP implementation
recently or have spent years customizing their ERP systems and related
products and do not want to see those years of work go to waste. In some
cases, it may make sense to wait. In all cases, the potential benefits of SAP
S/4HANA deserve a fair analysis.
Key Takeaways
Based on our research, when it comes to the progress SAP customers have SAP S/4HANA could
made in building their SAP S/4HANA business cases, the following takeaways
have a giant impact, but
are clear:
we are seven years into
• Those that have not yet started building their business case have an SAP Product
already fallen behind. Some customers have good reason for it. Some Lifecycle Management
have cited expectations that SAP will push back the deadline or provide (SAP PLM)
further discounts. No matter the reason, others have moved ahead, and implementation. We’ve
laggards should at least evaluate the potential benefits. gone through a series of
• The business case for SAP S/4HANA requires customers to change from
sprints over that time to
thinking about the project as another ERP upgrade to viewing it as a implement and
catalyst for business process optimization and digital transformation. customize SAP ECC and
SAP customers cannot think about SAP S/4HANA as the latest version of SAP PLM. Migrating to
SAP ECC and expect the price tag to make sense. Only by digging deeper SAP S/4HANA would
into the potential impact of SAP S/4HANA into every LoB will customers mean re-doing much of
find tangible benefits that might help them justify the sticker price. that work.
• All groups say they respond to a business focus on digital
transformation, but leaders chose this as a driver at a higher rate than
~ Director PLM/Engineering
the other groups. Also, only the leaders align their entire strategy around
Services, American Food &
that driver by learning how SAP S/4HANA will affect specific business Beverage Company
processes.
Chapter Two:
How Do Customers Approach the
SAP S/4HANA Business Case?
As suggested above, SAP customers typically approach the challenge of One of the ways we’re
assessing a business case for SAP S/4HANA in one of two ways: accelerating innovative
thinking and
• Develop a delta analysis on traditional functional and technical areas and collaboration between
overall cost as they have done with traditional ERP upgrades in the past IT and the business is
• Start with the assumption that SAP S/4HANA will have a measurable through design
impact on the processes and growth of every LoB as part of a digital thinking workshops. We
transformation start our workshops, not
by focusing on SAP
Although the industry average group and the laggards say they feel the
S/4HANA, but by
pressure to focus their businesses on digital transformation, they have not
engaging them in a
aligned their SAP S/4HANA business case strategies with that driver. Instead
discussion about their
they have tended to view it as a traditional ERP upgrade. Leaders, on the other
hand, bring IT and the LoBs together to reflect and imagine the possibilities of business pain points
a digital transformation based on SAP S/4HANA, and then they carve a path and how to think about
forward to building the business case. new ways to drive the
business processes
The next section dives into how these strategies align with the requirements
within the organization.
survey respondents need to succeed, the progress they have made thus far,
and the technologies in which they intend to invest.
~ Amr El Meleegy,
Top Requirements for Building the SAP S/4HANA Value Advisory and
Business Case Customer Success, SAP
The responses indicated that the vast majority (84%) of SAP customers
recognize the need for a delta analysis on existing business functionality (see
Figure 7). This largely represents the first step in evaluating an ERP system.
~ Director,
International Agricultural
Commodities Company
Delta analysis on existing Understanding of SAP Understanding of Understanding of license
business functionality S/4HANA deployment potential services and costs and impact
scenarios with associated consulting cost and
costs of support and impact
maintenance
Chapter Three:
Required Actions
To help ensure a successful SAP S/4HANA business case, companies need to
start the process now and, critically, bring IT and every LoB together to reflect,
imagine the possible, and carve a path forward that addresses the KPIs and
bottom lines of every LoB. The following actions will help leaders, the industry
average group, and laggards navigate the pitfalls of building a business case
for SAP S/4HANA and maximize the value of this massive investment.
• Follow through, track, and realize the added value. Leaders have
their business cases. They should have the support of every LoB. Now,
go forth and execute. Expand on initial focus areas and document and
track your results and lessons learned. Deliver on the promises and hold
internal and external stakeholders accountable for the results.
• Learn more about how SAP S/4HANA will affect specific business
processes and KPIs. It helps to use that cross-functional executive SAP
S/4HANA business case committee to identify your KPIs. But before
SAP customers even form their committee, they can use the business
scenario recommendations report to identify some digital
transformation opportunities with SAP S/4HANA.
Key Takeaways
Going forward, leaders, industry average organizations, and laggards should
keep the following in mind:
• Now that they have the business case, leaders need to execute and
continue to innovate. Leaders should support the LoBs with the
promises made in the business case and continue to work with the LoB
executives to continuously find tools and technologies that deliver
better results.
• Laggards need to dream bigger and cut loose the technical upgrade
mentality. Many laggards have spent years customizing their ERP
environments or have recently invested in an ERP upgrade. To build
this business case and put themselves in the best position to grow, they
must invest in analyzing the current environment and image future
states and possibilities. They should, at the very least, conduct research
Methodology
In August 2019, SAPinsider examined the issues, intentions, and experiences of
business and technology professionals related to their plans to develop a
business case for SAP S/4HANA. Our survey generated 338 responses.
• The main business and technology drivers that influenced their plans
for their SAP S/4HANA business case
• Job title: The job titles of the survey respondents included CXO (3%),
VPs and directors (16%), managers (27%), consultants (17%), architects
(22%), project managers (12%), and analysts (18%).
Appendix A:
The DARTTM Methodology
SAPinsider has rewritten the rules of research to provide actionable
deliverables from its fact-based approach. The DART methodology serves as
the very foundation on which SAPinsider educates end users to act, creates
market awareness, drives demand, empowers sales forces, and validates
return on investments. It’s no wonder that organizations worldwide turn to
SAPinsider for research with results.
Drivers: These are macro-level events that are affecting an organization. They
can be both external and internal and require the implementation of strategic
plans, people, processes, and systems.
Actions: These are strategies that companies can implement to address the
effects of drivers on the business. These are the integration of people,
processes, and technology. These should be business-based actions first, but
they should fully leverage technology-enabled solutions to be relevant for our
focus.