Upgrade Guide For SAP S4HANA
Upgrade Guide For SAP S4HANA
Upgrade Guide For SAP S4HANA
2 Getting Started. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
2.1 Documentation, Tools, and SAP Notes for the Upgrade. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
2.2 Overview of the Upgrade Process. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
2.3 SAP Readiness Check Versus SI-Check. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
This guide explains the upgrade process for the upgrade from all lower releases of SAP S/4HANA to SAP
S/4HANA 2023 (any feature package or support package stack).
Read this guide carefully to get an overview of how to do the upgrade from a lower release of SAP S/4HANA to
SAP S/4HANA 2023 (any feature package or support package stack) .
This guide has to be used together with the following documents and tools:
Recommendation
Although not mandatory, this tool is highly recommended. It is relevant for product release upgrades
(for example from SAP S/4HANA 2022 to 2023), but not for updates from one FPS or SPS to the next
(for example from SAP S/4HANA 2022 FPS02 to SPS03).
You find more information about these tools and guides (including where to find them), as well as additional
important documents and SAP Notes relevant for the upgrade in the section Documentation and SAP Notes
for the Upgrade [page 5].
The section Overview of the Upgrade Process [page 8] provides information about the different phases of
the upgrade and the tools involved.
The sections Preparing the Upgrade [page 14] and Realizing the Upgrade [page 34] provide details for those
upgrade phases.
Software Update Manager 2.0 <latest http://help.sap.com/sltoolset Describes how to do the upgrade to
SP> SAP S/4HANA 2023 using the Software
Software Logistics Toolset
Update Manager tool.
(SL Toolset) System Maintenance
Maintenance Planner User Guide http://help.sap.com/maintenanceplan- Describes how to use the Maintenance
ner Planner for calculating and download-
ing the required stack.xml file and soft-
ware packages.
SAP Readiness Check for SAP S/ https://sap.com/readinesscheck This tool analyzes your SAP S/4HANA
4HANA upgrades source system and highlights important
aspects of the upgrade to your SAP S/
4HANA target system, such as identifi-
cation of relevant simplification items,
high-level custom code analysis, add-on
compatibility, and more.
Recommendation
Although not mandatory, this tool
is highly recommended. It is rele-
vant for product release upgrades
(for example from SAP S/4HANA
2022 to 2023), but not for updates
from one FPS or SPS to the next
(for example from SAP S/4HANA
2022 FPS02 to SPS03).
Custom Code Migration Guide for SAP https://help.sap.com/ Provides instructions on how to adapt
S/4HANA s4hana_op_2023 Implement your custom code.
Notes relevant for the Simplification SAP Notes 2399707 and With these notes, the SI-Check is deliv-
Item Check 2502552 ered.
SAP S/4HANA 2023 - application spe- SAP Note 3340515 Information about errors that may oc-
cific notes in system conversion / up- cur during the preparation phase of the
grade preparation phase upgrade.
Additional information about the up- SAP Note for the latest ver- Information about errors that may oc-
grade with the Software Upgrade Man- sion of SUM 2.0 at https://sup- cur during the SUM phase of the up-
ager tool. port.sap.com/sltoolset System grade.
using SUM
SAP S/4HANA 2023 - application spe- SAP Note 3340526 Information about errors that may oc-
cific notes in system conversion / up- cur during the follow-on phase of the
grade follow-on phase upgrade.
SAP Fiori for SAP S/4HANA 2023: Re- SAP Note 3336823 -
lease Information Note
Maintenance and Update Strategy for SAP Note 2217489 Check dependencies according to the
SAP Fiori Front-End Server SAP Fiori front-end server maintenance
and update strategy
The following table lists important additional documents and SAP Notes.
The overview of the upgrade process shown in the figure below (including the tools, the phases, and the
activities involved in the upgrade process) is intended to help you to plan and perform the upgrade from lower
SAP S/4HANA releases to higher SAP S/4HANA releases.
Recommendation
We recommend that you do the activities in the sequence shown in the figure and explained in the sections
below.
Prepare Phase
To enable you to do an optimal planning of your upgrade, we provide the Simplification Item Catalog.
The Simplification Item Catalog is a tool that allows you to search or browse the complete collection
of simplification items grouped by product version and presented by application or functional area. Each
simplification item details the steps that need to be taken for the conversion and/or the upgrade from a
business and a technical point of view, both preparatory and follow-on steps and each item is available as a
SAP Note. You need to search for the upgrade-relevant simplification items – most of the simplification items
are not relevant for the upgrade.
Recommendation
We recommend that you consume the simplification items also via the SAP Readiness Check for SAP
S/4HANA upgrades. Based on an analyis of the configuration, data, and usage of your productive
SAP S/4HANA source release, the SAP Readiness Check for SAP S/4HANA for upgrades identifies the
simplification items relevant for your upgrade to your SAP S/4HANA target release.
For more information about how to use the SAP Readiness Check for SAP S/4HANA upgrades, see https://
sap.com/readinesscheck .
Note
When using the Simplification Item Catalog directly instead of the SAP Readiness Check for SAP S/4HANA
upgrades, please note that the catalog contains all the simplification items, not only those that are relevant
for your upgrade project. This means you need to identify those which are actually relevant for your
upgrade (which the SAP Readiness Check for SAP S/4HANA upgrades does automatically). And when you
have done this, you also need to look at the relevant simplification SAP Notes themselves to get all the
available information. The SAP Notes contain all the required information for each simplification item. The
SAP Readiness Check for SAP S/4HANA upgrades links directly to the most recent version of the SAP
Notes.
Before starting the realization phase of the upgrade process, you have to do the following preparatory
activities:
1. Planning
Recommendation
We highly recommend to run the SAP Readiness Check for SAP S/4HANA upgrades in advance of your
upgrade project to identify any issues you need to consider and activities you need to do in preparation
for your project.
For more information about how to use the SAP Readiness Check for SAP S/4HANA upgrades, see https://
sap.com/readinesscheck .
See also, SAP Readiness Check Versus SI-Check [page 11].
2. System Requirements
You need to be aware of system requirements, see Supported Start Releases [page 15].
3. Maintenance Planner
You need to run the maintenance planner tool as a first step in the upgrade process. It checks your
components, add-ons, and business functions to ensure compatibility with the SAP S/4HANA release to
which you are upgrading and also creates the stack file used during the upgrade process (done by the
Software Update Manager tool). For more information, see Maintenance Planner [page 15].
Note
This step is mandatory, because the Software Update Manager requires the stack file for the upgrade
process.
The Maintenance Planner has replaced the Maintenance Optimizer, which is not supported by SAP
S/4HANA.
4. Simplification Item-Check
This check identifies the steps you need to take to make sure that your system can technically be
upgraded and that your business processes can start running directly after the upgrade process has been
completed. The Simplification Item-Check (SI-Check) is called by the Software Update Manager. For more
information, see Simplification Item-Check [page 17].
Note
This step is mandatory and will be triggered by the Software Update Manager. Ideally, you run the
SI-Check report early in the upgrade process so that you can take note of the preparation information
provided by the SI-Check results (see also SAP Note 2399707 ).
While not mandatory, this step is highly recommended. Ideally, you combine the upgrade project with
housekeeping activities for your existing custom code base. In particular, you need a consolidated view
of productively used custom developments and you should remove custom code that is no longer used.
For more information, see the Custom Code Migration Guide for SAP S/4HANA at https://
help.sap.com/s4hana_op_2023 Implement Conversion & Upgrade Assets .
Recommendation
We recommend that you do the steps in the prepare phase in the sequence listed above. It is, however,
technically possible to do them independently or in parallel.
Realize Phase
After you have done the steps of the prepare phase, you continue with the activities of the realize phase:
The tools SAP Readiness Check SAP S/4HANA upgrades and Simplification Item-Check (SI-Check) are used
to support the upgrade process, see also Overview of the Upgrade Process [page 8]. The following table
explains the differences between the two tools.
Simplification Item-Check
• Add-on compatibility
• SAP Custom Development
projects
• Check of system consistency be-
fore conversion or upgrade
• Integration analysis
Mandatory No Yes
While both the SAP Readiness Check and the Simplification Item-Check can display information on
simplification item relevance and consistency, they serve different purposes and are both required:
• SAP Readiness Check for SAP S/4HANA upgrades is mainly a planning tool which you run early in an
upgrade project to get an overview about the required activities – including tasks related to simplification
items. It is also useful for tracking these activities during the project, for example, using the burndown
chart that shows simplification item consistency errors.
• The Simplification Item-Check is used on operational level during the cleanup of the simplification item
consistency errors, up to the downtime, before which the SUM tool does the final executions of the
SI-Check. So, the SI-Check offers a more detailed control over running the checks. This includes the option
to re-run checks for individual simplification items instead of running all checks like SAP Readiness Check
for SAP S/4HANA upgrades does. This option can significantly reduce the check runtime when you just
want to re-check if a specific error which you have just fixed is really gone.
In addition, the SI-Check offers the option to exempt certain types of errors (for details, see the blog post
linked below).
For the upgrade to SAP S/4HANA you have to prepare an overall project plan and schedule the tasks. The
preparation activities described in this section give you an idea of what is involved. Please make sure that
you also check the upgrade-relevant simplification items. For a short overview of the complete process, see
Overview of the Upgrade Process [page 8].
Note
In addition, review the planning section of the Software Update Manager guide Software Update Manager
(SUM) 2.0 <latest version> at https://support.sap.com/sltoolset Software Logistics Toolset System
Maintenance System Maintenance Scenarios Softwar e Update/Upgrade using SUM .
Note
You find some preparation steps in this guide and you get additional ones with the Simplification Item-
Check and custom-code checks as well as with the Simplification Item Catalog or the SAP Readiness Check
for SAP S/4HANA upgrades.
Please check the SAP S/4HANA 2023: Release Information Note 3307222 for the required feature package
stack equivalencies for the upgrade from SAP S/4HANA 1709, 1809, 1909, 2020, 2021, or 2022 (all feature
package and support package stacks) to 2023 (all feature package and support package stacks).
If you intend to move from an SAP ERP release to SAP S/4HANA 2023, you need to do a system conversion,
not an upgrade. For information about system conversion, see the Conversion Guide for SAP S/4HANA at
https://help.sap.com/s4hana_op_2023 Implement Guides .
Overview
You have to use the Maintenance Planner to do the upgrade to an SAP S/4HANA release. The Maintenance
Planner generates the download files (add-ons, packages, DBDs, and the stack configuration file) that the
Software Update Manager (SUM) uses to do the upgrade. In particular, the Maintenance Planner checks if the
following items are supported for the upgrade:
If there is no valid upgrade path for any of the items listed above (for example, an add-on is not released for
the upgrade yet), the Maintenance Planner prevents the upgrade. After the check, the Maintenance Planner
creates the stack configuration file (stack.xml).
Note
You need to run the Maintenance Planner before the Simplification Item-Check (SI-Check), because the
SI-Check report also requires the stack.xml file as an input.
For more information, see the Maintenance Planner User Guide at http://help.sap.com/
maintenanceplanner .
1. Set up the Maintenance Planner as described in the Maintenance Planner User Guide available at http://
help.sap.com/maintenanceplanner .
2. Check the SPAM/SAINT version in your source release system.
Note
Business Functions
Business functions can have the following status: always_on, customer_switchable, and always_off.
This results in the following behavior during the upgrade:
• If a business function was switched on in the start release system, but defined as always_off in the SAP
S/4HANA target release, then an upgrade is not possible with this release.
• If a business function was switched off in the start release system, but defined as always_on in the SAP
S/4HANA target release, then the business function will be activated during the upgrade.
• If a business function is defined as customer_switchable in the SAP S/4HANA target release, it will
keep the state defined in the target release during the upgrade.
For more information about always-off and always-on business functions in SAP S/4HANA, see SAP Notes
2240359 and 2240360 .
Add-Ons
Industry Solutions
For information about supported industry solutions, see SAP Note 3348949 .
The Simplification Item-Check (SI-Check) is called by the Software Update Manager (SUM) tool and it
identifies the simplification items relevant for your system upgrade.
The SI-Check is delivered with SAP Notes 2399707 and 2502552 . SAP Note 2399707 delivers the
new check report; SAP Note 2502552 delivers the check classes via transport-based correction instructions
(TCI) and prerequisite notes.
Note
If you follow the process described in SAP Note 2502552 exactly, you do not need to read any of the SAP
Notes required by SAP Note 2502552 . They do not contain any manual tasks and are independent of
business functionality. After you run the SI-Check, the result list will contain the SAP Notes you have to look
at in detail.
1. To enable TCI implementation, follow the instructions provided in SAP Note 2187425 (see especially the
PDF file attached to the SAP Note).
Note
If you do not enable your system to install TCI notes, SAP Note 2502552 will be implemented
without the TCI part, which will cause missing check class errors. However, if your system is on SAP
NetWeaver / ABAP Platform releases listed in the table, TCI is already enabled:
750 SP05
751 SP02
752 SP00
753 SP00
Or higher -
2. Follow the process description in SAP Note 2502552 to implement the SI-Checks.
You run the SI-Check to identify the simplification items relevant for your upgrade project. We recommend to
do this early in the project, to get an overview of the upgrade scope.
The report returns a list of relevant and irrelevant simplification items. We recommend that you check every
relevant simplification item for the impact it will have on your upgrade project.
Some simplification items have a consistency check. The consistency check identifies inconsistencies in the
system that would be a problem during the SUM process. It also provides additional information on how to
solve the problem. Some simplification items do not have a consistency check, but nevertheless are relevant.
This means that from a technical perspective an upgrade of your system is possible without any action from
you, but there will be an impact and you should investigate it.
Some of the error messages from the consistency check aim for you to read and understand the information
provided by the consistency check error – for example, the information might be about data loss incurred
during the upgrade process. These errors can only be processed by creating an exception for them which is
logged in the system. The errors are highlighted in the report in the column Exemption Possible, so that you can
see which errors need an exemption.
For more information about how to use the SI-Checks, see the user guide in SAP Note 2399707 .
The SI-Checks checks your system for data consistency (necessary for the upgrade of existing data) and
effects on the data after the upgrade. The severity of the resulting messages indicates whether there are no
inconsistencies, warnings you should look at, or inconsistencies you need to resolve. The results are provided
as green, yellow, or red messages:
Message Overview
Green 0 These messages indicate that there are no technical or other inconsistencies. They also
function as status messages and indicate that the upgrade can go ahead.
Yellow 4 These messages provide important information (or warnings) about various topics, such
as changes to business functions, or adaptations that can be done either before or
after the upgrade (but must be done to ensure business continuity). They indicate that
there are no technical problems for the upgrade itself. However, some of these yellow
messages provide information about possible data changes, changes in functionality, or
required tasks after the upgrade. For instance, per default, no custom table appends are
retained during the upgrade – the data from those fields is just lost.
Caution
Please do not underestimate yellow messages. Read them carefully and do what is
required to ensure system consistency after the upgrade, so that business continuity
is not compromised.
Red 7 These messages show skippable errors that indicate important changes for the affected
simplification items. The errors are no inconsistencies, but you need to confirm that you
have read and understood them. Usually they point out imminent data loss, deprecation,
or required activities after the upgrade. Once you have confirmed (that is, exempted)
them, they will no longer act as blockers for the upgrade.
Note
The Software Update Manager (SUM) runs the SI-Check at the beginning of the SUM
process and again just before the downtime. At the beginning, the SUM process is
stopped if a message with return code 12 is detected. Just before the downtime,
the SUM process is stopped if a message with return code 8 or higher is found.
So, for the SUM process to run successfully, you need to make sure that all the
inconstistencies found by the SI-Check with message return codes at 8 or higher are
solved.
The custom code migration checks are based on the simplification item concept. Before upgrading to SAP S/
4HANA 2023 (or any of its feature package or support package stacks), you need to check your custom code
against the SAP S/4HANA simplifications in an SAP S/4HANA 2023 system (on the correct feature package
or support package stack) with the Custom Code Migration tool or the ABAP test cockpit (ATC). These tools
provide you with a list of instances where your custom code does not comply with the scope and data structure
of SAP S/4HANA 2023 (any feature package or support package stack).
Although it is not mandatory, we highly recommend that you perform these checks regularly so that your
code remains in compliance with the SAP S/4HANA code.
For additional information about the Custom Code Migration tool, see:
• SAP Note 2241080 for information about how to download the simplification database.
• Custom Code Migration Guide for SAP S/4HANA at https://help.sap.com/s4hana_op_2023 Implement
Conversion & Upgrade Assets .
The following sections describe how to use the baseline functionality in the ABAP test cockpit and the Custom
Code Migration app to filter legacy findings in the context of an SAP S/4HANA upgrade:
To prepare the custom code analysis, you need to perform the following tasks:
1. Configure users
2. Apply SAP Notes
3. Implement the Custom Code Migration app
4. Import the Simplification Database
In the SAP S/4HANA system you need the user SAP_SATC_ADMIN to use transaction ATC to perform custom
code checks. The user provides the authorizations for setting up and using the ABAP test cockpit (ATC).
You also need the authorization object S_YCM for importing the Simplification Database into the system:
Name of the Authorization Object Names of the Authorization Field Values of the Authorization Field
ACTVT UL
Before you can implement the Custom Code Migration app, make sure that you have done the
steps for Implementing SAP Fiori Apps for Administrative, Configuration, and Extensibility Task, see
https://help.sap.com/s4hana_op_2023 Use Product Assistance (English) SAP S/4HANA Enterprise
Technology ABAP Platform Configuring the ABAP Platform .
You need to do settings in both the front-end and the back-end server:
1. Front-end server:
1. a. Enabling the app for access in the SAP Fiori launchpad:
1. In transaction PFCG, add the business catalog SAP_BASIS_BC_CCM (Custom Code Migration) to
the user roles that need to use the Custom Code Migration app. The catalog can be added to either
an existing user role or to a new one.
2. Assign the user roles to all users that need to use the Custom Code Migration app.
2. b. Activating OData services
In transaction /IWFND/MAINT_SERVICE, add the following technical service names as services:
List of Services
To check your custom code against the SAP S/4HANA simplifications, you need to download the Simplification
Database zip file and import its contents.
SAP provides content for the Simplification Database of an SAP product in the SAP Support Portal. It can be
downloaded as a zip file. The content of the zip file must then be imported into the system.
For information about the most recent content of the Simplification Database provided for SAP S/4HANA, see
SAP Note 2241080 .
To check for ABAP test cockpit (ATC) findings, you need to configure a local ATC run series that checks the
requested development objects. In addition, you can make use of the baseline functions to filter the findings
for the current release (hence not specific to the upgrade itself). With the baseline functions, you can take over
individual ATC results into the baseline and so, for example, exclude already known findings from the ATC result
list.
To configure ATC run series, schedule them, and add them to the baseline you need to do the following tasks:
Overview of Entries
Fields Descriptions
Description Enter a short description for the ATC run series you want
to configure.
Note
You can use the template provided by the Description
field. When you execute the run series, the built-in
variables are filled with data for the system, the day of
the week, the calendar week, and the year. However,
you can also add further texts to these variables, rear-
range them, or replace the built-in variables with your
own texts.
Check Variant Enter one of the following check variants that matches
your current SAP S/4HANA release:
S4HANA_READINESS_<year>_NO_FLE
Predefined settings:
S4HANA_READINESS_<year>
Predefined settings:
Note
These product-specific global check variants check
all the simplifications relevant for your current SAP S/
4HANA release as well as those for previous releases.
Objects to Check Specify the set of development objects you want to check.
Note
You can use the value help to choose the packages or
the object set in the remote system.
1. Select the required run series from the list and and click the Schedule button in the toolbar.
2. In the dialog that appears, adapt the settings for the Life Span of the series and for Execution to your
needs. Otherwise, leave these settings unchanged.
Note
Note: The Life Span defines how long (in days) the ATC results are kept in the system. After this period,
the ATC results are automatically deleted in the system.
Proceed as follows:
Overview of Entries
Fields Descriptions
Description Enter a short description for the ATC run series you want to
configure.
Note
You can use the template provided by the Description
field. When you execute the run series, the built-in varia-
bles are filled with data for the system, the day of the
week, the calendar week, and the year. However, you
can also add further texts to these variables, rearrange
them, or replace the built-in variables with your own
texts.
Note
When this setting is activated, all findings which are also
stored in the baseline are - depending on the baseline
option - suppressed, treated as exempted, or will be
shown with reduced priority.
Note:
Check Variant Enter one of the following check variants that matches your
target SAP S/4HANA release:
S4HANA_READINESS_2022_NO_FLE
Predefined settings:
S4HANA_READINESS_2022
Predefined settings:
Note
These product-specific global check variants check all
the simplifications relevant for SAP S/4HANA 2022, in-
cluding those for previous releases.
Objects to Check Specify the set of development objects you want to check.
Note
You can use the value help to choose the packages, or
the object set in the remote system.
Proceed as described in the section Schedule the ATC Run Series for the Current Release (see above) and select
the relevant run series for the target release. Choose Execute in Background (F9) to schedule the run series.
Note
In the toolbar, a filter button can be used to display either the unresolved findings (by default) and/or
the exempted findings – that, for example, have been included in the baseline.
The Custom Code Migration app (Fiori ID: F3191) enables you to scope and analyse custom code. In addition,
the app supports you with identifying unused custom code based on your collected usage data. It provides
a graphical representation of custom code analysis results. The results can be filtered by various categories,
such as quick fix availability, scope and usage data
To use the Custom Code Migration app to analyse your custom code, you need to do the following tasks:
1. Start the tile Custom Code Migration from the SAP Fiori launchpad.
2. Choose Create to create a new custom code migration project.
3. Enter a Project Description for your new project.
4. In the field Target Release specify your current SAP S/4HANA release.
Note
Make sure that the Material Number Length is set to the relevant value and the checkboxes
for Extended Amount Length, Extended Stock/Requirement Segment and Extended Season/Theme/
Collection are enabled, if you use them.
Proceed as explained in Add the ATC Run Series to the Baseline in section Using the ABAP Test Cockpit [page
22].
To create the project, proceed as explained in Create a Custom Code Migration Project for the Current Release
(see above), except that in the field Target Release you specify your target SAP S/4HANA release (for example,
SAP S/4HANA 2022).
When you create a custom code migration project, the SAP S/4HANA custom code checks are performed
automatically. The Custom Code Migration app then gives you an analytical representation of SAP S/4HANA
custom code check findings.
1. After the first analysis has been finished, choose Analysis to get an overview of the results.
2. Choose Analyze Findings to get a detailed analysis.
3. In the Custom Code Migration - Analysis - Findings view, you can specify various filters, for example:
• Simplification Item Category specifies whether findings are related to functionality which is not
available any more or has been changed in an incompatible way.
• SAP Note Number lets you analyze findings of a specific simplification Item (for example field length
extension of material number).
SAP Fiori can be deployed in an embedded and/or a hub scenario. In the sections below, you find information
about the components and versions required for each of the two scenarios.
The columns in the table below show the embedded components for the SAP S/4HANA releases 2020 to
2023.
Embedded Deployment
SAP Fiori for SAP S/4HANA SAP Fiori for SAP S/4HANA SAP Fiori for SAP S/4HANA SAP Fiori for SAP S/4HANA
2020 2021 2022 2023
SAP FES 2020 for SAP S/ SAP FES 2021 for SAP S/ SAP FES 2022 for SAP S/ SAP FES 2023 for SAP S/
4HANA 4HANA 4HANA 4HANA
SAP S/4HANA 2020 SAP S/4HANA 2021 SAP S/4HANA 2022 SAP S/4HANA 2023
SAP Gateway 7.55 SAP Gateway 7.56 SAP Gateway 7.57 SAP Gateway 7.58
ABAP Platform 2020 ABAP Platform 2021 ABAP Platform 2022 ABAP Platform 2023
See also, SAP Note See also, SAP Note See also, SAP Note See also, SAP Note
2935725 3085560 3237135 3348673
Standalone Deployment
The columns in the table below show the standalone and backend components for the SAP S/4HANA releases
2020 to 2023.
Standalone Deployment
SAP Fiori for SAP S/4HANA SAP Fiori for SAP S/4HANA SAP Fiori for SAP S/4HANA SAP Fiori for SAP S/4HANA
2020 2021 2022 2023
SAP FES 2020 for SAP S/ SAP FES 2021 for SAP S/ SAP FES 2022 for SAP S/ SAP FES 2023 for SAP S/
4HANA 4HANA 4HANA 4HANA
SAP Gateway 7.52 (minimum SAP Gateway 7.52 (minimum SAP Gateway 7.52 (minimum
version) version) version)
SAP NetWeaver 7.52 SP07 SAP NetWeaver 7.52 SP08 SAP NetWeaver 7.52 SP11
(minimum version) (minimum version) (minimum version)
SAP S/4HANA 2020 SAP S/4HANA 2021 SAP S/4HANA 2022 SAP S/4HANA 2023
SAP Gateway 7.55 SAP Gateway 7.56 SAP Gateway 7.57 SAP Gateway 7.58
ABAP Platform 2020 ABAP Platform 2021 ABAP Platform 2022 ABAP Platform 2023
See also, SAP Note See also, SAP Note See also, SAP Note See also, SAP Note
2935725 3085560 3237135 3348673
You can use the SAP Readiness Check for SAP S/4HANA upgrades to recommend SAP Fiori apps based
on your transaction usage history, see the section Recommended SAP Fiori Apps at https://sap.com/
readinesscheck Feature Scope Description SAP Readiness Check Functions of SAP Readiness Check
for SAP S/4HANA Upgrades .
If you plan an upgrade for SAP S/4HANA Java instances to SAP S/4HANA 2023 (any feature package or
support package stack), first check that your operating system is still supported. For more information, see the
Product Availability Matrix at https://apps.support.sap.com/sap/support/pam .
If your operating system is no longer supported, you have to migrate to a supported operating system
using the system copy procedure. For information see the system copy guide at https://support.sap.com/
sltoolset System Provisioning System Provisioning Scenarios Copy a System using Software
Provisioning Manager .
When upgrading to SAP S/4HANA 2023, software component SAP BASIS is also updated to Version 7.58. With
the upgrade of SAP BASIS 7.53, two technical job definitions automatically became active:
Before the upgrade, please check whether you have scheduled program ODQ_CLEANUP or ODQ_DAEMON with
your own variants. In this case, you must decide whether you continue with the scheduling of your own variants
after the upgrade, or instead, want to use the variants recommended by SAP in the technical job definitions. If
your own variants correspond to the variants recommended by SAP, choose to use the technical job definitions.
The data transition validation is a tool that allows you to compare business data before and after a system
conversion from SAP ERP to SAP S/4HANA, or before and after an SAP S/4HANA upgrade. The tool supports
validation of upgrade or conversion scenarios with predelivered content for business validation. The tool uses
business reports or transactions as instruments of comparison. It is available as part of the standard license.
To use DTV for the business validation after an upgrade, proceed as follows:
1. In the preparation phase of the uprgade, define the reports to be used for validation together with your
requesting lines of business and your internal or external auditors.
2. Create a project and maintain required test specifications in the DTV tool.
3. During the ramp-down of the system prior to the SAP S/4HANA system upgrade, trigger data extraction
from the source release.
4. Once the SAP S/4HANA system upgrade is finished, proceed with the tasks in the target release to validate
business correctness.
After the preparation phase, you start the upgrade using the Software Update Manager (SUM) tool. Make sure
that you also check the upgrade-relevant simplification items! For a short overview of the entire process, see
Overview of the Upgrade Process [page 8].
Software Update Manager (SUM) is the technical tool used for the upgrade to SAP S/4HANA.
Note
You have to run the Maintenance Planner before the SUM, because the SUM requires the stack.xml
generated by the Maintenance Planner as an input. For more information, see Maintenance Planner [page
15].
For all information about using the SUM, see the guide Software Update Manager 2.0 <latest version>
available at https://support.sap.com/sltoolset Software Logistics Toolset System Maintenance
System Maintenance Scenarios Software Update/Upgrade using SUM .
Note
Simplification Item-Check and custom-code migration checks are carried out by the SUM tool. It will
provide you with a list of results that may include manual application-specific activities you need to do
before the upgrade can be finalized.
An SDMI supports uptime capability for at least one release. Therefore zero-downtime upgrades are possible
if every release is taken into account. If an upgrade jumps over a certain release (for example, if the upgrade
goes from SAP S/4HANA 1809 straight to SAP S/4HANA 2020), the SDMIs from the release that was jumped
over (in this example, SAP S/4HANA 1909) are done during business downtime (if they do not support uptime
capability for the target release).
As of SAP S/4HANA 2020 (as start release) SDMIs also support three releases in uptime making it possible
to do jump-upgrades with zero downtime option (ZDO) over up to two releases (towards the third release), for
example from SAP S/4HANA 2020 to SAP S/4HANA 2023.
If the SDMIs are run during uptime, the SDMI job from the job repository starts and calls the SDMIs in
each client individually once the system comes out of the maintenance mode. To see all relevant SDMIs, call
transaction SDM_MON.
A user is therefore required in every client. The user can be maintained in transaction SDM_USER and can also
be created during the SUM process, when a dialog box appears asking you whether technical users for SDMIs
should be created. In this dialog, choose Yes, to allow SUM to create the technical users. If you choose No,
SUM will not create the technical users in clients where they are missing. During the post-processing phase the
SUM checks if the technical user exists. If not, a message will be created in the update log. If the users are not
created, the SDMIs cannot be started and the data will not be migrated. The SDMIs need to be done before the
next upgrade can happen.
Note
It is also possible to create the technical users after the SUM run. For more information, see https://
help.sap.com/s4hana_op_2023 Use Product Assistance English Enterprise Technology ABAP
Platform Adminstrating the ABAP Platform Administration Concepts and Tools Solution Life Cycle
Management Silent Data Migration Infrastructure .
• SAP Note 2850918 Authorizations required for Silent Data Migration (SDMI) in SAP S/4HANA Release
• SAP Note 2664638 Create and assign SDMI User in a client
• SAP Note 2907976 Silent Data Migration (SDMI) - FAQ
• SAP Note 2916801 Silent Data Migration (SDMI) Configuration Options
• https://blogs.sap.com/2019/10/03/s4hana-silent-data-migration-infrastructure-quick-guide/
The Obsolete Data Handling tool allows you to delete obsolete data that may remain after the upgrade.
Obsolete data originates from SAP S/4HANA data model simplifications in many application areas where
the related application data is migrated to new data structures. These areas include Material Management,
Financials, Sales and Distribution, Environment and Health Science and others. The source data is not deleted
automatically during the conversion because this would increase the business downtime and the obsolete data
Note
With SAP S/4HANA 2023 a new obsolete data handling tool is delivered.
The old tool (report/transaction code ODH_Data_processing) can only be used with SAP S/4HANA
2023 to view the logs of already finished cleaning runs. It will not be available at all for future SAP S/4HANA
releases. For the old tool, see SAP Note 2661837 .
All new obsolete data cleaning activity must be done with the new, class-based tool (transaction code
SODH). For information on how to enable and use this tool in the productive SAP S/4HANA 2023 system,
see SAP Note 3335020 .
Please perform the following tasks on your front-end server after the technical upgrade with the Software
Update Manager (SUM) to SAP S/4HANA 2023 to ensure that your SAP Fiori Launchpad and SAP Fiori
Applications are able to run properly:
1. Check the latest correction notes from the SAP Fiori for SAP S/4HANA 2023 Release Information Note
3336823 .
2. Update the SAPUI5 application index by running the report /UI5/APP_INDEX_CALCULATE.
For more information about how to run this report, see the product assistance at: https://help.sap.com/
s4hana_op_2023 Use Product Assistance English Enterprise Technology ABAP Platform UI
Technologies SAPUI5: UI Development Toolkit for HTML5 Developing Apps The SAPUI5 ABAP
Repository and the ABAP Back-End Infrastructure SAPUI5 Application Index .
3. Replicate app descriptors:
If you use Web Dynpro or SAP GUI for HTML Apps on your SAP Fiori Launchpad, it may be necessary to
update their app descriptors or to load new app descriptors from the backend catalogs into the technical
frontend catalogs.
1. Check that your system is configured as described in Replicate App Descriptors at https://
help.sap.com/s4hana_op_2023 Use Product Assistance English Enterprise Technology SAP
Fiori SAP Fiori Overview Implement SAP Fiori Apps UI-Specific Implementation Tasks Basic
Information .
2. Run the report /UI2/GET_APP_DESCR_REMOTE_ALL on your front-end server to start the replication.
Note
4. Invalidate caches:
1. Run transaction /UI2/INVAL_CACHES or report /UI2/INVALIDATE_GLOBAL_CACHES to invalidate all
UI2 caches.
2. If you are using the SAPUI5 cache busting mechanism for your SAP Fiori Launchpad, run the
report /UI2/INVALIDATE_CLIENT_CACHES to invalidate the client caches.
Note
The above steps are also required when updating to a new service pack (SP) or feature package stack
(FPS).
If you use SAP GUI for HTML Apps on your SAP Fiori Launchpad, check if the ICF node /sap/public/bc/its
and all its sub-nodes are activated (use transaction SICF).
As of SAP S/4HANA 1809 additional configuration settings are available for the SAP Fiori Launchpad that
improve the system performance when launching SAP GUI for HTML and Web-Dynpro apps.
Recommendation
When you upgrade from a lower SAP S/4HANA release or if these settings were not yet implemented
in SAP S/4HANA 1809, 1909, 2020, 2021 or 2022 we recommend that you enable these performance
improvements by activating the features described below on your front-end server after the upgrade to
SAP S/4HANA 2023 (any feature package or support package stack).
1. In-place navigation for classic UIs (SAP GUI for HTML and Web-Dynpro Apps)
Note
We recommend activating the in-place navigation centrally on your front-end server (on client level).
If this is not desired for some users or roles, you can override the central setting by defining a target
mapping parameter for ex-place and assigning it (using a catalog) to a specific role. In addition, it
is also possible define exceptions for ex-place navigation on app level (in the target mapping) in the
launchpad content.
In mixed backend scenarios, where backend products with lower SAP S/4HANA releases are also
connected to your front-end server, the features are not supported.
For more information on how to configure the SAP Fiori Launchpad, see https://help.sap.com/
s4hana_op_2023 Use Product Assistance English Enterprise Technology ABAP Platform UI
Technologies SAP Fiori Launchpad .
After the upgrade, you must do some follow-up activities regarding the authorization concept.
The default authorization values are the data basis for the provision of authorizations required for applications
in the Profile Generator (transaction PFCG).
Default authorization values for standard SAP applications are delivered via upgrade, support package
deployment, or SAP Note. This SAP-provided data is displayed and maintained in transaction SU22.
Customer default authorization values are maintained in transaction SU24. Only these customer default
authorization values are applied when PFCG is used.
After the upgrade the SAP default values may have been changed. You therefore must use transaction SU25 to
carry out a comparison of the default values (steps 2a and 2b) and transfer the default values maintained by
SAP.
For more information about this process, see SAP Notes 1539556 and 440231 .
After checking and updating the default authorization values you must do some follow-up activities for the
PFCG roles. You need to consider how changed default authorization values as well as new or changed content
in SAP Fiori Catalogs affect your PFCG roles. You adjust your PFCG roles using the transaction SU25 actions
Update of Application Groups in Role Menu and Roles to Be Checked.
• Tasks required after the upgrade from SAP S/4HANA releases lower than 1709:
In this case, you have to all the steps described in the section Follow-Up Activities for
Advanced Variant Configuration in the Installation Guide for SAP S/4HANA at https://help.sap.com/
s4hana_op_2023 Implement Guides .
• Tasks required after the upgrade from SAP S/4HANA releases equal to or higher than 1709:
In this case, you have to do the steps described in SAP Note 2987015 .
Handling of material plants that are Flagged for Deletion in PP/DS has been changed as of SAP S/4HANA 2022.
If you are upgrading from SAP S/4HANA 2021 or lower to SAP S/4HANA 2022 or higher, you must run the
report PPDS_DEACTIVATE_ADVN_PLN_PROD manually to update the Advanced Planning Status for material
plants that are Flagged for Deletion. However, if you are upgrading from SAP S/4HANA 2022 to SAP S/4HANA
2023, you do not need to run the report PPDS_DEACTIVATE_ADVN_PLN_PROD manually because the data in
the SAP S/4HANA 2022 system is already correct.
Note
Hyperlinks
Some links are classified by an icon and/or a mouseover text. These links provide additional information.
About the icons:
• Links with the icon : You are entering a Web site that is not hosted by SAP. By using such links, you agree (unless expressly stated otherwise in your
agreements with SAP) to this:
• The content of the linked-to site is not SAP documentation. You may not infer any product claims against SAP based on this information.
• SAP does not agree or disagree with the content on the linked-to site, nor does SAP warrant the availability and correctness. SAP shall not be liable for any
damages caused by the use of such content unless damages have been caused by SAP's gross negligence or willful misconduct.
• Links with the icon : You are leaving the documentation for that particular SAP product or service and are entering an SAP-hosted Web site. By using
such links, you agree that (unless expressly stated otherwise in your agreements with SAP) you may not infer any product claims against SAP based on this
information.
Example Code
Any software coding and/or code snippets are examples. They are not for productive use. The example code is only intended to better explain and visualize the syntax
and phrasing rules. SAP does not warrant the correctness and completeness of the example code. SAP shall not be liable for errors or damages caused by the use of
example code unless damages have been caused by SAP's gross negligence or willful misconduct.
Bias-Free Language
SAP supports a culture of diversity and inclusion. Whenever possible, we use unbiased language in our documentation to refer to people of all cultures, ethnicities,
genders, and abilities.
SAP and other SAP products and services mentioned herein as well as
their respective logos are trademarks or registered trademarks of SAP
SE (or an SAP affiliate company) in Germany and other countries. All
other product and service names mentioned are the trademarks of their
respective companies.