PUBLIC
Slavisa Lecic, S/4HANA Customer Solution Advisor
25.06.2020
Join the SAP S/4HANA Movement
2PUBLIC© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ
1. How to start
2. Best practices and references
3. System conversion reference projects
supported by SAP customer care
4. Ongoing projects in our market
5. Q&A
Agenda
3PUBLIC© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ
* Rezultati su dobijeni istrazivanjem tokom prezentacije
How to start
6PUBLIC© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ
1. You should to think
about the future – not
about preserving the past
Current
State Business
Current
State IT
Boundary
Conditions & Principles
Future
State Business
Future
State IT
Roadmap
Future State State Approach – S/4HANA transformation roadmap
2. You should to view
entire situation
3. You should to build an
individual, specific
roadmap
7PUBLIC© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ
Implementation Approach Do not go to SAP S/4HANA via Suite on HANA
Benefits of moving to S/4HANA in one step▪ Smaller / leaner / simpler system that supports growth and future innovations
▪ Operational reporting made easier with delivered embedded analytics and virtual data models
▪ Flexible deployment options (single, multi-tenant, hybrid models)
▪ SAP Cloud platform based extensions for complimentary capabilities
▪ Standard integration delivered with SAP cloud solutions
Best practice and referances
9PUBLIC© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ
SAP S/4HANA Momentum
Increase in
procurement
efficiency
45%Faster
order lead
times
44%Increase in
employee
productivity
75-80%
SAP S/4HANA
Customers
14,100+Live
Customers*
6,100+
Improvement in
ad hoc reporting
capabilities
80%Accelerated
calculation
time for MRP
85%Visibility of
inventory across
all locations
100%
Reduction in
billing process
time
50%
Planning
efficiency
improvement
90%
* Includes Core ERP and LOB Scenarios
10PUBLIC© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ
S/4HANA Projects by Project Type
New S/4HANA customer
68%
Others7%
Re-Implementation
44%
System Conversion
56%SAP ERP customer
transitioning to S/4HANA
25%
PROJECT TYPE
System conversion reference projects
supported by SAP customer care
12PUBLIC© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ
Wholesale Customer, Europe
Customer Profile Project Scope Duration
• Industry: Wholesale Distribution
• Customer is a distribution company with
a focus on the Polyurethane, Coating,
Ink & Adhesive industries. The
company has been distributing
chemicals since 1999.
• Product: S/4HANA On-Premise,
• System Conversion from SAP ERP 6.0 to S/4HANA 1909 FPS00
SAP ERP Scope: xxx
• S/4HANA Scope: xxx
32 company codes
9 sales org
26 plants
SD / MM / FICO / PP
• Project Duration:
7 months
• Project Start Date:
10.10.2019
• Go-Live Date:
11.05.2020
Project Top Issues & Critical Success
Factors
Business Challenges & Expected Customer Benefits
• Unexpected finance data
inconsistencies
• Expected customer benefit: reporting
13PUBLIC© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ
Power generation, Greece
Customer Profile Project Scope Duration
• Industry: Energy company
• Customer is a Group of companies
engaging in the production, supply and
trading of electricity. Having started its
operations in 2000, it is now supported
by three large energy Groups
• Product: S/4HANA On-Premise
• System Conversion from SAP ERP [release] to S/4HANA [1809 + FPS02] business
suite for Utilities
S/4HANA Scope: FI, CO, PS, MM and PM areas, following SAP Activate
methodology
• Fiori Platform
• Project Duration:
6 months
• Project Start Date:
2019-04-23
• Go-Live Date:
2019-10-29
Project Top Issues & Critical Success
Factors
Business Challenges & Expected Customer Benefits
• Customer wants to know the Fiori apps which
they should consider for activation. They have
been recommeded to run Readiness check
report or use Fioriapp library to determine the
same.
• Customer wants to activate more Fiori apps
but partner is not willing to activate. Finally,
partner has agreed to activate 147 apps.
• The first 1809 version + Fiori user experience
• First step with 147 apps to be activated for the user
14PUBLIC© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ
Power generation, Greece
Fiori Details Number of System Conversion Cycles Business Downtime
• Total Number of Fiori Apps: 147
• Analytical: 36
• Transactional: 100
• Factsheets: 11
• Custom: 45%
• SAP Business Client Used: Yes
• Fiori Deployment: Embedded
• Sandbox: xxx
• Development: HRD
• Quality Test: HRQ
• Mock/Dress Rehearsal: xxx
• Production: HRP
• SUM Technical Downtime Duration: xxx
• Finance Migration Duration: xxx
• Transport Duration: xxx
• 25 (including 1 request of SPDD
imported in the shadow system) :
Time needed, roughly 1/2 hour
• Number of Transport Requests
imported in the converted system
in the converted system = 19 :
Time needed, roughly 15 minutes.
System Location Software Update Manager Details
• Customer | <Partner Name> Hosting • Downtime Optimization Approach: Standard | Downtime Optimized | NZDT
• System Move Option: Yes | No
• Data Center Move: Yes from [data center] to [data center] | No
Extension and Integration Details Customer Vendor Integration
• SAP Cloud Platform Used: Yes | No
• List of SAP Cloud Platform Service(s) Used: xxx
• CoPilot Used: No
• Machine Learning Scenarios used: No
• Robotic Process Automation used: No
• WebIDE Used: Yes
• Completed with Conversion Project: Yes
• Number partner: around 3000
• Overlapping Number Ranges in ERP: No
• CVI Duration in SBX: 30 min
• CVI Duration in Prod: 30 min
15PUBLIC© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ
Consumer products, Italy
Customer Profile Project Scope Duration
• Industry: CP
• Revenue: ~ 800M
• Production of cosmetics
• Plants in Italy, Switzerland, USA,
China, Korea.
• Product: S/4HANA On-Premise
• System Conversion from SAP ERP ECC 6.0 to S/4HANA 1809 + SP2
• SAP ERP Scope: FI, CO, MM, WM, SD, PP, PS, APO
• S/4HANA Scope: FI, CO, MM, WM, SD, PP, PS, PPDS
• Other SAP Solutions: None
• Project Duration:
10 months
• Project Start Date:
10/06/2019
• Go-Live Date:
04/05/2020
Productive Users
• # of users: ~ 1.300
Project Top Issues & Critical
Success Factors
Business Challenges & Expected Customer Benefits Hardware
• Top Issue:
• Environment optimization
• Poor network capabilities
• Success factor:
• Direct SAP intervention to drive
environment provider activities
• Business challenge:
• Move from an high personalized and dated system to a new
enabling technology
• Customer benefit:
• Evolution toward a system more open to integration and new
enhancement (eg. EWM implementation)
• HW Provider:
Engineering Spa
• DB Size: 3 TB
• HANA Mem: 1,7 TB
16PUBLIC© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ
Consumer products, Italy
Fiori Details Number of System Conversion Cycles Business Downtime
• Total Number of Fiori Apps: - -
• Analytical: - -
• Transactional: - -
• Factsheets: - -
• Custom: - -
• SAP Business Client Used: No
• Fiori Deployment: Embedded
• Sandbox: 1
• Development: None (created from second Mock)
• Quality Test: None (created from second Mock)
• Mock/Dress Rehearsal: 4
• Production: 1
• SUM Technical Downtime Duration: 30h
• Finance Migration Duration: 12h
• Transport Duration: 3,5h
• Number of Transports: 550
• Validation Duration: 3h
System Location Software Update Manager Details Table Counts (At Cutover)
• Customer: Engineering Hosting
• Hyperscaler: No
• Downtime Optimization Approach: Standard
• System Move Option: No
• Data Center Move: No
• ACDOCA: 188M
• MATDOC: 47M
• MATDOC_EXTRACT: 47M
• PRCD_ELEMENTS: 21M
Extension and Integration Details Customer Vendor Integration Data Volume Management
• SAP Cloud Platform Used: No
• List of SAP Cloud Platform Service(s) Used: None
• CoPilot Used: No
• Machine Learning Scenarios used: No
• Robotic Process Automation used: No
• WebIDE Used: No
• Cloud-like Integration via public APIs: None
• Completed with Conversion Project: Yes
• Number of Account Groups: 38
• Overlapping Number Ranges in ERP: No
• CVI Duration in SBX: 3h
• CVI Duration in Prod: 3h (done before conversion
• Archiving done before conversion: No
• Which Objects: - -
• System Size Before: - -
• System Size After: - -
17PUBLIC© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ
Telco and Retail, Germany
Customer Profile Project Scope Duration
• Industry: Telco & Retail
• Revenue: ~2,93 Billion €
• Product: S/4HANA On-Premise
• System Conversion from SAP ERP 6.0 EHP 8 to S/4HANA 1809 FPS02
• SAP ERP Scope: FI/CO, MM, SD, QM WM, RM-CA
• S/4HANA Scope: FI/CO, MM, SD, QM WM, RM-CA
• Project Duration:
14 months
• Project Start Date:
Nov, 2018
• Go-Live Date:
March-30th, 2020
Productive Users
• # of users: 1100
Project Top Issues & Critical Success
Factors
Business Challenges & Expected Customer Benefits Hardware
• RMCA activated and Retail to be
activated
• CVI: >13M objects (archiving active)
• IBAN-Handling in BP (in particular
IBAN-only)
• ECCS and ACDOCA (Reconcilation)
• get rid of many old legacy systems such as Retail-solution (NON-SAP)
• be able to run Telco IS (RM-CA) and Retail on one platform
• build an E2E platform for their omnichannel business
• enable new UX
• implement new applications (e.g. CAR)
• drive evolvement / evolution of process-centric E2E business processes (instead of
a currently function-centric view / way of working)
• HW Provider: Fujitsu
• DB Size: 1800 GB
• HANA Mem: 1500 GB
• HANA Rev: HANA 2.0
Rev.44
18PUBLIC© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ
Telco and Retail, Germany
Fiori Details Number of System Conversion Cycles Business Downtime
• Total Number of Fiori Apps: approx. 15
• Analytical: 2
• Transactional: 10
• Factsheets: 0
• Custom: 8
• SAP Business Client Used: No
• Fiori Deployment: Hub
• Sandbox: 1
• Development: 1
• Quality Test: 1
• Mock/Dress Rehearsal: 1
• Production: 1
• SUM Technical Downtime Duration: 10:45
• Finance Migration Duration:
• Reconcilation Customizing: 2:00
• G/L Migration 5:25
• Credit Management Migration 1,25
• Transport Duration: 2h
• Number of Transports: 50
• Validation Duration:
• Reconciliation – ca. 3,75 h
• Nacharbeiten – ca. 3 h
• Sanity Checks – ca. 1,5 h
System Location Software Update Manager Details Table Counts (At Cutover)
• On premise (fujitsuTDS Hosting)
• Hyperscaler: No
• Downtime Optimization Approach: NZDT
• System Move Option: No
• Data Center Move: No
• ACDOCA:170 Mio
• MATDOC: 27 Mio
• MATDOC_EXTRACT: 14 Mio
• PRCD_ELEMENTS: 200 Mio
Extension and Integration Details Customer Vendor Integration Data Volume Management
• SAP Cloud Platform Used: No
• List of SAP Cloud Platform Service(s) Used: 0
• CoPilot Used: No
• Machine Learning Scenarios used: Yes / No
• Robotic Process Automation used: Yes / No
• WebIDE Used: Yes | No
• Cloud-like Integration via public APIs: None
• Number of records: 216K vendors and 13M Customers (thereof
10,85M FI-CA with already existing BP)
• Completed with Conversion Project: No (before)
• Number of Account Groups: 12 Vendors , 25 Customers
• Overlapping Number Ranges in ERP: Yes
• CVI Duration in SBX: 1st cycle >24h, 2nd cycle <16h
• in Prod: 4 Partitions (total: 8:20) 1) ref. to notes for details
• Archiving done before conversion: Yes
• Which Objects: CA_BUPA (-10,3M),
FI_FICA (-11,1M) for conversion (permanent
archiving was already active)
• System Size Before: n/a
• System Size After: n/a
19PUBLIC© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ
METANOLSKO-SIRĆETNI KOMPLEKS
Customer Profile3= Project Scope Duration
• Industry: Chemicals
• Revenue: 120 M EUR
Small Serbian Chemical customer north of
Belgrade. The company produces methanol
and acetic acid for the global market – mostly
EU countries and employs a bit over 500
employees.
The company also owns a terminal at a port in
Montenegro.
• Product: S/4HANA On-Premise
• System Conversion from SAP ERP 6.0 (EhP4) to S/4HANA 1809 SP00
SAP ERP Scope: scope included FI, CO, MM, SD, PP, HR, PP, SD
• S/4HANA Scope: aim was to convert to S/4HANA with minimum scope / re-establish
existing situation
• Other SAP Solutions: no
• Project Duration:
3+1 months
• Project Start Date:
30.03.2019
• Go-Live Date:
01.07.2019
Productive Users
• # of users: 70
Project Top Issues & Critical Success
Factors
Business Challenges & Expected Customer Benefits Hardware
Critical success factor was to convert to
S/4HANA with minimum scope / re-establish
existing situation. Now that they are live with
S/4HANA they will proceed to improve the
processes.
Incident 306693 / 2019 / Problem with currency
40 when migrating to S/4 Hana
• Fast and efficiently close books on time, and create financial statements
• Monitor cash flow in real time to manage and maintain liquidity
• Next project phase will include SAP Fiori part and expected benefits from Fiori apps
• HW Provider: Coming
cloud in Belgrade
• DB Size: 130 GB
• HANA Mem: xxx
• HANA Rev: xxx
Ongoing projects in our market
21PUBLIC© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ
• Utility company from Serbia (FI,CO,MM,SD, HR, EAM), 1 legal entity
• Pharma company from Bosnia and Herzegovina (FI,CO, MM,SD, QM, PP, WM) – 1 legal entity
• Pharma company from North Macedonia (FI,CO,MM,SD, PP, QM) – 6 legal entities
Ongoing projects
Contact information:
Slavisa Lecic
S/4HANA Customer Solution Advisor
https://www.linkedin.com/in/slavisalecic/
Hvala