Professional Documents
Culture Documents
Upgr Op1610 SPS03
Upgr Op1610 SPS03
2017-10-25
2 Getting Started. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
2.1 Documentation and SAP Notes for the Upgrade. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
2.2 Overview of the Upgrade Process. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
2.3 Upgrade from SAP HANA 1.0 to SAP HANA 2.0. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Table 1:
This guide explains the upgrade process for the upgrade from SAP S/4HANA, on-premise edition 1511 (all feature
and support package stacks) to SAP S/4HANA 1610 SPS03.
Read this guide carefully to get an overview of how to do the upgrade from SAP S/4HANA 1511 to SAP S/4HANA
1610 SPS02.
● Simplification List for SAP S/4HANA 1610 FPS02 (valid also for higher SPS)
● Software Update Manager (SUM) 2.0 <latest version> (guide)
● Maintenance Planner User Guide
You find more information about these documents and guides (including where to find them), as well as additional
important documents and SAP Notes relevant for the conversion in the section Documentation and SAP Notes for
the Upgrade [page 5]
The section Overview of the Upgrade Process [page 7] provides information about the different phases of the
conversion and the tools involved.
The sections Preparing the Upgrade [page 10] and Realizing the Upgrade [page 14] provide details for those
conversion phases.
Table 2:
Simplification List for SAP S/4HANA 1610 http://help.sap.com/ Lists the simplifications in comparison to
FPS02 (also valid for higher SPS) s4hana_op_1610_003 Additional the previous release, SAP S/4HANA 1511,
such as, simplified functions, merged da
Information
tabase tables, and new data models.
Software Update Manager (SUM) 2.0 http://help.sap.com/sltoolset Describes how to do the upgrade to SAP
<latest version> S/4HANA 1610 FPS02 using the Soft
Software Logistics Toolset (SL Toolset)
ware Update Manager tool.
System Maintenance
Maintenance Planner User Guide http://help.sap.com/maintenanceplan Describes how to use the Maintenance
ner Planner for calculating and downloading
the required stack.xml file and software
packages.
SAP Fiori for SAP S/4HANA 1610 Release SAP Note 2356208
Information Note
The following table lists important additional documents and SAP Notes.
Table 3:
Custom Code Migration http://help.sap.com/ Describes how you can check your cus
Migration
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 SAP S/4HANA, on-
premise edition 1511 to SAP S/4HANA 1610 SPS03.
Recommendation
We recommend that you do the activities in the sequence shown in the figure and explained in the sections
below.
Prepare Phase
Simplification List
You find the Simplification List at http://help.sap.com/s4hana_op_1610_003 Simplification List See also SAP
Note 2313884 to which the Simplification List is also attached (as an Excel list that contains all simplification
item SAP Notes). Use the Excel to select only the upgrade-relevant simplification items! – most of the
simplification items are not relevant for the upgrade.
Note
You should read the Simplification List to get an overview of all the simplification items that are relevant for your
upgrade process. When you have identified the simplification items relevant for your upgrade, you also need to
look at the relevant simplification SAP Notes themselves to get all the available information. The SAP Notes
may contain more information that the Simplification List, because they may contain attachments and may
reference other SAP Notes. This situation is not reflected in the text of the Simplification List PDF, which is only
an extract from the SAP Notes.
The simplification items are integrated with the pre-check and custom code migration tools. These tools provide
detailed reports when the code of your SAP S/4HANA, on-premise 1511 system does not comply with the scope
and data structures of SAP S/4HANA.
Before starting the realization phase of the upgrade process, you also have to do the following preparatory
activities:
1. System Requirements
You need to be aware of system requirements, see Supported Start Releases [page 11].
2. 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 SAP S/4HANA 1610 SPS03 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 11].
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.
3. Pre-Checks
These checks identify 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 pre-checks are run by the Software Update Manager.
Note
While not mandatory, this step is highly recommended. Ideally, you combine the SAP S/4HANA 1610
SPS03 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.
We recommend that you do the steps 2 to 4 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:
According to the Product Availability Matrix for supported database versions for the product SAP S/4HANA 1511,
the upgrade of an underlying SAP HANA database from release 1.0 to 2.0 can only be done after the successful
technical upgrade to SAP S/4HANA 1610 FPS01.
For more information, see the SAP S/4HANA Release Information Note 2346431 .
For the upgrade to SAP S/4HANA 1610 SPS03 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 7].
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 (SL Toolset) System
Maintenance .
Note
You get any application-specific preparation steps with the pre-check and custom-code migration check results
and with the Simplification List.
Please check the SAP S/4HANA 1610: Release Information Note 2346431 for the required feature or support
package stack equivalencies for the upgrade from SAP S/4HANA 1511 to 1610. Please also check this SAP Note for
information on an update from a lower SAP S/4HANA 1610 FPS or SPS to a higher one.
If you intend to move from an SAP ERP release to SAP S/4HANA 1610 SPS03, you need to do a system conversion,
not an upgrade. For information about system conversion, see the Conversion Guide for SAP S/4HANA 1610 SPS03
at http://help.sap.com/s4hana_op_1610_003.
Overview
You have to use the Maintenance Planner to do the upgrade to SAP S/4HANA 1610 SPS03. 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
Your need to run the Maintenance Planner before the pre-checks, because the pre-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. Setup 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
At least SPAM/SAINT patch 59 is required.
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 1610 SPS03, see SAP
Notes 2240359 and 2240360 .
Add-Ons
Industry Solutions
For information about supported industry solutions, see SAP Note 2333141 .
Before upgrading to SAP S/4HANA 1610 SPS03, you need to check your custom code against the SAP S/4HANA
simplifications in a SAP NetWeaver 7.51 system with the Custom Code Migration tool. After you run the tool, you
get a list of instances where your custom code does not comply with the scope and data structure of SAP S/
4HANA 1610 SPS03.
Note
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.
● SAP Help Portal at http://help.sap.com/s4hana_op_1610_003 SAP NetWeaver for SAP S/4HANA
Function-Oriented View Application Server Application Server ABAP Application Development on AS
ABAP Customer-specific ABAP Development Custom Code Migration
3.4 Upgrade Preparation for SAP Fiori for SAP S/4HANA 1610
FPS02
When planning your upgrade you need to consider the following SAP Fiori information:
After the preparation phase, you start the upgrade to SAP S/4HANA 1610 SPS03 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 7].
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 11].
For all information about using the SUM, see the guide Software Update Manager (SUM) 2.0 <latest version>
available at https://support.sap.com/sltoolset Software Logistics Toolset 1.0 (SL Toolset) System
Maintenance .
Note
Pre-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.
Please do the following tasks on your front-end server after the technical upgrade with the Software Update
Manager (SUM) to SAP S/4HANA 1610 SPS03 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 1610 Release Information Note
2356208 .
2. Clear caches:
1. Run transaction /UI2/INVAL_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.
For more information, see the product assistance at: http://help.sap.com/s4hana_op_1610_003 SAP
NetWeaver for SAP S/4HAN Function-Oriented View UI Technologies in SAP NetWeaver SAP Fiori
Launchpad Administration Guide Operations Performance Cache Buster for SAP Fiori .
3. Run the report /UI2/DELETE_CACHE_AFTER_IMP. It clears the UI2 cache on the front-end server.
3. Update the SAPUI5 application index by running the report /UI5/APP_INDEX_CALCULATE with the option
Full calculation enabled.
For more information, see the product assistance at: http://help.sap.com/s4hana_op_1610_003 SAP
NetWeaver for SAP S/4HANA Function-Oriented View UI Technologies in SAP NetWeaver SAPUI5: UI
Development Toolkit for HTML5 Developing Apps The SAPUI5 ABAP Repository and the ABAP Back-End
Infrastructure SAPUI5 Application Index .
4. Replicate app descriptors from the back-end system:
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 connected back-end system.
1. Check that your system is configured as described in section Replicate App Descriptors from Back-End
System in the UI Technology Guide for SAP S/4HANA 1610 SPS03. You find this guide at: http://
help.sap.com/s4hana_op_1610_003 Product Documentation UI Technology Guide .
2. Run the report /UI2/GET_APP_DESCR_REMOTE_ALL on your front-end server to start the replication.
Note
The above steps are also required when updating to a new service package stack (SPS) 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).
Coding Samples
Any software coding and/or code lines / strings ("Code") included in this documentation are only examples and are not intended to be used in a productive system
environment. The Code is only intended to better explain and visualize the syntax and phrasing rules of certain coding. SAP does not warrant the correctness and
completeness of the Code given herein, and SAP shall not be liable for errors or damages caused by the usage of the Code, unless damages were caused by SAP
intentionally or by SAP's gross negligence.
Accessibility
The information contained in the SAP documentation represents SAP's current view of accessibility criteria as of the date of publication; it is in no way intended to be a
binding guideline on how to ensure accessibility of software products. SAP in particular disclaims any liability in relation to this document. This disclaimer, however, does not
apply in cases of willful misconduct or gross negligence of SAP. Furthermore, this document does not result in any direct or indirect contractual obligations of SAP.
Gender-Neutral Language
As far as possible, SAP documentation is gender neutral. Depending on the context, the reader is addressed directly with "you", or a gender-neutral noun (such as "sales
person" or "working days") is used. If when referring to members of both sexes, however, the third-person singular cannot be avoided or a gender-neutral noun does not
exist, SAP reserves the right to use the masculine form of the noun and pronoun. This is to ensure that the documentation remains comprehensible.
Internet Hyperlinks
The SAP documentation may contain hyperlinks to the Internet. These hyperlinks are intended to serve as a hint about where to find related information. SAP does not
warrant the availability and correctness of this related information or the ability of this information to serve a particular purpose. SAP shall not be liable for any damages
caused by the use of related information unless damages have been caused by SAP's gross negligence or willful misconduct. All links are categorized for transparency (see:
http://help.sap.com/disclaimer).