Skip to Content


Installing SAP Fiori apps involves comprehensive consideration of technical prerequisites. SAP Fiori apps require front-end, back-end & if applicable SAP HANA components. The required front-end and back-end components are delivered in separate products and have to be installed in the system landscape. Maintenance Planner addresses the need to install front-end and back-end components delivered in separate products, by calculating all the system requirements for SAP Fiori apps installation.

Installation of SAP Fiori apps has been significantly simplified with integration between SAP Fiori apps reference library and Maintenance Planner. With this integration you can select SAP Fiori apps in SAP Fiori apps reference library which provides an overview of various available apps and their installation and configuration perquisites. Seamless integration between these two tools enables you to select SAP Fiori Apps and navigate directly to Maintenance Planner, letting you download required software packages for  back-end, front-end and SAP HANA in a single transaction.

Pictures below outlines overall process of SAP Fiori installation with SAP Fiori apps reference library and the maintenance planner.


Figure 1: Installing SAP Fiori apps with SAP Fiori apps reference library and Maintenance planner


Figure2: Installing SAP Fiori apps with SAP Fiori apps reference library & Maintenance planner

Installation process with Maintenance Planner offers following advantages:

  • Consolidated planning allows users to generate consolidated stack XML for all planned landscape changes
  • Installation of new systems supported
  • Required files for all involved systems can be pushed to download basket in a single planning step
  • Multiple deployment options to choose from

Planning SAP Fiori Apps Installation with Maintenance Planner

Selection of SAP Fiori Apps in SAP Fiori apps reference library

In SAP Fiori apps reference library, select SAP Fiori apps to view product features and implementation details


Figure 3: Selection of SAP Fiori apps – SAP Fiori apps reference library

Switching on the aggregate mode will let you install multiple Fiori apps with a single transaction. Click Aggregate to view aggregated installation and configuration requirements.


Figure 4: Aggregated installation & Configuration requirement for a selection of apps – SAP Fiori apps reference library

At this stage apps that can installed together on the same backend system need to be grouped together.

Click “Prepare Apps for planning with Maintenance Planner” to group apps that can installed together on the same backend system


Figure 5: Prepare apps for planning with Maintenance Planner – SAP Fiori apps reference library

Navigate to Maintenance planner

Once apps are grouped, navigate to Maintenance Planner directly from implementation details tab. In this scenarios, all the apps selected can be installed in a single instance of Maintenance Planner i.e. on a single back-end system.


Figure 6: Direct navigation to the maintenance planner– SAP Fiori apps reference library

Follow Three Step Procedure in Maintenance Planner


Figure 7: Three step process for planning SAP Fiori installation – Maintenance Planner


Check details about technical prerequisites for front-end, back-end & SAP HANA servers.


  Figure 8(a): Listed prerequisites for back-end, front-end & SAP HANA XS server – Maintenance Planner


Figure 8(b): Listed prerequisites for back-end, front-end & SAP HANA XS server – Maintenance Planner

Select Systems

In the next step, select Systems to install required product versions.

Maintenance Planner provides following details for back-end server:

  1. Current software version
  2. Minimal required release
  3. With above information and target version can selected

Maintenance planner provides options to select existing system, install a new system for front-end & SAP HANA XS server. New installation of front-end and SAP HANA system is supported. For existing systems current software state is displayed and target version can selected.

Maintenance planner offers flexibility of multiple deployment options. Following deployment options are possible with maintenance planner:

  1. Separate front-end, back-end and SAP Hana systems.
  2. Co-deployed front-end and back-end system with SAP HANA deployed separately.
  3. Co-deployed back-end and SAP HANA system with Front end deployed separately.
  4. Front-end, back-end and SAP HANA co-deployed.


Figure 9: System Selection – Maintenance Planner

  Impacted Systems

Once you have made the system selection, click Next to view the snapshot of all the impacted systems.

At this stage you can proceed to select files and download installation archives or chose install additional software to iteratively install additional software.


Figure 10 : Snapshot of impacted system – Maintenance Planner

The following icons indicate the type of action that is planned:

  • Fig13.jpg Indicates that the software is to be installed
  • Fig14.jpgIndicates that the software is to be updated
Select and Download Installation media

To select and download installation media select OS/DB files, select stack dependent and independent files.

Select OS/DB files for back-end & front-end systems:


Figure 11(a): Selection of OS/DB files – Maintenance Planner

Select OS/DB files for both systems and click Confirm Selection.


Figure 11b) : Selection of OS/DB files – Maintenance Planner

Click Next and move to the next step.


Figure 12 : Selection of stack dependent and independent files – Maintenance Planner

Download all the relevant files by clicking Download Stack XML and click Push to Download Basket to download the archives to download basket.


Figure 13: Download stack.xml, Maintenance Plan and push archives to download basket– Maintenance Planner


Figure 14: Pushing archives to download basket- Maintenance Planner

Provide an appropriate name for  the transaction and click Save to save your changes.


Figure 15: Planning saved in Maintenance Planner

Open the Maintenance Plan, download the installation media files with the link provided in the Maintenance Plan.


Figure 16: Link in the Maintenance Plan to download the installation media files.

Once you have downloaded the stack.xml and the relevant archives and tools, you can use relevant tools to implement the planned landscape changes.

Additional Information

About Maintenance Planner:

SAP Fiori – Installation

To report this post you need to login first.


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


    Priti Dhingra thanks for sharing this knowledge.

    I would like to ask you a question, we are trying to reproduce the steps indicated and we are getting an error before step 8b (select Systems), it indicates that “the response from the backend is not as expected”(see image below).

    Do you have any idea of the error ? thanks in advance.


    1. Priti Dhingra
      Post author

      Thanks for getting touch. I had a look at your query, I would recommend to raise an incident  for faster resolution  of the issue as we would need more information to analyze the issue. Please attach the logs to incident Regards, Priti

    2. Former Member

      Hello Rodolfo,

      we face the same problem as you did (“response from the backend is not as expected”).

      Can you please share how you have fixed it?

      Thank you and best regards,



        Hello Andrzej,

        you have to register your SAP landscape (every instance) in your SAP SOLMAN and then allow the service that connect this info to Maint. Planner.

        In a sentence, first it is required to perform every configuration of Maint. Plannet to ur landscape.


        1. Former Member

          Hello Rodolfo,

          thank you for your prompt answer.

          In fact all our systems are registered in SolMan system. I can use Maintenance Optimizer i.e. to calculate files need to patch any of our systems.

          Anyway, you are right that something is still missing for Maintenance Planner, since I cannot see some part of our systems there.

          Can you guide me please where is the place where I need to “allow the service to connect” to Maint. Planner?

          Best regards,


            1. Former Member

              Rodolfo, thank you for the tips.

              I managed to upload data of missing systems to mainetenance planner after following note 2002546. The note should be implemented in solman and then you can use “upload to sap support portal” option from LMDB to update missing data in maintenance planner..

              Best regards,


  2. Raufman Brasse

    Hi Priti ,

    You mentioned that the Fig14.jpgicon indicates that the Software is to be updated.  I’m getting this for every component of my backend system. 

    The component that I’m looking to install (FIORI ERP APPLICATIONS X1 1.0) has a minimum requirement of (EHP5 FOR SAP ERP 6.0 – SPS 03).  My system is currently at (EHP5 FOR SAP ERP 6.0 – SPS 07), exceeding the minimum requirements.  Is there a way to generate the stack xml without needing to “update” the other components?


    1. Priti Dhingra
      Post author

      Dear Christopher,

      While selecting BE system, you would see the list of systems in a dropdown, this list is populated based on technical systems information available in LMDB, do you see your system in LMDB in SAP Solution Manager?



  3. Former Member

    Hi Priti ,

    Thanks for the well documented steps. We followed the same for installing FIORI in our landscape( embedded deployment) and I was able to complete the transaction in MP and generate stack.xml and pdf files. But however I donot see the link in the PDF for ” Download Installation Media” However I did get the files in my download basket .

    Am I missing something ?


  4. Former Member

    Hello Everyone,

    i am planning to implement few FIORI apps on top of ERP system.

    Did anyone installed any FIORI apps using above mention procedure…?

    could someone share their real-time experiences.

  5. Julius Pereira

    Hi Priti,

    Can we use the maintenance planner tool even if we are using HCP OData Provisioning to take the place of the on-premises SAP Gateway HUB layer (IWFND)?



Leave a Reply