Skip to Content

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 refer other blogs as follows:

TOPIC                                                         release-> 1709 1610 1610 1610 1511 1511
                                                                       stack-> FPS0 FPS2 FPS1 FPS0 FPS2 FPS1
NEW INSTALLATION:
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
SYSTEM CONVERSION:
Part 1 – Maintenance Planner link
Part 2 – Pre-checks link
Part 3 – Custom Code Migration WorkList link

There is the video for of installation of S/4HANA 1610 FPS0 for reference:

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 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 Install a new SAP S/4HANA system. 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 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.

In the next screen click on Next

In the next screen click on Download Stack XML, Download 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_2000110386_2045_.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 INSTALLATION

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 belowIn 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 and separate the following into separate directories for convenience under /sapmedia:

51050947_EXP1
51050947_LANG (optional)
51051135_SCM (optional)
51051522_CLIENT
51051432_3_KERNEL (optional)
51051151_HANASP12_4             <-you can use latest DB,HANA 2 Requires min SUSE Linux 12
download                     <- This download  includes all files from MP + SPAM + HANA DB

 

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

To report this post you need to login first.

11 Comments

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

  1. sumit patel

    Hi Mahesh,

    Its really useful information , beautiful documentation.I am having 1 question regarding post steps. After installation of SAP S4HANA 1610 FP2 , do we need to perform any post steps?

    Regards,

    Sumit

     

    (1) 
  2. Rahul Rali

    Hi Mahesh,

    Your blog helps a lot on the 1610 FPS02 installation.

    Could you please shed some light on the process of upgrading 1610 from FPS00 to FPS02.

    Currently we are on SAP S4Hana 1610 base version. Need to upgrade to FPS02.

     

    Thanks in advance for your help.

     

    Thanks,

    Rahul

    (1) 
    1. Mahesh Sardesai Post author

      Hi Rahul,

      Yes, you can upgrade by using maintenance planner to download media and then using this downloaded media execute steps as mentioned in the blog Part 2 Installation  STEP 4: ADDON INSTALLATION USING SUM

      (0) 
  3. Prasenjit Roy

    Hi Mahesh,

    Its really very nice blog with necessary information. We have recently done two new system installation with S/4 HANA 1610 and now need to do a upgrade to feature pack 02. I am having question regarding HUB deployment

    What document I should follow for a feature pack upgrade? and is solution manager is essential for that?

    What are the different steps I need to execute for HUB deployment ?

    Also after installation of SAP S/4HANA 1610 is best practices content activation is part of a technical scope?

    Regards,

    Prasenjit Roy

     

    (1) 
      1. Prasenjit Roy

        Hi Mahesh,

         

        Thanks a lot.

        I have another question regarding HANA Log backup.

        We have deployed HANA as MDC and two instance has been created for S/4 HANA and Fiori in our landscape (HUB deployment approach).

        Now I observed that the HANA Instance for fiori is generating too many log backup even though we have same type of setup for other HANA instance as well and /hana/shared is getting full. This behavior only in the HANA instance of fiori. of So it would be nice to know if there is any special thing that we can configure for the fiori part of HANA and get rid of the disk full problem.

        //Prasenjit Roy

        (0) 
        1. Mahesh Sardesai Post author

           

          Hi Prasenjit,

          This issue seems to be related to HANA operations and not in line with this blog. It would require detailed investigation of processes in HANA Administration and comparison of parameters, etc.

          – Mahesh

          (0) 
  4. Prasenjit Roy

    Hi Mahesh,

     

    Thanks a lot for your answer.

    I will take a look then with respect to the DB configuration parameter.

    One more question to be cleared:

    If we deploy Fiori as HUB then do we need Fiori instance to be installed for each DEV, WAS and PROD systems separately? Or we can also configure all three S/4 HANA Back-end systems with one front end server

     

    Regards,

    Prasenjit Roy

    (0) 
    1. Mahesh Sardesai Post author

       

      Hi Prasenjit,

       

      It is recommended to keep them separate. It would simplify installation if client number in Front end is same client number as back end.

      Also this will help you to patch/upgrade the entire system for DEV (backend+front end) in one go without affecting QAS and Prod.

      • Mahesh
      (0) 
  5. Prasenjit Roy

    Hi Mahesh,

     

    Thanks a lot for your helpful answer. Its may not relevant here with the context. But Now we received a error while creating the HTTP RFC from Fiori front end system to S/4 HANA Back end system according to the below link

    https://help.sap.com/viewer/cc1c7615ee2f4a699a9272453379006c/7.5.6/en-US/522749ec852a4779845ee028e5b950a1.html

    SSL handshake with sap s/4 hana host:44301 failed: SSSLERR_PEER_CERT_UNTRUSTED (-102).

    Expecting your expert suggestion here to address this issue.

    Regards,

    Prasenjit Roy

    Regards,

    Prasenjit Roy

    (0) 

Leave a Reply