migration to s/4hana -...

CUSTOMER

Dragoljub Ljubičić, SAPDecembar, 2017

Migration to S/4HANA

2CUSTOMER© 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀ

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 serviceor subscription agreement with SAP. SAP has no obligation to pursue any course of business outlined in this presentation or any relateddocument, 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 andfunctionality are all subject to change and may be changed by SAP at any time for any reason without notice. The information in thispresentation is not a commitment, promise or legal obligation to deliver any material, code or functionality. This presentation is providedwithout a warranty of any kind, either express or implied, including but not limited to, the implied warranties of merchantability, fitness for aparticular purpose, or non-infringement. This presentation is for informational purposes and may not be incorporated into a contract. SAPassumes no responsibility for errors or omissions in this presentation, except if such damages were caused by SAP’s intentional or grossnegligence.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 their dates,and they should not be relied upon in making purchasing decisions.

Disclaimer


S/4 introduction

Overview Transition Scenarios

System Conversion

Agenda

S/4HANA introduction


Things are different with SAP S/4HANA

SAP S/4HANA Enterprise Managementis SAP’s next-generation Digital Core

§ Innovative in-memory database§ New architecture and data models§ Renewed applications§ New UI technology§ Cloud & on-premise deployment models§ Natively integrated

SAP S/4HANA is a new product line. The classical SAP Business Suite & SAP ERP is aseparate product line and will still be available.


SAP S/4HANA Architecture differs from the classical Business Suitearchitecture

Transactional and master data

Materialized aggregate, history and indextables

Finance

Inventory Management

Material Ledger

Sales & Distribution

� Data structures(Compatibility provided through Core Data Services)à Simplified Data Model

� Application re-design according toà Principle of 1à Segment of 1à Lot Size of 1à Live & at scale

� Launchpad / SAP Fiori(SAPGUI for Windows still available for compatibility reasons !!!)


SAP S/4HANA release strategyDefinition of deliveries and possible 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 pathAlternative path (as an example)

SAP Guided Beta programMaintstream Maintenance – Feature Packages (FPs)Maintstream Maintenance – Support Packages (SPs)

SAP ERP System

possible transition paths

https://support.sap.com/content/dam/support/en_us/library/ssp/release-upgrade-maintenance/maintenance-strategy/sap-releasestrategy-and-sap-portfolio-overview.pdf

Overview Transition Scenarios


Transition to SAP S/4HANAThree different approaches to move to SAP S/4HANA

SystemConversion

SAP S/4HANAOn-Premise

SAP ERPSystem

SAP S/4HANA

NewImplementation

SAP S/4HANACloud

SAP ERP orThird-partySystem

LandscapeTransformation

ERP SystemRegion A

ERP SystemRegion B

ERP SystemRegion C

SAP S/4HANA

New implementation / re-implementationReengineering and process simplification based onlatest 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 platforme.g. consolidation of current SAP Business Suitelandscape into one global SAP S/4HANA system orselective data migration based on legal entities

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



https://blogs.sap.com/2017/07/06/how-to-find-my-path-to-sap-s4hana-understand-the-available-transition-options/


Transition to SAP S/4HANASystem Conversion

Scenario descriptionA complete technical in-place conversionof an existing SAP Business Suite ERPsystem toSAP S/4HANA (Database, SAPNetWeaver and Application transition inone step).

Why would you choose thisoption?• Bring your existing business processes

to the new platform.• Keep your investment in custom code• Mitigate the risk and investment of a big

bang conversion project by reducing thescope of the transition project to a puretechnical conversion project, and adoptnew innovations at your speed at a laterpoint of time and in a phased approach.

(SAP GUI) / SAP Fiori

SAP HANA

SAP S/4HANA Core

SAP GUI

AnyDB / SAP HANA

SAP ERP Core

Software UpdateManager (SUM)with DatabaseMigration Option(DMO)

What How

In-place technicalconversion

tool-based technical conversion process of a SAP BusinessSuite ERP system to SAP S/4 HANA using SAP SoftwareUpdate manager (SUM);Downtime minimizing options available

*

*SCN Blog: SAP S/4HANA System Conversion – At a glance

SAP ERP 6.0 (any EHP level)


Transition to SAP S/4HANANew Implementation

Scenario descriptionNew implementation of SAP S/4HANA, e.g. forcustomers migrating a legacy system, also knownas “greenfield” approach.

Why would you choose this option?Customers planning to migrate• A non-SAP / 3rd-part legacy system,• A good option for a SAP System, which may be

• Of an older release and/or• Is highly customized/modified and/or• Does not meet the system requirements for

a technical system conversionBenefits for the customer are• Reengineering and process simplification

based on pre-configured business processes• Rapid adoption of new innovations in a

standardized manner

Steps How

Install SAP S/4HANA Software Provisioning Manager

Initial data load fromsource system

• SAP S/4HANA Migration Cockpit• SAP Data Services (SAP DS)both with best practice migration content

https://blogs.sap.com/2016/11/02/sap-s4hana-system-conversion-at-a-glance/


Scenario descriptionCustomers who want to consolidate theirlandscape or to selectively transform datainto a SAP S/4HANA system.

Why would you choose this option?

• Value-based migration: selective datatransformation allows a phased approachfocusing the first SAP S/4HANA migrationphase on parts of the business with highestROI and lowest TCI

• Agility: stay on current business processesbut move gradually to SAP S/4HANAinnovations à Move to SAP S/4HANA atyour own pace

• TCO reduction: system and landscapeconsolidation with harmonized/simplifiedprocesses and unified master data lead tolower cost of operations

Transition to SAP S/4HANALandscape Transformation

Technical migration on table level using pre-configured LT transformation solutions

ConsolidationSystem Merge of multiple source systems into one SAP S/4HANAsystem or transfer of clients into existing SAP S/4HANA system(build-up multiple client system)

Selective DataTransformation

Migration of business units/single entities such as company code

Re-platforming scenarios, e.g. PP/DS

Real-time reposting

Implementation ofcentral finance *

Real-time reposting of financial transactions into Central Financeinstance, e.g. to enable centralized reporting using SAP S/4HANA(synchronization of systems / side-car scenario)

Legacy

M I G R A T E Y O U R D A T A

select – transform on the fly - insert

*) SAP S/4HANA for central finance foundation (Central Finance)

On-Premise

System Conversion


SAP S/4HANA system conversionOverview technical process steps

Application specificfollow-up activitiesApplication specificfollow-up activitiesCustom code preparation

Preparation phase Realization phase

Systemrequirements

Software UpdateManager (SUM)

Simplification List

Cross-application & application specific preparation activities

Maintenanceplanner Pre checks Custom code preparation


System Conversion Paths (basically)

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

The transition to SAP S/4HANA doesnot require the source system to bealready on SAP HANA Database

Note 2: System has to be an AS ABAP-only system. Dual-stack systems (AS ABAP andAS Java combined in one system) are not supported for the conversion. If your system isas 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 1709should first update the database from SAP HANA 1.0 to SAP HANA 2.0 and then do the systemconversion (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

SAP S/4HANASystem Conversion – Transition Paths Overview (1/2)


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

33

11

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


available since:Q2/2016

22

Update DB to SAP HANA 2.0and 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 HANA 2.0

SAP S/4HANA 1709

Update DB to SAP HANA 2.0and Installation of S4CORE

Software

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

Q4/2017Update DB to SAP HANA 2.0

and InstallationSoftware (Upgrade)

4

SAP S/4HANA, on-premise edition 1511

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

Update DB to SAP HANA 2.0and Installation

Software (Upgrade)5

44

55

NOT SUPPORTED

SAP S/4HANASystem Conversion – Transition Paths Overview (2/2)


Size is importantMinimize & optimize data volume of SAP system landscapes & control data growth

Use SAP DVM: Data Volume Management Work Center in SAP Solution ManagerArchived Data are still accessible after conversion; data conversion happens during access to archive

For System Conversion:Focus on "relevant" tables

Trim down source• Archive data• Check data quality

Trim target operation• Consider data aging• Monitor data growth

ABAP sizing reports for move to SAP HANASAP Business Warehouse: SAP Note 1736976iMemory sizing report for SAP Business Suiteand SAP S/4HANA: SAP Note 1872170i

AnyDB


SAP Fiori front-end serverDeployment options SAP S/4HANA

https://eaexplorer.hana.ondemand.com/

https://launchpad.support.sap.com/






System requirements Software UpdateManager (SUM)

Simplification List




SAP S/4HANA system conversionMaintenance Planner for System Conversion

Ø The Planning tool (successor for MOpz)for update, upgrade, migration, conversion, installationhttp://apps.support.sap.com/sap/support/mp

Ø Preparations for Conversion: Check and Plan

Ø Checking Source Systemconcerning AddOns, Business Functions, Industry SolutionsLicense for SAP S/4HANA not required for check

Ø Planning for ConversionProvides Software Archives & Stack.xmlBackend and Frontend Server (FIORI) are considered

Ø Un-installation of AddOns can be planned now;3rd Party AddOns may have to be checked separately

http://service.sap.com/sap/support/notes/1736976

http://service.sap.com/sap/support/notes/1872170


SAP S/4HANA system conversionSimplification list

Ø List contains Simplification Itemsdescribing the change with SAP S/4HANAon solution and on transaction level

Ø Activities on Application Level requiredbefore, during, and after conversion

Ø Available as PDF & XLS, and as catalogNot all items are relevant for all customersSee help.sap.com/s4hana, SI catalog:https://launchpad.support.sap.com/#/sic

Ø List is foundation for other tools:Maintenance Planner, Pre-Checks,Custom Code Migration Worklist,SAP Readiness Check

https://eaexplorer.hana.ondemand.com/


SAP S/4HANA system conversionSimplification Item Catalog example


SAP S/4HANA system conversionSimplification Item Checks

n Replace the previous Pre-Check Framework (checkclasses) to be run before the conversion to SAPS/4HANA for target SAP S/4HANA 1709

n Can (and should) be run by the customers manually inadvance and will be run by SUM when starting theconversion

n Check if serious issues exist in the system which couldcause the system conversion/upgrade to fail.

n Compared to the previous Pre-Check Framework theSimplification Item Checks

§ Are easier to implement (2 SAP notes instead of >50 SAPnotes)

§ Support not only system conversions to SAP S/4HANA, butalso upgrade within SAP S/4HANA

§ Provide improved handling of the check results (e.g. exceptionhandling)

§ Also include relevancy checks for Simplification Items(same like the SAP Readiness Check for SAP S/4HANA)

For more information

Follow this link to SAP Notes 2399707

Follow this link to SAP Notes 2502552

http://apps.support.sap.com/sap/support/mp


SAP S/4HANA system conversionCustom code related process

Application specificfollow-up activitiesCustom code preparation


System requirements Maintenanceplanner Pre checks Software Update

Manager (SUM)

Remove obsolete codebased on Usage Procedure

Log (UPL/SCMON)

Custom codeevaluation

Adapt custom code to SAPHANA and SAP S/4HANA

related changes

Adapt modifications inSPDD/SPAU

Functionaladaptation

Custom code preparation Application specificfollow-up activities

Check SAP HANA relatedchanges (NO ORDER)

Check SAP S/4HANArelated changes

(Simplification DB)

SAPS/4HANA

checks

Tune performance ofcritical database queries

Performancetuning



Transparency with Custom Code Lifecycle Management(CCLM)§ Monitor usage of your custom code via SCMON (recommended) or

Usage Procedure Logging (UPL)§ Use usage data to prioritize your custom code efforts

Remove Waste with CCLM decommissioning cockpit§ Remove unused code before the S/4HANA conversionà Link

Custom Code Lifecycle Management tools


ABAP Test Cockpit – One tool forall quality aspects

Central infrastructure for functional,performance, security code checks

Uniform quality criteria for your whole systemlandscape

Quality assurance processes minimize errorsin productive systems

Smooth migration of ABAP code to SAPHANA and SAP S/4HANA

Extensible infrastructure for customerspecific checks

Security Checks (CVA)

SAP HANA Checks

Standard Code Inspector checks incl. SLIN

Customer specific checks

ABAP Unit Tests

SAP S/4HANA Checks

ABAPTest

Cockpit(ATC)




Setup remote ATC checks for SAP S/4HANA

1) Setup remote ATC in central system andimplement the SAP Note 2436688

2) Download the newest version of theSimplification Database from SAP ServiceMarketplace (SAP Note 2241080)

3) Install the Simplification Database on thecentral check system (transaction SYCM)

4) Run ATC with check variantS4HANA_READINESS_REMOTE

5) Analyze the ATC result list

Central Check System (SAP_BASIS 7.51)

CheckedSystem A(>=7.00)

CustomerCode

CheckedSystem B(>=7.00)

CheckedSystem C(>=7.00)

RFC RFC RFC

ABAP Test Cockpit (ATC)

Remote Stubs

CustomerCode

CustomerCode

SimplificationDB


ATC checks for SAP S/4HANA - example

Or use ATC in ABAP Development Tools forEclipse:

https://blogs.sap.com/2017/04/06/abap-call-monitor-scmon-analyze-usage-of-your-code/

http://scn.sap.com/docs/DOC-60525


Simplification example§ Domain MATNR changed from 18 to 40 characters

Issue§ Custom data elements, e.g. CHAR18 come in conflicts with MATNR

of 40 characters:– Data lost– Type conflicts– Length conflicts at comparison– Length conflicts at concatenation

Solution§ Use domain MATNR instead of custom data elements

Functional adaptation exampleMaterial number field length extension


Issue§ The sort order of a SELECT statement is not defined§ But: typically your code relies on the implicit sort order of the

database vendor§ This leads to issues (functional incorrectness) when you switch

database

Solution§ Add an ORDER BY clause to the SELECT statement or sort the

internal table before the READ

Functional adaptation exampleCode that relies on implicit sort order


You should§ Collect productive usage and SQL execution data

– Switch on SCMON (recommended) or UPL– Switch on SQL Monitor

§ Create new code “S/4HANA ready”– Setup remote ATC– Use S/4HANA ATC checks in your dev system

§ Make your developers “S/4HANA ready”– Gain practical skills in ADT in Eclipse– Get familiar with S/4HANA must-have

technologies (e.g. CDS, BOPF, OData)

You could§ Start to adapt your code in your dev system

– Convert to Unicode– Fix SAP HANA ATC findings (e.g. NO ORDER)– Optimize performance critical SQLs found in

SQL Monitor

§ Estimate custom code adaptation efforts– Run S/4HANA ATC checks for all custom code

What you can do today in your SAP Business Suite landscapeGet your custom code prepared for SAP S/4HANA


SAP S/4HANA system conversionNew SAP Readiness Check

Applicationspecific follow-up

activities

Application specificfollow-up activities

Database migration

Software update

Data conversion

Custom code preparation


Systemrequirements

Maintenanceplanner Pre checks Software Update

Manager (SUM)

Unicodeconversion

Custom code preparation

SAP Readiness Check

� A holistic system analysis is the foundation forfurther planning steps toward a successful andsmooth SAP S/4HANA system transition.

� The SAP Readiness Check for SAP S/4HANAsummarizes the most important aspects of theconversion in an easily consumable way.


§ Execute the SAP Readiness Check for SAPS/4HANA:

• Via your local SAP Solution Manager system(recommended) as of 7.1 SP12 or 7.2 SP3

• Via manual file upload to the cloud application

§ An analysis should be run as early as possibleto get a full understanding of the related tasksand efforts to support a smooth transition

§ The SAP Readiness Check analyzes softwareprerequisites, infrastructure requirements, SAPS/4HANA functional implications, necessarycustom code adaptations and application datamigration requirements already months beforea project starts

SAP S/4HANA system conversionSAP Readiness Check Run





System requirements Software UpdateManager (SUM)

Simplification List



Database migration

Software update

Data conversion


SAP S/4HANASystem conversion: technical Conversion by Software Update Manager (SUM)

Ø Technical Conversion executed by Software Update Manager (SUM)

Ø Conversion tasks for SUM:

– Database migrationProvide SAP HANA database (if required)

– Software updateProvide new applications and new tables

– Data conversionConversion of table content to new data model SUM

PAS Host

AnyDB

Source DB Host Target DB Host

SUM

PAS Host

Source = Target DB Host


SHD Instance

System Conversion procedure (source is non-HANA DB)

SourceKernel

Application Data

PRD REP

SHD REP

Application Data

Source DB Host SAP HANA DB Host

PAS HostPRD Instance

SHD KernelR3load

TGT KernelR3load

PAS

SUM

TGT REP

Uptime

Ø Pre-checks

Ø SHD Repository created

Ø SHD Repository migrated

Downtime

Ø Application Data migrated

Ø System update

Ø Application Data converted

Ø FI Data converted (IMG)

SUM activities


3 Approaches for System Conversion to SAP S/4HANA

� Standard approachusing Software update Manager (SUM)with several optimizations

� Downtime optimized System Conversionuses SUM as well, and reduces downtimeby moving data conversion partly to uptime

� Near Zero Downtime Technology (NZDT)Customer specific approachallows further reduction of downtimebased on a service project

Dow

ntim

e

Effo

rt

Decision about approachdepends on several factorsand should be taken after amigration planning workshoptogether with SAP.Downtime-optimized Conversion:currently only for source db non-HANA

Approach Path: 1503 1605 1511 1610 1709*

Standard √ √ √ √ √Downtime Optimized - piloted - piloted piloted

Customer Specific √ √ - √ √


Project planning aspects - High-level example project plan

QA Conversion

Purpose� Establish SAP HANA

QA environment� Enhance cookbook� Testing environment:

− Integration− Functional regression− Operational readiness− User acceptance

� Business FunctionTesting ofnew/adaptedprocesses

DEV Conversion

Purpose� Establish SAP HANA

dev environment� Refine cookbook

Note� Upgrade &

conversion steps willdiffer from production

� Perform mandatorycode adaptations andsimple codeoptimizations

� Perform post-conversion steps toadapt businessprocesses

PRD to “Sandbox”

Purpose� Test upgrade and

migration steps withcopy from production

� Create upgrade /migration cookbook

� Execute multipletechnical iterations tofamiliarize withprocess

Note� Check business

process requirementsto be performed andperform ABAP codeanalysis, house-keeping before themigration

Cycle 1 Cycle 2 Cycle 3 Cycle 4

PRD Conversion

Purpose� Establish new PRD

environment� Utilize downtime-

minimized approach

Note� Execute end-to-end

business downtimeprecisely as definedwithin cutover plan

� Execute technicalsteps precisely asdefined in cookbook

� Plan codeoptimization projects

Conversion Phase

Cycle 5

PRD to “Sandbox”

Purpose� Mock cutover� Final dress rehearsal� Optimize & validate

E2E businessdowntime

� Finalize & validatecookbook

� Finalize & validatecutover plan

� Testing environment:− Infrastructure testing− Post-cutover

operationalperformance testing

Cycle 4

Hvala.Contact information:

Dragoljub LjubičićSenior Technology [email protected]

migration to s/4hana -...

Documents