Moving to SAP S/4HANA

Moving to SAP S/4HANA
+ SAP’s Future Direction
28 May 2020Andrew Harding 1

WHAT’S NEW IN
S/4HANA
A brief summary of some of the major changes that come with S/4HANA.
28 May 2020 Andrew Harding - 2 -

SAP EASYACCESS ➔ SAP FIORI
Transaction
codes
Menu
Path
Transactions
Tile
Groups
SAP EasyAccess Fiori Launchpad
Tile
KPIs
Web based interface, access via web browser
(+ optional Windows Client & Mobile apps: iOS & Android
)
• Access transaction screens via Menu Path or by directly
entering transaction codes.
• Shows all available transactions with a Favourites
section for users to select commonly used transactions.
• Access Fiori applications via Tiles organised into configurable
groups - NO direct access to transaction codes!
• Shows commonly used tiles set by administrator, user can add
transactions they have access to + ability to add custom tiles.
Desktop application
(Windows, Mac & Unix)

S/4HANA FIORI APPLICATION TYPES
Transactional
Task-based access
Access tasks to create, change,
approve processes with guided
navigation.
There are essentially three main Fiori application types used in S/4HANA with many additional
page types/elements for a wide variety of specific UI screens (overview page, object page, worklist,
list page, etc.) to meet business needs.
Analytical
Insights
Get a visual overview of a complex
topic for monitoring or tracking
purposes.
Factsheets
Search & Explore
View essential information about an
object with contextual navigation
between related objects.

FIORI V3 LAUNCHPAD - S/4HANA 1909
Notifications
Link to
Home
Page
Me Area
Apps
quick access
Search
Business Objects & Apps
Help
Co-Pilot
(type/speak + chat bots)
Shell Header Bar
Can add custom icons/functionality for you company
To standardise Fiori across all client
platforms, a common layout has been
adopted with Fiori version 3.
Key User
access to
In-App
extensibility
+ Guided
demos on how
to perform
tasks
SCP

BENEFITS OF FIORI
Improved user performance,
e.g. clear incoming payments.
Designed for mobile phone
and tablet as well as
traditional desktops.
Easier to learn and use,
role based experience.
Simulation and
decision support.

BACKEND CHANGES - HANA
Reduced data footprint  fit in memory
 archive off old/historical data to
minimise data footprint
 data cleansing to meet stricter
S/4HANA data quality standards
HANA Push-down processing
 code change to
improve
performance
HANA Column Store
 code change to
improve performance
Anecdotal evidence suggests total
reduction may only be ⅓ to ⅛ in reality
depending on individual customer circumstances.

28 May 2020 Andrew Harding 8
BACKEND CHANGES - S/4HANA
Moving finance data
to the simplified table
structure requires
additional steps after
software and
database migration to
S/4HANA.
• In-Memory Database.
• Simplified Database structure,
aggregate tables removed.
• CDS views for backward compatibility
tables read/write access.
Universal Journal

THE NEW VIRTUAL DATA MODEL
ECC tables are still accessible as Core Data Services (CDS) Views that are built up in a
layered approach as a Virtual Data Model (VDM).
• No longer access database tables
directly, instead go via CDS views &
OData service.
• CDS compatibility views exist so data is
accessible as though previous tables
still exist.
• CDS views allow CRUD operations,
or built as Cubes for embedded
analysis purposes.
• Fiori apps enable one to add
fields/tables to VDM & user interface
in a consistent manner that is simpler
than with SAP ECC.
OData Service

SOME OF THE BENEFITS OF S/4HANA
Fiori
• Only show information relevant to the user Role and task being performed.
• Productivity improvements, less clicks to perform jobs.
• Common interface, easier for new uses to learn, thus reduced training time/cost.
• Works on multiple devices - PC, mobile phone, iPad, etc.
• New services such as Co-Pilot conversational AI, Intelligent RPA (Robotic Process Automation), etc.
• In-App extensibility without the need for expensive/complex development effort/cost.
In Memory DB
• Overall improved performance  create reports/analytics based on live data, removed delays
awaiting batch job production of aggregate tables and a data warehouse.
• Simulation of postings before committing, and action recommendations.
• Faster financial close production, and “Soft Close” simulation of account balances at anytime.
• Parallel accounting, multiple financial statements (IFRS, GAAP, local country, etc.).
+ Access to all the Latest Innovations/Enhancements from SAP

ON-PREMISE
VS
PUBLIC CLOUD
Key differences between On-Premise vs Public Cloud
Deployment & Functionality
28 May 2020 Andrew Harding 11
Public Cloud

S/4HANA - ON-PREMISE
Due to the volume of screens/functionality that needed to be re-written for the Fiori role
based interface the on-premise edition of S/4 still contains many elements of the old ECC
system that have not yet been replaced.
ECC
S/4HANA
Screens: 300,000+
TCodes: ~100,000
Modules:
MM, SD, etc
Lines of Business
&
Scope Items
(aka Scenarios)
2015 2027-20302020
New Functionality
With each new release of S/4HANA on-premise old ECC functionality is made obsolete (e.g. transactions, tables,
reports, etc.) and are replaced by new functionality such as Fiori apps replacing transactions with new Tcodes.
Announced
4th Feb 2020

S/4HANA CLOUD - PUBLIC CLOUD
Lines of Business
&
Scope Items
(aka Scenarios)
2015 2027-20302020
The public cloud version of S/4HANA only contains the new Fiori apps, and none of the old
ECC functionality/screens that have not yet been re-developed in Fiori.
No access to transaction codes only Fiori apps. No direct access to database tables only CDS views
Only BAPIs to integrate S/4HANA Cloud with SAP on-premise solutions until successor API is available.
S/4HANA
New Functionality
Announced
4th Feb 2020

LOCALIZATION
43 Countries S/4HANA Cloud 2002 25 Languages
53* Countries SAP Business Suite 39 Languages
42 Countries S/4HANA on-premise 1909 39 Languages
COUNTRIES LANGUAGES
(* verified on SAP Help Portal)

RELEASE CYCLES - ON-PREMISE & CLOUD
Cloud Releases:
• Full update quarterly - 1902, 1905, 1908, 1911, ...
• Release is mandatory, can not be delayed.
• Customer should test, particularly custom changes,
in two week period on Q-System.
• Has Test Automation Tool to speed up testing.
On-Premise Releases:
• Full update yearly - 1610, 1709, 1809, 1909, ...
Feature Pack Stack (FPS) quarterly.
• Release is optional, can delay until later date.
• Customer has to test manually, or use another
vendors tool/service.

CLOUD VS ON-PREMISE CUSTOMIZATION
Application
User Interface
Database (SAP HANA)
Side-by-side extensibility
via
SAP Cloud Platform
APP
UI
DB
User Interface
Application
Database (SAP HANA)
User Interface
Application
Database
S/4HANA
S/4HANA
Cloud
SAP
Customer, Partner
In-App extensibility
Classic extensibility
In-App extensibility
Classic customer and partner development
Classic extensibility, using development tools and techniques (e.g. transaction SE80,
Eclipse, BAdIs) is only possible for S/4HANA (On-Premise), and not for S/4HANA Cloud.
Extension Modifications
Direct Link
S/4 functionality
SAP Cloud
Connector
• In-App extensibility via the S/4HANA Fiori apps is available for Cloud and On-Premise versions.
• Beyond In-App extensibility in S/4HANA Cloud you have to used Side-by-Side extensibility with access
via SAP’s Whitelisted APIs &/or the use of custom OData services.
• S/4HANA on-premise edition can be connected to Side-by-Side extensions via SAP Cloud Connector.

CLOUD CUSTOMIZATION - IN-APP TO SIDE-BY-SIDE EXTENSIBILITY
Configure Adapt Extend New App Integrate
• Personalize
• Customise
• App Config
• UI Adaption
• Branding
• Modify UI Layout
• Custom Form/Report
• Field/table extension
• Business logic extension
• Custom UI &
business logic
• SAP App Integration
• Business process
composition
User Key User
Developer Integrator
In-App extensibility Side-by-Side extensibility
• UI Extension
scenarios
(e.g. Customer
Portal or Customer
Service extension)
• Integration
scenarios
• Completely new
solutions
• Customer/partner development in
Fiori/SAPUI5, JavaScript, Java, ABAP, and
native HANA development
• SAP Web IDE, Eclipse
• Custom apps loosely coupled to back-end
of S/4HANA via whitelisted APIs
• Benefits from open standards and partner
ecosystem to extend existing solutions/services
Field Extensibility
Add custom field to
database, application,
CDS and OData
Table Extensibility
Custom objects, node
extensibility
Business Logic
Extensibility
Editor app for custom
enhancement with
RESTful ABAP
UI Flexibility
Hide, move, add fields,
and change labels
Report Extensibility
Custom analytical
queries, CDS views, &
tiles for custom queries
Forms Extensibility
Adobe print forms and
email templates
Customization supported by system upgrades Customization de-coupled from system upgrades dependencies
Extending your S/4HANA system without creating complex dependencies that slow the adoption
of new innovations (releases), and incur considerable upgrade effort/costs.

BENEFITS OF S/4HANA CLOUD VS S/4HANA ON-PREMISE
Why move to S/4HANA Cloud (multi-tenant public cloud)?
Lowest TCO
Minimize software, service,
support and infrastructure
costs - all comes in One
service package.
Simplification &
Standardization
Focus on running your
business, not your ERP.
Easy to scale
Scale users easily as your
business grows, no need
to scale infrastructure.
Easy to replicate & deploy
Deploy globally within hours,
rapidly replicate across
divisions and departments.
Speed of innovation
Get the latest innovations
(S/4 enhancements)
delivered via seamless
quarterly releases.
Automation & AI
AI and ML innovations are first
delivered in the cloud, and
perform best in the cloud due
to data availability/access.

ON-PREMISE MIGRATION VS PUBLIC CLOUD - DETAILED COMPARISON
On-Premise Public Cloud (SaaS)
Customization
Complete flexibility/freedom to develop custom code
that has access to underlying S/4 code and Hana DB.
Restricted to In-App &/or Side-by-Side extensions,
can not directly access underlying S/4 code or Hana DB.
Cost
Company pays for hardware, infrastructure, support
staff as wells as license & maintenance costs, plus
cost of performing software upgrades.
Regular payment to cloud provider covers all infrastructure,
support & upgrades costs so should be less than on-premise
unless increased need for cloud provider services.
Security
Company requires dedicated security experts and
often extra security software to keep systems safe.
Cloud provider has an expert infrastructure and server
security team to keep SaaS systems safe.
Implementation
Need right personnel to set up environment and may
need to buy new hardware/software to implement.
Faster than on-premises since cloud version uses a ready-
made platform implemented/tested by the cloud provider.
Upgrades/Fixes
Company decides frequency & schedule of software
upgrades/fixes + requires IT work to implement.
Less control as Cloud Provider decides schedule, but less IT
work usually limited to validation testing review.
Integration
Less security risks integrating between systems on
company’s “secured” internal network. Integration
with other SAP cloud products requires more effort.
Integrating company systems can involve greater security
risks due to data sent over the internet. Integration between
companies and other SAP cloud products easier with CPI.
Compliance
Company has to ensure regulatory compliance -
cost in time, resources/money + possibly upgrades.
Cloud provider ensures baseline validation
 enforcing regulatory compliance is easier and faster.
Scalability
Requires long-term planning and commitment for
resources required for scaling by the company.
Scaling up or down is easier, faster and cheaper to meet the
changing needs of the company.

MOVING TO
S/4HANA
How to get to S/4HANA from SAP Business Suite or another ERP.

S/4HANA DESTINATIONS
Private Cloud (usually single-tenant)
• System dedicated to customer - On-Premise version of S/4HANA.
• Can be operated on customer site as well as remotely.
• System owned by customer, management and hosting by
customer or 3rd Party or both.
Public Cloud (multi-tenant)
• One system with multiple customers, data isolation/customer
self-service access and tools.
• Operated by Service Provider (SAP),
not by customer.
• Access via the Internet.
Hybrid Cloud (e.g. Two-Tier)
• System is a mixture of two or more deployment models.
• Integrated by standardized or custom interface technology
supporting transfer of data and transactions.
• Access via internal network and external VPN/internet.
On-Premise
• System dedicated to customer, access via
internal customer network.
• System is managed by customer or a 3rd Party.
• Operated on customer’s data centre.
AWS, Azure, Google Cloud
Public Cloud
Private Cloud
On-Premise
Public CloudPrivate Cloud
On-Premise

ON-PREMISE - PRIVATE CLOUD (IAAS & PAAS) - PUBLIC CLOUD (SAAS)
On-Premise Private Cloud Public Cloud
S/4HANA
Your Data Centre
S/4HANA
AWS/Azure/Google Cloud
S/4HANA
SAP HEC (HANA Enterprise Cloud)
S/4HANA Cloud
SAP
Client manages Vendor manages

UPGRADE PATHS TO S/4HANA
Complete conversion
of an existing SAP
Business Suite system
to SAP S/4HANA.
New customer, or
existing customer on
very old SAP system,
with initial data loading.
Consolidate regional SAP ERP
into one global S/4HANA
system, or selective data
migration (“Carve out”) of
business functions.aka Landscape
Transformation
Customer-tailored
Highly Standardised
(Best Practices & clean core)
Requires SAP or
SAP Partner
There are TWO main paths to take, System Conversion to keep much of what you have already, or
New Implementation to start anew, the third path is very selective requiring specialist assistance.

S/4HANA ON-PREMISE CONFIGURATION - SYSTEM CONVERSION & NEW IMPLEMENTATION
PFCG - Role DefinitionsS/4HANA On-Premise and Private Cloud
configuration still uses the Easy Access
transactions used by SAP ECC of SPRO and
PFCG, plus Fiori users/roles apps.
SPRO - System Configuration
Fiori Apps - User/Role Management

S/4HANA CLOUD CONFIGURATION (SSCUI) PRE 1911 - NEW IMPLEMENTATION
Self-Service
Configuration
Migration
Cockpit
Run Automated
tests
Author
Automated tests
Not all configuration tasks can be done via self-service, Expert configuration is performed by SAP Service Centre.
Training
Material
Activated
Scope Items
S/4HANA Cloud configuration there are NO transactions (i.e. SPRO - IMG & PFCG),
you have to use “Manage Your Solution” app (aka SSCUI - Self Service Configuration UI).

S/4HANA CLOUD - CENTRAL BUSINESS CONFIGURATION (CBC) - POST 1911 - NEW IMPLEMENTATION
SSCUI functions moved to
separate Fiori app tiles
• Migration Cockpit
• Author Automated Tests
• Run Automated Tests
Manage Project implementation and Perform Scope/Configuration of S/4HANA Cloud.
• The long term goal is for
CBC to be the central point
for managing/configuring
all SAP Cloud systems.
• After S/4HANA Cloud it is
planned to include
SuccessFactors for HR data
across both systems.

MODEL COMPANY
Model Company is a pre-packaged
solution to speed implementation
of SAP S/4HANA, SAP C/4HANA, &
SAP SuccessFactors solutions.
S/4HANA select either:
▪ Standard Model Company with
1 industry or LoB.
▪ Custom edition 1 industry with
1+ LoB & Localisation (2-4 weeks prep.).

Custom Code PreparationPre-checks
SYSTEM CONVERSION PLAN - ON-PREMISE
Conversion to S/4HANA is not an upgrade, it is more of a migration to a new system on new
hardware. Multiple test conversions are likely to be need to identify/resolve data quality and
customization issues.
• Identify & review the relevant Simplification items.
• Run Customizing pre-checks & adapt settings.
• Check consistency & reconcile/fix data issues.
• Period end closing activities.
• Document your posting data.
• Archive data you no longer need.
• Identify custom code to discard and required changes.
• Preparation & Migration of
Finance Customizing.
• Data Migration.
• Activities after Migration,
e.g. custom code adaption.
Major Issue:- 3rd Party Add-ons
❖ 3rd Party certification is lagging behind
S/4HANA yearly releases.
 SUM halts if it finds an non-certified Add-on.
Pre-Conversion
• Convert database
to Unicode
• Replace Customer
+ Vendor with
Business Partner
• Data Cleansing
No postings during migration!

SYSTEM CONVERSION - SAP READINESS CHECK - 1809+ - SYSTEM CONVERSION
• Simplification Items
• Activities Simplification Items
• Add-on Compatibility
• Active Business Functions
• SAP S/4HANA Sizing
• Custom Code Analysis
• Recommended Fiori Apps
• Integration
• Business Process Discovery
Manage Items list In/Out of Scope
Access relevant SAP Note
SAP Readiness Check is an enhanced tool to prepare for system conversion.

SYSTEM CONVERSION - CODE CONVERSION
S/4HANA simplified data model means custom code built for SAP Business Suite may not work
without modification due to changes in the underlying SAP code that is referenced by custom code.
1. Eliminate obsolete code - analyse usage procedure logging in SCMON & UPL logging to identify “dead” code
2. Check S/4HANA compatibility - Code Inspector checks against Simplification Database for issues
3. Custom Code Migration Worklist what needs fixing  adapt/fix code
4. Performance check - may require further code changes, e.g. use Where clause instead of retrieve entire row
5. Implement corrected code with Software Update Manager during system conversion
Potential Issues:
• Sort order  Order By
• Material number code
18 char  40 char
• DB specific code, e.g. DB
Procedures
• Pool/Cluster table
operations
• Write to aggregate table
requires extra function
modules

NEW IMPLEMENTATION - ON-PREMISE/CLOUD - SAP ACTIVATE
Principle of start with SAP Best Practices, then configure the solution to meet customer
requirements as much as possible before adding custom extensions.
Fit/Gap Analysis
Walk through standard SAP
config to identify config
settings and gaps with
required solution.
Scope & Configure
Setup base settings
(CoA & Org. structure)
then configure solution to
meet requirements.
Migrate, Integrate, Extend
Migrate data, develop
integrations and extensions,
then test all works correctly.

NEW IMPLEMENTATION - MIGRATION COCKPIT
Legacy
ERP
S/4HANA Cloud
S/4HANA
3. Direct Transfer
1. Template
File Upload
2. Staging
Tables
API based
data load
API based
data load S/4HANA
• Comes free of charge with S/4HANA & S/4HANA Cloud - is the recommended tool for loading data.
• New implementation only migrates Master Data, Open Items and Transaction Balances.
• Does not migrate Closed Items / Transaction history - impossible to reproduce in a new system
 Old data: a) create an archive; or b) store in a data warehouse; or c) discard if possible/desirable.

NEW IMPLEMENTATION - SAP DATA SERVICES
• ETL is free with S/4HANA (on-premise), but requires a Data Services license with S/4HANA Cloud .
• Data Quality features enable you to clean data errors, and enhance data content, but require Data Services
license for both On-premise and Cloud.
Data Services enables automated extraction of data from source files/databases via an ETL tool that
can also include data quality and data enhancement actions.
Input into
Migration
Cockpit

SELECTIVE DATA TRANSFER
Selective Data Transition should be considered when organizations need to:
• Go-Live in phases (e.g. by country or business unit).
• Reduce effort by re-using some areas (e.g. logistics) while re-designing others (e.g. finance).
• Reduce risk of a “Big Bang Go Live.
• Split or merge existing SAP ERP instances
(e.g. carve-out application areas/companies, and implement them on a separate instance, or in the cloud).
• Leave behind large amounts of old data, e.g. reduce duration of conversions & cutovers.
(An alternative to doing a large data archiving project followed by a system conversion.)
Selective Data Transition requires special
software (e.g. SAP DMLT or partner equivalent)
and specialist technical capabilities that will
need to be provided directly by SAP or certain
recommended SAP partners.

TWO-TIER IMPLEMENTATION APPROACH + BUILD S/4 EXPERIENCE
Tier 1
Fully
Functional
ERP
Tier 2
Lighter,
Simpler,
Cheaper,
Different
Why 2-Tier?
• Local flexibility while still conforming to IFRS and the need for central planning (IBP) + global processes.
• Simpler to implement and meet local regulatory requirements with quarterly S/4HANA cloud updates.
• Local regional cloud datacentre access to S/4HANA Cloud for faster user access, system responsiveness.
• Single-vendor solution for tiers  reduced cost/complexity using one data model and common user experience.
• Ability to run new/agile business models in subsidiaries without being constrained by central HQ commonality.
SAP Business Suite
OR
S/4HANA (on-premise)
S/4HANA
Cloud
S/4HANA
Cloud
S/4HANA
Cloud
Pre-Package & API Connectivity
Global Process
&/or
Local Process
IBP
Central Planning
Local Production Unit
as Supplier
Local Production Unit
as subcontractor
Local Inventory Unit

S/4HANA - ADOPTION
End of regular
Support
End of extended
Support
Current rate of
license purchase
(statista.com)
Approx. 40K
SAP ERP
customers
worldwide
Support & Maintenance
• SAP Business Suite 7 increased from 2025 to 2027, with optional extended support until 2030 (4th Feb 2020).
• SAP S/4HANA support up to 2040, and has a five year "life" under mainstream maintenance.
S/4HANA Adoption
• Has been slow, Resulting IT survey* in 2019 showed only 8% of customers had implemented S/4HANA with other
surveys indicating many more projects have started but not completed and many more were due to start.
• There will need to be an increased rate of adoption for most customers to complete implementation before the new
deadlines of 2027 & 2030.
Required rate of
implementation Current rate of
implementation
(Resulting IT Survey)
• Additionally initial adopters of S/4HANA will need to go through an upgrade cycle once every 5 years at a minimum in
order to stay under mainstream maintenance with S/4HANA.  increasing demand for S/4HANA resources
(* Resulting IT survey was worldwide with 59% of respondents from the UK)

SAP’S FUTURE
DIRECTION
How SAP is redefining it’s business model
from On-Premise software
to Cloud services provider.

SAP’S VISION OF EVOLUTION TO THE CLOUD
The SAP vision of the evolution of their ERP suite from On-Premise to Cloud.
• Clearly the timescales in this vision do not match the reality of SAP’s realisation of a move to a complete
cloud experience, or SAP customers willingness to move to a fully Cloud based environment.
• However, it does show SAP’s intention to adapt their product range to move to a Cloud based ecosystem
which reflects industry trends and investor expectations.

SAP FUTURE DIRECTION  CLOUD SERVICES
“The Street” - 28 Jan 2020
“SAP SE (SAP) - shares slumped to the bottom of the German market Tuesday after the enterprise
software group posted a mixed set of fourth quarter earnings and forecast 2020 sales from its burgeoning
cloud business that were below analyst's forecasts.”
“Nasdaq” - 28 Jan 2020
“SAP stock slid on Tuesday despite the German software company lifting guidance for 2020 after posting
profit and revenue gains in the fourth quarter. Despite impressive fourth quarter results SAP stock has
fallen, reflecting investor concerns over the company’s cloud growth.”
“Financial Times” - 28 Jan 2020
“SAP has said growth in new orders in its key cloud computing division cooled sharply at the end of last
year, sparking a drop in the German software group’s shares.”
“The reality is cloud is the focus now,” said Julian Serafini at Jefferies. “So it does raise questions as to
what is leading [the deceleration in growth]. It’s a little concerning.”
The importance investors see in SAP Cloud services growth can be seen by the reaction
of markets and news outlets to SAP’s announcement of financial results for 2019.

SAP PRODUCT RANGE CONSOLIDATION & MIGRATION TO CLOUD
SRM
• SRM ➔ S/4 Central Procurement (1809 release) & Ariba
• SCM ➔ Ariba (collaboration with suppliers) & IBP
• CRM ➔ C4C (Customer for cloud) as part of C/4HANA
• APO ➔ S/4HANA & IBP
• PLM ➔ as part of S/4HANA
• HCM ➔ SuccessFactors

SAP CLOUD PRODUCT RANGE
SCP - SAP Cloud Platform
CPI - Cloud Platform Integration
CBC - Central Business Configuration
SAP’s vision of “One Cloud Experience” can be seen by their cloud product range, the development of Central
Business Configuration to co-ordinate implementation and Cloud Platform Integration to link it all together on
SAP Cloud Platform.
SAP S/4HANA Cloud SAP Analytics Cloud
SAP SuccessFactors
SAP Integration
Business Planning
SAP Fieldglass
SAP C/4HANA
SAP Ariba
SAP Concur
CBC
SCP + CPI

SAP CLOUD PLATFORM INTEGRATION
SCP
Services
SCP Intelligent Technologies
Social
Networks
Public Authorities
On-Premise
Apps
Business
Partners
Cloud
Apps
SAP Cloud
Platform
Integration
many prebuilt
connectors
some prebuilt
connectors
SAP
Cloud
Apps
Document
Compliance
Statutory
Reporting
Integration
Advisor EDI
SAP Cloud Platform Integration enables business to connect SAP/non-SAP applications together, as well as
business partners and public authorities, and enables access to a multitude of cloud services.

CONCLUSIONS
Move to S/4HANA - now or later
After a slow start there the number of SAP customers who have implemented S/4HANA is relatively small. Despite end
of support for SAP Business Suite being put back to 2027/2030 the rate of implementation appears to be below the
rate required to ensure all customers are on S/4HANA by this new end date. To counter this SAP has increasingly
developed tools to make this major change easier to implement, and reduce the many issues/risks involved. Time will
tell how many will make it by this new deadline, and whether the end of support date gets pushed back again.
S/4HANA Cloud or On-premise
SAP has a vision of an interconnected digital experience in the cloud, though many of its customers would rather stay
on-premise as evidenced by countless surveys of SAP customers, only a small number are considering S/4HANA Cloud.
Many businesses are considering the halfway house of implementing S/4HANA on-premise version on hyperscalers
such as AWS - SAP has made this option much easier with fast tracked system provisioning.
Cloud Future
Despite many SAP customers sticking with the on-premise version of S/4HANA the ability to easily integrate with SAP
Cloud Platform to other applications, businesses and government bodies (e.g. HMRC for VAT) mean business will
increasingly drawn to the cloud. The addition of SAP cloud based services such as AI/Machine Learning, the Internet of
Things, Blockchain, mobile services, etc. will also see businesses increasingly using SAP Cloud Platform to extend the
capabilities of S/4HANA. Moving to the cloud is taking longer than SAP have envisioned, but is undoubtedly the future
for S/4HANA and the Intelligent Enterprise.

THANK YOU
Andrew.harding@Itanta.com

Moving to SAP S/4HANA

More Related Content

What's hot (20)

Similar to Moving to SAP S/4HANA (20)

Recently uploaded (20)

Moving to SAP S/4HANA