SAP ECC to S/4HANA Move

SAP ECC to S/4HANA Move
Options, Transition scenarios, Preparation, Tools
Abhishek Goel
S/4HANA Movement Specialist
April, 2019
V20190407

2CUSTOMER© 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀ
Agenda
 S/4HANA (OP / Cloud) Options, Positioning & Deployment options
 S/4HANA Transition Scenarios
 Green Field or conversion ?
 Introduction to NZDT for S/4HANA conversion
 High level planning & preparation steps for S/HANA conversion
 S/4HANA Migration Impact to other systems
 S/4HANA Sizing
 S/4HANA Conversion - Custom Coding Impact
 Side by side S/4HANA Custom Code Extension using SCP
 Migration Approach / Sequence
 Optional consumption of Innovation during S/4HANA conversion
 S/4HANA conversion (pre, conversion & post) steps
 Questions ?

SAP S/4HANA is SAP’s next generation Digital Core
 Optimized for SAP HANA
 New architecture and data models
 “Principle of One”
 Renewed applications
 Fiori based User Experience
 Cloud & on-premise deployment models
SAP S/4HANA – Digital Core
SAP S/4HANA is a new product line.
The classical SAP Business Suite & SAP ERP is a separate product line and
will still be available.
System conversion including custom code from existing
SAP Business Suite or SAP ERP is possible.

SAP S/4HANA
Release strategy for 2018 / 2019 and definition of deliveries
FPS01*
Feature Package Stack
(technically SPS 01)
RTC planned for
Jan 30, 2019
FPS02*
Feature Package Stack
SPS03*
Support Package Stack
SAP S/4HANA 1809 SPS00
New release incl. new
technology stack
(NetWeaver AS ABAP 7.53 SP00
including UI1.56
SAP HANA 2.0 SP03 as minimal Version)
2018 2019
Q4 Q1 Q2 Q4Q3
SAP S/4HANA 19xx
SPS00*
New release incl. new
Technology Stack
Maintenance Line
2020
Q3 Q1 Q2 Q3 Q4
Important Links
2655761 - Restrictions and
recommendations regarding specific
revisions of the SAP HANA database for
use in SAP S/4HANA
2659710 - SAP S/4HANA 1809:
Restriction Notes
* This is the current state of planning and may be changed by SAP at any time without notice.
Support Package Stack for SAP S/4HANA 1809*
After general availability of SAP S/4HANA 1809, Feature Package Stacks (FPS) and Support Package Stacks (SPS) contains
stabilizations bundled with corrections and legal changes. Customers benefit from this functionality as part of their maintenance
fee. First SPS of a new release can contain selected features and are labelled Feature Package Stack (FPS) accordingly.
Support Package Stacks are compiled periodically and made available on the SAP Software Download Center
Product information will be available on the User Assistance Content Platform

S/4HANA (OP / Cloud) Options &
Positioning

SAP S/4HANA Cloud,
single tenant edition
SAP S/4HANA
(On-premise managed by cloud
providers or customers)
SAP S/4HANA
(Private cloud managed by SAP)
Cloud ERP* ERP in the Cloud ERP OP
SAP S/4HANA Cloud
One SAP S/4HANA: the right solution for each customer cloud journey
Implementation Greenfield with data migration
Greenfield with data and
configuration migration
Greenfield or conversion of existing
implementations
Greenfield or conversion of existing
implementations
Functional Scope
Business configuration of standardized core ERP
and select LOB processes
Full functional S/4HANA scope of core ERP
and extended LOB and industry processes
Industries
Supported
In-depth support for professional services and
component manufacturing;
more industries on road map
All industries supported All industries supported All industries supported
Extensibility
S/4HANA Extensibility Framework and
extensions via SCP, using whitelisted APIs
S/4HANA Extensibility Framework and
extensions via SCP, with full extensibility
option
Customization, modification, and
extensibility possible
Customization, modification, and
extensibility possible
Innovation Cycle Quarterly
2 upgrades a year, one mandatory within 12
month window of release
Annual;
speed of adoption on customers’ schedule
Annual;
speed of adoption on customers’ schedule
Deployment
Benefits
Multi-tenant environment,
Lowest TCO and fastest time to value
Single-tenant environment
Low TCO and fast time to value
Customer controlled deployment and
implementation efforts
Customer controlled deployment and
implementation efforts
Licensing Subscription licensing Subscription licensing BYOL + infrastructure subscription Perpetual licensing
Infrastructure Shared public cloud
Dedicated system landscape on cloud
infrastructure
Customer specific system landscape
Runs on SAP HANA Enterprise Cloud
Runs on customer preferred infrastructure
*according to Gartner Cloud (SaaS) Definition

Finding the Right Fit for Your Customer or Prospect (Internal)
Begin with public cloud (SaaS) as the best option for a
digital future
 LowestTCO
 Fastest time-to-value
 Shortest innovation cycle
Continue with private edition as a full cloud offering
with more flexibility
 LowTCO
 More flexibility
 Customer-influenced innovation cycle
Progress to next option in order to meet customer needs
(consider capability and policy requirements)
Starting point
CloudERP
SAP S/4HANA Cloud
SAP S/4HANA Cloud,
private edition
SAP S/4HANA
(Private cloud managed by SAP)
SAP S/4HANA
(On-premise managed by cloud providers
or customers)

TODAY
Highly Customized
FUTURE
Cloud ERP
Private Managed Cloud
SaaS
Completely SAP Managed Transformation with SAP’s Private Managed Cloud
On Premise
SAP Data Center
Lift & Shift
Bring your SAP solutions on
SAP HANA platform in HANA
Enterprise Cloud
S/4 HANA Migration
Migrate your individual ERP-
solution to newest
S/4 HANA release
Innovation Extension
Extend the latest innovations
of S/4 HANA and extend with
SCP
Values
 Private & Secure
 Adaptive & Scalable
 Best-Practice Services
 Reference Architecture
 License Subscription
Facts
 840+ DCC Customers
 3500+ SAP HANA Databases
 66TB+ Largest Instance
 99.99% Average Availability
 1100+ S/4HANA Systems on DCC
A customer path to S/4HANA Cloud
INTERNAL© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ

Transition to SAP S/4HANA
Different approaches to move to SAP S/4HANA
Type Approach Available for Purpose
System
Conversion
(Tool: Software Update Manager)
New
Implementation
(Tool: SAP S/4HANA migration
cockpit)
Hybrid Data
Transition
(Customer-tailored
service/consulting offering)
Reusing
byin-place
conversion
Bringing your business processes to the new
platform
 A complete technical in-place conversion of an existing ERP
software system in SAP Business Suite to SAP S/4HANA
 Adoption of new innovations at your speed
New implementation/reimplementation
 Reengineering and process simplification based on latest innovations
 Implementing innovative business processes with preconfigured
content on a new platform
 Performing initial data load
 Retiring old landscape
Value-driven data migration to the new platform
 You need more than master data and open items, such as
transactional data, complete or selected by a time slice
 Migrate a selection of data (such as by organizational units), or
migrate data from more than one system, or migrate application-
related data into an SAP S/4HANA–based solution landscape
Standardized
Customer
tailored
Reengineering
withdatamigration
SAP S/4HANASAP ERP
system
SAP S/4HANASAP ERP or
third-party
system(s)
SAP S/4HANA
SAP S/4HANA
Cloud
SAP ERP or
third-party
system(s)
SAP Community blog: How to find my path to SAP S/4HANA

SAP S/4HANA
New Implementation
Scenario description
New implementation of SAP S/4HANA e.g. for
customers migrating a legacy system.
Legacy
Any customers
legacy system
Initial data load from
Legacy or SAP System
with SAP S/4HANA
Migration Cockpit
What How
Install SAP S/4HANA
SWPM (Software
Provisioning Manager)
Initial data load from
source system
• SAP S/4HANA Migration
Cockpit (Legacy system
via file upload)
• Optional: SAP Data
Services with SAP Best
Practice Migration content
1
2
(SAP GUI) / SAP Fiori
SAP HANA
SAP S/4HANA Core

SAP S/4HANA
System Conversion – Transition Paths Overview
Prerequisites on source system
• Unicode is required
• ABAP single stack required
• SAP HANA database not required
• SAP Suite on HANA customers who are planning a system
conversion to SAP S/4HANA 1709 or 1809 must first update
the database from SAP HANA 1.0 to SAP HANA 2.0 and
then do the system conversion
SAP HANA
SAP S/4HANA 1809
SAP S/4HANA System Conversion – At a glance
Conversion requirements incl. min./max. SP-level on source system:
2625407 - SAPS/4HANA 1809: Release Information Note
2482453 - SAP S/4HANA 1709: Release Information Note
AnyDB or SAP HANA
SAP ERP 6.0, EHP xx
Prerequisites on target system
• SAP S/4HANA 1809 is based on SAP ABAP Platform 1809
• SAP ABAP Platform 1809 has different OS coverage

Comparing the Paths to SAP S/4HANA
Questions influencing the choice of the transition scenario
System Requirements
New
Implementation System Conversion
A company has restrictions that do
not allow to move to SAP
S/4HANA on-premise in a one-
step procedure.
New
New
A company has business processes
that already fit to the current
requirements.
New
New
Custom Code
Time to Value
A company has checked and is
able to take over existing custom
code.
A company wants to go live rather fast.
Business Processes
A company seeks to fundamentally
redesign its business processes.

Near Zero Downtime Overview (only Available via involving SAPC via DBS)
SAP S/4HANA Conversion as sample
ERP
6.0x
via DMO of SUM
Data model
conversion
S/4
HANA
ERP
6.0x
ERP
6.0x
S/4
HANA
Create clone
Software update, database
migration, …
Repeated replay and
data conversion of delta
Final delta replay
S/4
HANA
Production
operation
Uptime UptimeDowntime
1. Start recording on PRD
2. Create the NZDT clone
3. Start converting the clone to S/4HANA – SUM/DMO
4. Convert the original data to SAP S/4HANA data model
5. Start on-line replay and conversion of the recorded data
(repeated replay and conversion to S/4 data model possible)
6. Begin downtime and finalize replay of the recorded data
7. Convert the remaining data to SAP S/4HANA data model
8. Validate the system and go live with SAP S/4HANA
1
2
3 4 5 6 7 8
Recording
Final data
conversion

High Level Planning & preparation Steps for S4HANA conversion
 Project Planning, resources, existing ECC UAT scripts
 Any Data Archiving, Housekeeping etc to reduce database size
 Check for and remove obsolete custom code (i.e CCLM), unnecessary modifications and clones of SAP standard
objects, in order to keep your code base clean.
 Check your custom code and start HANA database related adjustments as part of preparation for S/4HANA
 Execute S/HANA Sizing, HANA Hardware and infrastructure provisioning by customer, Split any dual stack systems
 Execute the S/4HANA Readiness check using the Maintenance planner, pre-transition checks etc to check
 your SAP ERP system (including SAP and partner add-ons) can technically be converted to S/4HANA.
 Check Technical scope and restrictions, Check the pre-requisite SAP Notes
 Check Installed ERP & partner add-ons, Industry solutions are compatible with HANA or S/4HANA
 Check custom code for needed adaptations to the new SAP data model etc.
 Explore the simplification items - the functionalities relevant for you that have changed
 Review the S/4HANA simplification List, cook Book, conversion guides etc
 Any OS /DB scripts which needs to be adjusted in the target OS / DB systems.
 In S/4HANA Business Partner replaces the ERP Customer/supplier concept. Get accustomed to Business Partner
Know-How
 Check for consistent customer/supplier data and valid and consistent customer/supplier and Business Partner
customizing entries in ERP system
 Clean up your customer and vendor data in preparation for the Business Partner and Customer/Vendor Integration
(CVI) (SAP Notes: 2211312, 2210486, 2216176)
 Execute Pre-conversion check to ensure that all the necessary CVI mappings are done for both customer and vendor.
 Note 2216176 delivers the pre-conversion checks for Business Partner which have to be executed before the conversion
to S/4

SAP S/4HANA conversion impact to other NW systems
 SAP Note 1388258 – Central Hub systems like Portal, PI & BW need to be upgraded mandatorily to
Netweaver 7.31 (min)
 Either a new Fiori setup would need to be Greenfield implemented or existing Fiori will need to be upgraded in
synch with the Target S/4HANA version
 Solution Manager must be minimum version 7.01 SPS 23 or 7.1 SPS 10
 If the source ECC system is on HANA 1.0, an upgrade to HANA 2.0 will be needed as a pre-requisite
 If applicable, upgrade of other NW systems can be done as pre-requisite steps or within the same S/4HANA
conversion project.
SAP PI, BW,
Portal
AS ABAP < 7.31
AnyDB
SAP PI, BW,
Portal
AS ABAP >=7.31
AnyDB
SAP PI, BW or Portal systems lower
than Netweaver 7.31
SAP PI, BW or Portal systems
would need to be upgraded to
minimum Netweaver 7.31

S/4HANA Sizing
 Apply the necessary SAP Notes on the ERP system on AnyDB
 Refresh Database statistics
 Execute the Sizing Report
 Analyze the output for the HANA Appliance Memory output
 Work with the preferred Hardware vendor to order the HANA appliance
 Only the database server needs to be changed, the application server can be reutilized

Why do we need Custom Code Analysis?
Drivers of Change within a S/4HANA Migration Project
Possible Sources of Impact to Custom Code
– Software Changes
The change of software levels (e.g. SPS, EHP, and/or version) has the potential of impacting custom
code, especially when custom code makes references to the standard objects that were
enhanced/modified as part of the software update.
– Platform Changes
As there may be platform specific performance hints implemented within custom code, the change of
the underlying platform (i.e. to SAP HANA) could impact the performance of that code. Additionally,
implications like sort order also have to be accounted for when changing platforms.
– Unicode Conversion
The migration to SAP HANA requires that the database is Unicode. If the source system has yet to
converted, the conversion can be included in the scope of the migration project. As a requirement
for the conversion, all custom code must be Unicode enabled.
– Business Requirements
Evolution in the business and adoption of innovations can both be drivers for change to custom
code. With the migration to SAP HANA, the business may decide to include some of these
enhancements within the scope of the project.
– Data Model Simplification
The simplification of the data model with S/4HANA can have a potential impact on custom code. For
instance, custom code that directly writes to the total tables will need to be adjusted.

Custom Code Management
Approach for Remediating Custom Code
Get transparency
on Custom Code
Go back to SAP Standard**
Remove waste
 Readiness
Check
 Logging
 Usage &
Procedure
Logging
 Innovation Control Center
Adjust HANA specifics
 Sort order, DB hints,
EXEC SQL…
**) Not covered in this deck
1 2
Refactoring
BP Re-Design
Analyze Impact &
Create a plan
 Code Inspector /
ATC
3
 Technical replacement
of custom by SAP code
 Re-Engineer & improve BP
Adjust Upgrade / EHP specifics
 Changed / removed SAP
code
Adjust S/4HANA specifics
 Write access on totals
 Views on totals, appends
 Incompatible SAP
software changes
Can happen upfront of a migration project
4
Identify Analyze Improve
We are
Here !!
Next
Step

Custom Code Extensibility using SCP –
side by side Extensions

Custom Code Extension using SCP - enables Extension, Integration, development
Extend cloud solutions
running in the cloud with
custom extensions also running
in the cloud
Build new custom solutions
running in the cloud
Extend on-premises
solutions running in your data
center with custom extensions
running in the cloud
On-Demand Extensions Hybrid Solutions New Cloud Solutions
On-Premise
Services DataServices Data
On-Premise
Extension
Data
SAP Business
Suites …
Services Data
Cloud Extension
Data
Cloud
Solutions
Cloud Application
Extend
Cloud & On-Prem Apps
Integrate
Your Apps and Data
Build
New Cloud Apps

Side-by-side Extensibility for SAP S/4HANA using SAP Cloud Platform ABAP
Environment
KEY CAPABILITIES
Develop and deploy side-by-side extensions on
a separate PaaS
Integrate with SAP S/4HANA
Consume SAP S/4HANA data via
whitelisted APIs
BENEFITS
Leverage your ABAP know how in the cloud
Transform your ABAP custom code to the cloud
Benefit from SAP Cloud Platform environment
Application
Clients
Corporate Identity Provider
Backend system, i.e
SAP S/4HANA Cloud,
SAP S/4HANA,
SAP ERP, SAP
NetWeaver AS ABAP
SAP CLOUD PLATFORM
Custom Data
SAP HANA tenant
Your ABAP
extension
Connectivity
Please note: first version supports S/4HANA Cloud extensions only, on-prem support will be released in Q4 2018

Custom Code - When to decouple and to use side-by-side extensions by use
case examples
In-App Side by side
Modification to SAP Standard Code
-Modifying SAP S/4HANA software (SAP Standard programs) with full access to ABAP Workbench (SE80) X
Developing custom code enhancements in SAP Standard applications
-using Customer exits, Z-Programs on customer name spaces, BAdIs, APIs X X
-adding functionality, Fields, Tables to standard SAP software without actually the original standard delivered objects X X
Developing (incl. ABAP) custom applications integrated to and decoupled from SAP Standard application
-Custom Apps combining SAP and/or non-SAP data – write back to ERP X X
-Custom Apps combining SAP and/or non-SAP data – no write back to ERP X
-ERP Z-ABAP code still required and reasonable/feasible to be decoupled from core ERP X
Connecting to IoT sensors, streaming and (incl. instantaneous) analyzing of IoT data X
Exploring and Running AI, Predictive, Machine Learning, IoT services on ERP data and non-ERP data X
Integration of AI, Predictive, Machine Learning, IoT “results” (back) into standard core ERP processes, S4, ECC… X
Consumer-grade UX
-UX - User Interface - Design Time cloud, Run Time on premise, Portal on premise X
-UX - User Interface - Design Time cloud, Run Time cloud, incl. single Fiori Launchpad for cloud and on-premise Fiori X
-UX - Mobile Apps deployed in Cloud Portal, and/or corporate AppStore incl. Apple SDK X
-ERP Z-transaction to be replaced with mobile Apps or custom UX for example prior to conversion to S/4HANA X
Flexible Process Integration based on API’s with on-premise and cloud applications, SAP and 3rd-party X
BI Self Service and Data Integration, which deviate from standard corporate (stable core) BI, KPI’s etc.
-Data Transformation X
-Combining SAP data with non-SAP data X
-Creating ad-hoc queries and KPI’s against live production data without transports X
Big Data Storage and Exploration X

Conversion
 Prepare the digital core to be stable, clean
and lean for S/4HANA conversion
 Decouple modifications from S/4HANA to
SAP Cloud Platform wherever possible
Greenfield
 Keep the new stable core clean and lean
from the start
 Stay close to Standard as much as possible
 Minimize Modifications in stable core
Accelerate your Journey to S/4HANA

ECC to S/4HANA conversion steps
ERP DEV /
AnyDB
 New S/4HANA production support systems to replace the current ERP systems
ERP QAS /
AnyDB
ERP PRD /
AnyDB
SAP S/4HANA
DEV
SAP S/4HANA
QAS
SAP S/4HANA
PRD
New Hardware
Existing Instances
S/4HANA Conversion steps
1. Build a Sandbox (SBX) system on AnyDB via system
copy from Production
2. Migrate Sandbox (SBX) system on AnyDB to SAP
S/4HANA. Fix all issues, custom coding here.
3. Migrate Development system to S/4HANA. Use the
DEV S/4HANA system as Development system for the
conversion project
4. Migrate Quality system. This will be used as S/4HANA
Quality system for the conversion project.
5. Mock Cutover and Dress-Rehearsal (Migration to
S/4HANA) based on a fresh system copy of PRD
6. Go-live. Conversion of the S/4HANA Production
system
7. Decommission ERP systems running on AnyDB
database, decommission S/4HANA SBX system.
SAP ERP SBX /
AnyDBS/4HANA SBX
1
2
3 4 6
5
7

Optional – Include Additional Innovations or solution to existing pain points
Technical Migration Business Process Transformation
New Implementation (‚Greenfield‘)
System Conversion (technical project)
Landscape Transfomation w/ individual Scope
System Conversion with additional/full scope of BP Transformation (aka‘Big Bang‘)
seperate, single implementation projects
(i.e. BP re-design, new Applications, Fiori UX, etc.)
i.e. mandatory Simplifications
and FI Migration

3 Elements of S/4HANA Conversion
Database
Migration
Functional
Impact
Custom Code
Impact
S/4HANA conversion consists of 3 mandatory logically distinct efforts
• Effort is similar to other DB migrations a customer may have already done
• No longer required for SoH customers
• Functional impact of application simplification and following the principle of one
• Many simplification list items can be done on start release as preparation for S/4HANA conversion
• Upgrade-like tasks with SPAU, SPDD and S/4 specific custom code efforts
• Experience shows that SPAU and SPDD efforts often exceed S/4 specific custom code efforts
• S/4 specific custom code efforts are mainly resulting from data model changes
• Recommendation: perform housekeeping (get rid of unused code, delete unused data, …)
Optional
consumption of
innovation
• Traditional capabilities are generally available thus it is possible to convert to S/4HANA rather
technically
• The degree of process change is largely a business decision when planning the conversion project
Mandatory
Optional

S/4HANA System Conversion – Best Practices
Conversion Tasks
Preparation Activities Pre - Conversion Activities Conversion to S/4HANA Post-Conversion Activities
1 2 3 4
 S/4HANA Conversion
preparation activities
 Maintenance Planner Checks
 Functional Pre-Checks
 Custom Code Migration
Worklist
 Check on the Add-Ons (SAP
INVOICE MGMT BY OT 6.0-
VIM 0600_600)
 System Conversion Pre-
Checks Activities
 Check Currency Settings and
CO Configuration
 Create Production Versions for
all BOM & Routing
combinations
 Convert Storage Locations
to MRP Areas
 Customer Vendor Integration
 Perform month end closing
for all previous periods –
including periodic asset
postings
 Perform consistency checks
(total of open items to GL
balance)
 Perform reconciliation across
various Functional applications
• SUM-DMO to migrate
ERP system to S/4HANA
1809 system
• Gateway Server
installation and
configuration
• Fiori Add-on Installation
and Configuration for S/4
HANA
• Track the issues faced
during the conversion
• SPDD Activities
• Activation of new Asset
Accounting and SAP
Credit management
• Material Ledger activation
at Valuation Area level
• System Conversion Post
Check Activities
• Reconcile balances of
Universal journal with the
pre-conversion balances
• Replacement of MBxx and
Sales master data
transactions
• Fiori Activation

High Level Conversion Timeline – no two customers are same
Activate Phases - > Prep
Project Week Responsibility 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24
Project Preparation Partner / Customer
Cycle 1: SBX (copy of PRD)
Prepare ECC to 1809 conversion (CVI, custom code analysis, application checks, SAP Notes) Partner
SBX Fiori upgrade or new Installation Partner
SAP ECC to 1809 Conversion using SUM w DMO option Partner
Post Activities to Complete SAP S/4HANA Conversion Partner
Custom Code Fixes Partner
Functional verification by users Customer
Cycle 2: DEV
DEV Pre - conversion S/4HANA tasks (CVI, Application checks, SAP Notes) Partner
Quick Functional verification by users Customer
Cycle 3: QAS
DEV Pre - conversion S/4HANA tasks (CVI, Application checks, SAP Notes) Partner
Integration Test / UAT Customer
Any extra Testing, GO/No-Go decision in view of testing results status Customer
Cycle 5: CutOver Rehearsal
Refresh ECC sandbox from ECC Production Customer
Cutover Rehearsal simulating actual go-live Partner / Customer
Cycle 4: PRD
cut over planning & preparation Partner / Customer
Go-live (S4, Fiori) Partner / Customer
Go-live Support Partner
Deploy RunExplore Realize
This is a draft timeline only. Every customer is different. Actual timeline will depend on customer setup
like Business functionality, custom code impacted, number of cycles needed, UAT issues, duration etc

SAP S/4HANA
Important tools supporting your transition to SAP S/4HANA
Application
specific follow-
up activities
Application
specific follow-
up activities
Custom code
preparation
Realization phase
System
requirements
Software Update
Manager (SUM)
Cross-application & application specific preparation
activities
Maintenance
planner
Pre
checks
Custom code
preparation
Preparation phase
Simplification List
Planning phase
Transformation
Navigator
Roadmap
Viewer
SAP S/4HANA
Readiness Check
Uninstall ABAP Add-ons
During System Update
Database migration
Software update
Data conversion
Remote Scans with ABAP Test Cockpit
Simplification
Item Catalog
Unicode conversion
See also the Custom Code Migration Guide
New Framework via
Simplification Item Catalog
New SUM 2.0 incl.
Prerequisite Check
SAP S/4HANA
Readiness Check Remote Scans with
ABAP Test Cockpit

Discover Determine Prepare Adapt Migrate
Discover Your Destination Execute Your MoveBuild Your Business Case
 SAP Fiori apps reference library
 Business Scenario
Recommendations (BSR)
 Solution Explorer
 Value Lifecycle Manager (VLM)
 Pathfinder
 Innovation Discovery Tool
 SAP Roadmap
 SAP Best Practice Explorer
 SAP S/4HANA Trial
 Feature Scope description
 SAP Roadmap Viewer
 SAP Transformation Navigator
 SAP Readiness Check for SAP S/4HANA
 Simplification Item Catalog
 Simplification Item Check
 Code Inspector / Custom Code Migration Worklist
 Pre-Checks
 SAP Activate
 Maintenance Planner
 Migration Cockpit
 SAP Data Services with Rapid Data
Migration content
SAP S/4HANA Deployment Strategy
Tool List

OpenSAP Course: OpenSAP course “Your Path to SAP S/4HANA”
SAP S/4HANA product related Training: SAP S/4HANA Overview and
Business Processes
Discover SAP S/4HANA
Gives an introduction to the next-generation business suite SAP S/4HANA
SAP S/4HANA Trials
Experience SAP S/4HANA with trials for the cloud and on-premise
editions
Detailed SAP S/4HANA Roadmaps: SAP product & solution roadmaps
Feature Scope Description (PDF)
Provides an overview on the available features
SAP Help Portal: http://help.sap.com/s4hana:
Tipps & Tricks:
CVI cookbook
BI Extractors: SAP note 2500202 now provides full transparency for
customers on availability of BI extractors in SAP S/4HANA.
SD Foreign Trade:Most of the former SD Foreign Trade scope is
meanwhile available directly in SAP S/4HANA. Therefore customers
currently using SD Foreign Trade can in most cases avoid the effort of
migrating to SAP GTS.
SAP Community Blog: the top simplificationlist items
Useful links: application specific preparation
SAP Readiness Check for SAP S/4HANA
SAP S/4HANA System Conversion – At a glance
Maintenance Planner (SAP Help Portal) oder http://help.sap.com/maintenanceplanner
 SCN BLOG: Maintenance Planner
 SCN BLOG: Maintenance Planner – Release Highlights
Simplification Item Catalog
Pre-checks in System Conversion
SAP S/4HANA Simplification Item Check – How to do it right‘
ABAP Test Cockpit – an Introduction to SAP’s new ABAP Quality Assurance Tool ,
 Remote Code Analysis in ATC – One central check system for multiple systems on various releases
 Remote Code Analysis in ATC – Technical Setup step by step
 Remote Code Analysis in ATC – Working with Baseline to suppress findings in old legacy code
 Remote Code Analysis in ATC for Developers
 Remote Code Analysis in ATC – Working with Exemptions
 Remote Code Analysis in ATC – Scanning customer extensions
 Remote Code Analysis in ATC – Working efficiently with ATC Result List
 Remote Code Analysis in ATC – FAQ
ABAP Testing and Analysis Community: Link
ABAP Call Monitor (SCMON): Link
Usage Procedure Logging (UPL): Link
Best Practices Custom Code Lifecycle Management (CCLM): Link
ABAP custom code migration and recommendations for SAP HANA:
• SAP Note: 1912445
• SAP Community: Link
Further information see
• SAP Community Blog on Custom Code Adaptation process
• SAP Note: 2241080
• SAP Note: 2190420

Questions ?
Thank you !
Abhishek Goel
S/4HANA Movement Specialist
abhi.goel@sap.com

SAP ECC to S/4HANA Move

Recommandé

Recommandé

Contenu connexe

Tendances

Tendances (20)

Similaire à SAP ECC to S/4HANA Move

Similaire à SAP ECC to S/4HANA Move (20)

Plus de AGSanePLDTCompany

Plus de AGSanePLDTCompany (20)

Dernier

Dernier (20)

SAP ECC to S/4HANA Move