Skip to Content

When you use the Transition Scenario – System Conversion to S/4HANA 1610, in the Prepare phase you follow the steps for Maintenance Planner. This blog describes the procedure.

Please refer other blogs as follows:

TOPIC                                                         release-> 1709 1610 1610 1610 1511 1511
                                                                       stack-> FPS0 FPS2 FPS1 FPS0 FPS2 FPS1
Part 1 – Maintenance Planner  link link link
Part 2 – Installation  link link link
Part 3 – Best Practices Content Activation – USA  link link link link link link
Part 3A – Best Practices Content Activation – Germany  link link link link
Part 1 – Maintenance Planner link
Part 2 – Pre-checks link
Part 3 – Custom Code Migration WorkList link

As system conversion varies widely between different systems please use this only as a guide. Your conversion may need more detailed work if it is older version/has more components but overall steps are same.

Maintenance Planner checks if Add-ons, Active Business Functions and Industry Solutions are supported for the conversion. If there is no valid conversion path for any of the items listed above (for example, an add-on is not released for the conversion yet), the Maintenance Planner prevents the conversion.
TIP: If you don’t have S/4HANA license you will be able to do the check but not able to generate stack.xml file.
As a prep you may like to empty the download basket for your S-000 user so that any files added to the download basket are meant for this task and will help to ensure that only the required files are included.
You need to login to Maintenance Planner to access system assigned to your S-user. Please ensure landscape data is uploaded to SAP support portal via LMDB of SAP Solution Manager. The system that you are converting has to be defined in OSS under your customer ID. The diagram below shows the Maintenance planner cloud service and how it integrates with Customer system.The source system data is (1) sent to SLD. (2) data from SLD is synchronized with Landscape Management Database (LMDB). (3) From LMDB the data is uploaded to customer profile in SAP support portal using Solman daily job – “landscape Fetch”. If there is issue in replicating you may be asked to apply Note 2186164 – Problem in replicating systems to Maintenance Planner
TIP: This data based on Customer Number is used by Maintenance Planner for all planning activities. So ensure you use same customer number to define system in sapnet as well as use same S-user id.

Select the Fiori tile Plan for SAP S/4HANA
Choose Plan an SAP S/4HANA conversion of an existing system. You can click on the link for Product Availability Matrix and SAP S/4HANA Conversion Guide for the documentation. Click on Next

In the next screen enter SID = ERP; select Target Version = SAP S/4HANA 1610; Target Stack = Initial Shipment Stack and Click on Next.

In the next screen choose Co-deployed with Backend and checkmark Target Product Instances depending on which SAP FontEnd Applications you need.
In the next scree click on Continue Planning

In the next screen Click on Next
In the next screen select OS/DB dependent files checkmark Linux on x86_64 bit and click on Confirm Selection.Click on OK

In the next screen click on Download Stack XML, Download Stack Text File, Download PDF and Export to Excel Generate Side Effects to download the files to your desktop. Out of these you will have to ftp the stack.xml file to the server. It will look something like this – MP_Stack_2000121202_2038_.xml

Click on Push to Download Basket. This will load the Download Basket with files you need.
In the pdf file downloaded above, in the Planned Changes section there is a link provided that takes you directly to Service Marketplace to download the media.

In the screen below choose UPGRADE(AUTOMATED DOWNLOAD)

Checkmark to select below files to add to Download Basket
In addition to above please download latest version of SPAM – KD75163 or above as shown below

In case you want to install new HANA DATABASE please download media below. If you already have a database the procedure to add database container will be shown in next part. Add this to the download basket

If you want to install LiveCache you will require the HANA database LCAPPS plugin as below:

Download all the media into separate directories under /sapmedia
download                            <- This will include all files selected from MP + SPAM + HANA DB


Here is an example of a report where Pre-checks resulted in a failure.

Here you can see that items are marked with red exclamation. If you open Note 2214409 – SAP S/4HANA: Compatible Add-ons. As this is a partner product you have to go to Note 2392527 – SAP S/4HANA, on-premise edition 1610: Compatible partner products.

The successor Product version of Add-On: SAP INVOICE MGMT BY OT 7.0, is now SAP Invoice Management by OpenText for SAP S/4HANA. This is released for S/4 HANA 1610.

For the 3rd Party software components please refer note 2308014 – Conversions to SAP S/4HANA On-Premise with 3rd Party / non-SAP Add-Ons. You have to contact 3rd Party vendor with the exact version you are converting to. The note describes more details of what the vendor is required to do.

TIP: Key facts about Add-ons – They are delivered using the Add-On Assembly kit. If the Add-ons were built using older Add-on Assembly kit when 3P vendors were not required to deliver deinstallation option. S/4HANA Add-ons are with AAK5 and this requires deinstallation kit for the Add-on. The first note to refer here is Note 2214409 – SAP S/4HANA: Compatible Add-ons. There are attachments that show the compatible addons for the versions and the list is expected to increase.

Here are some more examples of errors from some time ago but should be OK with 1610. The check report below is for 1511FPS1 and business function FIN_GL_REORG_1 was flagged Always_Off and is not a issue to convert to 1511FPS2, Also IS_AD_MPN is not an issue to convert to 1610.

All certified Solutions can be found in Application Development Partner Directory
IP: Just enter (parts of) the product or company name in the search field on top left, then click on the found companies to get further details. Companies having solutions certified for S/4HANA on Premise, will be found by entering “S/4” in the search field

Hope you have got valuable information to proceed with conversion ….

Mahesh Sardesai
Product Expert – S/4HANA RIG (Regional Implementation Group)

To report this post you need to login first.


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

  1. Joachim Rees

    Hi Mahesh,


    Thanks for this walkthrough!


    I’m not a basis person but one think caught my attention:


    You use “Co-deployed with Backend” for the frontend server, without any further explanation – I think, for productive usage, this is not recommended, right?!




  2. David Nguyen

    Great blog Mahesh! I have a question and hopefully you can help out. Currently we are running on SAP ECC 6.0 EHP7 with Oracle Database. If we want to upgrade to S4/Hana business suite, can we still stay on Oracle database? or we have to migrate or ORacle to Hana database?



    1. Mahesh Sardesai Post author


      Hi David,

      The process is known as “Conversion” not upgrade and is done using scenario S/4HANA System conversion. When you convert to S/4HANA you cannot stay on Oracle database , you have to use DMO tool to migrate to HANA Database.

  3. Former Member

    Hi Mahesh

    I’m doing a conversion from 1511 to 1610 , Customer has not Solman configured and connected to OSS connection so we used xml file generated in SPAM to create the system on the Maintenance planner . So during the configuration phase we got the below erro message:

    I looked in to the language files generated from the stack and I couldn’t find any missing lenguage also compared with the current installed on SMLT and nothing wrong. Logs files  not saying to much.


    “archive language for product s4hana_op_1610”

      1. Mahesh Sardesai Post author

        Hi Basis & Gianpietro,


        Please download the language archives for the version and provide as per
        KBA :


        1. Gianpietro Dal Zio

          Hello Mahesh,
          thank you for your answer.

          I mean i already follow the procedure described in the mentioned note.

          I try to apply the instructions again.


  4. Petrica Avdei-Mina

    Hello Mahesh,

    We are preparing a conversion to s/4hana from ERP 6.0 EHP4 on ORACLE

    Please tell me if it is necessary to make an upgrade of oracle first, in order to be able to make the conversion, or it will be done automatically by SUM.


    In the book “Migration to S/4hana” from SAP PRESS it says that for Frontend Server for System Conversion “A separate SAP Fiori frontend server must be installed or SAP Fiori Cloud is
    required for the system conversion scenario if you want to use SAP Fiori
    applications.” So the co-deployed system is not an option, right?

    Thank you in advance!



Leave a Reply