Browse The Book: First-Hand Knowledge

First-hand knowledge.
Browse the Book

Chapter 3, Cloud, On- Premise, and Hybrid Scenarios, conveys a funda-
mental understanding of these operating models and introduces the
deployment options within the SAP S/4HANA product family. It descri-
bes the differences between the various models so that you can make a
fact-based decision for the best deployment model. Because you need
to consider adaptability to your own operational specifics when planning
the migration to SAP S/4HANA, you will also learn about the available
adaption and enhancement options.
“Cloud, On-Premise, and Hybrid Scenarios”
Contents
Index
The Authors
Frank Densborn, Frank Finkbohner, Jochen Freudenberg, Martina Höft,

Kim Mathäß, Boris Rubarth
Migrating to SAP S/4HANA
606 Pages, 2nd, updated and revised edition 2021, $89.95
ISBN 978-1-4932-2094-6
www.sap-press.com/5279
Chapter 3
Cloud, On-Premise, and Hybrid 3
Scenarios
You can use SAP S/4HANA in various cloud-based and on-premise editions.
But what are the differences between these operating models? And what
are the differences between the individual SAP S/4HANA editions?
When migrating to SAP S/4HANA, you’ll have to make some basic deci-
sions. You’ll have to select the type of system landscape and decide which
SAP S/4HANA functions you want and how they are supposed to be used
(see Figure 3.1). First, you’ll need to choose whether you want to run SAP
S/4HANA on-premise (i.e., the software is utilized on your enterprise’s hard-
ware), in the cloud (i.e., the software is leased and hosted by a provider), or
in a hybrid scenario (i.e., some parts of the business scenarios are out-
sourced to the cloud, other parts are kept on-premise). Furthermore, you’ll
have to decide whether you want to leverage the migration process to rede-
sign your existing business processes (greenfield approach) or whether to
generally keep these business processes with minimal alteration (brown-
field approach).
On-Premise
SAP S/4HANA
Cloud
SAP
Business Suite
SAP S/4HANA
Greenfield Cloud
Brownfield
Figure 3.1 Strategic Decisions for Migrating to SAP S/4HANA
89
3 Cloud, On-Premise, and Hybrid Scenarios 3.1 Overview of Operating Models
This chapter covers the basic options for and differences between the vari- ware are not required on premise. The enterprise’s IT staff can thus focus on
ous operating models and provides the basic information required to make other tasks.
the necessary decisions for your migration strategy. First, we’ll provide an Internet access is usually necessary to access the solution, and users can
overview of the operating models and define fundamental concepts. Then, access the cloud software from anywhere and, in most cases, also via
3
we’ll introduce and compare the individual editions of the SAP S/4HANA mobile end devices. One of the major benefits of the cloud operating model
product family. is the associated cost transparency. In cloud, the infrastructure is usually
Usually, an enterprise wants to customize its business processes. In addi- shared by multiple customers.
tion to business configuration settings, individual enhancement options To ensure efficient operation, individual customers can only influence the Limited scope for
can be an essential way for an enterprise to differentiate itself from com- maintenance cycles and schedules of the cloud software to a minimum intervention
petitors. The last section of this chapter describes in detail SAP S/4HANA’s extent. Additionally, the customization options in the cloud operating
enhancement concepts. model are usually more limited than in the on-premise operating model.
Another issue that needs to be analyzed specifically in each case is data
security (cloud security). In general, the data security standards and pro-
3.1 Overview of Operating Models cesses of trustworthy cloud providers are higher or more extensive than
the security infrastructure of the average enterprise.
To enable you to choose an SAP S/4HANA operating model, this section
describes the basic characteristics of the different operating models. Sec- How to evaluate the cloud operating model, however, also significantly Service and
depends on the service and deployment models used. Figure 3.2 provides deployment models
tion 1.2 gives an overview about the SAP S/4HANA product family and Sec-
tion 3.3 then compares the operating models of SAP S/4HANA. an overview of these service and deployment models, which are based on
the definitions from the National Institute of Standards and Technology
(NIST; https://www.nist.gov).
3.1.1 On-Premise Operating Model
For service models, the following three categories are differentiated: Service models
Full control of Usually, on-premise operating model refers to using software that a cus-
쐍 Software as a service
hardware and tomer has purchased upfront and runs and manages the operation of this
software In the case of the software-as-a-service (SaaS) model, customers use the
software on hardware owned by the customer. As a result, the customer is
applications of a provider, which are operated on a cloud infrastructure.
in full control of the hardware and software, of mission-critical application
Typically, customers access these applications via the internet using a
data, and of software maintenance schedules. Moreover, the customer
web browser. In the SaaS model, the provider is responsible for manag-
achieves maximum flexibility with regards to custom enhancements and
ing and controlling the cloud infrastructure. Customers do not have any
integration with other systems (in-house solutions or external systems).
functions for managing or controlling the software that go beyond user-
But the customer is also fully responsible for the availability of the soft- specific configuration settings.
ware, as well as access, security, and system stability. In addition to the
In addition to the SAP S/4HANA public cloud editions, the following SAP
costs for hardware and software, powerful and complex ERP systems incur
solutions fall into this category: SAP SuccessFactors, SAP Sales Cloud,
further costs for the IT experts needed to introduce, manage, and maintain
SAP Ariba, SAP Concur, and SAP Fieldglass.
the software.
쐍 Platform as a service
In the platform-as-a-service (PaaS) model, application developers are
3.1.2 Cloud Operating Model provided with programming languages and tools as a service. As in the
Leasing software In cloud operating models, a customer does not operate or manage the SaaS model, the provider is responsible for managing and controlling
and services software himself but rather engages a service provider for this purpose. The the underlying cloud infrastructure. The customers manage their own
software and the corresponding services are leased for a defined period of applications, which they have built on the basis of the development
time in the cloud operating model. Hardware and operating system soft- environment provided. One example of this model was SAP Cloud Plat-
form.
90 91
3 Cloud, On-Premise, and Hybrid Scenarios 3.1 Overview of Operating Models
In this model, the customers have control over the schedule and mainte-
SAP Cloud Platform Brand Retirement and SAP Business Technology nance of their own application, but not over the tools and services used
Platform by this application.
As of January 27, 2021, the SAP Cloud Platform brand has been sunset and its 쐍 Infrastructure as a service 3
many services and tools now run on SAP Business Technology Platform (SAP Infrastructure as a service (IaaS) refers to a service that provides users
BTP). SAP BTP is a unified platform of SAP technologies. At the time of this with access to computing power, data storage, and network capacity. In
book's writing, it has four pillars: database and data management, analytics,
this model, the customers control the applications and operating sys-
application development and integration, and intelligent technologies. The
tems used and usually also install them themselves. Nevertheless, the
application development and integration pillar includes cloud services that
provider is again responsible for controlling and managing the cloud
previously ran on SAP Cloud Platform and were known by the SAP Cloud
infrastructure. SAP HANA Enterprise Cloud (Section 3.2.3) belongs to this
Platform brand. The cloud-based application development services are
category.
referred to with the name SAP Extension Suite. The cloud-based integration
services are referred to with the name SAP Integration Suite.
For more information about SAP BTP, check here: https://www.sap.com/ PaaS
products/business-technology-platform.html. For information about the
SaaS
SAP Cloud Platform brand change, see this page: https://www.sap.com/ IaaS
products/cloud-platform.html.
Throughout this book, we will use the updated terminology to refer to SAP
Cloud Platform and SAP Cloud Platform services, but you should always
check the service catalog on the SAP Discovery Center (https://discovery- Service Model (Cloud Services)
center.cloud.sap/viewServices?) or reach out to SAP for an up-to-date list of
services and their names. Table 3.1 highlights a few important changes Deployment Model (Cloud Type)
that you’ll see referenced in this book:
Retired Terminology Current Terminology
SAP Cloud Platform services SAP Business Technology Platform’s cloud- Hybrid Cloud
based application development and inte- Public Cloud
gration services
Private Cloud
SAP Cloud Platform applica- SAP Extension Suite
tion development services
Figure 3.2 Cloud-Based Service and Operating Models
SAP Cloud Platform Integra- SAP Integration Suite
tion Suite
For the cloud deployment models, we differentiate three types: Deployment models
SAP Cloud Platform, Cloud SAP BTP, Cloud Foundry environment
쐍 Public cloud
Foundry environment
With public clouds, services and applications are publicly available and
SAP Cloud Platform, Neo SAP BTP, Neo environment can generally be used by everyone. Usually, users share the resources of
environment the cloud infrastructure, made available by a provider.
SAP Cloud Platform, ABAP SAP BTP, ABAP environment 쐍 Private cloud
environment In a private cloud, the cloud infrastructure is deployed for specific cus-
SAP Cloud Platform Identity SAP Platform Identity Provider service for tomers or only one customer. The cloud infrastructure can be deployed
Provider SAP BTP internally or by an external provider. The same applies to operating a
Table 3.1 SAP Cloud Platform Terminology Changes
92 93
3 Cloud, On-Premise, and Hybrid Scenarios 3.2 The SAP S/4HANA Product Family
private cloud. The difference to the on-premise operation model is grad-

ual and depends on the individual decision on how flexible and scalable
you need the IT infrastructure to be, how business applications will be
Cloud On-Premise
accessed via the internet, or how regularly programs should be updated 3
automatically.
쐍 Hybrid cloud Business Partners Business Partners Master
A combination of a public cloud and private cloud is referred to as a Data
hybrid cloud. In this case, part of the IT infrastructure is operated on Products Products Integration
premise, while other services are provided by an external public cloud
provider.
Order Purchase Order

3.1.3 Hybrid Operating Model Process
In hybrid operating models, some parts of the business scenario are oper- Integration
Invoice Invoice
ated on premise, and some parts are operated in the cloud. Hybrid operat-
ing models enable you to combine the characteristics of the on-premise
operating model and the cloud operating model.
For example, core areas of your enterprise, for which you want a high Figure 3.3 Integration in Hybrid Scenarios
degree of control and a high level of flexibility, can be operated on premise,
while other enterprise areas can be operated in the cloud because common Therefore, when choosing an operating model, you should consider your
industry standards are sufficient. specific requirements for master data and process integration.
Hybrid Structures in Human Resources

3.2 The SAP S/4HANA Product Family
An example of an enterprise area in which business processes are largely
outsourced to the cloud is human resources (HR). As described in Chapter 1, Customers can choose between multiple editions of the SAP S/4HANA
SAP’s target architecture for HR business processes is the cloud. With the product family
SAP SuccessFactors solution portfolio, SAP enables HR departments to out-
In general, we differentiate between the on-premise edition and the cloud On-premise and
source to the cloud functions such as workforce administration or manag-
edition. However, all members of the SAP S/4HANA product family are cloud editions
ing job candidates and applications, employee performance, or talent.
based on the same program code. End users will only see differences
between the editions due to the different UI concepts. SAP S/4HANA Cloud
Hybrid scenarios can also make sense based on the organizational struc-
only provides SAP Fiori-based UIs, while the SAP S/4HANA on-premise ver-
ture of an enterprise. For example, you might want to run global business
sion allows you to continue to use the traditional interfaces based on SAP
processes at your headquarters on premise, while the regional business
GUI for Windows.
processes at your subsidiaries can be standardized and outsourced to the
cloud. The deployment as a so-called private-managed cloud solution is a combi-
nation of the on-premise deployment model and the cloud deployment
Integration With regard to technology and content, a combination of on-premise pro-
requirements cessing and cloud-based processing poses specific requirements for inte- model. Depending on the attributes, characteristics of the on-premise ver-
grating the various solutions used, as outlined in Figure 3.3. sion can be deployed here. SAP offers a private cloud option in SAP HANA
Enterprise Cloud.
94 95
Figure 3.4 provides an overview of the entire SAP ERP product family as on-
premise and cloud versions for the respective market segments. Additional Information on SAP ERP Products
쐍 You can always find additional information on the individual SAP prod-
ucts on the SAP product page at https://www.sap.com/products.html. 3
쐍 For more information on SAP Business ByDesign go to http://s-prs.co/
Cloud On-Premise
52792000.
쐍 For more information on SAP Business One go to http://s-prs.co/52792
SAP S/4HANA Large 001.
SAP S/4HANA
Cloud Enterprises
3.2.1 SAP S/4HANA On-Premise Edition

SAP Business SAP S/4HANA for SAP In the SAP S/4HANA on-premise edition, customers operate the software in
ByDesign Medium Enterprises Business All-in-One their own system landscape. They are responsible for purchasing the neces-
sary hardware, for installing and managing the software, and for maintain-
ing the system (for example, implementing software changes).
SAP Business One SAP
(Cloud) Small Enterprises Business One In November 2015, SAP S/4HANA was published as the first version of a The digital core
new, comprehensive solution for core business processes within the on-
premise edition. The product name was SAP S/4HANA, On-Premise Edition
Figure 3.4 Entire SAP ERP Product Family 1511 (also referred to as SAP S/4HANA Enterprise Management in some doc-
uments). This on-premise edition is continuously enhanced on an annual
For better readability, we’ll combine the variants of the SAP S/4HANA prod- basis. SAP refers to SAP S/4HANA as a new digital core for enterprise soft-
ucts in this book. In Table 3.2, you can find the assignment of the terms used ware. Figure 3.5 shows this digital core, including the relevant innovations
in this book. that cover various lines of business (LOBs).
Classification SAP Products (as of August 2020) Terminology in this Book

SAP Ariba SAP SuccessFactors SAP Ariba
On premise SAP S/4HANA SAP S/4HANA SAP Fieldglass SAP Fieldglass
SAP S/4HANA
Private cloud SAP HANA Enterprise Cloud SAP S/4HANA SAP S/4HANA SAP S/4HANA Sourcing & SAP S/4HANA SAP S/4HANA
Finance Human Resources Procurement Supply Chain Manufacturing
SAP S/4HANA Cloud, extended
Digital Core
Digital Core
edition
SAP S/4HANA Enterprise Management
Public cloud SAP S/4HANA Cloud, essentials SAP S/4HANA Cloud,
edition essentials edition
SAP S/4HANA Cloud
SAP S/4HANA SAP S/4HANA Sales SAP S/4HANA SAP S/4HANA SAP S/4HANA
Marketing and Service Asset Research and
Table 3.2 SAP S/4HANA Product Family Commerce Management Development
In addition to SAP S/4HANA products, small and medium-sized enterprises Figure 3.5 Different Business Areas in SAP S/4HANA
can also use SAP Business ByDesign and SAP Business One. SAP S/4HANA
for SAP Business All-in-One is an industry-specific SAP ERP solution for For more information on product innovations in the individual business
medium-sized enterprises that was developed by SAP partners. The transi- areas, Section 3.3.
tions between these SAP ERP suite products are smooth. In this book, we’ll
only detail the various editions of SAP S/4HANA.
96 97
Compatibility SAP S/4HANA is supplemented by functions from so-called compatibility The useful life of the functions covered by the compatibility packages is Fixed-term
packages packages (see Figure 3.6). restricted. Up to the end of 2025, you can continue to use these functions in compatibility
packages
the traditional format. After 2025, the license for their usage in SAP S/4HANA
will no longer be valid. 3
SAP S/4HANA for central finance is a deployment variant of SAP S/4HANA. SAP S/4HANA for
In this variant, customers can connect their distributed system landscapes central finance
SAP S/4HANA
to a central SAP S/4HANA Finance system. Figure 3.7 demonstrates an
example of a combination of SAP and non-SAP systems in which financial
Business Areas and documents are replicated in SAP S/4HANA for central finance.
Industry Solutions Postings from finance and controlling are submitted from existing opera- SAP Landscape
Innovation tional source systems to the complementary central finance system. The Transformation
Functions Replication Server
SAP S/4HANA SAP Landscape Transformation Replication Server is responsible for repli-
Enterprise Management cating the actual data from the decentralized source systems to the central
finance system after the data has been initially exchanged. Optionally, a
central master data system (e.g., SAP Master Data Governance) can ensure
Traditional
the relevant financial master data is distributed.
Compatibility Packages SAP ERP
Functions
Non-SAP
System Central Finance
Figure 3.6 SAP S/4HANA Compatibility Packages
Non-SAP FI/CO
System
Compatibility packages provide functions with the traditional design you SD/ … Central
FI/CO SAP Landscape FIN Reporting
Central Finance
Non-SAP
are familiar with from SAP ERP—functions, for example, for human capital System Transformation
Interface
management (SAP ERP HCM), for warehouse management (SAP Warehouse SD/ … Replication Integrated Planning
…/… Server and Consolidation
Management), or for transport management (LE-TRA). After migrating to
Relevant
SAP S/4HANA, these functions are still available in the same format (e.g., …/…
Financial Documents Central Access
the data model is not adapted and the user interfaces remain the same). to All Financial Data
However, these functions are not the target architectures from the techno-
logical perspective. For example, the target architecture for human capital
management is SAP SuccessFactors; for warehouse management, SAP
Extended Warehouse Management (SAP EWM); and for transport manage-
Financial Master Data
ment, SAP Transportation Management (SAP TM). Consequently, compati-
bility packages provide functions that give you the option of continuing to SAP Master Data Governance
use traditional functions to simplify the migration to SAP S/4HANA. Usage

of these compatibility packages is intended for a transition phase only. Figure 3.7 SAP S/4HANA Central Finance
Gradual Migration to the Target Architecture

More Information on SAP S/4HANA On-Premise Editions
Fixed-term compatibility packages enable you to choose whether you
쐍 For further information on SAP S/4HANA Finance, see the SAP Help at
want to migrate directly to the target architecture in these subareas or
http://s-prs.co/52792002.
whether you’d rather continue using the traditional functions.
98 99
쐍 The SAP S/4HANA Compatibility Scope Matrix, attached to SAP

3.2.3 SAP HANA Enterprise Cloud
Note 2269324, lists the functions mapped by compatibility packages. Another variant is to deploy SAP S/4HANA as a private cloud solution—that Private cloud
쐍 For more details on SAP S/4HANA Central Finance, see SAP Notes is, as a hosted service. For this purpose, SAP provides SAP HANA Enterprise
Cloud. In this deployment variant, customers can individually choose
3
2148893 (Central Finance: Implementation and Configuration) and
2154420 (SAP Landscape Transformation Replication Server for Central between infrastructure and application management services. Depending
Finance). on the scope of the selected services, the result can vary between a private
cloud IaaS offering and an on-premise like implementation.
In this context, SAP HANA Enterprise Cloud supplements the SAP S/4HANA
3.2.2 SAP S/4HANA Cloud
editions and links infrastructure services and application services. Custom-
In SAP S/4HANA Cloud, SAP operates and maintains the software. Custom-
ers can either solely use the cloud infrastructure or additionally outsource
ers access their SAP S/4HANA Cloud systems from any network with inter-
the operation and maintenance of the SAP S/4HANA software. You can use
net access by using a browser and a unique, customer-specific URL.
all functions of SAP S/4HANA on-premise with this operating variant.
Multiple types of end devices are supported.
Customers can also flexibly select the application management services Application
Security Sophisticated security procedures such as the Transport Layer Security management
provided by SAP HANA Enterprise Cloud. For example, 24/7 service desk
(TLS) encryption procedure secure the communications between custom- services
operations, internal notification processing, transportation tasks (e.g.,
ers and the SAP S/4HANA Cloud system. In addition to this technical proce-
implementing SAP Notes), job management, authorization management,
dure, the following security and quality principles apply to SAP S/4HANA
print management, or interface administration can be outsourced to ser-
Cloud:
vice providers. SAP HANA Enterprise Cloud is not only provided by SAP but
쐍 Business data is stored in data centers according to the highest security also available from selected service partners, such as IBM or Hewlett Pack-
standards. ard Enterprise.
쐍 Customers may share physical hardware, but their data is always stored
separately.
3.2.4 SAP S/4HANA Cloud, Extended Edition
쐍 Users requiring access to business data have to authenticate themselves,
SAP S/4HANA Cloud, extended edition is a variant that meets specific Private cloud option
and their identity needs to be verified by user and access management.
enhancement and security requirements. For example, in the extended
쐍 Customers always remain the owners of their respective customer data. edition, customers are provided with enhancement options that go beyond
Implementation The technical deployment of the SAP S/4HANA cloud system is followed by the scope of the options of the public cloud edition. Customers have dedi-
the adaptation to individual requirements. For this purpose, the customer cated systems and do not share system resources. With regard to functions
implements the required business processes based on SAP S/4HANA and supported country versions, the extended edition corresponds to the
guided configuration. Then, you can use the SAP S/4HANA migration cock- SAP S/4HANA on-premise version.
pit to migrate the necessary data from your legacy system to the SAP Figure 3.8 shows an overview of the various SAP S/4HANA deployment
S/4HANA Cloud system. options.
SAP S/4HANA Cloud is a SaaS offering. In principle, monthly subscription In this specific context, you can imagine SAP HANA Enterprise Cloud as a
fees are based on the number and type of users. bridge from on-premise to SAP S/4HANA Cloud. With regard to the name,
Latest available The public cloud version is subject to a continuous innovation cycle. At the SAP S/4HANA Cloud stands for the public cloud version, which provides a
version time this book was created, the innovation cycle was quarterly. higher degree of standardized services. For this reason, maintenance cycles
and other operating parameters cannot be customized—just like in SAP
S/4HANA Cloud, extended edition.
Additional Information
For additional information on SAP S/4HANA Cloud, go to http://s-prs.co/
527920.
100 101
3 Cloud, On-Premise, and Hybrid Scenarios 3.3 Comparing the Operating Models
applications are fully installed. For the public cloud editions, SAP is respon-
Cloud On-Premise sible for operating, monitoring, and maintaining the system (implement-
ing enhancements and upgrades).
3
SAP S/4HANA, SAP S/4HANA Cloud
SAP S/4HANA Cloud SAP S/4HANA On-Premise Version
쐍 The customer 쐍 SAP or selected service part- SAP S/4HANA

SAP S/4HANA Cloud SAP S/4HANA
owns and main- ners provide the hardware Cloud (private
(Essentials Edition)
tains the hard- and infrastructure. cloud scenarios)
ware. 쐍 Depending on the service
SAP S/4HANA 쐍 The customer is level agreement, the cus-
SAP S/4HANA
Cloud
Enterprise responsible for tomer and SAP or selected ser-
(Extended
Cloud installing, operat- vice partners install the
Edition) Private Cloud
ing, maintaining, applications.
and managing the 쐍 Depending on the service-
applications. level agreement, the cus-
tomer and SAP or selected ser-
Figure 3.8 SAP S/4HANA Deployment Options
vice partners operate and
maintain the applications.
Additional Information 쐍 Hardware and infrastructure SAP S/4HANA

are located at SAP. Cloud (public
For more information on SAP HANA Enterprise Cloud, go to http://s-prs.co/
쐍 When the system is handed cloud scenarios)
52792003.
over, the applications are fully
installed.
쐍 SAP operates, maintains, and
manages the applications.
3.3 Comparing the Operating Models
Table 3.3 Overview of Hardware, Software, Operation, and Maintenance of
This section describes the individual characteristics of the respective oper-
SAP S/4HANA Editions
ating models in detail and compares how the corresponding editions of the
SAP S/4HANA product family meet these criteria.
At the time of this writing, maintenance cycles are specified as follows: Maintenance cycles
in the public cloud
쐍 Hotfix collection
3.3.1 Hardware, Software, Operation, and Maintenance A hotfix collection is implemented every two weeks.
Operation The most obvious difference between the on-premise and cloud editions is 쐍 Release upgrade
the fact that you operate, maintain, and manage the SAP S/4HANA on- Upgrades to the next SAP S/4HANA Cloud release are implemented
premise editions yourself, while SAP carries out these tasks in the public quarterly. Upgrades contain new functions and hotfix collections.
cloud editions. Public cloud editions are available via SaaS operating mod- 쐍 Emergency patch
els. All SAP S/4HANA Cloud editions are operated at different data centers Critical corrections for a specific customer system, if required, are imple-
located in various countries and regions around the world. Table 3.3 lists mented as soon as possible.
the differences in detail.
In the managed private cloud, customers can customize the scope of the Differences in the
Hardware in the For each public cloud edition, the hardware can be obtained in different managed private
public cloud
required hardware and the supported services to a large extent. For the
packages, depending on the number of users and the required size of the cloud
hardware, you can choose between a two-tier or three-tier landscape (public
SAP HANA database storage. When the cloud system is handed over, the
cloud editions consist of a two-tier system landscape). From the services
102 103
3 Cloud, On-Premise, and Hybrid Scenarios 3.3 Comparing the Operating Models
available, you can choose implementation services (requirements analysis, innovations are available. However, the editions vary with regard to their
implementation, data migration, go live) and operation services (incident, functional scope, the supported country versions, and the options for cus-
problem, and change management and application monitoring). In SAP tomizing the business processes (see Table 3.5).
S/4HANA in SAP HANA Enterprise Cloud, you can even control details like 3
maintenance dates. SAP S/4HANA, SAP S/4HANA Cloud
On-Premise Version
쐍 64 countries with 쐍 64 countries with SAP stan- SAP S/4HANA Cloud

Additional Information
SAP standard dard localization (private cloud)
You can find further information on this topic in the SAP agreement docu- localization 쐍 Process flexibility accord-
ments at http://s-prs.de/v631617. 쐍 Process flexibility ing to on-premise configu-
according to on- ration options
premise configura-
쐍 41 countries with SAP stan- SAP S/4HANA Cloud
3.3.2 User Interfaces tion options
dard localization (public cloud)
UI technology In all SAP S/4HANA editions, the role-based approach of SAP Fiori is the 쐍 Process flexibility accord-
basic target UI technology. Thus, the public cloud editions are completely ing to cloud scenarios and
the guided configuration
designed for this target architecture. In individual cases, public clouds also
approach of the public
use other web-based SAP technologies, such as Web Dynpro, in addition to
cloud
SAP Fiori. In the on-premise edition and the private cloud edition, you can
also use SAP GUI for Windows in addition to the web-based UI technologies Table 3.5 Functional Scope and Supported Country Versions for SAP
(see Table 3.4). SAP GUI-based transactions that can no longer be executed S/4HANA Editions
in SAP S/4HANA on-premise are included in the simplification list for SAP
S/4HANA (see Chapter 7, Section 7.2.3). You should use the SAP Fiori launch- The on-premise versions and the private cloud edition have the same busi- On-premise version
ness functions and support the same country versions. The complete func- and private cloud
pad as the central entry platform for end users in all SAP S/4HANA editions.
tional ERP scope is supported in 64 countries with the standard SAP localiza-
tion. To adapt these SAP S/4HANA editions to your specific requirements, all
Gradual Migration to the SAP Fiori Target Architecture
the traditional configuration options are still available in the Implementa-
Because traditional user interfaces are still supported, gradual migration
tion Guide (IMG).
to SAP S/4HANA is feasible.
The functional ERP scope provided in the public cloud editions differs par- Public cloud
tially from the functional scope of the on-premise edition. For example,
SAP S/4HANA, SAP S/4HANA Cloud compatibility packages (Section 3.2.1) are not available in the public cloud
On-Premise Version edition. The supported functional scope is based on the best practices con-
쐍 Web technologies 쐍 Web SAP S/4HANA Cloud tent of the public cloud edition, which has been deployed as preconfigured.
쐍 SAP GUI for Win- 쐍 SAP GUI for Windows (private cloud) SAP S/4HANA Cloud supports more than 40 countries with corresponding
dows localizations and numerous languages. The functional scope and localiza-
쐍 Web SAP S/4HANA Cloud
tions are extended continuously.
(public cloud)
Table 3.4 UI Technologies of SAP S/4HANA Editions Additional Information

쐍 For more details on the functional scope and supported country ver-
3.3.3 Functional Scope and Supported Country Versions sions, see Feature Scope Description in the SAP Help Portal (http://
The on-premise and public cloud editions of SAP S/4HANA are based on the help.sap.com/s4hana) and in the globalization area (http://s-prs.de/
same program code line. Consequently, the same data models and product v631618), as well as in SAP S/4HANA Cloud.
쐍 The product roadmap is available at http://s-prs.co/52792004.
104 105
3 Cloud, On-Premise, and Hybrid Scenarios 3.4 Extensibility of SAP S/4HANA
3.3.4 Options for Enhancement 3.3.6 Model for Migration to SAP S/4HANA
Cloud editions Basically, you can use the key user enhancement tools and enhancement With SAP S/4HANA on premise, customers can choose either the brown- Brownfield or
options, which are based on SAP Extension Suite (extension services that field approach or the greenfield approach. In other words, you can either greenfield approach
run on SAP BTP), in all editions of the SAP S/4HANA product family (see convert an existing SAP ERP system to an SAP S/4HANA system or install a
3
Table 3.6). In SAP S/4HANA Cloud (private option), you can carry out further completely new SAP S/4HANA system.
adaptations through ABAP programming. With these adaptations, modifi-
Migrating to SAP S/4HANA Cloud always entails a new installation of the
cation-free enhancements are possible, which can be used for Business
system. The business processes supported in SAP S/4HANA Cloud are
Add-Ins (BAdIs) and user exits.
implemented according to best practices, and the required master and doc-
On-premise editions Beyond that scope, in the on-premise editions it is theoretically possible to ument data is transferred to the cloud system (see Table 3.8).
even modify SAP objects, but we don’t recommend doing this considering
the increasing costs for future release changes. Section 3.4 describes the SAP S/4HANA, SAP S/4HANA Cloud
SAP S/4HANA enhancement options in detail. On-Premise version
Brownfield or green- New installation with sub- SAP S/4HANA Cloud

field approach sequent data migration (private cloud)
On-Premise Version
쐍 Traditional enhance- 쐍 Selected enhancement options SAP S/4HANA SAP S/4HANA Cloud
ment options through through ABAP programming Cloud (private (public cloud)
ABAP programming 쐍 Usage of the key user enhance- cloud)
쐍 Usage of the key-user ment tools for SAP S/4HANA Table 3.8 Migration Scenarios for SAP S/4HANA Editions
enhancement tools 쐍 Enhancements based on SAP
for SAP S/4HANA Extension Suite For more information on new implementations or on converting single
쐍 Enhancements based systems, see Part II of this book.
쐍 Usage of the key user enhance- SAP S/4HANA
on SAP Extension
ment tools for SAP S/4HANA Cloud (public
Suite
쐍 Enhancements based on SAP cloud)
Extension Suite 3.4 Extensibility of SAP S/4HANA
Table 3.6 Enhancement Options for SAP S/4HANA Editions Every enterprise is unique, not just in the specifications for its products or
services, but in its employees, its goals, and thus its business process struc-
3.3.5 Payment Model and Runtime tures. In the ideal case, business software supports such uniqueness and
License or Variants of SAP S/4HANA on-premise still offer the traditional license and the resulting differences because these details differentiate the enterprise
subscription maintenance model, whereas the public cloud editions are provided via a from its competitors.
cloud subscription model with flexible runtimes (see Table 3.7). The actual To date, SAP has supported differentiation to the greatest extent possible Previous SAP
costs for the subscription model depend on the number of users, the appli- with its software: SAP provided released interfaces and disclosed the source enhancement
options
cation scope used, and the hardware packages selected. code of the entire application. Moreover, SAP offered SAP NetWeaver Appli-
cation Server ABAP (SAP NetWeaver AS ABAP), which is a development
environment in the application system. SAP provided several options for
On-Premise Version
integration with other applications, such as SAP Process Orchestration.
License and 쐍 Flexible model (license and main- SAP S/4HANA Cloud With this portfolio, SAP has created an optimally customizable solution
maintenance fee tenance fee or subscription) (private cloud)
with scalable enhancement options. Third-party providers also appreciate
쐍 Customers can contribute exist-
ing SAP licenses
this extensibility and can deliver supplementary functions for standard
SAP solutions. When planning your migration to SAP S/4HANA, you should
쐍 Subscription with flexible run- SAP S/4HANA Cloud
always pay attention to the solution’s extensibility.
times (public cloud)
Table 3.7 Payment Models and Runtimes of SAP S/4HANA Editions
106 107
Extensibility put In SAP S/4HANA, SAP has refined this extensibility, which has been adapted To implement this extensibility, SAP follows two approaches:
to test according to SAP’s simplification philosophy for products. Particular atten-
쐍 Side-by-side enhancements
tion was paid to allowing customization without comprehensive program-
쐍 In-app enhancements
ming knowledge but also provide the flexibility required for significant 3
enhancements. In SAP S/4HANA, these concepts were improved. In this Both approaches complement each other and can be combined. Figure 3.9
way, the disadvantages of extending the standard software to meet individ- compares the two enhancement approaches. These approaches are des-
ual requirements are minimized. In the past, the high degree of flexibility cribed in detail in the following sections.
in SAP ERP could lead to risks that had to be considered individually in each
specific case: comprehensive enhancements entailed projects involving SAP S/4HANA Enhancement Options
several parties within the enterprise, and sometimes implementation part-
In-App Enhancements Side-By-Side Enhancements
Interaction Regarding Maintenance Operations

ners as well. Thus, it could take some time before an enhancement could
End Users Enhancement via SAP Cloud Solutions, e.g.
actually be used. When enhancements were implemented, the next risk • Personalize Layout • SAP Success Factors
• Simple Data Operations • SAP Ariba
was in the operation of the software: During the lifecycle of the software, • SAP Concur
• Forward Navigation
hotfixes and planned updates to the default software are usually installed. • SAP Fieldglass
Testing and adjusting custom developments in this constantly updating Business Key Users Enhancement via SAP Extension Suite on SAP BTP
• Custom Fields/Tables
software lifecycle can involve a great deal of effort. • Forms
• Custom Calculation Rules/Logics Custom Enhancement Third-Party Providers
New extensibility Consequently, the extensibility in SAP S/4HANA has been adapted to accel- • Custom SAP Fiori UIs • Integration with
• Custom ABAP- & JAVA- Third-Party
concepts erate the implementation of enhancements and simultaneously reduce the Traditional Extensibility Based Enhancements Solutions
• Full Access to SAP ABAP Source Code • SAP HANA Development
costs of these enhancements. In particular, modifying the default SAP code
can be avoided in most cases. For this purpose, SAP S/4HANA provides tool- SAP S/4HANA Add-Ons
• Traditional Enhancement in Single System Through Third-Party Providers
based enhancement options in the applications themselves, as well as plat-
Available for S/4HANA Cloud
form-based enhancement options outside the software product. These
functions support the following characteristics: Available for S/4HANA On-Premise
쐍 Scaled extensibility
Figure 3.9 Enhancement Options in SAP S/4HANA
The default software can be customized at various levels. For example,
end users can personalize their user interfaces and implement their own
The in-app and side-by-side approaches involve various levels. The deeper
(restricted) enhancements. Selected experts can be authorized to imple-
the level, the greater the impact on the software lifecycle. Not all options
ment further enhancements that affect the processes of multiple users.
are available in all deployment options (Section 3.3.4).
At the top level, you can customize the entire application in an imple-
mentation project.
쐍 Scaled lifecycle 3.4.1 Side-By-Side Operation
You can loosely couple enhancements. While enhancements can The characteristic of side-by-side enhancements is that they use Extension SAP Extension Suite
exchange data with SAP S/4HANA and are merged on the user interface, Suite services that run on SAP BTP. In addition to the SAP HANA database,
they can also perform independent software maintenance cycles. this solution contains comprehensive tools for developing, testing, inte-
쐍 Openness grating, and operating the SAP software.
SAP S/4HANA includes a vast array of open interfaces, so partners can
Enhancements on SAP Extension Suite can be carried out using various
implement existing enhancements or offer their own enhancements.
implementation approaches, such as Java code, HTML5 commands, and
SAP HANA database queries. Consequently, this enhancement approach is
Extensibility of SAP S/4HANA particularly suited to developing custom user interfaces easily and inte-
You can customize SAP S/4HANA using various enhancement procedures. grating additional steps into SAP standard business processes.
108 109
ABAP in the Cloud Since the end of 2018, SAP has also offered a cloud-based ABAP development Gateway for integration with SAP Fiori. Consequently, SAP Extension Suite
and runtime environment: SAP BTP, ABAP environment (previously, SAP is the optimal basis for enhancements—not only for SAP S/4HANA but also
Cloud Platform, ABAP environment). By using this product for side-by-side for other applications in the landscape.
enhancements, you can efficiently utilize existing ABAP know-how for cre- Extending SAP S/4HANA via SAP Extension Suite uses SAP’s APIs, including Released interfaces
3
ating future-proof enhancements—both for SAP S/4HANA Cloud and for the following:
the on-premise version.
쐍 New SAP S/4HANA interfaces:
You can find more details on this topic in Section 3.5.
– Representational State Transfer (REST) web services
– Simple Object Access Protocol (SOAP) web services
Side-By-Side Operation
– Open Data Protocol (OData) web services
The enhancement options based on SAP Extension Suite are ideal for cre-
쐍 Traditional SAP interfaces:
ating custom user interfaces or additional business process steps.
– BAPIs
– Intermediate Documents (IDocs)
User Interfaces
The traditional interfaces are included for compatibility reasons and only
Development The SAP Fiori user interfaces are written with HTML5 and are based on cen-
released for the enhancement of the SAP S/4HANA on-premise version. The
environment for tral SAP libraries (SAPUI5). The software development process for HTML5
SAPUI5: SAP Web number of interfaces released is continuously increasing.
applications differs from the development in ABAP, which is the language
IDE
used to implement the SAP S/4HANA application logic. Therefore, SAP
Using the SAP API Business Hub
S/4HANA does not contain a development environment for HTML5.
Instead, SAP provides an optimized development environment for SAP In some cases, it’s a challenge to find the right interfaces for a planned
Fiori user interfaces called SAP Web IDE, available via the SAP Extension enhancement. In addition to finding the interface and interpreting the
interface parameters, you also need to consider for which application
Suite on SAP BTP. In addition to development tools such as an editor, this
cases the interfaces were released by SAP. For this reason, SAP provides
also includes tools for packaging and deploying the user interfaces devel-
SAP API Business Hub as a central repository for APIs. This repository
oped (see http://s-prs.co/527921).
doesn’t cover all available SAP APIs, but instead focuses on the interfaces
and Core Data Services (CDS) views that are recommended for cloud-ori-
Business Processes ented enhancements. The usage of interfaces is described and a test
Additional Java SAP S/4HANA enables you to supplement existing business processes with option is provided. You can find the SAP API Business Hub at https://
applications your own business logic and data. In most cases, you’ll only need to adjust api.sap.com/. In the SAP S/4HANA Cloud or SAP S/4HANA category, you’ll
the SAP standard processes to your specific business requirements. In some find the interfaces that are relevant for the enhancement of SAP S/4HANA.
cases, however, your processes deviate so much from the processes of your
competitors that this deviation can no longer be mapped by in-app en-
hancements. SAP Extension Suite is the ideal enhancement solution here, 3.4.2 In-App Enhancements
allowing you to build complex custom applications side by side and then In-app enhancements are striking because of their simplicity: These
integrate them with SAP S/4HANA. Communication with the platform is enhancements are implemented in the same system, connections to other
via web services. The enhancement logic itself can be created either in Java systems are not necessary, and latency is reduced. Furthermore, you can
or—since 2019—in ABAP (Section 3.5). use the existing application as a base and use the powerful ABAP Dictio-
Integration SAP BTP already provides the required integration infrastructure for both nary, which contains the CDS, to create table views, for example.
infrastructure cases: a central integration middleware with SAP Integration Suite and SAP
110 111
Enhancements You don’t necessarily need any development know-how for enhancements
without developer and you can leverage the following extensibility options:
knowledge
쐍 End user extensibility
3
쐍 Key user extensibility
The key user extensibility in particular provides the options shown in Fig-
ure 3.10.
Enhancements Enhancements Enhancements Enhancements

End User A End User B End User C End User D
Key-User Enhancements
Adaptation of Custom Analyses

Custom Forms
User Interfaces and Reports
Custom Fields
Custom
Custom Tables Application Logic
(Code-Based)
Traditional Enhancements (On-Premise only)
Figure 3.11 End User Enhancements for User Interfaces

Figure 3.10 In-App Extensibility
Key User Enhancements
Enhancements carried out by central key users impact all users of the sys- SAP also provides enhancement options that can be implemented partially Modeling
tem, who in turn can make specific adaptations. The traditional extensibil- using modelling procedures, which is useful when customizing user inter-
ity of the ABAP source code is only available on premise and is mainly faces or supplementing custom fields or tables. In a new enhancement mode,
included for compatibility reasons. you only need basic development know-how to modify the calculation logic
without directly changing the application code. One of the advantages of this
End User Enhancements method is that you don’t have to adapt enhancements manually when main-
User-specific End user enhancements can be implemented directly in SAP Fiori applica- taining your SAP software. As a result, operating costs are reduced compared
customization tions. These enhancements are user-specific and do not affect other users to traditional, code-based enhancements. In contrast to end user enhance-
of the SAP S/4HANA system. Simple enhancements include customizing ments, key user enhancements affect all system users. Remember that a spe-
screen layouts or selection fields, simple column operations, and basic set- cific authorization is required for these key user enhancement options. This
tings for object-based navigation. These enhancements can only be carried authorization needs to be defined in the SAP_CORE_BC_EXT application catalog
and assigned in accordance with the application role.
out in specifically prepared applications, and you can access enhancements
via the cogwheel icon in the application (see Figure 3.11). You can even cus-
tomize the cogwheel icon in most SAP Fiori screens. Advantages of Key User Enhancements
Key user enhancements use modeling rules that will not need subsequent
adaptations for maintenance operations.
112 113
Enhancement Key user enhancement options are selected via SAP Fiori tiles, which are addition, you can point an interface to access this newly created busi-
options predefined by SAP. Among others, the following options are provided: ness object. Doing so enables you, for example, to access these business
쐍 Customizing user interfaces objects when specifying calculation logic. To access business objects,
Similar to end user customization, you can change the layout of SAP select the User-Defined Business Objects tile in the Extensibility group. 3
Fiori applications. Examples include hiding fields, renaming identifiers, 쐍 Adjusting the calculation logic
rearranging blocks, and creating selection variants. These activities do You may often find it necessary to check the meaning of entered or dis-
not require any development know-how. To customize a user interface, played data, to specify defaults, or to trigger exception handling.
in the application that you want to change, select the user icon in the Another example of a calculation logic adjustment is specific calculation
upper left of the screen first. You can then change the user interface procedures that are not provided in the SAP standard. In these cases,
using the Adjust UI icon. additional logic can be inserted in the relevant applications.
쐍 Field extensibility
The logic is defined in a code-based implementation via a web editor (see
In the business contexts provided for that purpose, you can define addi-
Figure 3.13).
tional fields for the application to use (see Figure 3.12). Select the User-
Defined Fields and Logic tile in the Extensibility group on the SAP Fiori
launchpad. These fields are not only displayed on the user interface but
can also be stored in the SAP data model and are thus available in the
database views, for searches, and for other operations.
Figure 3.12 Extensibility of Fields
쐍 Table extensibility
Besides new fields, you can also define and use custom tables in SAP
S/4HANA. Similar to custom fields, custom tables are created within
SAP S/4HANA and integrated into user interfaces. The application then Figure 3.13 User-Defined Fields and Logic
exchanges data with the table. A custom table is a special kind of user-
defined business object. In the editor, the syntax is simplified in comparison to traditional ABAP so
that detailed ABAP know-how is not required. For this adaptation, use the
쐍 Business objects
User-Defined Fields and Logic tile in the Extensibility section and then the
You can define specific business objects for your enhancements. Busi-
ness objects are sets of tables between which you define relationships. In
114 115
3 Cloud, On-Premise, and Hybrid Scenarios 3.5 ABAP-Based Enhancements via SAP BTP, ABAP Environment
User-Defined Logic tab. However, you will need some development know- 3.4.3 Checking Custom Enhancements when Migrating
how for this activity. Compared to traditional enhancement options, you’ll to SAP S/4HANA
be provided with numerous commands and instructions in this tile. You When you plan to migrate to SAP S/4HANA, you should analyze existing Analyzing existing
can also save these enhancements and export them to other systems. adaptations 3
adaptations to the current system:
쐍 End-user customization
Transport of Enhancements Individual end-user adaptations are lost when you migrate to SAP
In general, key user enhancements should be implemented and tested in a S/4HANA. Users will have to then customize the new product again, as
quality assurance system first. To transport verified enhancements to the described in Section 3.4.2.
production system, you can follow this export and import procedure: After
쐍 Generic enhancements for all users
developing your enhancement, select the Export Software Collections tile
Generic enhancements that are effective for all system users can be im-
in the Extensibility group. Next, assign your enhancement to a software
plemented when migrating to the new product. The appropriate proce-
collection, which you can then export.
dure for this implementation depends on the operating model selected
Now, in the target system, select the Import Collection tile in the Extensi-
for SAP S/4HANA. You should generally implement these enhancements
bility group, where you can import the previously exported enhancement.
using the key user enhancement options, which will result in fewer fol-
Note that export and import should be carried out by a software logistic
low-up costs and simplify the maintenance of the enhancements.
administrator; as a result, this activity requires specific roles with access to
the SAP_CORE_BC_SL_EXP (for exporting) and SAP_CORE_BC_SL_IMP (for If the source system is an SAP source system, you should run SAP’s cus-
importing) application catalogs. tom code check first. This check identifies custom code in the existing
system and generates a task list. Chapter 7, Section 7.2.6 discusses this
check in detail.
Additional Information on Enhancement Options

Further options are available in addition to the described enhancement
options. For more details, see the Extensibility section in the product docu-
3.5 ABAP-Based Enhancements via SAP BTP,
mentation at http://s-prs.co/52792005. ABAP Environment
When planning the migration to SAP S/4HANA, users were faced with a dif-
ficult dilemma: if they wanted to reduce the interaction of their custom
Traditional Extensibility enhancements with SAP maintenance events, at the time, they had to use
ABAP In the on-premise version of SAP S/4HANA, you can still enhance or even SAP Cloud Platform (now SAP Extension Suite services on SAP BTP). There-
enhancements modify the ABAP source code using the tools from the traditional SAP Busi- fore, the enhancement had to be implemented completely anew, for exam-
ness Suite, such as the ABAP Workbench. While this approach offers the ple, in Java. If they wanted to implement the applications in ABAP, usually
maximum freedom to develop your own custom enhancements, interac- only the SAP S/4HANA on-premise version qualified, whereby a link to SAP
tions regarding maintenance operations in the system will often be neces- maintenance events still existed.
sary. When implementing new SAP corrections, you’ll always have to adjust
Fortunately, a new option provides additional alternatives for planning
your enhancements to the SAP Notes. As a result, you need to install correc-
custom ABAP code. SAP has published a new product line called SAP BTP,
tions in close cooperation with your development department. When
ABAP environment.
migrating to SAP S/4HANA, you should also consider how custom enhance-
ments can be re-implemented using the new options. You don’t have to do
this for all existing enhancements; it’s subject to individual consideration. 3.5.1 SAP BTP, ABAP Environment
In addition to these more formal enhancement options, SAP S/4HANA also SAP BTP, ABAP environment (formerly known as SAP Cloud Platform, ABAP
provides comprehensive applications for defining custom data analyses or environment) is a stand-alone cloud product of SAP. It provides the latest,
creating custom forms. cloud-optimized version of ABAP design and runtime (see Figure 3.14).
116 117
The application core of SAP systems remains mostly unchanged because

Eclipse
Development SAP BTP, ABAP Environment you only need to implement interfaces. This is another advantage with
Environment regard to complying with security requirements.
as Frontend
ABAP Design and Runtime Layer The system is managed by SAP because SAP BTP, ABAP environment is a System
3
native cloud application. This reduces the workload of the enterprise’s IT management
SAP Fiori UI
Environment by SAP
department. This also results in easy scalability because you don’t need to
Source Code SAP HANA Persistence Layer take care of hardware procurement.
Management
via GitHub Considered as a whole, the approach of implementing custom enhance-
ments via SAP BTP, ABAP environment enables you to use the advantages
Cloud-Based Deployment of the cloud without having to complete the migration of all your applica-
tion systems to the cloud.
Figure 3.14 Overview of SAP BTP, ABAP Environment
Possible Migration Scenarios
It offers numerous advantages—not only with regard to the migration of Chapter 4 discusses the basic scenarios for migrating to SAP S/4HANA New migration
existing SAP ERP systems to SAP S/4HANA: Cloud. If you include SAP BTP, ABAP environment in your considerations, concepts
쐍 Utilization of the existing ABAP knowledge base interesting new approaches for project planning arise. This section dis-
The enterprise’s ABAP expertise that has been established over the years cusses these additional options.
can still be utilized. But other SAP Extension Suite services can also be The starting point for migrating to SAP S/4HANA is the general decision for
integrated. this target scenario—for example, SAP S/4HANA Cloud or the SAP S/4HANA
The original extensibility of SAP S/4HANA Cloud can be supplemented on-premise version—and the planning and realization of the technical and
with comprehensive side-by-side enhancements. content-related conversion project. This conversion project can be devel-
oped in more detail using SAP S/4HANA Cloud.
쐍 Independent innovation cycles
The innovation cycles for custom coding can be specified independent
of the SAP application system. As a cloud product, SAP BTP, ABAP envi- Utilization of SAP HANA
ronment receives the latest functional enhancements at short intervals If your SAP application system is not yet operating on the SAP HANA data-
while still providing full compatibility with existing implementations, base, you might want to gain experience with SAP HANA to enable better
so the speed of innovation in custom developments can be increased planning of the migration effort. In this case, you have the option of migrat-
considerably. ing the existing SAP application system to SAP HANA. However, this may
쐍 Custom SAP HANA database also entail unnecessary additional effort because the conversion to SAP
SAP BTP, ABAP environment includes its own SAP HANA database. This HANA takes place anyway together with the planned migration to SAP
enables you to use the advantages of the SAP HANA database without S/4HANA.
your SAP application systems having been migrated to SAP HANA yet. SAP BTP, ABAP environment offers a cloud environment that is already SAP HANA-based
based on SAP HANA. You can replicate selected data to your SAP BTP, ABAP cloud environment
Custom enhancements are future-proof. As side-by-side enhancements,
environment. This enables you to immediately investigate how you must
they are not included in the SAP source code, but they communicate with
optimize your code for SAP S/4HANA and which additional options arise
the SAP application using stable interfaces. For these interfaces, a contract
through SAP HANA. The side-by-side approach ensures that the application
against modifications exists. Therefore, they don’t need to be synchronized
system remains completely unaffected.
when the SAP application is maintained. Their enhancements are located in
a separate system in the cloud and thus become independent of version Similarly, you can start to supplement your production system(s) with SAP
changes. HANA-based enhancements to bridge the systems until the full conversion
to SAP S/4HANA takes place.
118 119
Alternative Check of Custom Code 3.5.2 Migrating Custom ABAP Code to SAP BTP, ABAP Environment
The migration to SAP S/4HANA includes the check and adaptation of cus- The migration of your existing code to SAP BTP, ABAP environment com-
tom code. As described in Section 3.4.3, custom code must be checked for prises several steps:
compatibility with SAP S/4HANA. Adjustments may be necessary. 3
1. Analyzing the existing code
If you need to check and adapt your code within the scope of the SAP
2. Estimating the modification effort
S/4HANA migration project, SAP BTP, ABAP environment offers two inter-
3. Creating a roadmap
esting approaches:
4. Technical migration
Decoupled lifecycle 쐍 Architectural decoupling
Depending on the scope of your existing enhancements, it may be advis- 5. Adapting the migrated code
able to decouple the architecture. If you have comprehensive custom 6. Testing
code, you may want to decouple the software lifecycle of your code from 7. Converting
the application system’s lifecycle in the future. In this case, it’s advisable
to separate the code in a side-by-side approach. Fortunately, SAP offers various tools that facilitate several of these steps.
This minimizes the effort of migrating the code to SAP BTP, ABAP environ-
Unfortunately, SAP no longer offers any further development for SAP
ment. The following sections provide an insight into the processes for the
NetWeaver. This eliminates the option to run this decoupling through
an (on-premise) SAP NetWeaver system. This gap is filled with SAP BTP, individual steps.
ABAP environment. You can separate your applications into this cloud-
based system. Analyzing the Existing Code
쐍 Time-wise decoupling The migration to SAP BTP, ABAP environment also involves a code scan
Thanks to the independent lifecycles of the SAP application system and using special checks. This process is similar to the one described in Chap-
your enhancement system, you can immediately start to migrate your ters 7 and 8. In this special case, in addition to the adaptation to SAP S/4HANA
applications. You do not need an SAP S/4HANA system for this purpose. described previously, you must also identify adaptations required for the
You also do not have to synchronize in terms of time when converting adaptation to the ABAP cloud environment. For this purpose, you can use
the applications. an SAP BTP, ABAP environment system as the check system. Your current
application system doesn’t need to be upgraded to a specific SAP version to
SAP offers supporting services for transferring your existing code to SAP
get the latest checks. However, the checks must be made against a func-
BTP, ABAP environment, which are described in the next section.
tional combination of code and content. We therefore recommend a check
against your current source system.
Trial System for SAP BTP, ABAP Environment
SAP offers comprehensive options for extensions via the SAP Extension
Duplicate Check?
Suite on:
You require two checks for the migration of custom code to SAP BTP, ABAP
https://www.sap.com/products/extension-suite/capabilities.abap.html
environment (which is discussed in this chapter) within the scope of a
Details on SAP BTP, ABAP Environment can be found at: migration to SAP S/4HANA:
https://discovery-center.cloud.sap/serviceCatalog/abap-environment
1. One check is for the compatibility of the code against the new version
The option to use a free trial system is particularly useful. Although this of the SAP S/4HANA application because functions from SAP ERP
trial system does not offer the full functional scope and is shared with
releases are no longer available in the same form due to simplification.
other users, it still enables you to get an initial practical impression of the
2. The other check is for compatibility with the new ABAP language scope
basic offering, as described in a blog post at:
in SAP BTP, ABAP environment.
http://s-prs.de/v745537
120 121
Custom code check For this purpose, you provision an appropriate cloud system at SAP using 쐍 Importance for future operating processes in SAP S/4HANA
your cloud cockpit. This system establishes a remote connection to your How important is this function for the planned business target pro-
current application system—for example, your development system. The cesses?
ABAP test cockpit will be used for the actual checks. For this purpose, you 3
Particularly if you use an older version of an SAP ERP system, some of your
run the cloud platform readiness check using the SAP_CP_READINESS RFC-
enhancements may no longer be required in the current scope because
enabled check variant. You can check systems as of SAP Basis version 7.00.
they can be covered through the new default functional scope.
Check using your As an alternative, you can also use your own ABAP test cockpit system on
own ABAP test When you estimate the modification effort, consider both the adaptations
premise. However, this scenario requires the availability of an ABAP test
cockpit system to the language scope of SAP BTP, ABAP environment and the adaptations
cockpit system with SAP Basis 7.52 SP 1 or higher. You also must first imple-
to SAP S/4HANA.
ment the following SAP Notes in this scenario (at the time of this book's
writing, these notes still used the SAP Cloud Platform brand in their titles):
Technical Migration
쐍 SAP Note 2682626, Code Inspector Check for Restricted Language Scope
SAP BTP, ABAP environment supports Git, the current source code manage-
Version 5 (ABAP for SAP Cloud Platform)
ment system. The sources are no longer processed using SAP Transactions
쐍 SAP Note 2684665, Custom Code Checks for SAP Cloud Platform, ABAP
like SE80 or the like. Instead, they are processed using the ABAP Developer
Environment
Toolkit for Eclipse.
쐍 SAP Note 2830799, Custom Code Checks for SAP Cloud Platform, ABAP
From the technical point of view, this means that sources that reside in the Git repository
Environment
current ABAP systems must be transferred to Git. For this purpose, we
The technical prerequisites in the target system are identical in both cases. assume that you already have a Git account. For the transfer, you can use
You will find more details in SAP Note 2364916. In both cases, you configure the open-source ZABAPGIT program, which is available in the repository at
the target systems to be checked using Transaction SM59. http://s-prs.co/527922. This utility program is maintained by an open-
source community and is not provided by SAP.
Estimating the Adaptation Effort Ensure that the appropriate ABAP Git enhancement is installed on the
Once the checks are complete, you receive a list of any potential issues Eclipse frontend used. This enhancement should appear in the feature list
detected. Based on this, you can estimate the resulting efforts in detail. under the name abapGit for ABAP Development Tools (ADT). You can also
Partially automated Note that SAP offers so-called quick fixes for numerous adaptations. The use the following URL: http://eclipse.abapgit.org/updatesite/.
adaptations via list of available quick fixes is updated continuously. If a quick fix is avail- Additional information on installing ABAP Git is available on the SAP Help
quick fixes
able, it’s highlighted in the result list, and you can select it in the context Portal: http://s-prs.de/v745539.
menu of the check result. Thus, these results can be repaired in a mecha- The code is transferred at package level. We recommend the following pro- Transferring
nized way, so to speak. cedure: Create a list of packages whose objects are to be transferred from the codes
the source system. Add these packages to your Git repository in ZABAPGIT. In
Creating a Roadmap the target system project, create the packages in the development environ-
Similar to the project to migrate to SAP S/4HANA, we recommend consider- ment using the same name. In the target system project, connect the newly
ing several dimensions when planning your adaptations: created packages with your ABAP Git repository.
쐍 Effort of adaptations Your objects are now available in the target system project. Note that the Separating
code lines are separated from this point on. Because objects of the source code lines
Is it possible to do “mechanical” adaptations using quick fixes? Or are
there many outdated technologies, such as Dynpro, which must be con- system usually cannot be run without making adaptations in the target sys-
verted to SAP Fiori UIs? tem, the implementations of your objects differ. Corrections to the source
쐍 Urgency system objects should be made manually. It is not recommended to repli-
Which functions must or should be updated first? cate them.
122 123
3 Cloud, On-Premise, and Hybrid Scenarios
Adapting the Migrated Code

You must remedy any incompatibilities that were found in the analysis
step for the code that you want to use in the planned business scenario.
Many conversions can be made mechanically thanks to the support of
quick fixes.
Adapting outdated When planning your project, you should take into account that only a sub-
UI technologies set of the adaptations can be made partially automated. In some areas, new
implementations might be necessary. Outdated UI technologies, such as
ALV or Web Dynpro, are no longer supported. Therefore, user interfaces
must be created completely anew in the form of SAP Fiori UIs. Only this
technology enables the intended user experience.
Integration via Due to the side-by-side approach, the application system’s data must be
interfaces accessed via interfaces. Direct access to tables of the target system is no lon-
ger possible. We recommend migrating to remote OData accesses. Also
note that in this model, the persistency of your enhancements and their
data—for example, custom data elements or tables—resides in the pro-
vided SAP BTP, ABAP Environment development system and not in the
tables of the application system.
SAP HANA If your enhancements make runtime-critical accesses to the database, these
optimization accesses should be optimized for SAP HANA. Although existing selects can
usually be transferred, they do not provide the desired runtime benefits. In
this context, also refer to the descriptions provided in Section 2.3.
Test and Conversion

These steps do not differ from the procedure of further developments or
conversion of your code in on-premise systems. They are based on your
processes for code modifications.
3.6 Summary
This chapter dove into the different deployment options for SAP S/4HANA
and their advantages. In particular, we outlined the options you can lever-
age to tailor the SAP S/4HANA system to your company’s needs via the var-
ious extensibility options provided. Based on this information, you may
scope your migration project. In the next chapter, we’ll discuss the detailed
preparations with your scope in mind.
124
Contents
Preface ............................................................................................................................... 17
Introduction .................................................................................................................... 19
PART I SAP S/4HANA: Basic Principles
1 SAP S/4HANA: Requirements and

Benefits 27
1.1 Future Business Challenges ...................................................................... 28

1.1.1 Digitization of Business Processes ............................................ 29
1.1.2 Trends of the Digital Transformation ...................................... 32
1.2 The Pledge of SAP S/4HANA ..................................................................... 38
1.2.1 Simplification of the Functionality ........................................... 39
1.2.2 Simplification of Data Structures ............................................. 42
1.2.3 Simplified User Interfaces ........................................................... 44
1.2.4 Simplified Analyses ........................................................................ 45
1.3 Business Functions in SAP S/4HANA .................................................... 46
1.3.1 Accounting ........................................................................................ 47
1.3.2 Logistics ............................................................................................. 51
1.3.3 Human Resources .......................................................................... 56
1.3.4 Procurement .................................................................................... 60
1.3.5 Connecting Business Data Using Experience
Management ................................................................................... 64
2 SAP S/4HANA versus the Traditional

SAP Business Suite 67
2.1 Comparing the Available Solutions: SAP S/4HANA and

the Digital Core ............................................................................................... 67
2.2 Simplification .................................................................................................. 71
2.3 The New Data Model and the SAP HANA Database ...................... 73
2.3.1 SAP HANA .......................................................................................... 74
2.3.2 The Data Model ............................................................................... 75
7
Contents Contents
2.3.3 Handling Existing Data ................................................................. 78 PART II Preparing for Migration to SAP S/4HANA
2.3.4 Sizing ................................................................................................... 78
2.4 SAP Fiori User Interfaces ............................................................................. 79 4 Which Migration Options Are Available? 127
2.4.1 Technological Changes ................................................................. 80
2.4.2 Operating Concept ......................................................................... 82 4.1 Basic Considerations .................................................................................... 127
2.5 Interfaces ........................................................................................................... 85 4.2 The Three Migration Scenarios ................................................................ 132
2.6 SAP S/4HANA Embedded Analytics ....................................................... 86 4.2.1 New Implementation of SAP S/4HANA .................................. 133
2.7 Summary ............................................................................................................ 88 4.2.2 System Conversion to SAP S/4HANA ....................................... 137
4.2.3 Selective Data Transition to SAP S/4HANA ........................... 145
4.3 Summary ........................................................................................................... 148
3 Cloud, On-Premise, and Hybrid Scenarios 89
3.1 Overview of Operating Models ............................................................... 90 5 Selecting Your Migration Scenario 149
3.1.1 On-Premise Operating Model ..................................................... 90
3.1.2 Cloud Operating Model ................................................................ 90 5.1 Overview of Procedures and Input Helps ........................................... 149
3.1.3 Hybrid Operating Model ............................................................... 94 5.1.1 SAP Innovation and Optimization Pathfinder ...................... 151
3.2 The SAP S/4HANA Product Family .......................................................... 95 5.1.2 SAP Transformation Navigator .................................................. 152
5.1.3 SAP Readiness Check ..................................................................... 154
3.2.1 SAP S/4HANA On-Premise Edition ............................................ 97
3.2.2 SAP S/4HANA Cloud ....................................................................... 100 5.2 Creating Your Own Roadmap .................................................................. 156
3.2.3 SAP HANA Enterprise Cloud ........................................................ 101 5.2.1 Initial Situation: Single System .................................................. 160
3.2.4 SAP S/4HANA Cloud, Extended Edition ................................... 101 5.2.2 Initial Situation: Decentralized System Landscape ............. 164
3.3 Comparing the Operating Models .......................................................... 102 5.2.3 Sample Roadmaps .......................................................................... 167
3.3.1 Hardware, Software, Operation, and Maintenance ............ 102 5.3 The Most Important Criteria for Your Decision ................................ 171
3.3.2 User Interfaces ................................................................................. 104 5.4 Summary ........................................................................................................... 174
3.3.3 Functional Scope and Supported Country Versions ............ 104
3.3.4 Options for Enhancement ............................................................ 106
3.3.5 Payment Model and Runtime ..................................................... 106
3.3.6 Model for Migration to SAP S/4HANA ..................................... 107 6 Trial Systems 175
3.4 Extensibility of SAP S/4HANA .................................................................. 107

3.4.1 Side-By-Side Operation ................................................................. 109 6.1 The SAP S/4HANA Trial System ............................................................... 175
3.4.2 In-App Enhancements ................................................................... 111 6.2 SAP S/4HANA Fully Activated Appliance ............................................ 177
3.4.3 Checking Custom Enhancements when Migrating
6.3 Solution Scope of SAP S/4HANA Fully Activated Appliance ...... 180
to SAP S/4HANA .............................................................................. 117
6.4 Summary ........................................................................................................... 183
3.5 ABAP-Based Enhancements via SAP BTP, ABAP Environment ... 117
3.5.1 SAP BTP, ABAP Environment ....................................................... 117
3.5.2 Migrating Custom ABAP Code to SAP BTP,
ABAP Environment ......................................................................... 121
3.6 Summary ............................................................................................................ 124
8 9
Contents Contents
PART III Migration through System Conversion PART IV New Implementation and Data
According to the Brownfield Approach Migration According to the Greenfield
Approach
7 Preparing System Conversion 187
9 SAP Activate 259
7.1 Overview of the System Conversion Project ..................................... 187
7.1.1 System Conversion Process ......................................................... 189 9.1 SAP Activate Content ................................................................................... 260
7.1.2 System Group Conversion ............................................................ 191 9.1.1 SAP Best Practices ........................................................................... 262
7.2 System Requirements and Checks ......................................................... 195 9.1.2 Tools for Adaptation and Extensibility .................................... 265
7.2.1 General Considerations ................................................................ 195 9.1.3 SAP Activate Methodology .......................................................... 271
7.2.2 System Requirements ................................................................... 197 9.2 SAP Activate Phases ..................................................................................... 272
7.2.3 Simplification List ........................................................................... 199
7.2.4 Maintenance Planner .................................................................... 202
7.2.5 Simplification Item Checks .......................................................... 206
7.2.6 Analyzing Custom Developments ............................................. 210 10 Installing and Configuring SAP S/4HANA
7.2.7 Database Sizing for SAP S/4HANA ............................................ 223 On-Premise or in the Private Cloud 277
7.2.8 Software Update Manager with Prerequisite
Check Extended ............................................................................... 224 10.1 Installation ....................................................................................................... 278
7.2.9 SAP Readiness Check for SAP S/4HANA .................................. 226
10.2 System Configuration .................................................................................. 284
8 Executing System Conversion 229

11 Setup and Configuration of SAP S/4HANA
8.1 Using Software Update Manager ........................................................... 229 Cloud 289
8.2 Activities after SUM ...................................................................................... 234

11.1 Setting Up SAP S/4HANA Cloud .............................................................. 289
8.2.1 Converting Accounting ................................................................. 234
11.1.1 Discover Phase: Setting Up the SAP S/4HANA Cloud
8.2.2 Monitoring Silent Data Migration ............................................. 237
Trial System ...................................................................................... 290
8.2.3 Adapting Custom Developments .............................................. 238
11.1.2 Prepare and Explore Phase: Setting Up the
8.2.4 Setting Up the SAP Fiori Frontend Server ............................... 240
SAP S/4HANA Cloud System ....................................................... 291
8.2.5 Migrating to SAP Fiori User Interfaces ..................................... 243
11.1.3 Realize Phase: Setting Up the SAP S/4HANA Cloud
8.2.6 Deleting Obsolete Data ................................................................ 245
Quality System ................................................................................ 298
8.3 Estimating and Reducing the Downtime ............................................ 246 11.1.4 Deploy Phase: Setting Up the SAP S/4HANA Cloud
8.3.1 Tuning of the Standard Conversion .......................................... 249 Production Systems ....................................................................... 300
8.3.2 Uptime Migration (Downtime-Optimized DMO) ................ 250
11.2 Configuring SAP S/4HANA Cloud ........................................................... 301
8.3.3 Downtime-Optimized Conversion ............................................ 252
11.2.1 Scoping ............................................................................................... 302
8.3.4 Near-Zero Downtime Technology ............................................. 253
11.2.2 Fine-Tuning ...................................................................................... 302
8.4 Insights from Previous Customer Projects .......................................... 254
10 11
Contents Contents
11.3 Setup and Configuration of SAP S/4HANA Cloud via 13 SAP S/4HANA Migration Cockpit 349
SAP Central Business Configuration ...................................................... 307
11.3.1 System Landscape with SAP Central Business 13.1 Data Migration Using the SAP S/4HANA Migration Cockpit ..... 349
Configuration ................................................................................... 308
13.1.1 Overview of the Migration Approaches of the
11.3.2 SAP Activate Methodology and SAP Central Business
SAP S/4HANA Migration Cockpit .............................................. 350
Configuration ................................................................................... 309
13.1.2 Available Migration Objects ....................................................... 351
11.3.3 Project Experience .......................................................................... 312
13.1.3 Differences Between the Old and the New
11.3.4 Defining the Scoping ..................................................................... 313
Migration Cockpits ......................................................................... 353
11.3.5 Configuration of SAP S/4HANA Cloud via SAP Central
13.1.4 Additional Useful Sources of Information ............................. 355
Business Configuration ................................................................. 315
13.2 Transfer Option 1: Transferring Data from a File ............................ 355
13.2.1 Assigning Roles for the Migration ............................................ 355
13.2.2 Initial Screen of the Migration Cockpit ................................... 356
12 Planning Data Migration 317 13.2.3 Data Migration Process ................................................................ 357
13.2.4 Creating a Migration Project ...................................................... 358
12.1 Data Migration Using SAP Activate ....................................................... 318 13.2.5 Editing a Migration Project ......................................................... 362
12.1.1 Data Migration in SAP Activate Roadmaps ............................ 318 13.2.6 Filter the Migration Project Screen ........................................... 364
12.1.2 SAP Activate Methodology for Business Suite and 13.2.7 Calling the Migration Project ..................................................... 367
On-Premise—Agile and Waterfall Roadmap ......................... 319 13.2.8 Downloading Migration Templates ......................................... 374
12.1.3 SAP Activate Methodology for SAP S/4HANA 13.2.9 Loading a File to Staging Tables ................................................ 378
Cloud Roadmap ............................................................................... 320 13.2.10 Prepare ............................................................................................... 384
13.2.11 Monitoring ........................................................................................ 385
12.2 Data Migration Phases ................................................................................ 322
13.2.12 Maintenance of Mapping Values .............................................. 386
12.2.1 Data Analysis .................................................................................... 324
13.2.13 Job Management ............................................................................ 390
12.2.2 Data Cleansing ................................................................................. 327
13.2.14 Simulating the Migration ............................................................ 391
12.2.3 Mapping ............................................................................................. 328
13.2.15 Migrating Data ................................................................................ 393
12.2.4 Implementation .............................................................................. 329
13.2.16 Displaying Migration Object Instances ................................... 395
12.2.5 Testing ................................................................................................ 330
13.2.17 Creating a Correction File ............................................................ 398
12.2.6 Data Validation ................................................................................ 333
13.2.18 Downloading Messages ............................................................... 399
12.2.7 Productive Load and Support ...................................................... 335
13.2.19 Finishing the Project ...................................................................... 401
12.3 Project Planning Using SEAMAP .............................................................. 336 13.2.20 Checking for Updates and Updating the Object .................. 402
12.3.1 Overview of General Work Packages for SAP S/4HANA
13.3 Transfer Option 2: Migrate Data Using Staging Tables ............... 404
Systems .............................................................................................. 337
13.3.1 Technical Implementation in SAP S/4HANA Cloud ............ 405
12.3.2 Work Packages for SAP S/4HANA Cloud-based
13.3.2 Technical Implementation in SAP S/4HANA ......................... 406
Systems .............................................................................................. 341
13.3.3 Staging Tables in the SAP S/4HANA Migration Cockpit .... 408
12.4 Tools for Data Migration Planning ......................................................... 342
13.4 Transfer Option 3: Direct Transfer of Data from an
12.4.1 Estimating the Effort Using Microsoft Excel ......................... 342
SAP System ....................................................................................................... 410
13.4.1 Differentiation and Areas of Use .............................................. 410
13.4.2 Technical Requirements and System Preparations ............ 411
13.4.3 Migration Objects for SAP ERP Systems and Other
SAP Source Systems ....................................................................... 412
12 13
Contents Contents
13.4.4 Assigning Roles for the Migration ............................................. 413 15 Rapid Data Migration 519
13.4.5 Running a Project with Direct Data Transfer ......................... 414
13.5 Performance Considerations .................................................................... 428 15.1 Tools .................................................................................................................... 519
13.5.1 Transfer Process .............................................................................. 428
15.2 Architecture ..................................................................................................... 521
13.5.2 Transfer Method and Infrastructure ........................................ 428
13.5.3 System Parameters and Configuration ................................... 429 15.3 Migration Content ........................................................................................ 524
13.5.4 Direct Transfer: Specific Considerations ................................. 430 15.3.1 Interfaces as Part of the Migration Content ......................... 525
15.3.2 Example: Migrating Bank Master Data ................................... 527
13.6 Supporting Applications ............................................................................. 430
13.6.1 Setting the Migration Key Date for Financial Objects ........ 431 15.4 Connecting to Source Systems ................................................................ 531
13.6.2 Checking the Status of Data Migration (Cloud) ................... 435 15.5 Data Profiling .................................................................................................. 534
13.7 Summary ............................................................................................................ 449 15.6 Field Mapping ................................................................................................. 537
15.7 Value Mapping and Conversion Tables ............................................... 544
15.8 Data Validation .............................................................................................. 551

14 SAP S/4HANA Migration Object Modeler 451
15.9 Importing Data ............................................................................................... 554
15.10 Monitoring ........................................................................................................ 556

14.1 General Structure of the SAP S/4HANA Migration
Object Modeler ............................................................................................... 452 15.11 IDoc Performance Optimization ............................................................. 558
14.1.1 Selecting an Existing Migration Object ................................... 454 15.12 Summary ........................................................................................................... 562
14.1.2 Advanced Search (All Objects) .................................................... 455
14.2 Modeling for Data Migration using Staging Tables ....................... 456
14.2.1 The Migration APIs Used .............................................................. 457
16 Comparing Data Migration and Modeling
14.2.2 Displaying a Migration Object .................................................... 458
14.2.3 Creating a Migration Object ........................................................ 462 Tools 563
14.2.4 Extending Existing Migration Objects ..................................... 466
14.2.5 Creating user-defined Migration Objects ............................... 475 16.1 Comparing Data Migration Tools ........................................................... 563
14.2.6 Creating user-defined Rules and Translation Objects ........ 488 16.1.1 Costs ................................................................................................... 564
14.2.7 Simulating or Debugging Migration Objects ........................ 492 16.1.2 Availability of Migration Tools ................................................... 565
14.2.8 Transferring Migration Projects from One System 16.1.3 Coverage of Migration Objects .................................................. 566
to Another ......................................................................................... 494 16.1.4 Technical Characteristics ............................................................. 567
16.1.5 Performance ..................................................................................... 567
14.3 Modeling for Transfer Data Directly from SAP Systems ............... 495
16.1.6 Volume and Customer Segment ............................................... 568
14.3.1 Basic Knowledge for Modeling ................................................... 496
14.3.2 Creating a Migration Object (Copy) .......................................... 499 16.2 Comparing Modeling Tools ....................................................................... 569
14.3.3 Synchronizing Structures ............................................................. 500 16.3 Conclusion ........................................................................................................ 570
14.3.4 Creating Custom Migration Objects ........................................ 500
16.4 Outlook .............................................................................................................. 572
14.3.5 Creating User-Defined Rules ....................................................... 511
14.3.6 Changing the Standard Selection .............................................. 513
14.3.7 Migrating Table Field Extensions (Z Fields) ............................ 515
14.3.8 Simulating and Debugging Migration Objects ..................... 516
14.3.9 Transporting Projects .................................................................... 517
14 15
Contents
Appendices 573
A Available Migration Objects ..................................................................... 573
B The Authors ...................................................................................................... 591
Index ................................................................................................................................... 595
16
Index
A Authentication, SAP S/4HANA

Cloud ......................................................... 294
ABAP Call Monitor .................................... 212 Automation .................................................... 33
ABAP Data Dictionary ............................. 111 Availability check, global .......................... 52
ABAP Developer Toolkit ......................... 123
ABAP Development Tools (ADT) ........ 123 B
ABAP Dictionary table ............................... 77
ABAP enhancements ............................... 116 B2B ..................................................................... 50
ABAP report ................................................... 46 Backend system ............................................ 81
abapGit for ABAP in Eclipse .................. 123 Backend template role SAP_CA_hDMC_
AcceleratedSAP .......................................... 259 MC_USER ................................................. 355
Accelerator .................................................. 271 Backup ................................................. 331–332
Accounting ..................................................... 47 Bank account management ..................... 50
simplification ........................................... 43 Bank master ................................................ 527
Accounts payable ......................................... 50 BAPI ......... 85, 328, 330, 334, 457, 520, 527
Accounts receivable .................................... 50 ALE interface .......................................... 527
Actual data ...................................................... 49 asynchronous ........................................ 527
Adaptive Server Enterprise ................... 523 BAPIRET2 ...................................................... 476
Add-on ........................................................... 139 Batch input ......................................... 330, 429
partner ...................................................... 205 BC sets ............................................................ 285
SAP ............................................................. 205 Best of breed ................................................... 39
Add-on Installation Tool ........................ 283 Big data ............................................................. 38
Admin guide ............................................... 285 Brownfield ................................... 89, 107, 187
Advanced available-to-promise .......... 167 Browser ............................................................ 81
Aggregate table ............................................. 76 Building block .................................... 266, 285
ALWAYS_OFF .............................................. 206 Building Block Builder ............................. 284
Amazon Web Services ............................. 176 Business configuration sets .................. 285
Analysis, simplification ............................. 45 Business function ..................................... 205
Analytical app ................................................ 80 Business Intelligence Launchpad ....... 557
API ................................................................... 111 Business object ........................................... 324
App Finder ................................................... 245 custom ...................................................... 114
App ID ............................................................ 440 Business process ........................................ 172
APPLANA.XML ........................................... 248 Enhancement ......................................... 110
Appliance ..................................................... 177 harmonize ............................................... 157
Application catalog Business process document ................. 264
SAP_CORE_BC_EXT ............................. 113 Business suite ................................................ 70
SAP_CORE_BC_SL_EXP ..................... 116
SAP_CORE_BC_SL_IMP ..................... 116 C
Application Link Enabling (ALE) ......... 527
Application management services .... 101 Cash operations ............................................ 50
Application Programming Interface Category for extended statistics ......... 445
(API) ........................................................... 111 CDS ........................................................... 86, 111
Application role ......................................... 356 CDS behavior definition ................ 351, 567
Archiving ............................................. 138, 165 CDS view .......................................................... 86
Ariba Network ................................. 51, 61, 63 Central finance .............................................. 48
ASAP ............................................................... 259 Central hub .................................................. 242
ASCS Instance Move ................................ 195 Central Management Console ............. 521
ATL file format ........................................... 524 Change standard selection .................... 513
595
Index Index
Changes for business models .................. 31 Conversion table ........................................ 544 Data migration (Cont.) Dialog process ............................................ 560
Check list for SAP S/4HANA Cloud ..... 301 Core business processes ........................... 67 using SAP Activate ............................... 318 Digital core ...................................................... 70
Check routine, SAP Data Services ....... 551 Core Data Services (CDS) ........................... 86 validation function ............................. 553 Digital farming .............................................. 33
Check variant .............................................. 213 Core process, business ............................... 67 Data migration landing page ............... 325 Digital native ................................................. 71
Client .............................................................. 181 Core, digital ............................................. 38, 97 Data migration status ............................. 435 Digitalization ................................................. 29
000 ............................................................ 284 Credit management ....................... 188, 200 Data migration to SAP S/4HANA from Direct transfer from SAP systems ..... 350,
copy ............................................................ 284 Credit Risk Analyzer ................................... 50 staging (2Q2) .......................................... 406 573
profile ........................................................ 284 Crowdfunding ............................................... 32 Data model .................................................. 498 Discover phase ........................................... 132
SAP Best Practices ................................ 284 Crowdsourcing ............................................. 32 simplification ........................................... 75 DMIS add-on ............................................... 411
traditional ............................................... 284 CSV file ........................................................... 381 Data replication ......................................... 146 DMO with system move ........................ 195
Cloud ................................................................. 89 Custom code adaptation ........................ 211 Data retention time ................................. 363 Download Basket ....................................... 279
deployment model .................................. 93 Custom code analysis .............................. 189 Data security .................................................. 91 Downport ..................................................... 352
Operating model ...................................... 90 Custom code check ......................... 117, 142 Data selection ............................................. 505 Downtime ................................. 193, 233, 246
Security ................................................. 37, 91 Custom code migration worklist ........ 142 Data snapshot ................................... 331–332 business downtime .............................. 247
Service model ............................................ 91 Custom development .................... 172, 210 Data storage, architecture ........................ 77 technical downtime ............................. 247
Cloud Appliance Library Automatic check ................................... 142 Data structure, simplification ................ 42 Downtime-optimized conversion ...... 252
subscription ........................................... 178 Customer identity provider .................. 309 Data transfer Dual-stack system ..................................... 198
Cloud computing ......................................... 36 Customer master ....................................... 524 directly from SAP systems ............... 341, Duplicates .................................................... 328
Cloud Connector ....................................... 110 Customer-vendor integration (CVI) ... 524 349–350, 573 Duration files .............................................. 249
Cloud edition ................................................. 95 Customizing ................................................ 108 using files and staging tables .......... 350
Cloud readiness check ............................. 122 data migration ...................................... 523 using staging tables ........ 349–350, 355, E
Code Inspector ........................................... 213 SAP S/4HANA Cloud ............................ 301 435, 573
Code pushdown .................................. 77, 213 Cutover .......................................................... 194 Data transfer job ....................................... 390 eCATT ............................................................. 285
Codeployment ................................... 166, 278 Cutover plan ................................................ 193 Data transfer using files and staging E-learning ........................................................ 35
Column-based storage ............................... 75 CVI ................................................................... 524 tables ......................................................... 350 Embedded analytics .................................... 86
COMMIT CVI cockpit ................................................... 207 Data validation ................................. 333, 551 Emergency patch ....................................... 103
Explicit ...................................................... 476 Cybersecurity ................................................ 37 Data volume .................................................. 68 End user extensibility ...................... 84, 112
Implicit ..................................................... 476 Data warehouse ......................................... 338 End user training ....................................... 197
Commit control ......................................... 470 D Data, historical ........................................... 165 End-to-end process ...................................... 70
Communication scenario ...................... 406 Database Enhancement
Communication scenario Data aging ..................................................... 138 integration .............................................. 532 custom ...................................................... 107
SAP_COM_0259 .................................... 406 Data analysis ............................................... 324 migration, custom in-app ........................................................ 111
Communication scenario Data backup ................................................. 331 developments ................................... 213 side by side .............................................. 109
SAP_COM_259 ...................................... 406 Data cleansing ......................... 321, 327, 523 server ......................................................... 521 Enhancement option ............................... 106
Company code ........................................... 431 Data comparison ....................................... 524 sizing ......................................................... 223 Event rule ..................................................... 472
Compatibility packages ............................. 98 Data conversion .................................. 78, 233 traditional .................................................. 73 Execution of class after import .............. 78
Configuration Data flow ....................................................... 529 view ............................................................... 76 Execution of program after import ...... 78
guided .............................................. 260, 265 Data footprint ................................... 131, 138 Database as a service ............ 350–351, 406 Execution phase ........................................ 207
self-service ............................................... 267 Data governance ........................................ 524 Database Migration Option .................. 143 Exemption ................................................... 210
testing ....................................................... 268 Data import ................................................. 554 migration control center ................... 249 Explicit COMMIT ....................................... 476
Configuration expert Data lineage ................................................. 520 Database schema ...................................... 359 Extended statistics ................................... 445
Business Network Integration ......... 406 Data migration Datastore ...................................................... 532 Extensibility
Data migration ..................................... 406 content ............................................ 521, 524 Decommissioning cockpit .................... 212 business objects .................................... 114
Consistency check .................................... 140 field mapping ......................................... 537 Deduplication ............................................. 520 business process .................................... 110
Consolidation ................................................ 43 implementation phase ....................... 329 Deliverables ................................................ 336 extensibility ............................................ 115
Content ......................................................... 544 monitoring .............................................. 556 Delta reconciliation ................................. 524 field ............................................................ 114
Content activation .................................... 285 performance ........................................... 558 Deploy phase .............................................. 300 in-app approach .......................... 109, 111
Controlling ...................................................... 49 phase .......................................................... 322 Deployment option key user ..................................................... 112
Conversion ................................................... 544 platform ................................................... 522 operating model ................................... 127 side-by-side approach ........................ 109
Conversion of accounting to SAP rapid data migration .......................... 519 Development package ............................ 415 table ........................................................... 114
S/4HANA .................................................. 235 template ................................................... 537 Development system traditional ............................................... 116
Conversion scenario to SAP S/4HANA from Staging conversion ............................................... 192 user extensibility .................................. 112
Migration ................................................. 149 (2Q2) ...................................................... 406 system configuration ......................... 284 user interface ......................................... 110
596 597
Index Index
Extract, transform, load .......................... 341 HTTP request ............................................... 379 J Mapping templates .................................. 424
Extraction program .................................. 329 Human capital .............................................. 35 Market Risk Analyzer .................................. 49
Human resources ........................................ 56 Job ................................................................... 528 Mass processing ......................................... 422
F Hybrid cloud .................................................. 94 log ............................................................... 546 Mass transfer ID ......................................... 358
Hybrid operating model ........................... 94 validation ................................................ 551 Massive open online courses
Fact sheet ......................................................... 80 Job management ....................................... 418 (MOOCs) ............................................ 35, 270
Field assignment ....................................... 509 I Master client ...................................... 181, 284
Field extension ........................................... 515 K Master data .................................................. 325
Field mapping .......................... 328, 529, 537 ID mapping .................................................. 364 employee .................................................. 291
Field, custom ............................................... 114 Identity authentication service ........... 308 Key relationship ........................................ 541 Master system ............................................ 146
File interface ................................................ 532 Identity provider ....................................... 294 Key user ........................................................ 298 Material number field ............................. 200
File, flat .......................................................... 532 IDoc ....... 111, 328, 330, 334, 520, 525, 568 configure users ............................. 291, 302 Memory ........................................................... 74
Filter ...................................................... 497, 506 background processing ...................... 558 Key user extensibility ...................... 84, 112 Message class .............................................. 392
FIN conversion ........................................... 235 basic type ................................................. 526 Knowledge base article ........................... 377 Message type ............................................... 441
Financial closing ........................................... 47 control record ......................................... 556 Metadata .............................................. 521, 531
Financial planning ....................................... 49 enhancement .......................................... 526 L Methodology ..................................... 260, 271
Fit-gap workshop .............................. 183, 287 import ....................................................... 554 Microsoft Azure ......................................... 176
Fit-to-standard analysis .......................... 183 inbound .................................................... 556 Landscape Management Database Microsoft Excel XML Spreadsheet
Flat file ........................................................... 532 message type .......................................... 526 (LMDB) ...................................................... 203 2003 ........................................................... 374
Frontend server .................................. 81, 240 monitoring .............................................. 558 Landscape strategy ................................... 158 Migration ......................................................... 20
add-on deployment ............................. 241 parallel processing ............................... 560 Legacy System Migration Workbench content ..................................................... 524
central hub deployment .................... 241 performance ........................................... 558 (LSMW) ............... 136, 330, 339, 341, 563 key date .................................................... 431
deployment options ............................ 241 status ............................................... 526, 558 Level of digitalization ................................. 31 new implementation .......................... 133
embedded deployment ...................... 241 transfer ..................................................... 555 License ........................................................... 106 scenario .................................................... 132
installation .............................................. 242 type ............................................................. 526 Lines of business .......................................... 97 system conversion ............................... 133
Function module .......... 457, 470, 498, 526 IMG .................................................................. 431 Liquidity management .............................. 50 Migration API ............................................. 475
Function module documentation ..... 457 Implementation Live tile ............................................................. 82 Migration content .................................... 329
method ............................................ 259, 271 Load test ....................................................... 332 Migration key date ................................... 431
G process-oriented .................................... 129 Load, productive .............................. 335, 340 Migration object ..................... 134, 324, 412
technical ................................................... 128 Local object library ................................... 528 custom ...................................................... 475
General Data Protection Implicit COMMIT ....................................... 476 Logical unit of work ................................. 559 determine ................................................ 326
Regulation ............................................... 402 Importing employee data ...................... 298 Lookup field ................................................ 544 Migration object documentation ....... 353
General Ledger Accounting .................. 431 In-app extensibility ............... 369, 566, 571 Lookup table ............................................... 544 Migration object instance ............ 422, 498
Global availability check ........................... 52 Industry 4.0 .................................................... 27 Migration object overview .................... 437
Global available-to-promise ................. 167 Information Steward ................................ 520 M Migration project ...................................... 127
Global system .................................... 158, 169 Infrastructure as a service ....... 22, 93, 101, Migration scenario .......................... 132, 149
Global variable ........................................... 555 176, 277 Maintenance ........................................ 33, 106 Migration Services ........................... 544, 548
Golden record ............................................. 520 Infrastructure service ................................ 35 Maintenance cycle ................................... 103 Migration status app
Greenfield ................. 89, 107, 187, 317, 324 Initial situation ........................................... 149 Maintenance plan ..................................... 202 category for extended statistics ..... 447
Guided buying ............................................... 62 Initial value .................................................. 383 Maintenance planner ..................... 188, 279 message .................................................... 448
Guided configuration .............................. 265 In-memory database ........................... 68, 74 landscape data ...................................... 202 Migration template .... 328, 351, 357, 374,
Guided procedure ..................................... 368 Innovation strategy and roadmap ..... 155 SAP Fiori ................................................... 243 376, 378, 405
In-place procedure .................................... 230 Make legacy data transfer settings .... 431 add field ................................................... 466
H Installation ................................................... 278 Mandatory field ......................................... 538 field list ............................................ 375, 381
Integration ..................................................... 85 Mandatory structure ............................... 376 introduction .................................. 374, 377
Hard disk ......................................................... 74 Interface ........................................................ 111 Manufacturing execution system ........ 54 key field .................................................... 376
Hardware ............................................... 74, 102 Internet of Things .................. 27, 33, 38, 69 Manufacturing management mandatory structure .......................... 376
requirement ............................................ 278 Inventory management ........................... 51 system ......................................................... 54 release ....................................................... 376
Harmonization .......................................... 157 simplification ........................................... 43 Mapping tool tip ............................................. 381, 383
Hotfix ............................................................. 103 Invoice processing ...................................... 62 on paper .......................................... 530, 538 transfer structure ................................. 375
HR ....................................................................... 56 ISO code ......................................................... 547 SAP Data Services Designer ............. 539 view ............................................................ 468
HTML5 total ................................................. 110 ISO code unit of measure ....................... 378 template ................................................... 530 ZIP file ....................................................... 380
598 599
Index Index
Migration template file .................. 378, 405 Parallel accounting ..................................... 48 Realize phase .............................................. 298 SAP Activate (Cont.)
Migration tool ............................................ 349 Perform an audit ....................................... 443 Regional system ............................... 158, 169 task ............................................................. 273
Migration Workbench ............................. 355 Phased rollout ................................... 340, 343 Relationship Profile Request ................ 536 workstream ............................................. 273
Minimized downtime services ............ 253 Planned data .................................................. 49 Relevance analysis .................................... 196 workstream, data management .... 321
Modification ................................................ 210 Planning .......................................................... 49 Relevance check ........................................ 140 SAP Adaptive Server Enterprise .......... 523
Modification adjustment ....................... 283 Platform as a service (PaaS) ..................... 91 Remote database schema ...................... 359 SAP Add-On Installation Tool .............. 206
Multicore processor .................................... 74 Platform, digital ........................................... 34 Remote Function Call (RFC) ........ 414, 555, SAP Advanced Planning and
Multisystem landscape ........................... 297 Plausibility check ....................................... 553 559 Optimization (SAP APO) ................ 40, 53
Portal ................................................................ 79 Remote SAP HANA database SAP API Business Hub ............................. 111
Portfolio Analyzer ....................................... 50 schema ..................................................... 381 SAP Apparel and Footware .......... 411–412
N
Predecessor .................................................. 371 Replication server ........................................ 99 SAP Ariba ......................................................... 40
Near-zero downtime ................................ 143 Predecessor object .................................... 371 Reporting ........................................................ 45 SAP Best Practices ....... 180, 260, 262, 317,
Near-zero downtime technology ........ 253 Predictive analytics .................................... 33 Repository ................................................... 521 328, 330, 341, 521, 566
New implementation .......... 133, 149, 161, Prepare phase, SI check ........................... 207 Representational State Transfer activation ................................................ 285
164, 317, 324 Principle of one ..................................... 39, 41 (REST) ........................................................ 111 baseline .................................................... 263
rapid data migration .......................... 519 Private cloud ........................................ 93, 277 Required field ............................................. 538 building block ........................................ 266
New installation ......................................... 278 Private cloud solution ............................. 101 Research and development ..................... 54 Explorer .................................................... 265
Non-SAP system ........................................ 149 Private managed cloud solution ........... 95 Retention time of data ............................ 363 localization ............................................. 264
Non-Unicode system ............................... 411 Procedure, guided ..................................... 368 Revolution, industrial ................................ 28 rapid data migration .......................... 519
Procurement ................................................. 61 Roadmap ................................... 156, 168, 336 SAP Model Company .......................... 175
Not null ......................................................... 383
Product assistance ...... 353, 357, 377, 433, Roadmap Viewer ................... 156, 273, 283, scope item ............................................... 266
Note Analyzer ............................................. 404
435, 448 312, 318 system configuration .......................... 284
Note Assistant ............................................ 404
Product version SAPSCORE ................... 349 Role ....................................... 83, 298, 392, 413 SAP Best Practices content .................... 566
Production ..................................................... 53 key user .................................................... 293 SAP Best Practices Explorer ......... 265, 406
O Production planning and detailed sched- SAP S/4HANA Cloud starter SAP BTP, ABAP environment ...... 110, 117
uling (PP/DS) ............................................ 40 system .................................................. 293 SAP Business All-in-One ......................... 263
Object, semantic ........................................ 439
Production system .................................... 286 SAP_BR_ADMINISTRATOR .............. 293 SAP Business ByDesign .............................. 96
Obsolete data handling ........................... 246
global ......................................................... 158 SAP_BR_BPC_EXPERT ........................ 296 SAP Business Client .................................. 240
OData ............................................................. 111
regional ..................................................... 158 SAP_BR_CONF_EXPERT_BUS_hNET_ SAP Business One ......................................... 96
OData service .............................................. 241
Productive load ................................ 335, 343 INT ......................................................... 406 SAP Business Planning and
OLO include ................................................. 487
Profiling ............................................... 520, 523 SAP_BR_CONFIG_EXPERT_hDATA_ Consolidation (SAP BPC) ...................... 49
One-step procedure .............. 162, 189, 197
column ...................................................... 534 MIG .............................................. 355, 406 SAP Business Suite ....................................... 70
Online analytical processing (OLAP) .... 73 relationship ............................................. 536 Rollback ........................................................ 476 SAP Business Warehouse (SAP BW) ... 158
Online course .............................................. 271 Project experience .......................... 307, 312 SAP BusinessObjects Business
Online transactional processing
(OLTP) ........................................................... 73
Project planning ........................................ 127 S Intelligence .................................... 519, 556
Proof of concept ............................... 178, 180 SAP BusinessObjects Web
On-premise ..................................................... 89 Public cloud ................................ 93, 102, 289 Intelligence .................................... 520, 558
S4CORE ................................................. 349, 564
On-premise edition .............................. 95, 97 S4CORE total ............................................... 229 reports ....................................................... 556
Open Database Connectivity
(ODBC) ............................................. 532, 567
Q Sales ................................................................... 53 SAP Cash Management .............................. 50
Sandbox system ..................... 177, 179, 278 SAP Central Business
openSAP ........................................................ 270 Quality assurance system ...................... 286 SAP Activate ................... 259, 289, 307, 309, Configuration ........... 307–309, 311–312
Operating model ................................ 90, 127 conversion ............................................... 192 317–318, 323, 328, 336 SAP Cloud Appliance Library ................ 175
Cloud ............................................................ 90 Quick fix .............................................. 122, 239 accelerator .............................................. 273 SAP Cloud for Real Estate .......................... 44
hybrid ........................................................... 94 Quick Sizer .................................................... 223 activities .................................................. 273 SAP Cloud Identity .................................... 294
on-premise ................................................. 90 content ..................................................... 259 SAP Cloud Platform ..................................... 91
Operation ..................................................... 102 SAP Community ........................................ 355
ORDER BY statement ...................... 213, 239
R deliverables ............................................. 273
deploy ....................................................... 335 SAP Credit Management .................... 39, 41
Organizational unit ......................... 412, 496 Random-access memory (RAM) ............ 79 goals .......................................................... 261 SAP Customer Relationship
Rapid data migration .......... 328–330, 341, methodology .......................................... 271 Management (SAP CRM) ... 70, 411–412
P 519, 564, 567 modules ................................................... 261 SAP Data Services ........ 136, 328, 330, 335,
API ............................................................... 334 phase ......................................................... 272 341, 409, 519, 564
P2Q .................................................................. 340 Rapid deployment solution .................. 263 realize .............................................. 328–329 data flow .................................................. 529
Paper mapping .................................. 328, 339 Package ..................................................... 521 SAP Model Company .......................... 175 designer ........................................... 525, 528
600 601
Index Index
SAP Data Services (Cont.) SAP HANA smart data integration ..... 409 SAP S/4HANA (Cont.) SAP S/4HANA migration cockpit ....... 100,
import ....................................................... 525 SAP HANA Studio ...................................... 409 human resources ..................................... 56 134, 269, 341, 349
job ............................................................... 524 SAP Help Portal .......................................... 325 implementation .................................... 259 control parameter ............. 367, 369, 387
license ........................................................ 525 data migration installation ............................................. 278 correlation file ....................................... 398
profiler ...................................................... 534 landing page ............................ 325, 330 logistics ....................................................... 51 default view ............................................ 362
SAP Data Services Designer .................. 525, SAP Information Steward ....................... 520 migration ................................................... 20 dependency ................................... 371–372
528, 551 SAP Innovation and Optimization on-premise ....................................... 97, 278 display messages .................................. 404
SAP datastore .............................................. 554 Pathfinder ................................................ 151 operating model ...................................... 90 documentation ..................................... 368
SAP Discrete Industries and Mill SAP Jam .......................................................... 275 operation ................................................. 102 download mapping templates ........ 388
Products ...................................................... 40 SAP Landscape Transformation Replica- procurement ............................................. 61 download values .................................. 389
SAP Download Manager ......................... 279 tion Server ................................................. 99 product family .......................................... 95 finish project ................................. 367, 401
SAP EarlyWatch Alert ............................... 151 SAP Launch .................................................. 259 public cloud ............................................ 100 fixed value ............................ 367, 369, 387
SAP Engineering Control Center ............ 54 SAP Learning Hub ........................... 270–271 regional system .................................... 158 history .............................................. 370, 399
SAP Enterprise Information SAP Manufacturing Execution ............... 54 requirements ............................................. 67 instance ................................. 378, 381, 395
Management .......................................... 519 SAP Master Data Governance ................. 99 Roadmap Viewer .................................. 283 job management ......................... 367, 391
SAP ERP ........................................ 67, 149, 412 SAP Model Company sizing ......................................................... 278 local SAP S/4HANA database
SAP Extended Warehouse Management client .......................................................... 182 system configuration ......................... 284 schema .............................. 359, 405–406
(SAP EWM) .............. 52, 98, 201, 411–412 SAP NetWeaver ........................................... 120 trial system .................................... 175, 262 long text of a message ....................... 392
SAP Fieldglass ......................................... 61, 63 SAP NetWeaver Application Server .... 107 SAP S/4HANA Admin Guide ................. 285 mapping task ............ 367, 369, 386, 396
SAP Fiori SAP Note 1972819 ....................................... 49 SAP S/4HANA central finance ................ 99 message .................................................... 378
App Finder ............................................... 245 SAP Note 2184567 ....................................... 49 SAP S/4HANA Cloud ....................... 100, 405 migration message .............................. 386
frontend server ...................................... 240 SAP Note 2290622 ..................................... 145 configuration ................................ 296, 301 migration object ................................... 372
relevance analysis ................................ 243 SAP Note 2799003 ....................................... 41 Customizing ........................................... 301 migration object
role concept ............................................ 244 SAP Note 2825650 ....................................... 54 data migration ...................................... 349 documentation ................................. 377
transition phase .................................... 243 SAP Note 2841107 ....................................... 54 hardware ................................................. 102 migration object instance ....... 395–396
SAP Fiori 2.0 ...................................... 44, 71, 79 SAP Notes 2148893 ..................................... 49 implementation checklist ................. 301 monitoring ................ 367, 378, 385, 393,
app type ....................................................... 80 SAP Notes 2816584 ..................................... 40 maintenance cycle ............................... 103 399, 404
documentation ........................................ 84 SAP Platform Identity Provider operation ................................................. 102 object ID ................................................... 371
extensibility ............................................... 84 service ....................................................... 294 starter system ........................................ 291 parallelization ....................................... 390
help ................................................................ 84 SAP Portfolio and Project trial system .................................... 176, 290 predecessor object ................................ 373
operating concept ................................... 82 Management ............................................ 55 user interface ............................................ 85 prepare ..................................................... 384
role ................................................................ 83 SAP Process Integration ............................ 85 SAP S/4HANA Cloud Customer remote SAP HANA database
technology ................................................. 80 SAP Process Orchestration ...................... 85 Community ............................................ 449 schema .............................. 359, 405–406
X-ray ............................................................. 84 SAP Product Lifecycle SAP S/4HANA Community .......... 283, 567 retention time for data ............ 401–402
SAP Fiori app Management ..................................... 54–55 SAP S/4HANA database .......................... 405 running activity ........................... 367, 378
custom code migration ...................... 193 SAP Query ..................................................... 335 SAP S/4HANA database schema, setting ....................................................... 367
data migration status ........................ 435 SAP Readiness Check for SAP local ........................................................... 359 staging ...................................................... 565
SAP Fiori apps reference library ..... 44, 80, S/4HANA ............ 137, 139, 142, 154, 226 SAP S/4HANA embedded staging area ............................................ 405
196, 439 SAP S/4HANA .................................. 19, 67, 97 analytics ............................................... 46, 86 staging table .......................................... 405
SAP Fiori launchpad ...... 82, 240, 243, 350, accounting ................................................ 47 SAP S/4HANA Enterprise technical information ............... 371, 402
355 admin guide ............................................ 285 Management ............................................ 97 technical name ...................................... 371
group .................................................. 83, 292 architecture ............................................... 81 SAP S/4HANA Environment, Health, and template ID ............................................. 371
navigation ............................................... 292 asset management ................................ 55 Safety ........................................................... 55 value mapping .................. 367, 369, 387,
provider .................................................... 241 business function .................................... 46 SAP S/4HANA Finance .............. 49–50, 163 396, 446
SAP for Retail ................................................. 40 compatibility packages ................. 58, 98 SAP S/4HANA for customer view ................................................... 362, 369
SAP Gateway ..................... 81, 111, 240–241 component ................................................ 46 management ..................................... 40, 53 SAP S/4HANA migration object
SAP GUI ............................... 79, 104, 240, 243 configuration ......................................... 265 SAP S/4HANA fully activated modeler .............. 330, 341, 361, 472, 569
SAP HANA ....................................................... 74 digital transformation ......................... 38 appliance ................................................. 176 advanced search ................................... 456
custom development .......................... 213 extensibility ............................................ 107 SAP S/4HANA guided copy wizard ............................................. 463
initial value ............................................. 409 frontend server ...................................... 240 configuration ......................................... 100 documentation ..................................... 453
SAP HANA database ................................. 359 global system ......................................... 158 SAP S/4HANA Installation Guide ....... 281 event-based rule .......................... 459–460
SAP HANA Enterprise Cloud ........ 101, 277 guided configuration .......................... 100 favorites list ............................................ 453
602 603
Index Index
SAP S/4HANA migration object SEAMAP ............................ 317, 336–337, 342 Software Update Manager System conversion ..... 133, 137, 142, 149,
modeler (Cont.) Segment ........................................................ 525 (SUM) (Cont.) 161, 164, 187, 197
field mapping ................................ 472, 481 SELECT statement ...................................... 213 Database Migration Option ............ 229 downtime ................................................ 193
field-based rule ................... 460, 482, 490 Selection ........................................................ 421 default procedure ................................. 230 monitoring .............................................. 249
fixed value ............................................... 460 Selection engine ......................................... 496 downtime-optimized one-step procedure ..................... 189, 197
global data .............................................. 466 Selection setting ........................................ 502 conversion .......................................... 252 prerequisite ............................................. 189
import/export project ........................ 494 Self-enablement ......................................... 324 downtime-optimized DMO .............. 250 project phase .......................................... 189
internal rule ............................................ 460 Self-service configuration ...................... 267 duration file ............................................ 249 system group .......................................... 191
MOVE rule ...................................... 473, 482 Sensor data ..................................................... 33 maintenance strategy ........................ 234 system landscape ................................. 191
navigation node .................................... 459 Service .............................................................. 35 near-zero downtime maintenance technical ................................................... 143
navigation tree ...................................... 458 Service model ................................................ 91 (NZDM) ................................................ 252 System freeze .............................................. 193
object browser .............................. 452, 458 Service process, smart ............................... 33 prerequisite check ................................ 225 System group .............................................. 191
rule proposal .......................................... 485 Setup instructions ..................................... 406 prerequisite check extended ............ 224 System landscape ...................................... 191
simulation ............................................... 492 Shadow instance ........................................ 231 system conversion ............................... 229 data ............................................................ 202
source structure .................................... 466 Shadow repository .................................... 231 UPGANA.XML ........................................ 247 decentralized .......................................... 159
structure mapping ...................... 471, 480 Shadow system ........................................... 231 uptime migration ................................ 250 deployment option .............................. 166
target structure ..................................... 469 Silent data migration ............................... 237 Solution scope ............................................ 307 simplification ............................................ 39
translation object ........................ 460, 489 Simple Object Access Protocol Solution scope file .................................... 285 strategy .................................................... 158
use project in different client ........... 495 (SOAP) ........................................................ 111 Source system, integration with SAP System Landscape Directory ................ 203
user-defined field .................................. 472 Simplification ........................................ 39, 71 Data Services .......................................... 531 System requirement ....................... 171, 189
variable ..................................................... 460 analysis ....................................................... 45 Sourcing
SAP S/4HANA test version .................... 262 data structure .......................................... 42 operative ..................................................... 61 T
SAP Smart Data Integration .................. 409 functionality ............................................. 39 SQL .................................................................. 213
SAP Solution Builder ....................... 266, 284 Simplification database .......................... 216 SQL Monitor ................................................ 214 Table
SAP Solution Manager ................... 274, 284 Simplification item ................................... 154 SQLScript ...................................................... 213 ACTDOCA .................................................... 43
LMDB ......................................................... 203 Simplification item catalog .................. 139, Stack XML ............................................ 205, 231 custom ...................................................... 114
release 7.2 ................................................. 284 172, 199 Staging DMC_C_WL_DBCO_OP ..................... 407
SAP SuccessFactors ...................................... 56 Simplification item catalog for data transfer using files and staging MATDOC ..................................................... 43
employee master data ........................ 295 SAP S/4HANA ........................................... 72 tables .................................................... 350 Target architecture ...................................... 98
SAP SuccessFactors Employee Simplification item check ...................... 189 data transfer using staging Target landscape ........................................ 156
Central ......................................................... 57 list ............................................................... 207 tables .................................................... 355 TCI SAP Notes ............................................. 566
SAP Supplier Relationship Management Simplification list .................... 58, 172, 188, Staging area .............................. 350, 523, 544 Template
(SAP SRM) ............................................ 40, 70 199, 452 Staging tables global ............................................... 158, 169
SAP Supply Chain Management category .................................................... 200 data transfer using staging migration template ............................. 351
(SAP SCM) ............................................ 51, 70 item ............................................................ 199 tables .................................................... 349 Template role .............................................. 355
SAP Support Portal ................................... 202 Simulate ........................................................ 391 Standard software ..................................... 183 Test .................................................................. 268
SAP Transformation Navigator ........... 152 Situation handling .................................... 448 Starter system ............................................ 291 Test landscape ............................................ 342
SAP Transportation Management ......... 98 Sizing .................................... 78, 138, 223, 278 Statistics, extended .................................. 445 Test script ..................................................... 264
SAP Treasury and Risk Management ... 49 Sizing report ......................................... 79, 223 Storage snapshot Test Your Processes function ............... 268
SAP Web Dispatcher .......................... 81, 241 SKIP rule ........................................................ 514 data snapshot ........................................ 331 Theming ........................................................... 84
SAP Web IDE ............................................ 44, 84 SM30 ............................................................... 407 Structure assignment ............................. 507 Three-system landscape ......................... 191
SAP_APPL ..................................................... 229 Smart product ............................................... 33 Subscription ................................................ 179 Tile, live tile ..................................................... 82
SAP_CUST ..................................................... 284 Smart services ............................................... 33 Subscription model ................................. 106 Time recording .............................................. 57
SAP_UCUS .................................................... 284 Software as a service (SaaS) .................... 91, Supply chain management ...................... 51 Time to value .............................................. 173
SAPSCORE ..................................................... 564 102, 127 Support Package Manager ............ 206, 281 Tool tip .......................................................... 375
SAPUI5 total ................................................ 110 Software component ............................... 229 S-user ............................................................. 203 Total cost of ownership (TCO) .............. 131
Scenario ................................................ 412, 414 Software Logistics Toolsets ................... 189 System Trade-off ....................................................... 130
hybrid ........................................................... 89 Software Provisioning Manager global ............................................... 158, 169 Transaction
Scenario bundle ......................................... 314 (SWPM) ........................................... 133, 282 leading ...................................................... 338 ATC ............................................................. 216
Scope definition ......................................... 218 Software Update Manager regional ........................................... 158, 169 BD87 ........................................................... 558
Scope item ....................... 265–266, 285, 315 (SUM) ........... 78, 142, 189–190, 281–282 transactional ......................................... 158 BDBG ................................................ 522, 526
Scoping card ................................................ 315 analysis file ............................................. 234 System configuration ............................. 284 LTMOM ..................................................... 451
System consolidation .......... 147, 157, 164 MIGO ......................................................... 218
604 605
Index
Transaction (Cont.) Unit of measure (Cont.)

SA38 ........................................................... 494 ISO ............................................................... 333
SAINT ......................................................... 283 technical unit of measure .................. 333
SCI ............................................................... 214 Unit of one ..................................................... 34
SCMON ............................................. 212, 214 Universal Journal ......................................... 43
SE37 ............................................................ 457 Upgrade .................................................. 72, 103
SE38 ............................................................ 494 Usage analysis ............................................. 196
SM37 ........................................................... 386 Usage procedure logging (UPL) ............ 212
SNOTE ....................................................... 283 User
SPAM ...................................... 206, 281, 283 authentication ....................................... 294
SPAU ................................................. 222, 283 technical ................................................... 291
SPDD .......................................................... 222 User administration ................................. 295
SQLM ......................................................... 214 User experience ........................................... 36
ST03 ........................................................... 196 User interface ................................ 71, 79, 104
SUSG .......................................................... 218 enhancement .......................................... 110
SYCM .......................................................... 216 simplification ........................................... 44
WE02 .......................................................... 558 User interface (UI) ....................................... 71
WE05 .......................................................... 558 User maintenance in SAP S/4HANA
WE20 .......................................................... 558 Cloud .......................................................... 291
Transaction data ........................................ 325 User role ........................................................ 373
Transaction Manager .................................. 50
Transaction SPAU adjustment ............. 283 V
Transactional app ......................................... 80
Transfer date ............................................... 433 Validation ..................................................... 551
Transfer method ........................................ 343 data validation ...................................... 551
Transformation internal ..................................................... 540
digital ........................................................... 27 Validation function .................................. 553
disruptive .................................................... 31 Validation rule ............................................ 335
landscape transformation ................ 146 Value mapping ........................ 385, 544, 550
Transformation rule ....................... 498, 512 Variable, global 씮 Global variable ..... 539
Transport connection ..................... 415, 517 Virtual data model (VDM) ........................ 86
Transport Layer Security (TLS) ............. 100
Transport route .......................................... 286 W
Transport system ...................................... 285
Transport-based correction instruction Warehouse management ....................... 200
(TCI) ................................................... 369, 404 Web Dispatcher ................................... 81, 241
Trial system ........................................ 175, 262 Web servers ........................................ 241, 521
client .......................................................... 181 Whitelisting ................................................. 407
on-premise .............................................. 176 Wizard ............................................................ 501
SAP S/4HANA Cloud ............................ 176 Work process ............................................... 559
Troubleshooting ........................................ 553 Workload Monitor .......................... 151, 196
Two-step procedure ................................. 163 Wrapper function module ........... 466, 476
Two-system landscape ............................ 297
Type conversion ........................................ 541 X
U X-ray ................................................................. 84
UI technology ............................................. 104 Z

Unicode ......................................................... 197
Unit of measure ......................................... 378 Z field .............................................................. 515
commercial unit .................................... 332 ZABAPGIT ..................................................... 123
internal unit of measure .................... 333 Zeros, leading .............................................. 409
606
First-hand knowledge.
Frank Densborn is a migration expert at SAP. He has occupied

a multitude of roles in both Germany and the US since he started
working there in 2004. Currently, he is a process lead in Cloud Ser-
vice Management in Palo Alto where he is working on the migrati-
on of SAP support systems to the cloud.
Frank Finkbohner is the product owner for the development of

the predefined SAP S/4HANA Cloud data migration content for
the SAP S/4HANA migration cockpit at SAP.
Dr. Jochen Freudenberg has more than 20 years of SAP expe-

rience in the areas of ABAP development, process standards for
software development, and release and maintenance strategies
for SAP products.
Martina Höft works in SAP S/4HANA product management in

the area of data migration and data transformation, with a focus
on the SAP S/4HANA migration cockpit.
Kim Mathäß leads product management for SAP S/4HANA

cross topics, which is responsible for data management and
migration for SAP S/4HANA.
Dr. Boris Rubarth has been working for SAP since 1999. To-
day, he is a product manager in software logistics. There he is
Frank Densborn, Frank Finkbohner, Jochen Freudenberg, Martina Höft, responsible for the Software Update Manager and manages the
Kim Mathäß, Boris Rubarth knowledge transfer to the SAP Community and user groups.
Migrating to SAP S/4HANA
606 Pages, 2nd, updated and revised edition 2021, $89.95
ISBN 978-1-4932-2094-6 We hope you have enjoyed this reading sample. You may recommend
or pass it on to others, but only in its entirety, including all pages. This
www.sap-press.com/5279 reading sample and all its parts are protected by copyright law. All usa-
ge and exploitation rights are reserved by the author and the publisher.

Browse The Book: First-Hand Knowledge

Uploaded by

Copyright:

Available Formats

Browse The Book: First-Hand Knowledge

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Browse The Book: First-Hand Knowledge

Uploaded by

Copyright:

Available Formats

What are the differences between the various operating models for SAP S/4HANA?

What are the differences between the various operating models for SAP S/4HANA?

What factors should be considered when choosing an operating model?

What factors should be considered when choosing an operating model?

First-hand knowledge.

Browse the Book

“Cloud, On-Premise, and Hybrid Scenarios”

Frank Densborn, Frank Finkbohner, Jochen Freudenberg, Martina Höft,

Figure 3.1 Strategic Decisions for Migrating to SAP S/4HANA

Retired Terminology Current Terminology

Table 3.1 SAP Cloud Platform Terminology Changes

private cloud. The difference to the on-premise operation model is grad-

Order Purchase Order

Hybrid Structures in Human Resources

3.2.1 SAP S/4HANA On-Premise Edition

Classification SAP Products (as of August 2020) Terminology in this Book

SAP S/4HANA Cloud, extended

use traditional functions to simplify the migration to SAP S/4HANA. Usage

Gradual Migration to the Target Architecture

쐍 The SAP S/4HANA Compatibility Scope Matrix, attached to SAP

쐍 The customer 쐍 SAP or selected service part- SAP S/4HANA

Additional Information 쐍 Hardware and infrastructure SAP S/4HANA

쐍 64 countries with 쐍 64 countries with SAP stan- SAP S/4HANA Cloud

Table 3.4 UI Technologies of SAP S/4HANA Editions Additional Information

Brownfield or green- New installation with sub- SAP S/4HANA Cloud

Table 3.7 Payment Models and Runtimes of SAP S/4HANA Editions

Interaction Regarding Maintenance Operations

Enhancements Enhancements Enhancements Enhancements

Adaptation of Custom Analyses

Traditional Enhancements (On-Premise only)

Figure 3.11 End User Enhancements for User Interfaces

Figure 3.12 Extensibility of Fields

Additional Information on Enhancement Options

The application core of SAP systems remains mostly unchanged because

Adapting the Migrated Code

Test and Conversion

PART I SAP S/4HANA: Basic Principles

1 SAP S/4HANA: Requirements and

1.1 Future Business Challenges ...................................................................... 28

2 SAP S/4HANA versus the Traditional

2.1 Comparing the Available Solutions: SAP S/4HANA and

2.2 Simplification .................................................................................................. 71

3 Cloud, On-Premise, and Hybrid Scenarios 89

3.4 Extensibility of SAP S/4HANA .................................................................. 107

8 Executing System Conversion 229

8.2 Activities after SUM ...................................................................................... 234

15.7 Value Mapping and Conversion Tables ............................................... 544

15.8 Data Validation .............................................................................................. 551

15.10 Monitoring ........................................................................................................ 556

A Available Migration Objects ..................................................................... 573

B The Authors ...................................................................................................... 591

Index ................................................................................................................................... 595

A Authentication, SAP S/4HANA

Transaction (Cont.) Unit of measure (Cont.)

UI technology ............................................. 104 Z

Frank Densborn is a migration expert at SAP. He has occupied

Frank Finkbohner is the product owner for the development of

Dr. Jochen Freudenberg has more than 20 years of SAP expe-

Martina Höft works in SAP S/4HANA product management in