Week 4: Technical Topics and Project Management

Unit 1: Preparing Custom Developments and

Adjustments
Preparing Custom Developments and Adjustments
Custom code tools in the context of SAP S/4HANA

Preparation phase Realization phase

Application-
System Maintenance Custom code Software Update
SI checks Custom code preparation specific follow-up
requirements planner preparation Manager (SUM)
activities

SIMPLIFICA- SOFTWARE
MAINTENANCE UPL /
TION CHECK SYCM UPDATE SPAU/SPDD
PLANNER SCMON
REPORT MANAGER

SIMPLIFICA-
ABAP TEST SQL
TION ITEM
COCKPIT MONITOR
CATALOG

ABAP TEST
COCKPIT

ABAP
DEVELOPER
TOOLS

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 2

Preparing Custom Developments and Adjustments
Custom code process in SAP S/4HANA

Preparation phase Realization phase

Application-
System Maintenance Custom code Software Update
SI checks Custom code preparation specific follow-up
requirements planner preparation Manager (SUM)
activities

Custom SAP Perfor-

code S/4HANA Functional
mance
evaluation checks adaptation
tuning

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 3

Preparing Custom Developments and Adjustments Custom
Evaluating custom code with custom code management tools code
evalua-
tion

There is no need to adapt all objects. Focus on the most critical based on usage and impact.

Transparency with custom code lifecycle management

(CCLM)
▪ Monitor usage of your custom code via SCMON
(recommended) or Usage and Procedure Logging (UPL)
▪ Use usage data to prioritize your custom code efforts

Remove waste with CCLM decommissioning cockpit

▪ Remove unused code before the SAP S/4HANA conversion

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 4

Preparing Custom Developments and Adjustments SAP
Running remote ATC checks for SAP S/4HANA S/4HANA
checks

1. Set Up Central Check System

✓ Apply Notes in Checked Systems Central Check System (SAP_BASIS 7.52)
✓ Connect to Checked Systems
ABAP Test Cockpit (ATC)
2. Download Simplification Database Simplifi-
cation DB
3. Install Simplification Database RFC RFC RFC
4. Run ATC
✓ Variant S4HANA_READINESS_REMOTE
Checked Checked Checked
5. Analyze System A System B System C
(>=7.00) (>=7.00) (>=7.00)
Custom Custom Custom
Code Code Code

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 5

Preparing Custom Developments and Adjustments SAP
Running SAP S/4HANA readiness checks S/4HANA
checks

Simplification use cases

▪ Functionality no longer available SAP S/4HANA checks
▪ Data model changes
▪ Data type changes

SAP HANA use cases

▪ Use of DB vendor specifics (native SQL) SAP HANA checks
▪ DB operations on pool/cluster tables
▪ SELECT/OPEN CURSOR statements
without ORDER BY

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 6

Preparing Custom Developments and Adjustments
Functional adaptation overview Functional
adaptation

Run ATC check with Run ATC check again

Detect and correct errors
S4HANA_READINESS variant and confirm fix

No errors are detected!

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 7

Preparing Custom Developments and Adjustments
Functional adaptation examples Functional
adaptation

MSEG

CI_COBL

MATDOC
1. SAP Note
2240878
2. SAP Note
CI_COBL 2242679

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 8

Preparing Custom Developments and Adjustments Perfor-
Performance tuning and refactoring mance
Tuning

1. Business process
list ranked by total BEFORE AFTER
DB time SELECT SELECT BSEG
BKPF LEFTOUTER
JOIN BKPF
LOOP at LOOP statement is
2. Drill down to the ITAB used in ERP as it is not
possible to use JOIN for …
SQL profile of SELECT JOIN BSEG to
cluster table
report BSEG BKPF in
SELECT
… Statement

3. Navigate to Runtime Runtime

the code Improved!
DB App Front DB App Front

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 9

Preparing Custom Developments and Adjustments
Get your custom code prepared for SAP S/4HANA

You should You can also

▪ Collect production usage and SQL execution ▪ Start to adapt your code in your dev system
data
 Convert to Unicode
 Switch on SCMON (recommended) or UPL
 Fix SAP HANA ATC findings (e.g. NO ORDER)
 Switch on SQL Monitor  Optimize performance-critical SQL statements
▪ Create new code “SAP S/4HANA ready” found in SQL Monitor
 Set up remote ATC ▪ Estimate custom code adaptation efforts
 Use SAP S/4HANA ATC checks in your
 Run SAP S/4HANA ATC checks for all custom
dev system
code
▪ Make your developers “SAP S/4HANA ready”
 Gain practical skills in ADT in Eclipse
 Get familiar with SAP S/4HANA must-have
technologies (e.g. CDS, BOPF, OData)

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 10

Thank you.
Contact information:

open@sap.com
Follow all of SAP

www.sap.com/contactsap

© 2018 SAP SE or an SAP affiliate company. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of
SAP SE or an SAP affiliate company.
The information contained herein may be changed without prior notice. Some software products marketed by SAP SE and its
distributors contain proprietary software components of other software vendors. National product specifications may vary.
These materials are provided by SAP SE or an SAP affiliate company for informational purposes only, without representation or
warranty of any kind, and SAP or its affiliated companies shall not be liable for errors or omissions with respect to the materials.
The only warranties for SAP or SAP affiliate company products and services are those that are set forth in the express warranty
statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional
warranty.
In particular, SAP SE or its affiliated companies have no obligation to pursue any course of business outlined in this document or
any related presentation, or to develop or release any functionality mentioned therein. This document, or any related presentation,
and SAP SE’s or its affiliated companies’ strategy and possible future developments, products, and/or platforms, directions, and
functionality are all subject to change and may be changed by SAP SE or its affiliated companies at any time for any reason
without notice. The information in this document is not a commitment, promise, or legal obligation to deliver any material, code, or
functionality. 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, and they
should not be relied upon in making purchasing decisions.
SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered
trademarks of SAP SE (or an SAP affiliate company) in Germany and other countries. All other product and service names
mentioned are the trademarks of their respective companies.
See www.sap.com/corporate-en/legal/copyright/index.epx for additional trademark information and notices.
Week 4: Technical Topics and Project Management
Unit 2: Considerations Around Sizing, Archiving,
and Data Aging
Considerations Around Sizing, Archiving, and Data Aging
Prepare and Realize phases

Prepare Phase Realize Phase

Run Sizing
Determine Determine a Adapt Data
Run SAP Exercise for
Quick Wins Data Archiving
S/4HANA Embedded
Toward Data Temperature and Data
Sizing Report Analytics and
Reduction Strategy Aging
SAP Fiori

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 2

Considerations Around Sizing, Archiving, and Data Aging
Prepare phase

Prepare Phase Realize Phase

Run Sizing
Determine Determine a Adapt Data
Run SAP Exercise for
Quick Wins Data Archiving
S/4HANA Embedded
Toward Data Temperature and Data
Sizing Report Analytics and
Reduction Strategy Aging
SAP Fiori

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 3

Considerations Around Sizing, Archiving, and Data Aging
Prepare phase: Run SAP S/4HANA sizing report

Step 1 Step 2
Review SAP Note 1872170 – Business Suite Execute sizing report /SDF/HDB_SIZING
on HANA and S/4HANA sizing report

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 4

Considerations Around Sizing, Archiving, and Data Aging
Prepare phase: interpreting the sizing results

1. Review memory requirement for initial sizing and determine

future growth for additive

2. Ensure analysis is done on all tables successfully –

No partial or error in table analysis

3. Use FAQ of SAP Note 1872170 to review more detail

information on SAP S/4HANA report

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 5

Considerations Around Sizing, Archiving, and Data Aging
Prepare phase

Prepare Phase Realize Phase

Run Sizing
Determine Determine a Adapt Data
Run SAP Exercise for
Quick Wins Data Archiving
S/4HANA Embedded
Toward Data Temperature and Data
Sizing Report Analytics and
Reduction Strategy Aging
SAP Fiori

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 6

Considerations Around Sizing, Archiving, and Data Aging
Prepare phase: Determine quick wins towards data reduction

Objective is to reduce data before migration +

conversion to SAP S/4HANA with
housekeeping and deletion procedure

Check for clean-up potential

SAP Note 2388483 – How-To: Data Management for Technical Tables
SAP Note 49545 – Deletion of work items that are no longer required
SAP Note 1574016 – Deleting idocs with WE11/ RSETESTD
SAP Note 195157 – Application log: Deletion of logs
SAP Note 2335014 – DBTABLOG | Reduce size

SAP Note 1582301 – Temporary RSDRD reports are not deleted

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 7

Considerations Around Sizing, Archiving, and Data Aging
Prepare phase: Determine quick wins towards data reduction

Objective is to reduce
data before migration +
conversion to
SAP S/4HANA with
possible data archiving

Using this section, you can:

▪ Identify what are the largest
estimated SAP HANA objects that
might require archiving
▪ Determine if archiving has been done
in the past and when

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 8

Considerations Around Sizing, Archiving, and Data Aging
Prepare phase

Prepare Phase Realize Phase

Run Sizing
Determine Determine a Adapt Data
Run SAP Exercise for
Quick Wins Data Archiving
S/4HANA Embedded
Toward Data Temperature and Data
Sizing Report Analytics and
Reduction Strategy Aging
SAP Fiori

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 9

Considerations Around Sizing, Archiving, and Data Aging
Run sizing exercise for embedded analytics and SAP Fiori

It is necessary to add the resource for embedded analytics, which can be estimated with Quick Sizer.

Read “How to fill in the questionnaire” about the parameter values in detail.

Expert sizing required

if table count is >= 500
Mio. lines

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 10

Considerations Around Sizing, Archiving, and Data Aging
Run sizing exercise for embedded analytics and SAP Fiori

It is necessary to add the resource for SAP Fiori front-end server (FES) in addition in case FES is
embedded in SAP S/4HANA back-end server. It can be estimated with Quick Sizer.

Read “How to fill in the questionnaire” about the parameter values in detail.

▪ Enter the highest number of users who log on within one hour. If the users log on over a period of two
hours, you then need to size only half of the users.
▪ Choose the appropriate back end, for example S/4 server if the SAP Fiori front-end server is embedded in
the S/4 server.

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 11

Considerations Around Sizing, Archiving, and Data Aging
Realize phase

Prepare Phase Realize Phase

Run Sizing
Determine Determine a Adapt Data
Run SAP Exercise for
Quick Wins Data Archiving
S/4HANA Embedded
Toward Data Temperature and Data
Sizing Report Analytics and
Reduction Strategy Aging
SAP Fiori

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 12

Considerations Around Sizing, Archiving, and Data Aging
Determine data temperature strategy

Data Data Data Storage

Business Value Possible Actions
Temperature Classification Management Technology

Hot / Current
Active/ operationally-relevant data stored within
SAP HANA Write, Read, Update,
Hot Current Default SAP HANA memory. Hot data is frequently
In-Memory Delete
accessed and has higher performance
requirements.

Optimizing the SAP HANA memory footprint

SAP HANA Cold / Historical
Cold Historical Data Aging Write, Read, Delete
On Disk Data which is closed/cleared and
is moved to cold partitions on disk

Data Volume and Data Lifecycle Management

Data which is read only/infrequently accessed Write, Read
Data (historical) is moved to ADK files (enriched with Destruction function
Frozen Archived retention time) on a secure long-term storage available using
Archiving
(important before migrating to SAP Business SAP ILM
Suite on HANA or SAP S/4HANA)

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 13

Considerations Around Sizing, Archiving, and Data Aging
Realize phase

Prepare Phase Realize Phase

Run Sizing
Determine Determine a Adapt Data
Run SAP Exercise for
Quick Wins Data Archiving
S/4HANA Embedded
Toward Data Temperature and Data
Sizing Report Analytics and
Reduction Strategy Aging
SAP Fiori

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 14

Considerations Around Sizing, Archiving, and Data Aging
Adapt data archiving and data aging

SAP Business Suite SAP Business Suite SAP S/4HANA

Hot/
Current

Classic Archiving SAP ILM Data Aging

Cold/
Footprint reduction
Historical potential estimated
by sizing report
(SAP Note 1872170)
SAP ILM

Frozen

Archive Compliant Compliant

Archive Archive
© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 15
Considerations Around Sizing, Archiving, and Data Aging
Data aging objects

Data Aging Objects SAP S/4HANA Help Link

Application Logs ✓ ✓
IDocs ✓ ✓
Change Documents ✓ ✓
Workflow ✓ ✓
FI Document ✓
Unified Journal Entry ✓
Material Document ✓
MM – Purchase Order ✓
SD – Sales Document ✓
SD – Billing Document Sizing Report Output on
✓
Largest Table
LE – Delivery ✓
© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 16
Thank you.
Contact information:

open@sap.com
Follow all of SAP

www.sap.com/contactsap

© 2018 SAP SE or an SAP affiliate company. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of
SAP SE or an SAP affiliate company.
The information contained herein may be changed without prior notice. Some software products marketed by SAP SE and its
distributors contain proprietary software components of other software vendors. National product specifications may vary.
These materials are provided by SAP SE or an SAP affiliate company for informational purposes only, without representation or
warranty of any kind, and SAP or its affiliated companies shall not be liable for errors or omissions with respect to the materials.
The only warranties for SAP or SAP affiliate company products and services are those that are set forth in the express warranty
statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional
warranty.
In particular, SAP SE or its affiliated companies have no obligation to pursue any course of business outlined in this document or
any related presentation, or to develop or release any functionality mentioned therein. This document, or any related presentation,
and SAP SE’s or its affiliated companies’ strategy and possible future developments, products, and/or platforms, directions, and
functionality are all subject to change and may be changed by SAP SE or its affiliated companies at any time for any reason
without notice. The information in this document is not a commitment, promise, or legal obligation to deliver any material, code, or
functionality. 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, and they
should not be relied upon in making purchasing decisions.
SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered
trademarks of SAP SE (or an SAP affiliate company) in Germany and other countries. All other product and service names
mentioned are the trademarks of their respective companies.
See www.sap.com/corporate-en/legal/copyright/index.epx for additional trademark information and notices.
Week 4: Technical Topics and Project Management
Unit 3: How to Check Whether Downtime
Optimization Is Required
How to Check Whether Downtime Optimization Is Required
Agenda

Downtime optimization is required if experienced downtime is longer than required downtime

Part 1: Which parts influence the downtime?

– Parts of the conversion that impact the technical downtime
– Properties of the source system that impact the technical downtime

Part 2: Which downtime optimization approaches are possible?

– Downtime optimization for standard approach
– Downtime-optimized conversion approach
– Near-Zero Downtime Technology (NZDT)

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 2

How to Check Whether Downtime Optimization Is Required
Main conversion steps with focus on technical downtime

Business Downtime

Technical Downtime

SUM Uptime Ramp FI & ML Business Ramp

Technical SUM Downtime Post Activities
Processing Down Data Conversion Validation Up
Migration Update Conversion

Database Migration Data Conversion

(if source is not yet SAP HANA) Convert table content to new data model
Partially triggered by SUM, partially after SUM
Software Update
Add / update components

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 3

How to Check Whether Downtime Optimization Is Required
Properties of the source system that impact the technical downtime

System SAP Business Suite SAP S/4HANA

performance (Migration) Data Conversion

Quality of data Any

DB

Database size
Source DB SAP HANA

Portion of tables
affected by data conversion
FI conversion:
issues coming up in FI conversion have to be corrected,
this happens in downtime of test conversion
(not relevant for PRD conversion)

Second run is always faster  decide on approach only after second run
© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 4
How to Check Whether Downtime Optimization Is Required
Agenda

Downtime optimization is required if experienced downtime is longer than required downtime

Part 1: Which parts influence the downtime?

– Parts of the conversion that impact the technical downtime
– Properties of the source system that impact the technical downtime

Part 2: Which downtime optimization approaches are possible?

– Downtime optimization for standard approach
– Downtime-optimized conversion
– Near-Zero Downtime Technology (NZDT)

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 5

How to Check Whether Downtime Optimization Is Required
Which downtime optimization approaches are possible?

▪ Standard approach

Downtime
using Software Update Manager (SUM)
with several optimizations
▪ Downtime-optimized conversion approach Decision about approach
uses SUM as well, and reduces downtime depends on several factors
by moving data conversion and migration and should be taken after a
partly to uptime (currently only piloted) migration planning workshop.
▪ Near-Zero Downtime Technology approach (Service component of SAP Value
Assurance for SAP S/4HANA)

Effort
allows further reduction of downtime
by executing the conversion on a clone;
it is a consulting service project (aka NZDT)
Approach Path: 1709 1809
Standard √ √
Downtime-Optimized Conversion piloted piloted

NZDT piloted √
© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 6
How to Check Whether Downtime Optimization Is Required
Downtime optimization for standard approach

➢ DMO optimization: see blog in SAP Community: https://blogs.sap.com/?p=135725

➢ SAP Note 2351294 – S/4HANA System Conversion / Upgrade: Measures to reduce technical downtime
➢ SAP Note 2553722 – Performance optimization of XPRA RMXPRAS4SIMIGRATION
➢ SAP Note 1616401 – Parallelism in the Upgrades, EhPs and Support Packages implementations
➢ SAP Note 2353814 – SAP S/4HANA conversion reports in SD: optimize parallel execution of conversion reports
➢ SAP Note 2355049 – Parameters for conversion report MFLE_XPRA_PARALLEL_CALL

SUM Uptime Ramp Post FI & ML Business Ramp

Technical SUM Downtime
Processing Down Activities Data Conversion Validation Up

Migration Update Conversion

Database size: Number of

consider archiving background processes
DMO
optimization
© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 7
How to Check Whether Downtime Optimization Is Required
Downtime-optimized conversion approach

➢ Table conversion moved to uptime processing

➢ Field conversion moved to uptime processing (KONV and VBFA tables)
➢ Uptime migration for selected big application tables (without data conversion)

SUM Uptime Ramp Post FI & ML Business Ramp

Technical SUM Downtime
Processing Down Activities Data Conversion Validation Up

Migration Update Conversion

Conversion partially moved to uptime for

 FIN and Material Ledger (MM-ML)
& Inventory Management (MM-IM)
 KONV and VBFA tables ➢ See SAP Note 2293733 for Prerequisites and Restrictions
© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 8
How to Check Whether Downtime Optimization Is Required
Near-Zero Downtime Technology (NZDT) for SAP S/4HANA conversion – “10,000-foot view”

Building components
▪ Standard upgrade/migration steps, coding adjustments, performance improvements
▪ Provisioning of hardware and operations in data centers
▪ Delta-enabled migration software for SAP S/4HANA
▪ DMIS 2011 add-on with SP 15 required
▪ Business restrictions need to be adhered to
▪ Near-Zero Downtime Technology (NZDT) and project management capabilities of the minimized downtime service
 Use SAP Note 693168 as starting point for your NZDT journey!
Principles of the NZDT method – “10,000-foot view”:

Activate Create Clone

triggers in clone of becomes new
PROD system PROD system PROD system

1 2 3 4 5
Perform Synchronize
maintenance clone with
event on clone PROD system
© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 9
Thank you.
Contact information:

open@sap.com
Follow all of SAP

www.sap.com/contactsap

© 2018 SAP SE or an SAP affiliate company. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of
SAP SE or an SAP affiliate company.
The information contained herein may be changed without prior notice. Some software products marketed by SAP SE and its
distributors contain proprietary software components of other software vendors. National product specifications may vary.
These materials are provided by SAP SE or an SAP affiliate company for informational purposes only, without representation or
warranty of any kind, and SAP or its affiliated companies shall not be liable for errors or omissions with respect to the materials.
The only warranties for SAP or SAP affiliate company products and services are those that are set forth in the express warranty
statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional
warranty.
In particular, SAP SE or its affiliated companies have no obligation to pursue any course of business outlined in this document or
any related presentation, or to develop or release any functionality mentioned therein. This document, or any related presentation,
and SAP SE’s or its affiliated companies’ strategy and possible future developments, products, and/or platforms, directions, and
functionality are all subject to change and may be changed by SAP SE or its affiliated companies at any time for any reason
without notice. The information in this document is not a commitment, promise, or legal obligation to deliver any material, code, or
functionality. 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, and they
should not be relied upon in making purchasing decisions.
SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered
trademarks of SAP SE (or an SAP affiliate company) in Germany and other countries. All other product and service names
mentioned are the trademarks of their respective companies.
See www.sap.com/corporate-en/legal/copyright/index.epx for additional trademark information and notices.
Week 4: Technical Topics and Project Management
Unit 4: Preparing for SAP Fiori and the New UI
Innovations
 Preparing for SAP Fiori and the New UI Innovations
SAP Fiori app strategy for your implementation
Recommended initial steps:
+8000 +8000 +8000 1. Define SAP Fiori adoption strategy:
 Full SAP Fiori
Classic Classic Classic
Apps Apps Apps  Phased adoption
955
2. Define Internet-facing scenarios:
547  Internal access Favor SAPUI5, Web Dynpro
ABAP, SAP GUI for HTML
 External access Favor SAPUI5

317
3. Consider SAP Fiori launchpad
SAPUI5 SAPUI5 SAPUI5 technology integration options:
 Web Dynpro ABAP
SAP S/4HANA 1511 1610 1709
 SAP GUI for HTML

➢ 8,000+ SAP Fiori apps plus classic apps  SAP Business Client

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 2

 Preparing for SAP Fiori and the New UI Innovations
SAP Fiori architecture recommendations Multiple deployment options
are now possible
Past Present EMBEDDED IS NOW
RECOMMENDED IN
S/4HANA CONTEXT

FES UIX01EAP
FES FES
UIX02RT4 UIS4HOP UIS4HOP
1709
1610
UI2_SRVC

HUB NOT RECOMMENDED

IN S/4HANA CONTEXT

BES SRA001 BES

BES BES
SRA008 S4CORE S4CORE S4CORE
1709 1610
SRA009

FES: Front-End Server

BES: Back-End Server
© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 3
 Preparing for SAP Fiori and the New UI Innovations
SAP Fiori for SAP S/4HANA client strategy – New SAP Fiori implementation
System Landscape Embedded Hub
1. Plan

BES 100 BES 100 1. Configure FES 100 2. Configure

DEV 110 DEV 110 2. Remove DEV 110 3. Copy

BES 200 BES 200 FES 200 4. Transport

TRANSFORM
QA 220 QA 220 QA 220 5. Copy

BES BES FES

400 400 400
PRD PRD PRD
3. Transport 6. Repeat
7. Transport Deltas

FES: Front-End Server

BES: Back-End Server
© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 4
 Preparing for SAP Fiori and the New UI Innovations
Getting started – Configuration guides and welcome pack

New SAP Fiori Implementation Upgrade to SAP Fiori 2.0

Detail Guides on Fiori Configuration High Level Guides on Fiori Configuration SAP S/4HANA

SAP Fiori SAP Fiori 2.0

SAP S/4HANA Fiori Foundation
Configuration (MAA)

SAP S/4HANA Fiori Basic Network

and Security Configuration (MAB) • Administration Guide –
Used for new installation
with best practice SAP Fiori SAP Fiori
SAP S/4HANA Other App Types Upgrade
Deployment (MAL) front-end front-end
server server

SAP S/4HANA Fiori App • UI Technology Guide –

Deployment (MAD)
Used for post conversion SAP SAP
Upgrade
S/4HANA or S/4HANA
SAP S/4HANA Fiori Launchpad SAP ERP XXXX
Operation (MAG)

Note: UI Technology and Admin guides are FPS/SPS specific

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 5

 Preparing for SAP Fiori and the New UI Innovations
5 steps to SAP Fiori

30
Step 1 Step 2 Step 3 Step 4 Step 5
Objective
Objective Gateway Configuration SAP
FIORIFiori App
Configuration Special Launchpad Troubleshooting & Extensibility
Basic FIORI
SAP Fiori Configuration features
Features Performance Analysis
Configuration
Required
RequiredResources
Resources Basis Consultant Basis Consultant Basis Consultant Basis Consultant ABAP Developer
UX Consultant Application Consultant Application Consultant Application Consultant UX Developer
(testing) (testing) UX Consultant
UX Consultant UX Consultant

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 6

Preparing for SAP Fiori and the New UI Innovations
Performance

Update UI5 Use what you need Use an HTML5 fully

libraries compliant browser

Try tab bar Update unified Update kernel

rendering libraries

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 7

Preparing for SAP Fiori and the New UI Innovations
Extensibility

In-App Extensibility Side-by-Side Extensibility

ADT
ABAP Code New Apps
CDS Views

SAPUI5 Code SAP Web IDE

Integration /
Enhancement

Key User Extensibility

Custom “operation”
Machine
apps IoT
Learning

Cloud
Predictive
Solutions

UI Flexibility

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 8

Preparing for SAP Fiori and the New UI Innovations
Troubleshooting

SAP Fiori Launchpad

User interface errors
User Interface
(SAP Fiori App)

OData Service

Business logic or ABAP object errors

Application
(ABAP | CDS)

Database Table Database errors

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 9

Preparing for SAP Fiori and the New UI Innovations
Lessons learned by RIG

Discover Prepare Explore Realize Deploy Run

Be familiar with Do not leave SAP Check SAP Fiori landscape Plan
Plan your future
your future
SAP S/4HANA Fiori for later overall performance upgrades
upgrades and SAP
scope Fiori adoption

Decide on the Leverage the Create the Perfect Incident

correct transition configuration guides to save time and effort
path

Use the trial Define the number of Make sure UATs are
system to get an apps to implement performed for all the apps –
overview of the Avoid surprises!
apps

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 10

Thank you.
Contact information:

open@sap.com
Follow all of SAP

www.sap.com/contactsap

© 2018 SAP SE or an SAP affiliate company. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of
SAP SE or an SAP affiliate company.
The information contained herein may be changed without prior notice. Some software products marketed by SAP SE and its
distributors contain proprietary software components of other software vendors. National product specifications may vary.
These materials are provided by SAP SE or an SAP affiliate company for informational purposes only, without representation or
warranty of any kind, and SAP or its affiliated companies shall not be liable for errors or omissions with respect to the materials.
The only warranties for SAP or SAP affiliate company products and services are those that are set forth in the express warranty
statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional
warranty.
In particular, SAP SE or its affiliated companies have no obligation to pursue any course of business outlined in this document or
any related presentation, or to develop or release any functionality mentioned therein. This document, or any related presentation,
and SAP SE’s or its affiliated companies’ strategy and possible future developments, products, and/or platforms, directions, and
functionality are all subject to change and may be changed by SAP SE or its affiliated companies at any time for any reason
without notice. The information in this document is not a commitment, promise, or legal obligation to deliver any material, code, or
functionality. 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, and they
should not be relied upon in making purchasing decisions.
SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered
trademarks of SAP SE (or an SAP affiliate company) in Germany and other countries. All other product and service names
mentioned are the trademarks of their respective companies.
See www.sap.com/corporate-en/legal/copyright/index.epx for additional trademark information and notices.
Week 4: Technical Topics and Project Management
Unit 5: Impact on BW Integration, SAP HANA Live,
and Embedded Analytics
Impact on BW Integration, SAP HANA Live, and Embedded Analytics
SAP S/4HANA – BW roadblock check list

▪ Not all ERP data sources supported in SAP S4HANA

(see SAP Note 2500200 for which ones impact you)
▪ Changes in business process with the adoption of SAP
S/4HANA, may impact upon BW design, which may
trigger a retrofit of BW transformation to the new
business process
▪ Need to have a plan on dealing with unsupported
extractors
▪ Downstream processes extracting from BW might be
impacted due to change in unsupported extractors,
business process, transformation

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 2

Impact on BW Integration, SAP HANA Live, and Embedded Analytics
SAP S/4HANA – BW considerations

▪ How much effort to spend decommissioning BW reports

▪ Which reports can easily be taken over by standard
embedded analytics
▪ Which extraction processes can be decommissioned
from BW as a result of adoption of embedded analytics
▪ Where will users execute reports (SAP Fiori)
▪ Real-time operational style reports may not be required
in BW
▪ How/where will financial statements get produced with a
change in SAP S/4HANA and impacts on BW

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 3

Impact on BW Integration, SAP HANA Live, and Embedded Analytics
SAP S/4HANA – SAP HANA Live

SAP HANA Live provides reporting capabilities for

SAP Business Suite and Suite on HANA customers.
In SAP S/4HANA, database tables have changed in
many areas. A strategic decision was taken to
switch the technology from calculation views to CDS
views with SAP S/4HANA.
▪ If SAP HANA Live views are used, time and resources
should be planned for migration to CDS views
(SAP Note 2242330)
▪ SAP HANA Live based on new data model for SAP
S/4HANA is provided only for finance area
▪ Existing SAP HANA calculation view model including
SAP HANA Live would have to adjust for the data model
change in SAP S/4HANA

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 4

Impact on BW Integration, SAP HANA Live, and Embedded Analytics
What is SAP S/4HANA embedded analytics?

BPC for SAP S/4HANA Embedded Analytics

Business User: SAP Fiori Content/Tools for Analytics
Multi- Multi- Smart Analytical
dimension Query Overview Analytical List
dimension Business KPI SAP Fiori List Report
Report Browser Report Page Page
(generic/APF) Apps
Analysis
Office Key-User: Fiori tools for Analytics
Custom APF Report
Custom CDS KPI Design Design
View Browser Analytical Configuration
Views Modeler Apps Modeler Apps
Queries Modeler

Embedded BW ABAP CDS View

BW VDM
InfoProvider (CDS View)

▪ SAP S/4HANA embedded analytics provide real-time analytics on live transactional data.
▪ Embedded Analytic reports are provided through standard SAP Fiori applications for multiple user types.
▪ BPC for SAP S/4HANA is a planning application in SAP S/4HANA uses the embedded BW function. It is not included
in the definition of embedded analytics, but a reporting function is included in this solution.
© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 5
Impact on BW Integration, SAP HANA Live, and Embedded Analytics
What is a virtual data model (VDM)?

Spend Off-
Contract
Incoming
Sales Order
PO Avg.
Delivery Time
Non-Managed
Purchasing Spend
….
Virtual Data Models (VDMs)

SAP S/4HANA Physical Tables

▪ A virtual data model (VDM) is a structured representation of SAP HANA database views, which was
introduced to be used in SAP HANA Live for SAP Business Suite.
▪ It provides direct access to SAP business data using standard SQL or OData requests.
▪ The virtual data model (VDM) exposes the business data of an SAP system as an understandable,
comprehensive and executable model for consumers in transactional applications, analytics, and external
interfaces.
© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 6
Impact on BW Integration, SAP HANA Live, and Embedded Analytics
Content types for SAP Fiori analytics

There are some content types for SAP Fiori analytics. The function is different in each type.
Name Definition
KPI App – Generic Tile with figures populated from OData and detail analysis displayed in the application

APF App Tile with figures populated from OData and series of detail analysis steps are displayed in the
application
Analytical List Page A list page with visualization – Filtering and drilldown are possible

Overview Page A page consists of several cards including figures and chart.

Multidimensional Report Web Dynpro application where multidimensional analytical operations are possible (e.g. slicing, dicing,
drilldown)

UI5 Analytical App UI5 application for reporting consuming OData

Query Browser Analytic queries of CDS views are listed and fields in each query can be displayed. Multidimensional
analysis (Design Studio) can be launched for a selected query.

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 7

Impact on BW Integration, SAP HANA Live, and Embedded Analytics
Can/should BW reporting be placed into SAP S/4HANA embedded analytics?

Question: Can/should BW reporting be placed into SAP S/4HANA embedded analytics?

▪ In SAP S/4HANA, BW operational reporting should be shifted to SAP S/4HANA, so existing operational
reporting in BW could be placed into embedded analytics, e.g. sales report
▪ Strategic reports continue to be provided from BW, e.g. integration report between SAP S/4HANA and
external system

BW
?
SAP S/4HANA
ERP
embedded analytics

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 8

Impact on BW Integration, SAP HANA Live, and Embedded Analytics
Direction – Embedded analytics instead of traditional reporting tools

▪ 2579584 – Recommendations for Financial Reporting in SAP S/4HANA

 SAP recommends a gradual switch to the new CDS-based reporting with the SAP Fiori user interface.
 Report Writer, Report Painter, drilldown reporting, and the SAPGUI applications for line items are still
available in the SAP S/4HANA system. These reports are still supported and have been technically
adapted and optimized for the new architecture. For technical reasons, these classic reporting tools can
only partially benefit from the new SAP HANA capabilities. Therefore going forward, we recommend to
create new reports using the CDS-based reporting tools instead of using Report Painter or Report Writer.

▪ 2349297 – S4TWL – Reporting/Analytics in Controlling

 Most existing reports in Report Writer/Painter, drilldown reporting, and ABAP List Viewer (ALV) will
continue to work using compatibility views, which will provide access to all fields available in the original
report but will not provide insight over and above what was already available in SAP ERP.
~ Activate appropriate SAP Fiori reporting apps and test with end users.

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 9

Thank you.
Contact information:

open@sap.com
Follow all of SAP

www.sap.com/contactsap

© 2018 SAP SE or an SAP affiliate company. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of
SAP SE or an SAP affiliate company.
The information contained herein may be changed without prior notice. Some software products marketed by SAP SE and its
distributors contain proprietary software components of other software vendors. National product specifications may vary.
These materials are provided by SAP SE or an SAP affiliate company for informational purposes only, without representation or
warranty of any kind, and SAP or its affiliated companies shall not be liable for errors or omissions with respect to the materials.
The only warranties for SAP or SAP affiliate company products and services are those that are set forth in the express warranty
statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional
warranty.
In particular, SAP SE or its affiliated companies have no obligation to pursue any course of business outlined in this document or
any related presentation, or to develop or release any functionality mentioned therein. This document, or any related presentation,
and SAP SE’s or its affiliated companies’ strategy and possible future developments, products, and/or platforms, directions, and
functionality are all subject to change and may be changed by SAP SE or its affiliated companies at any time for any reason
without notice. The information in this document is not a commitment, promise, or legal obligation to deliver any material, code, or
functionality. 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, and they
should not be relied upon in making purchasing decisions.
SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered
trademarks of SAP SE (or an SAP affiliate company) in Germany and other countries. All other product and service names
mentioned are the trademarks of their respective companies.
See www.sap.com/corporate-en/legal/copyright/index.epx for additional trademark information and notices.
Week 4: Technical Topics and Project Management
Unit 6: Guidelines for Functional and Technical
Testing
Guidelines for Functional and Technical Testing
Test objectives

▪ Functional and technical testing is an integral part of

every SAP S/4HANA conversion project
▪ Testing requires a substantial testing strategy to
effectively validate the functionality of the
implementations before the go-live
▪ The goal of testing is to find important problems early
▪ Tests will be designed to cover business processes
and will be prioritized on the basis of business risk,
technical complexity, and the impact of failure

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 2

Guidelines for Functional and Technical Testing
Prerequisites for good testing

A test strategy should cover

▪ Test types and purpose
▪ Test scope
▪ Test data
▪ Test environment and system landscape
▪ Test management, process, roles, and governance
▪ Test tools
▪ Test automation
▪ Test scripts

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 3

Guidelines for Functional and Technical Testing
Overview of test types

Most common tests in an SAP S/4HANA conversion

▪ Unit test
▪ Functional test
▪ Integration test
▪ Regression test
▪ User acceptance test
▪ Performance test

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 4

Guidelines for Functional and Technical Testing
Testing activities during the project lifecycle

Prepare Explore Realize Deploy Run

▪ Test strategy including test ▪ Prepare test data

process and governance ▪ Provide test landscape including
▪ Test planning connected systems
▪ Test scope determination ▪ Test execution
▪ Prepare test infrastructure
▪ Staff resources required for testing

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 5

Guidelines for Functional and Technical Testing
Key learnings from customer projects

▪ Early controlling and follow-up on test cycles helped

to bring the right attention and the required support
▪ War room testing is an excellent idea and worked out
very well
▪ Prepare the (worldwide) testers and organize the
testing well, specifically for the UAT
▪ Training and parallel system testing did not help, so
keep it separated
▪ Conversion tests done several times based on copy
of production system with real data
▪ Consider and start the testing already on the
sandbox
▪ Do a broad and deep testing since it is a conversion
and not just an upgrade
▪ Don’t forget to test interfaces and authorization
© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 6
Thank you.
Contact information:

open@sap.com
Follow all of SAP

www.sap.com/contactsap

© 2018 SAP SE or an SAP affiliate company. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of
SAP SE or an SAP affiliate company.
The information contained herein may be changed without prior notice. Some software products marketed by SAP SE and its
distributors contain proprietary software components of other software vendors. National product specifications may vary.
These materials are provided by SAP SE or an SAP affiliate company for informational purposes only, without representation or
warranty of any kind, and SAP or its affiliated companies shall not be liable for errors or omissions with respect to the materials.
The only warranties for SAP or SAP affiliate company products and services are those that are set forth in the express warranty
statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional
warranty.
In particular, SAP SE or its affiliated companies have no obligation to pursue any course of business outlined in this document or
any related presentation, or to develop or release any functionality mentioned therein. This document, or any related presentation,
and SAP SE’s or its affiliated companies’ strategy and possible future developments, products, and/or platforms, directions, and
functionality are all subject to change and may be changed by SAP SE or its affiliated companies at any time for any reason
without notice. The information in this document is not a commitment, promise, or legal obligation to deliver any material, code, or
functionality. 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, and they
should not be relied upon in making purchasing decisions.
SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered
trademarks of SAP SE (or an SAP affiliate company) in Germany and other countries. All other product and service names
mentioned are the trademarks of their respective companies.
See www.sap.com/corporate-en/legal/copyright/index.epx for additional trademark information and notices.
Week 4: Technical Topics and Project Management
Unit 7: Project Management Considerations
Project Management Considerations
Course recap

Building up knowledge of system conversion

▪ Fundamentals and technical tooling
▪ Changes to system landscape and Finance
▪ Changes in Logistics and their impact
▪ Technical topics and project management

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 2

Project Management Considerations
Key success factors

Simplification

Finance

Trials 2 to 3

UX

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 3

Project Management Considerations
Recommendations

▪ Archiving
▪ Testing
▪ Sufficient time
▪ Dress rehearsal
▪ Evaluating data inconsistencies in Finance
▪ Embedded analytics

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 4

Project Management Considerations
Planning

Prepare Explore Realize Deploy Run

SAP ERP PRD System

Copy

Proj. Prep. Copy

SBX Conversion Unit Tests

Time
window
to correct SHT Conversion Integrated Tests
issue in
PRD

Have we allowed ENOUGH TIME to correct issues in

Production? What is the RISK that the next copy from
Production contains UNRESOLVED inconsistencies?
Preparation & Analyses

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 5

Project Management Considerations
Recommendations

Prepare for the The transformation is Your first steps into

project an iterative process SAP S/4HANA are a
foundation for consuming
more innovations
incrementally over time

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 6

Thank you.
Contact information:

open@sap.com
Follow all of SAP

www.sap.com/contactsap

© 2018 SAP SE or an SAP affiliate company. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of
SAP SE or an SAP affiliate company.
The information contained herein may be changed without prior notice. Some software products marketed by SAP SE and its
distributors contain proprietary software components of other software vendors. National product specifications may vary.
These materials are provided by SAP SE or an SAP affiliate company for informational purposes only, without representation or
warranty of any kind, and SAP or its affiliated companies shall not be liable for errors or omissions with respect to the materials.
The only warranties for SAP or SAP affiliate company products and services are those that are set forth in the express warranty
statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional
warranty.
In particular, SAP SE or its affiliated companies have no obligation to pursue any course of business outlined in this document or
any related presentation, or to develop or release any functionality mentioned therein. This document, or any related presentation,
and SAP SE’s or its affiliated companies’ strategy and possible future developments, products, and/or platforms, directions, and
functionality are all subject to change and may be changed by SAP SE or its affiliated companies at any time for any reason
without notice. The information in this document is not a commitment, promise, or legal obligation to deliver any material, code, or
functionality. 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, and they
should not be relied upon in making purchasing decisions.
SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered
trademarks of SAP SE (or an SAP affiliate company) in Germany and other countries. All other product and service names
mentioned are the trademarks of their respective companies.
See www.sap.com/corporate-en/legal/copyright/index.epx for additional trademark information and notices.