Döhler’s Lessons learned during Upgrade to SAPS/4HANA 1909

Winfried Winterstein, Head of SAP Technology

Global Customer COE & Support Info Day

Sep-2016

2

Agenda

01 Döhler: Company Overview, Current SAP Landscape

02 Project Overview, Highlights and Challenges

03 Lessons learned

3

01Döhler: CompanyOverview, Current SAPLandscape

4

Döhler is a global producer, marketer and provider ofNatural Ingredients, Ingredient Systemsand Integrated Solutionsfor the food and beverage industry.

5

>7,000dedicated employees

>750R&D experts

Customers in

>130countries

>1,000,000MT of products

>5,000different raw materials

>15,000Applications in the market

>2bn USSales

>22,000customers

6

Always closeto our customersproduction sites

>455

7

Current SAP System Landscape (Boxes View)As of September 2020

Business Systems

ERP(S/4HANA)

EWM

HR

BW on HANA CE

EnterprisePortal

(Intranet)

Enterprise Portal(Extranet)

Jam(internal)

FI/CO SD

PP/PI QM

EAM PLM

MM

BCS

BPC

[y] Marketing

Success Factors

Jam(external)

RD

Celonis ProcessMining

WM

AnalyticsCloud

LeonardoIoT

Ariba

PS

LMPC SER

Vistex Allevo

TM EWM

CM

Supporting Systems

GTS

AdobeDocumentServices

NWDI

CloudConnector

SLD

SolutionManager

ProcessIntegration

Cloud Platform(SAP CP)

IAS

WebDispatcher

CPI

IPS

HANA Cockpit

Front-EndServer

LandscapeManagement

Secure LoginServer

Portal

IdentityManagement

ABAP TestCockpit

CUA(SolMan)

Running System

System Implementation

System Decommissioning

aATP advanced Availability To PromiseBCS Business ConsolidationBO Business ObjectsBPC Business Planning and ConsolidationC4C Cloud for CustomerCE Composition Environment (Java)CIG Cloud Integration Gateway (Ariba)CO ControllingCPI Cloud Platform IntegrationCUA Central User AdministrationDDMRP Demand Driven ReplenishmentEAM Enterprise Asset ManagementEWM Extended Warehouse ManagementFI FinanceGB Guided BuyingGTS Global Trade SystemIAS Identity Authentication ServiceIBP Integrated Business PlanningIPS Identity Provisioning ServiceLBN Logistics Business NetworkMII Manufacturing Integration and IntelligenceMM Materials ManagementNWDI NetWeaver Development InfrastructureP2O Purchase to OrderPA Predictive AnalyticsPCM Product Content ManagementPLM Product Lifecycle ManagementPP/PI Production Planning / Process IndustryPP/DS Production Planning / Detailed SchedulingQM Quality ManagementSOP Sales and OperationsSD Sales and DistributionSLD System Landscape DirectorSLP Supplier Lifecycle and PerformanceSOP Sales & Operations PlanningTM Transportation Management

CIG

Enable Now

Recruiting Onboarding

Compen-sation

Perform. &Benefits

Learning Succession& Develop.

C/4HANA

Commerce Cloud

Store PCM

Sales Cloud

Data Hub

P2O GB

ABAPIBPMDG

EmployeeCentral

C4C

APIMgmt.

MII

Cloud Platform(SAP CP)

CashApp LBN

aATP ePPDS

GR/IRReconc.

SOP

DDMRP

Demand

ConcurExt. Fact.Kyma RT

BW/4HANA

Work Zone

SignatureMgmt.

Customer DataCloud

(Consent, Identity, Profile,B2B Add-on)

Supply ChainControl Tower

Response& Supply

8

02Project Overview,Highlights andChallenges

9© DÖHLER

Intelligent Enterprise JourneyWhere we came from, where we are going to

1994

First SAP R/3Go-Live

Suite OnHANA

2016

S/4H1610

2017

S/4H1709

2018

C4CCPI

2019

S/4H1809

Several upgrades(all brownfield)

Cash App

Embedded EWM

2020

S/4H1909

Embedded TMAriba

SACMDQ

today

SFSF

SCP

ePPDSMDGStandalone S/4H EWMData HubIBP

10© DÖHLER

• 2016• SAP ERP running on MaxDB @ Döhler• SAP go-to solution for ERP is S/4HANA• Management decision to go for S/4HANA

• Move towards SAP go-to solutionè leverage HANA, new data model, new functions

• Brownfield approach: project duration too long for fastchanging industry, reuse of custom development

• Perform process redesigns on new data model• Evaluation of S/4H 1511

• Too many gaps, no logistics simplifications, project• Decision: Go two-step approach

• Replace MaxDB by HANA

• 2017• System conversion to S/4H 1610

• perform mandatory adjustments for system conversiononly, improvements in follow-up projects

Why S/4HANA?Situation at DÖHLER before decision was taken for SAP S/4HANA

• 2018• Upgrade to S/4H 1709

• Drivers: Implement embedded TransportationManagement (went live for one site already), …

• 2019• Upgrade to S/4H 1809

• Drivers: Implement embedded Master Data Quality,…

• 2020• Upgrade to S/4H 1909

• Drivers: MDQ for Business Partner, stand-alone S/4HEWM integration, gCTS, Target-driven Formulation(RD)

• Stand-alone embedded EWM based on S/4H 2020(planned for Q4)

• 2021• Upgrade to S/4H 2020 (planned)

11

S/4HANA 1909 UpgradeTight project schedule – go-live postponed by 1 month due to COVID-19

Sandbox

6 weeks

Code Conversion

3 weeks

Integration Test

1.5 weeks

UAT

2 weeks

Cut over /go live

1 week

Hyper-care

2 weeks

Nov-Dec.`19

Feb / Mar‘20

Mar`20

Apr`20

Apr`20

2+1 months

12

Project Facts and Figures (2020, 2017)Project executed mainly with internal IT resources*

Production sites

32 / 15 SAP

Tester worldwide

220 Months project duration

6

SAP user worldwide

4.000

Internal IT Consultants involved

38

Coding issues

5.350

Functional code changes

150 Custom code objects

33.000

Lines of custom code

3.700.000 External resources (2017):• S/4HANA Customer Care / RIG• SAP consulting for impl. of SAP CCS Condition Contract Settlement• External partner for automated custom code conversion

2.800

2 (net)

45 19

140

4.100

64.700.000

41.000

40

13

S/4H 1909 System Upgrade System LandscapeOptimized Set-up for fast upgrade

Maintenance(S/4H 1809

FPS 02)

Release(S/4H 1909

FPS 01)

Master(ERP, EWM, BW, FES)

Retrofitmandatory

BW1

SharedassignmentATC

Server

Batch importduring cut-over

Satellite Systems:• Comp. Env.• Intranet• HR• Hybris Commerce• Scanning: SER• Optical Archive• ADS• ZBV• PI / CPI (incl. SETS)• Felten• Aucotec• ORSoft• AKI (OMS)• AS/400 (NL)• Simulation-SW for EWM• LIMS (QM)• C4C• MII• Hybris Marketing• Hype• …

ERP

EWM

BusinessWarehouse

Front-EndServer

Direct transports S/4H(only for emergencies)

Note• Test landscape (S/4, BW, EWM, FES) will be copied from production• There is no maintenance test landscape

Overall topics• Refresh of cloud test tenants (C4C, Ariba, LBN,

Commerce (Azure, Shop))

14

S/4HANA Custom Code ConversionSAP ERP @Doehler since 1994 and high amount of custom code

Custom Code§ 41,000+ custom objects (2016: 36,000)

§ 4.7+ Mio LoC (2016: 3.9)

S/4HANA 1610Code Check§ 5.350 non-functional

“errors”, 900adjustments needed(S/4HANA & HANA CodeCompliance)

§ External tool canautomate / remediate allnon-functional issues

§ 150 functional gaps tobe analyzed

Suite on HANACode Check§ 200.000+ almost 100%

issues resolved in 2weeks (automated)

Custom code @Doehler

2016

2017

S/4HANA 1709Code Check§ 850 S/4H code

compliance issuesresolved

§ 9.500 pseudocommented inserted forfalse-positive entries inATC/SCI

§ 350 HANA codecompliance issuesresolved

2018

S/4HANA 1809Code Check§ 5200 findings

§ 4200 carry-overs(mostly falsepositives, partlymitigated by pseudocomments)

§ 1000 new§ 130 simplification-

driven

§ 370 adjustmentsperformed

2019

S/4HANA 1909Code Check§ 4126 findings

§ 2190 carry overs§ 1938 new§ 350 simplification

driven

§ 6 adjustmentsperformed forsimplifications

§ 52 Prio 1 adjustmentsperformed overall

§ 39 objects marked fordecommissioning

2020

15

03Lessons learned

16

• Simplification is not only simplification but change!• Categorization of our findings

• Change of existing functionality• Examples: Extension of material number length, Business Partner

• Functionality not available anymore• Need to check for functional equivalent• Examples: SAP FI-AR-CR Credit Management, SAP SD Rebates / Bonus

• Non-strategic function• Need to check for functional equivalent (midterm)• Example: SAP PP-PI-PCM Production Campaign Management

• CHECK à Some old transactions, reports, tables are still existing and useable – but needs to be alignedwith SAP how long that will be supported (compatibility scope till 2025 SAP note 2269324)

• WARNING à Some tables incl. content are still available but will not be updated anymore with S/4HANAfunctions

S/4HANA overallSimplification list

17

• S42S4 Upgrade comparable to Enhancement Package Upgrade in ERP times

• Reduced time for code conversion and functional change

• No additional upgrade tests for cut-over preparation (just sandbox, dev, test)

• No housekeeping in Finance needed upfront

• New simplifications to be considered (but limited amount)

• Business downtime reduced from 48 to 34 to 29 to 26 hours

• False-positives in custom code checks eliminated with pseudo comments

• Duration: 2 months preparation plus 3 (2) months for main project

• Add-on certification for 1709 to 1909 also critical

• still not consistent from SAP partners

Updated Experiences based on 1709, 1809 and 1909 Upgrade

18

• Leverage new functionality• Within S/4H (embedded TM & EWM, aATP, ePPDS)• Together with SCP services (Cash App, LBN, GR/IR Reconciliation)• UI side (Fiori apps provided, Fiori Launchpad & SAPUI5 framework enhancements)

• Limit functional gap between upgrades• Use also for yearly refresh of test landscape• Upgrade perceived as standard project per year• People are more interested in optimizations since frequency of upgrade projects is clear

Drivers for yearly UpgradesRun upgrade project with a factory approach

19

• Leverage Readiness Check• Currently deactivated for S42S4 upgrades from SAP

• Test Automation• User Interfaces• Interfaces via Cloud Platform Integration

• Code Quality – in general, to decrease effort during upgrade• Leverage ATC

• incl. Clean Code (s. GitHub)• Roll-out Fiori UIs

• Could use recommendations from Readiness Check…

Planned Improvements for S42S4 Upgrades