Skip to Content
Technical Articles

New Installation of S/4HANA 1909 FPS1- Part 1 – Maintenance Planner

This procedure is Part 1 of the series which describes the very first steps to download the media. We will focus on creating Sandbox type instance with co-deployed (embedded) gateway.

Please find other blogs as follows at SAP S/4HANA SQUARE ONE


NEW INSTALLATION     PART1 – MP PART2 –  Installation
PART3 –  BP Activation
PART4 – Fiori Activation PART5 – DATA MIGRATION
S/4HANA 1909 fps2 fps1  fps0  fps2 fps1  fps0 fps2 fps1  fps0 fps2 fps1  fps0 fps0
S/4HANA 1809 fps2  fps1  fps0 fps2  fps1  fps0 fps2  fps1  fps0 fps2  fps1  fps0
S/4HANA 1709
fps2  fps1  fps0 fps2  fps1  fps0 fps2  fps1  fps0
UPGRADE   t2 – MP t3 – SIC
t4 – CCM t5 – SUM
SAP S/4HANA 1809 link link link link
t5 – CCM t6 – SUM 
SAP S/4HANA 1909 rc2 link link link prepare
SAP S/4HANA 1809



link link link EHP7/hdb
SAP S/4HANA 1909 link – custom     link – standard link
SAP S/4HANA Certification Exams through SAP Certification Hub link

This is the Video for SAP S/4HANA 1909 FPS0 (Please note its not for FPS1)

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.

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 diagram below shows the Maintenance planner cloud service and how it integrates with Customer system.

The source system is first defined in Maintenance planner (1) generates (2) stack.xml, used for (3) Installation and (4) Upgrade and then system is (5) registered with Solution Manager. The system data is synchronized with Landscape Management Database (LMDB). From LMDB the data is (6) uploaded to customer profile in SAP support portal. (7) Data Fetch occurs 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. Also ensure you use same Customer Number to define system in sapnet. Use the S-user id of this Customer Number.

Select the Fiori tile Plan for SAP S/4HANA

In the next screen,choose Install a new SAP S/4HANA system. Here you can click on the link for the SAP S/4HANA Installation Guide for the documentation and click on Next.

In the next screen enter SID = S4H; select Target Version = SAP S/4HANA 1909; Target Stack = 01 (02/2020) FP. The componnets SAP Predictive integrator, SAP HANA Rules Framework and selected by default. Click on Next.
TIP: The selection of component above will only download the files. You have to install them as per the procedure for the component. 

In the next screen choose Co-deployed with Backend. Please refer SAP Fiori Deployment Options and Landscape recommendations for detailed information. Please select checkmark Target Product Instances as applicable depending on which SAP FontEnd Applications you need among Human Capital Management, Master Data Governance and Travel Management.

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.

In the next screen click on Next.

Click on NON-ABAP and unselect the language files that are not required. Languages DE and EN are selected by default and cannot be unselected.TIP: The files are only selected above for download. Later on during installation, you have to define the languages in the SUM tool.

In the next screen click on Download Stack XMLDownload Stack Text File, Download PDF and Export to Excel 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_1000889837_20200212_.xml

TIP: Before you click on Push to Download Basket on next screen, please ensure that download basket is empty so that the download contains only the files needed for SAP S/4HANA installation.

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.

Download all the media and separate the following into separate directories for convenience under /sapmedia/download. This includes files from Maintenance Planner 

You need the files below for the installation, please check if these are in download folder:

SWPM20SP05_0-80003424.SAR – Latest version of Software Provisioning Manager
SUM20SP07_0-80002456.SAR – Latest version of Software Update Manager

Please refer SAP Note 2872472 – SAP S/4HANA 1909 Feature Package Stack 01: Additional Release Information for SAP HANA database release details. Please download the files below from

TIP: The minimum required revision of SAP HANA 2.0 is Support Package 04 Database Revision 044. However, please check Note to ensure there are no problems with this SAP HANA release. Refer 2655761 – SAP S/4HANA – restrictions and recommendations regarding specific revisions of SAP HANA database for use in SAP S/4HANA

IMDB_SERVER20_046_0-80002031.SAR – Latest version of SAP HANA Database as of this blog (Linux x86_64 64bit)

You also need to download latest version of the SAP HANA client from Software Downloads => SUPPORT PACKAGES AND PATCHES => SAP HANA PLATFORM EDITION => SAP HANA CLIENT 2.0
IMDB_CLIENT20_004_182-80002082.SAR – HANA Client (Linux x86_64 64bit)

If you want to install LiveCache you will require the SAP HANA database LCAPPS plugin from Software Downloads => SUPPORT PACKAGES AND PATCHES => SAP HANA PLATFORM EDIT 1.0 =>  SAP HANA LCAPPS => SAP HANA LCAPPS 1.00

IMDB_LCAPPS_2046_0-20010426.SAR – Corresponding version of SAP HANA LCAPPS (Linux x86_64 64bit)

Download all the media and separate the DB files IMDB* into separate directories for convenience under /sapmedia

In addition
, please download file for best practices content activation from SAP Note 2870570 – SAP S/4HANA 1909 – SAP S/4HANA 1909 FP-Stack 01 (02/2020) SAP Best Practices Content activation note

crlbag.p7s from


You can open OSS messages using component BC-UPG-MP


Maintenance Planner – User Guide
Maintenance Planner Help Portal
Maintenance Planner – Frequently Asked Questions

Mahesh Sardesai
Product Expert – SAP S/4HANA

You must be Logged on to comment or reply to a post.
  • SAP note 2870570 is now available.


    In addition, please download file for best practices content activation from SAP Note 2870570 – SAP S/4HANA 1909 – SAP S/4HANA 1909 FP-Stack 01 (02/2020) SAP Best Practices Content activation note (THIS NOTE IS NOT YET RELEASED AS OF 15-FEB. PLEASE CHECK BACK IN A COUPLE OF DAYS)

  • Hi Mahesh,


    Thanks for your blog, It's very useful for us. If possible can you blog on Migration steps as well...


    I think there is no Blog explaining E2E Migration steps.

  • Hi Mahesh,

    I seem to be running into a problem when I select Select Additional Systems -> Frontend Server Selection -> Co-Deployed with Backend -> S4H.  There are no options for me to select in the Target Version and Target Stack and I cannot go beyond the page.  Please advise.


    Thanks and Regards


  • I have almost zero basis experience, but need to get a Test or Sandbox system up and running. This article seems brilliant as it seems like I would be able to do it by following the instructions. Thank you very much for this. I have just some questions that is still "grey".

    1. You selected Linux on x86_64 bit as OS, can we go for Windows on x86_64 bit as our IT staff mainly supports Windows?
    2. In the next article you provide links to system requirements. Can you maybe just list the minimum recommended requirements? A list that I can give to the IT guys as my SAP requirement?


    • Hi Johan,

      Please see SAP note below for supported OS platforms. Note 2235581 - SAP HANA: Supported Operating Systems

      To Answer your question:
      1. You cannot install S/4HANA on Windows x64_64.
      2. For S/4HANA the minimum RAM is 128GB to install and tor really work on it 256GB is required.

      - Mahesh

  • Hello Mahesh,

    I have one question regarding upgrade, hope you can help.

    My SAP system is on S4 HANA 1610, with the Central & Dialog instances on Solaris 10 while the HANA 2.0 Database runs on SUSE Linux.

    Now I have to upgrade to S4 1909. However, in maintenance planner, I cannot see Solaris OS to download the kernel files (see screenshot below):




    Is application server on Solaris no longer supported? PAM also does not give much info on that.

    If this is true, then do I need to migrate the app server from Solaris to Linux? How to do that?

    I cannot find much information on this issue out there, hope you can clarify, please.




  • Hi Mahesh,


    Thank you very much for the valuable info.

    I read the note too.

    Your video on Open SAP is very useful.

    Keep up the good work!

    I had a few questions just to close on that:

    1. In my scenario, I have a Solaris host having the ASCS00 and DVEBMGS01 together and 2 other Solaris hosts running Dialog instances called D02 and D03. So we'll use the option where ASCS00 and DVEBMGS01 are in the same host and move the ASCS to the new Linux Dialog during the SUM upgrade, is this right?
    2. Once the ASCS moves to the new Dialog, the Dialog will remain there or we should later move it another host?
    3. I use SWPM to install the new supported Linux Dialog instance, then for SUM, I use the xml file from this new Dialog instance to feed into Maintenance Planner?
    4. I do not upgrade the other Solaris Dialog instances and discontinue then. Rather I install new Dialog instances on the supported Linux as and when required, is this right?

    Kindly advise.



    • Hi Suraj,

      Please find my answers below:

      1. Yes the SUM upgrade process will move the ASCS to Linux host and will not start the ASCS on Solaris. At the end of the upgrade you have to manually remove the Solaris ASCA host.
      2. Once the ASCS moved th Linux host you can leave it on Linux and run it there. Please add a Linux host that will be permanent so a move to other host is not required.
      3. As you are already into the upgrade process, I dont think a fresh xml through maintenance planner makes sense in the middle of the upgrade process. It should not be necessary to create a fresh xml although this is a valid concern.
      4. Yes at the end of the upgrade you discontinue and remove all the Solaris hosts.
      • Mahesh
  • Hi Mahesh,

    I have a question. If I send the data to SLD via RZ70, then the date in SLD (last update) is only updated for the tenant DB.

    The last update date is not updated for System DB.

    Is this normal behavior?

    Many Thanks
    Best Regards