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 ofSAP. Except for your obligation to protect confidential information, this presentation is not subject to your license agreement orany other service or subscription agreement with SAP. SAP has no obligation to pursue any course of business outlined in thispresentation 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 platformsdirections and functionality are all subject to change and may be changed by SAP at any time for any reason without notice. Theinformation in this presentation is not a commitment, promise or legal obligation to deliver any material, code or functionality. Thispresentation is provided without a warranty of any kind, either express or implied, including but not limited to, the impliedwarranties of merchantability, fitness for a particular purpose, or non-infringement. This presentation is for informational purposesand may not be incorporated into a contract. SAP assumes no responsibility for errors or omissions in this presentation, except ifsuch 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 fromexpectations. Readers are cautioned not to place undue reliance on these forward-looking statements, which speak only as of theirdates, 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 SIMPLIFIED

SAP FIORI

SAP HANA AS THE UNDERLYING PLATFORM

• OLAP & OLTP MERGE

• IN-MEMORY COMPRESSION

• INCREASE IN SPEED

SIMPLIFICATION OF APPLICATIONS AND UNDERLYING DATA MODEL

• NO AGGREGATES & NO INDICES

• HIGHER FLEXIBILITY & THROUGHPUT

• DATA FOOTPRINT REDUCTION

• SAP FIORI AS THE USER EXPERIENCE (UX) PARADIGM;

• CROSS-APPLICATION USER EXPERIENCE

• WEB-BASED, ALL DEVICES

• ROLE-BASED

• 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

Any Database

SEARCH(TREX)

TX(OPEN SQL)

BW

DATA ACCESS

(ODP)

UISearch

UIDashboard

Business application

Analytical application

ONEDatabase

SAP HANA

ONEcommon data modelling

technology

ONEprogramming model

ONEUI experience

TREX

Business application

Programming model for SAP S/4HANAEfficient ABAP programming model for all types of SAP Fiori apps

TRANSITION SCENARIOS, SYSTEM

CONVERSION, TECHNICAL PROCEDURE

AND TOOLS

Release Strategy and Adoption Paths

Maintenance Line

Maintenance Line

Maintenance

SAP S/4HANA 1511

SAP S/4HANA 1610

SAP S/4HANA 1709

SAP S/4HANA 1809

SAP Release Strategy

General availability (GA / RTC)

Innovation path

Alternative path (as an example)

SAP Guided Beta program

Mainstream Maintenance – Feature Packages (FPs)

Mainstream Maintenance – Support Packages (SPs)

SAP ERP System

possible transition paths

3 Different Approaches to Move to S/4HANA

SystemConversion

On-PremiseSAP ERPSystem

SAP S/4HANA

New Implementation

On-Premise

S/4HANA Cloud

SAP ERP or 3rd -partySystem

LandscapeTransformation

On-Premise

SAP ERP SystemRegion A

SAP ERP SystemRegion B

SAP ERP SystemRegion C

SAP S/4HANA

New implementation / re-implementationReengineering and process simplification based on latest innovations• Implement innovative business processes with best-practice

content on a new platform• Perform initial data load• Retire old landscape

Bring your business processes to the new platform• A complete technical in-place conversion of an existing

SAP Business Suite ERP system to SAP S/4HANA. • Adopt new innovations at your speed

Value driven data migration to the new platform

e.g. consolidation of current SAP Business Suite landscape into one global SAP S/4HANA system or selective data migration based on legal entities

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

The SAP S/4HANA Family and Transition Paths

SAP Business Suite(e.g. BS7i2013)

SAP S/4HANA family

New implementation only!

System ConversionNew ImplementationLandscape Transformation

SAP ERP System(on AnyDB)

SAP ERP System(on SAP HANA)

(On-Premise)

SAP S/4HANA

SAP S/4HANA Finance1503, 1605

S/4HANA Cloud

SAP Central Finance

or

Questions Influencing the Choice of Transition Scenario

System Requirements

New Implementation System Conversion

A company has restrictions that do not allow to move to SAP S/4HANA on-premise in a one-step procedure.

New Implementation System Conversion

New Implementation System Conversion

A company has business processes that already fit to the current requirements.

New Implementation System Conversion

New Implementation System Conversion

Custom Code

Time to Value

A company has checked and is able to take over existing custom code.

A company wants to go live rather fast.

Business Processes

A company seeks to fundamentally 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)

– Deployment times

– Update frequency / impact on running processes

– Customizations

– Regulatory, industry, and regional requirements

– System operations skills and efforts

– efforts for maintaining custom code and modifications during every maintenance event

On-PremiseCloud

New Implementation

Landscape Transformation

New Implementation

System Conversion

Landscape TransformationPerfect choice, if:

✓ Functional scope is sufficient

✓ Focus is on Standardization

✓ Faster delivery on innovation

System Conversion – Transition Paths Overview

System Conversion Paths (basically)

Note 1: For older SAP Business Suite releases or systems on Non-Unicode an additional step to SAP ERP 6.0 EHPxx is required.

The transition to SAP S/4HANA does notrequire the source system to be already on SAP HANA Database

Note 2: System has to be an AS ABAP-only system. Dual-stack systems (AS ABAP and AS Java combined in one system) are not supported for the conversion. If your system is as dual-stack system, you have to split it before doing the conversion.

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

AnyDB or SAP HANA

SAP ERP 6.0, EHP xx

SAP HANA

SAP S/4HANA 1709

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).

Conversion requirements incl. min./max. SP-level on source system: 2482453 - SAP S/4HANA 1709: Release Information Note2346431 - SAP S/4HANA 1610: Release Information Note

System Conversion – Transition Paths Overview

SAP HANA 1.0

SAP Simple Finance, on-premise edition 1503

SAP HANA 1.0

SAP HANA 1.0

SAP S/4HANA, on-premise edition 1511

SAP HANA 1.0

SAP S/4HANA 1610

3

1

SAP S/4HANAFinance 1605

SAP S/4HANA 1709 Planned for: Q4/2017

SAP Simple Finance, on-premise edition

1503

SAP S/4HANA 1709 Planned for : Q4/2017

SAP Simple Finance, on-premise edition

1503

SAP S/4HANAFinance 1605

available since: Q2/2016

2

Update DB to SAP HANA 2.0 and Installation of S4CORE

Software

Installation of sFINSoftware (Upgrade)

System Conversion fromSAP S/4HANA Finance to SAP S/4HANA

Upgrade within theSAP S/4HANA product family

Start Release Target Release Availability Remarks

1

2

3

SAP S/4HANAFinance 1605

SAP HANA 2.0

SAP S/4HANA 1709

Update DB to SAP HANA 2.0 and Installation of S4CORE

Software

SAP S/4HANA 1610 SAP S/4HANA 1709 Planned for:

Q4/2017

Update DB to SAP HANA 2.0 and Installation

Software (Upgrade)

4

SAP S/4HANA, on-premise edition 1511

SAP S/4HANA 1709 Planned for: Q4/2017

Update DB to SAP HANA 2.0 and Installation

Software (Upgrade)

5

4

5

NOT SUPPORTED

System Conversion or Upgrade with HANA 2.0

SAP HANA 1.0

SAP S/4HANAversion X

SAP HANA 2.0

SAP S/4HANAVersion X

SAP HANA 2.0

SAP S/4HANA 1709

SAP HANA 1.0

SAP ERP 6.0

SAP HANA 2.0

SAP ERP 6.0

Step 1: Database Upgrade

Step 1: Database Upgrade

Step 2: Conversion

Step 2: Upgrade

System Conversion Technical Process

Application specific follow-up activitiesApplication specific follow-up activities

Database migration

Software update

Data conversion

Custom code preparation

Preparation phase Realization phase

System requirementsSoftware Update Manager (SUM)

Unicode conversion

Simplification List

Cross-application & application specific preparation activities

Maintenance planner

Pre checks Custom code preparation

**) incl. migration of FI Customizing and Data

*) incl. preparation of financial data

• 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 browsethe Simplification Items.

• Also other products (e.g. BW/4HANA) aregoing to join the Simplification Item Catalog.

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

1709 will still be available as PDF document.

Simplification Item Catalog

Application specific follow-up activitiesApplication specific follow-up activities

Custom code preparation

Preparation phase Realization phase

System requirementsMaintenance

plannerPre-Checks

Software Update Manager (SUM)

Custom code preparation

Customer-specific Simplification ListS-Item Title Area Relevancy Business Impact Note

COST ELEMENTS FIN - Controlling 2270419

Currencies in Universal Journal FIN - General 2344012

Business Partner Approach Master Data 2265093

… … …

Pre-CheckThe pre-check framework will be delivered via one SAP Note and all coded pre-check classes will be delivered with one TCI Note (Transport-Based Correction Instructions)

Pre-Check

Report

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

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.

Pre-Checks

Simplification List and Pre-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

like the SAP Readiness Check for SAP S/4HANA)

For more information see SAP Notes

• 2399707

• 2418800

Simplification Item Checks

S/4HANA READINESS CHECK

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

Simplification items• Simplification Items represent application or

architecture changes in comparison to ERP

• About 470 Simplification Items exist for S/4HANA 1610

• They are grouped by business priority (e.g. Core Finance) and industry, respectively

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

Recommended Fiori Apps• Fiori apps recommended based on the

transaction usage history in the evaluated system

Transactions• SAP GUI transactions replaced or deprecated in

SAP S/4HANA, such as Classic MM-PUR GUI transactions

Readiness Check Coverage

Migration Cockpit / -Modeler

Data Migration Options

• Part of SAP S/4HANA Cloud and on-premise solution

• Supports customers with the New Implementation scenario

• Included in SAP S/4HANA license

• Tool of choice for SAP S/4HANA Cloud

New Implementation

SystemConversion

LandscapeTransformation

On-Premise

S/4HANA Cloud

On-Premise

On-Premise

S/4HANA Cloud

ERP System

ERP SystemRegion A

ERP SystemRegion B

ERP SystemRegion C

SAP S/4HANA

Third-partySystem

Migration Cockpit

S/4HANA Migration Cockpit Overview

Migration Cockpit

Content

Single point of entry

Guided procedure

Data selection

Data transformation

Monitoring

Logs

Documentation

Process Data load

Object Modeler

Files

Data Provisioning

API-based Extract

Third-partySystem

ERP System

*

* Only in On-Premise version

Preconfigured migration objects and mapping

</> Integration of custom objects

Data validation

Generation of migration programs

On-Premise

S/4HANA Cloud

S/4HANA Migration Cockpit – Cloud 1708 / On-Premise 1709

• 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

Migration Template for G/L Open ItemsOverview Migration Objects

Pre-configured Migration Content

1. Select Migrate Your Data from the Guided Configuration menu 2. Create a migration project

Migration Guidance

3. Select the relevant migration objects

4. Generate a file template for the selected 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.

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 Guidance

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 theSAP S/4 HANA Migration Cockpit

Available for On-Premise and private cloud

Migration Object Modeler – for Custom Data Integration

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 – Source 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 – Target Structures

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 – Structure 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

Migration Object Modeler – Field Mapping

• 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

Planned Pre-Configured Business Objects – Cloud 1708 / On-Premise 1709

Questions and Answers