What You Must Know to Make Your Conversion to SAP

S/4HANA Seamless with SAP S/4HANA RIG Support

Lars Rueter, Thomas Csapo • 5 September 2017
 Legal Disclaimer

The information in this presentation is confidential and proprietary to SAP and may not be disclosed without the permission of
SAP. Except for your obligation to protect confidential information, this presentation is not subject to your license agreement or
any other service or subscription agreement with SAP. SAP has no obligation to pursue any course of business outlined in this
presentation or any related document, or to develop or release any functionality mentioned therein.

This presentation, or any related document and SAP's strategy and possible future developments, products and or platforms
directions and functionality are all subject to change and may be changed by SAP at any time for any reason without notice. The
information in this presentation is not a commitment, promise or legal obligation to deliver any material, code or functionality. This
presentation is provided without a warranty of any kind, either express or implied, including but not limited to, the implied
warranties of merchantability, fitness for a particular purpose, or non-infringement. This presentation is for informational purposes
and may not be incorporated into a contract. SAP assumes no responsibility for errors or omissions in this presentation, except if
such damages were caused by SAP’s intentional or gross negligence.

All forward-looking statements are subject to various risks and uncertainties that could cause actual results to differ materially from
expectations. Readers are cautioned not to place undue reliance on these forward-looking statements, which speak only as of their
dates, and they should not be relied upon in making purchasing decisions.
Agenda
• Lessons Learnd
• Guiding Architecture Principles
• Transition Scenarios, System Conversion, Technical Procedure and Tools
• Readiness Check, Custom Code, Back to Standard
• Migration Cockpit / -Modeler, Data Migration Options
• Q&A
LESSONS LEARNT – REGIONAL
IMPLEMENTATION GROUP APJ
 SAP S/4HANA Projects Overview

• 2600+ active projects (800 in Asia)

• 970+ live customers (340 in Asia)
• All industries
• New Implementations and System Conversions
• 65 % of existing SAP ERP customers choosing System Conversion
• Clear trend towards System Conversion
SAP S/4HANA Projects

Insights from engaging with

SAP S/4HANA implementation
projects
 Lessons Learned?

SAP S/4HANA RIG Knowledge Assets on

SAP.COM reaching 140k page views

+
https://go.support.sap.com/roadmapviewer
 Based on the experience gained from current
projects, a customer system will be affected by
30 to 50 of the currently around 400
Simplification Items
GUIDING ARCHITECTURE PRINCIPLES
The 3 Key Enablers For Digital Transformation

SAP HANA AS THE UNDERLYING SIMPLIFICATION OF APPLICATIONS AND

PLATFORM UNDERLYING DATA MODEL
• OLAP & OLTP MERGE • NO AGGREGATES & NO INDICES
• IN-MEMORY COMPRESSION • HIGHER FLEXIBILITY & THROUGHPUT
• INCREASE IN SPEED SAP HANA SIMPLIFIED • DATA FOOTPRINT REDUCTION

SAP FIORI

• SAP FIORI AS THE USER EXPERIENCE • WEB-BASED, ALL DEVICES

(UX) PARADIGM; • ROLE-BASED
• CROSS-APPLICATION USER EXPERIENCE • DECISIVE, PREDICITVE, SIMULATION
High Level Stack Architecture SAP S/4HANA
Architecture is much simpler
than the Business Suite
architecture

• Data structures
(Compatibility provided through Core Data
Services)

• Application engines
• Launchpad / Fiori
(SAPGUI for Windows still available for
compatibility reasons On Premise)
The New S/4HANA Programming Model

Search ONE
UI Dashboard
UI UI experience

Business Business Analytical ONE

application application application programming model

DATA ONE
TX SEARCH common data modelling
(OPEN SQL) (TREX)
ACCESS
(ODP) technology

ONE
Any Database TREX BW Database
SAP HANA
Programming model for SAP S/4HANA
Efficient ABAP programming model for all types of SAP Fiori apps
TRANSITION SCENARIOS, SYSTEM
CONVERSION, TECHNICAL PROCEDURE
AND TOOLS
Release Strategy and Adoption Paths
General availability (GA / RTC)
Innovation path SAP S/4HANA 1809
Alternative path (as an example)
SAP Guided Beta program
Mainstream Maintenance – Feature Packages (FPs)
Mainstream Maintenance – Support Packages (SPs) SAP S/4HANA 1709
Maintenance

SAP S/4HANA 1610

Maintenance Line

SAP S/4HANA 1511

Maintenance Line

possible transition paths

SAP ERP System

SAP Release Strategy
3 Different Approaches to Move to S/4HANA
Bring your business processes to the new platform
• A complete technical in-place conversion of an existing
System SAP ERP SAP Business Suite ERP system to SAP S/4HANA.
On-Premise • Adopt new innovations at your speed
Conversion System
SAP S/4HANA

New implementation / re-implementation

SAP ERP On-Premise
Reengineering and process simplification based on
New or latest innovations
Implementation 3rd -party • Implement innovative business processes with best-practice
System S/4HANA Cloud content on a new platform
• Perform initial data load
• Retire old landscape

SAP ERP System Value driven data migration to the new platform
Region A
e.g. consolidation of current SAP Business Suite
Landscape SAP ERP System On-Premise landscape into one global SAP S/4HANA system or
Transformation Region B
selective data migration based on legal entities
SAP ERP System SAP S/4HANA
Region C

SCN Blog: How to find my path to SAP S/4HANA

The SAP S/4HANA Family and Transition Paths
SAP Business Suite SAP S/4HANA family
(e.g. BS7i2013)

S/4HANA Cloud
New implementation only!

SAP ERP System

(on AnyDB)

or
SAP Central Finance

SAP S/4HANA Finance

1503, 1605

SAP ERP System

(on SAP HANA)
SAP S/4HANA
(On-Premise)

System Conversion
New Implementation
Landscape Transformation
Questions Influencing the Choice of Transition Scenario
System Requirements Business Processes Custom Code

New
Implementation System Conversion New
Implementation System Conversion New
Implementation System Conversion

A company has restrictions that do A company has business processes that A company has checked and is able
not allow to move to SAP S/4HANA already fit to the current requirements. to take over existing custom code.
on-premise in a one-step procedure.

Time to Value

New
Implementation System Conversion New
Implementation System Conversion

A company seeks to fundamentally A company wants to go live rather fast.

redesign its business processes.
 Choice of Deployment
• SAP S/4HANA and SAP S/4HANA Cloud share following characteristics
for consistency at every level of your enterprise:

– Share same code line

– Designed for in-memory
– Same simplified data model
– Improved user experience

• Important considerations:
– Scope of business functionality (i.e. industry solutions)
Cloud On-Premise
– Deployment times
– Update frequency / impact on running processes New Implementation New Implementation

– Customizations Landscape Transformation System Conversion

Landscape Transformation
– Regulatory, industry, and regional requirements Perfect choice, if:
– System operations skills and efforts ✓ Functional scope is sufficient
– efforts for maintaining custom code and modifications during ✓ Focus is on Standardization
every maintenance event
✓ Faster delivery on innovation
System Conversion – Transition Paths Overview

The transition to SAP S/4HANA does not

require the source system to be already
on SAP HANA Database
SAP ERP 6.0, EHP xx SAP S/4HANA 1709

AnyDB or SAP HANA SAP HANA System Conversion Paths (basically)

From SAP Business Suite
(ERP6.0, EHP xx, Any DB or SAP HANA DB)
to SAP S/4HANA 1709 SPS00

Note 1: For older SAP Business Suite releases or systems on Non-Unicode an additional step to
SAP ERP 6.0 EHPxx is required. Conversion requirements incl. min./max. SP-level on source
system:
Note 2: System has to be an AS ABAP-only system. Dual-stack systems (AS ABAP and AS Java 2482453 - SAP S/4HANA 1709: Release Information Note
combined in one system) are not supported for the conversion. If your system is as dual-stack
2346431 - SAP S/4HANA 1610: Release Information Note
system, you have to split it before doing the conversion.

Note 3: SAP Suite on HANA customers who are planning a system conversion to SAP S/4HANA 1709 should first
update the database from SAP HANA 1.0 to SAP HANA 2.0 and then do the system conversion (either in the
same or a separate downtime).
System Conversion – Transition Paths Overview

SAP S/4HANA 1709

Start Release Target Release Availability Remarks
SAP HANA 2.0 Update DB to SAP HANA 2.0
SAP S/4HANA SAP S/4HANA 1709 Planned for: and Installation of S4CORE
1 Finance 1605
Q4/2017 Software
SAP S/4HANA 1610
4
1 SAP Simple Finance,
SAP S/4HANA 1709 Planned for :
Update DB to SAP HANA 2.0
SAP HANA 1.0 2 on-premise edition
Q4/2017
and Installation of S4CORE
1503 Software
2 SAP S/4HANA, on-premise
5 SAP Simple Finance, SAP S/4HANA available since: Installation of sFIN
edition 1511
3 on-premise edition Finance 1605 Q2/2016 Software (Upgrade)
SAP HANA 1.0 1503

Planned for: Update DB to SAP HANA 2.0

NOT SUPPORTED
4 SAP S/4HANA 1610 SAP S/4HANA 1709 Q4/2017 and Installation
SAP S/4HANA Software (Upgrade)
Finance 1605
SAP S/4HANA, on- Planned for: Update DB to SAP HANA 2.0
SAP S/4HANA 1709
SAP HANA 1.0 5 premise edition 1511 Q4/2017 and Installation
Software (Upgrade)
SAP Simple Finance, on-
premise edition 1503 3
SAP HANA 1.0
System Conversion from
SAP S/4HANA Finance to SAP S/4HANA
Upgrade within the
SAP S/4HANA product family
System Conversion or Upgrade with HANA 2.0

SAP S/4HANA 1709

SAP HANA 2.0

Step 2: Conversion
Step 2: Upgrade

SAP S/4HANA SAP S/4HANA

version X Version X

SAP HANA 1.0 SAP HANA 2.0

SAP ERP 6.0 SAP ERP 6.0

Step 1: Database Upgrade
SAP HANA 1.0 SAP HANA 2.0

Step 1: Database Upgrade

 System Conversion Technical Process
Preparation phase Realization phase

Maintenance Software Update Application specific

Application specific
System requirements Pre checks Custom
Custom code preparation
preparation
planner Manager (SUM) follow-up activities
follow-up activities

Unicode conversion Database migration

Software update
Cross-application & application specific preparation activities
Data conversion

Simplification List

**)
incl. migration of FI
Customizing and Data

*) incl. preparation of

financial data
Simplification Item Catalog
• With SAP S/4HANA 1709 web-based UI for searching and displaying Simplification Items:
https://launchpad.support.sap.com/#/sic/

• Allow customers to directly search and browse

the Simplification Items.

• Also other products (e.g. BW/4HANA) are

going to join the Simplification Item Catalog.

• In parallel the Simplification List for SAP S/4HANA

1709 will still be available as PDF document.
 Simplification List and Pre-Checks
Preparation phase Realization phase

Maintenance Software Update Application specific

Application specific
System requirements Pre-Checks Custom
Custom code preparation
preparation
planner Manager (SUM) follow-up activities
follow-up activities

 Pre-checks are shipped as SAP Notes to customers that plan to convert to SAP S/4HANA. Pre-Checks

 Pre-checks are executed on the (SAP Business Suite) start system (preparation phase)
to determine relevant Simplification Items.
 Pre-Checks are executed again as step in the Software Update Manager (SUM). In case
dedicated Simplification Items require mandatory preparation steps the conversion procedure can stop to ensure a consistent system conversion.

Customer-specific Simplification List

Pre-Check S-Item Title Area Relevancy Business Impact Note
The pre-check framework will be COST ELEMENTS FIN - Controlling 2270419

delivered via one SAP Note and all coded Pre-Check Currencies in Universal Journal FIN - General 2344012
pre-check classes will be delivered with Report Business Partner Approach Master Data 2265093
one TCI Note (Transport-Based Correction
… … …
Instructions)
Simplification Item Checks
• Replace the old Pre-Check Framework (check classes)
to be run before the conversion to SAP S/4HANA.
• Can (and should) be run by the customers manually in
advance and will be run by SUM when starting the
conversion
• Check if serious issues exist in the system which could
cause the system conversion/upgrade to fail.
• Compared to the old Pre-Check Framework the
Simplification Item Checks
• Are easier to implement (2 SAP notes instead of >50 SAP
notes)
• Support not only system conversions to SAP S/4HANA, but
also upgrade within SAP S/4HANA
• Provide improved handling of the check results (e.g. exception
handling)
• Also include relevancy checks for Simplification Items (same
For more information see SAP Notes
like the SAP Readiness Check for SAP S/4HANA)
• 2399707
• 2418800
S/4HANA READINESS CHECK
 Readiness Check Coverage
Custom Code & Custom Dev
• Custom Code must be analyzed with respect to
SAP S/4HANA compliance, based on the SAP
simplification database
• SAP Readiness Check provides BOM of affected
objects as well as SAP Custom Development
Projects (CDP‘s)
• An in-depth custom code management activities
to follow during project execution
AddOn’s & Business Functions
• SAP AddOn’s and Business Functions as well as
3rd party AddOn’s have to be checked for their
compatibility with SAP S/4HANA
• SAP software is listed and rated
• 3rd party software is listed only
S/4HANA Sizing
• To prepare for SAP S/4HANA, a system sizing is
the baseline for further discussions regarding the
future target size
• SAP Readiness Check summarizes the technical
sizing result so that customers can further engage
internally, with SAP or with partners to discuss
the future target system size

Simplification items
• Simplification Items represent application or
architecture changes in comparison to ERP
Recommended Fiori Apps
• About 470 Simplification Items exist for S/4HANA
• Fiori apps recommended based on the
1610
transaction usage history in the evaluated system
• They are grouped by business priority (e.g. Core
Finance) and industry, respectively
Transactions
• SAP GUI transactions replaced or deprecated in
SAP S/4HANA, such as Classic MM-PUR GUI
transactions
Migration Cockpit / -Modeler
Data Migration Options
 S/4HANA Migration Cockpit Overview
• Part of SAP S/4HANA Cloud and New Third-party Migration On-Premise

on-premise solution Implementation System Cockpit

S/4HANA Cloud

• Supports customers with the

New Implementation scenario
System ERP System On-Premise
• Included in SAP S/4HANA license Conversion SAP S/4HANA

• Tool of choice for SAP S/4HANA

ERP System
Cloud Landscape
Region A On-Premise
ERP System
Transformation Region B
ERP System S/4HANA Cloud
Region C
S/4HANA Migration Cockpit – Cloud 1708 / On-Premise 1709
S/4HANA Cloud

Migration Cockpit On-Premise

Third-party Data Provisioning Process Content Data load

System
Single point of entry Preconfigured migration
objects and mapping
Guided procedure
Extract API-based
Data selection Generation of migration
Files programs
Data transformation
Data validation
Monitoring

Logs </> Integration of custom

objects
ERP System Documentation

*
Object Modeler

* Only in On-Premise version

 Pre-configured Migration Content
• Preconfigured content and mapping for each migration object, e.g. G/L Open items

• Predefined templates (Microsoft Excel XML files) for each object

• Automated mapping between template and target structure

• Migration programs are automatically generated - no programming required by the customer

• Available for private and public cloud and on-premise

Overview Migration Objects

Migration Template for G/L Open Items
 Migration Guidance
1. Select Migrate Your Data from the Guided Configuration menu 2. Create a migration project
 Migration Guidance
3. Select the relevant migration objects

Data migration objects delivered with the SAP S/4HANA Migration Cockpit will be listed in the migration project.
Select the migration objects you need, and generate a migration template for them.

4. Generate a file template for the selected migration objects

 Migration Guidance
5. Start the transfer and monitor the data migration process

The ‘Simulate Import’ feature checks migration data against the Customizing data in the system.
 Migration Object Modeler – for Custom Data Integration
SAP S/4HANA Migration Object Modeler - Part of the SAP S/4HANA Migration Cockpit
Design functionality to easily integrate custom objects and enhancements
Integration of newly created objects
▪ Custom objects
▪ SAP standard objects that are not yet in the scope of the SAP S/4HANA Migration Cockpit
Customer-specific enhancements (e.g. add new fields) to SAP standard objects delivered with the
SAP S/4 HANA Migration Cockpit
Available for On-Premise and private cloud
Migration Object Modeler – Source Structures
Under Source Structures, you can adjust the source structure so that your data can be transferred to the SAP S/4HANA system

Example: You can add a new field, and specify the relevant information for the field.

Choose ‘Insert Field’

 Migration Object Modeler – Target Structures
Under Target Structures you can get an overview of the target structures associated with the migration object
Structures can be single fields, multiple fields, or tables

Example: Before you add a new field to the source structure, you can determine which target structure the source field should be mapped to.
 Migration Object Modeler – Structure Mapping
Under Structure Mapping, you can check how the source structure is mapped to the corresponding target structure

As a prerequisite, the source structure must be mapped to a target structure before you can map the fields of the source to
the target structure (see Field Mapping)
 Migration Object Modeler – Field Mapping
Under Field Mapping, you can map fields from the source structure to fields in the target structure
Simply drag the relevant field from the right-hand side to the target structure field on the left-hand side
If a field from a source structure has been mapped to a target field, the system displays a green icon and a red icon, if it has
not been mapped
Filter for mapped/
unmapped fields
 Planned Pre-Configured Business Objects – Cloud 1708 / On-Premise 1709

• Accounts Payable (Vendor Open Item) • Functional Location • Pricing condition

• Accounts Receivable (Customer Open Item) • Functional Location Task List • Profit Center
• Activity Price • G/L account balances (classic G/L) • Purchase Order
• Activity Type • G/L account open item • Purchasing Info Record (with Conditions)
• Bank Master Data • General Task List • Routing
• Batches • Inspection Method • Sales Contract
• Bill of Material • Inspection Plan • Sales Order
• Characteristic • Internal Order • Scheduling Agreement
• Class • Inventory Balances • Selected Set & Selected Set Codes
• Code / Code Group • Maintenance Plan • Source List
• Commercial Project Management (CPM – only Cloud) • Maintenance Task List • Supplier*
• Contracts (Purchasing) • Master Inspection Characteristic • TRM Foreign Exchange Spot
• Cost Center • Material* (including Long Text) • TRM Foreign Exchange Swap-Contract
• Customer* • Material Inspection Type • TRM Interest Rate Instrument
• Equipment • Material Commodity Code • TRM Interest Rate Swap
• Equipment Task List • Material Consumption • Work Center
• Exchange Rate • Material Classification
• Fixed Asset (incl. Balances) • Material Price Change *Supports extension of organizational level
Questions and Answers