Skip to Content

This guide explains the upgrade process for the upgrade from SAP S/4HANA, on-premise edition 1511 and SAP S/4HANA 1610 (all feature package stacks) to SAP S/4HANA 1709. As a prerequisite for SAP S/4HANA OP 1709, the HANA DB Version must be upgraded to HANA 2.0 SPSxx or higher. For information on SAP HANA revision strategy, and SAP HANA Maintenance, please refer to SAP Note 2021789 – SAP HANA Revision and Maintenance Strategy.

  • To download the HANA DB Revision, go to http://support.sap.com/swdc >> Support Packages and Patches >> Software Downloads >> Support Packages and Patches >> By Alphabetical Index (A-Z) >> H >> SAP HANA PLATFORM EDITION >> SAP HANA PLATFORM EDIT. 1.0. Then decide if you want to upgrade by Support Package Stack or Entry By Component and the revision you want to upgrade to. Please refer to SAP Note 2021789 – SAP HANA Revision and Maintenance Strategy for revision strategy. Download your files with download manager and copy to the SAP HANA DB server.

The high-level steps for the S/4 HANA 1709 upgrade include the following:

  • Full database backup both backend and frontend systems.
  • Upgrade HANA DB to version 2.0 SPSxx or higher.
  • Maintenance Planner for both SAP backend and frontend systems.
  • Download upgrade and SUM software.
  • SAP Simplification Pre-Checks.
  • SAP SUM upgrade for S/4HANA 1709 backend system.
  • SAP SUM upgrade for S/4HANA 1709 frontend system.
  • SPDD and SPAU adjustments.
  • Post Upgrade Activities.

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 SAP S/4HANA 1709.

Pre-Requisites

The overview of the upgrade process is shown in the previous Introduction section. It is recommended to review and complete the Prepare Phases – System Requirement, Maintenance Planner, SI Checks, and Custom Code Migration, successfully before starting actual upgrade process in Realize Phase. This document will detail the Maintenance Planner process to generate a valid Stack.xml file for both Backend Server (BES) and Frontend Server (FES) systems. In addition, implementation of SI-Checks procedure is discussed in detail in this document but Custom Code Migration will not be included as it is very specific to the customer environment. But it’s advisable to review the custom code migration procedure to complete the upgrade successfully.

For S/4HANA 1709, HANA 2.0 database is a mandatory. This requirement may result in an upgrade from HANA 1.0 to HANA 2.0 and/or an Operating System upgrade prior to the S/4HANA 1709 application upgrade. Please review the Product Availability Matrix (PAM) for HANA 2.0 to plan the upgrades.

SAP Maintenance Planner

The first step in S/4HANA conversion is to analyze the source system using the Maintenance planner tool. With all S/4HANA implementation and upgrades, the Maintenance Planner become a mandatory solution to start any activity in a S/4HANA project to download the software or check the SAP ERP solution readiness to be converted S/4HANA and building the stack file for system conversion. It checks your components, add-ons, and business functions to ensure compatibility with SAP S/4HANA 1709 and also creates the stack file used during the upgrade process (done by the Software Update Manager tool).

Simplification Item-Checks

The Simplification Item-Checks 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 run by the Software Update Manager. Before starting the Simplification Item Checks, you will need complete the following steps to install the software in your source SAP S/4HANA backend system. 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.

SAP S/4HANA 1709 SUM – Backend System

Software Update Manager is the technical tool used for upgrade to SAP S/4HANA 1709. It is recommended to download the latest SUM tool to perform the upgrade. Before starting the upgrade make sure you have a valid stack.xml created using Maintenance Planner, which will be required to start the upgrade. Also, check the upgrade relevant simplification items and a valid system backup exists, in case if the system needs to be restored to pre-upgrade state.

SAP S/4HANA 1709 SUM – Frontend System

Software Update Manager is the technical tool used for upgrade to SAP S/4HANA 1709. It is recommended to download the latest SUM tool to perform the upgrade. Before starting the upgrade make sure you have a valid stack.xml created using Maintenance Planner, which will be required to start the upgrade. Also, check a valid system backup exists, in case if the system needs to be restored to pre-upgrade state.

Please refer to the following document for step by step instructions on upgradig your S/4HANA 1511 or 1610 system to the latest S/4HANA 1709 system.

Link to document – https://www.sap.com/documents/2017/12/04b5120e-e57c-0010-82c7-eda71af511fa.html

 

Thanks,

SAP S/4HANA RIG

 

To report this post you need to login first.

2 Comments

You must be Logged on to comment or reply to a post.

  1. Chandrakanth Angannagari

    hi,

    1. What is the recommended approach when we have to do a FPS update to a S/4 system? Do we start the SUM in parallel for backend and frontend at the same time ? Or we have to do it on backend first and then on the front end?

    2. Does SUM include the SI-Checks or we have to use the report from sap note 2399707 to run             this check manually first?

     

    Thanks

    Chandrakanth

    (0) 
    1. Gilbert Wong Post author

      Hi Chandrakanth,

      You should run SUM in parallel and take down both systems at the same time during the downtime phase.  If you decide to run the SUM upgrade first for the backend system and then frontend, you will need to wait until both systems are upgraded until you can let the end users log in.

      The steps for the SI checks are listed in the attached how to guide.

      Thanks for the questions.

       

      (0) 

Leave a Reply