Skip to Content


Maintenance planner supports planning of new installations on a chosen stack level. Maintenance Planner significantly simplifies the installation process by eliminating the steps of system registration and a separate system update planning during installation. With Maintenance Planner, you can generate a consolidated stack configuration file which allows you to install and later update your system at the chosen SPS level. Maintenance Planner allows you to select target software level and push archives to the download basket in a single step. Simplified process is offered for ABAP & Java systems.

This document explains the process with Maintenance Planner comparing the existing process with the new improved process.

       Planning New System Installation with Maintenance Planner


                    Figure 1: New, improved process followed for a new installation and update.

Installation process with Maintenance Planner offers following advantages:

  • A single place for the customer to define his target for installation.
  • Simplified process allowing users to generate consolidated stack.xml for planned landscape changes without registering the system in SAP Solution Manager.

Existing Process to Reach the Target Software Level

The following graphic illustrates the process of an installation and update without Maintenance Planner:


                                     Figure 2: Current process followed

Improved Process for New System Installation along with the Involved Tools

The following graphic shows the new improved process with Maintenance Planner:


                                                   Figure 3: Up-To-Date Installation

  • In Maintenance Planner, the IT Administrator plans, validates and generates stack XML and media files are later consumed by Software Logistic tools, such as the Software Provisioning Manager (SWPM) and Software Update Manager (SUM) for accomplishing the planned landscape changes.
  • Software Provisioning Manager consumes the generated stack XML.
  • Standard post-installation activities need to be completed before you use SUM .
  • SUM consumes the same stack.xml to update the system with the selected service packs (SPs) or add-ons.


To start using enhanced functionality, SAP Note 1940845  needs to be implemented in the SAP Solution Manager system.

Planning Installation with Maintenance Planner

Example: The IT administrator wants to install a SAP NetWeaver 7.4 ABAP system with Application Server ABAP on the latest Support Package stack, including an add-on SAP Liquidity Risk Management 1.1.

Perform the following steps:

  • Go to the Product Availability Matrix at and search for the Product Version ‘SAP Liquidity Risk Management 1.1’.
  • Check the required Product Version for SAP Liquidity Risk Management 1.1, which is SAP NetWeaver 7.4.
  • In Maintenance Planner, plan a new installation by selecting the current Product Version (SAP NetWeaver 7.4) and then updating over an add-on.

In the home page of Maintenance Planner, click Plan a New System tile

Home Screen.png

                                             Figure 4: Maintenance Planner home page

In the maintenance cycle screen, click Plan to start planning new system installation.


                                       Figure 5: Planning new installation in Maintenance Planner

Follow the 4-step procedure, starting with Define target. Enter SID for the new system and select target software level details.


               Figure 6: Target Software details selection in Maintenance Planner

Select Support Package stack and click confirm selection.


                         Figure 7: Product version and Support package stack selection

At this stage you can choose to install additional software or proceed to complete the planning process. The above steps can be repeated any number of times to install additional software. The stack.xml file generated at the end of the planning process contains the metadata of all the planned actions.

Select Install or Maintain Add-on to select Add-on to be installed.


                                        Figure 8: Additional software selection

Select the Add-on, Support Package stack and click Confirm Selection.


                             Figure 9:  Selection and confirmation of target software details

Click Next to move to the next stage of the installation planning process.


                                   Figure 10: Confirmation of target software details

Select OS/DB dependent files to be added to the download basket and click Confirm Selection.


                                        Figure 11: OS/DB dependent files selection

Select Stack Dependent and Independent files and click Next.


                                   Figure 12: Stack dependent and independent files selection

Click Push to Download Basket to download the archives from SAP Service Marketplace.


                                   Figure 13: Pushing archives to the download basket

Download the installation consolidate stack XML by clicking Download Stack XML


                              Figure 14: Downloading stack XML

Click Next. You can find the link to the initial installation media towards the end of the maintenance plan.


                         Figure 15: Downloading installation media from Service Market Place

At this stage, you can complete the planing process by clicking Set to Complete.


                     Figure 16: Completion of planning activities in Maintenance Planner

The link in Maintenance Plan would direct to SAP Service Marketplace to download the related media files.



              Figure 16: Link from Maintenance Plan directed to SAP Service Market Place for the media download.                       

Consuming Generated stack XML and Media Files by Software Logistics Tools

Download the related Software Provisioning Manager version out of the Download Basket, follow the recommendations of SAP Note 1680045.

Follow the guide to install your system – especially consider the instructions for installations using a stack configuration file.

Refer to the installation guide for Software Provision Manager at:

Start Software Provisioning Manager with the parameter SAPINST_STACK_XML=<absolute path>


UNIX: ./sapinst SAPINST_STACK_XML=/download/Stack_1000001234_20150423.xml

Microsoft Windows: sapinst.exe SAPINST_STACK_XML=C:\tmp\Stack_1000001234_20150423.xml

In the Welcome screen, you get installation options filtered according to your stack XML file:


                                                                 Figure 17: Software Provisioning Manager home screen                                       

Post-Installation Steps

After the successful completion of the installation, follow the instructions provided in Post-Installation section of the installation guide to complete the configuration. For more information, see Based on the OS and DB requirements, choose the installation guide:


                    Figure 18: Post installation steps in the installation guide.

Executing Update Activities

Start Software Update Manager and provide the generated stack.xml file to complete the update activity.


                                        Figure 19: Home screen of SUM (Software Update Manager)

Executing Post-Update Activities

At, select the guide for the product for which you have completed the update activity.


Choose the Upgrade and Update Guide and select the stack applicable for the system.


Follow the instructions provided in the guide to complete the update process.


More Information

To report this post you need to login first.


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

  1. Gary Mason

    Thanks for the doco.

    I’ve used the Maintenance Planner a few times now for new ‘up-to-date’ installations and it works great!

    1 question I have though….. from the options it seems that this process can only be used for ABAP instances, is this correct? To progress beyond the target software level, you can only select ABAP based products, Portal or PO is not available.



    1. Boris Zarske

      Dear Gary,

      Thanks a lot for your feedback! You are right, the up-to-date installation is currently only available for ABAP systems – but there are plans to extend the coverage also to Java, so look out for corresponding updates in the upcoming months.

      Best regards,


    2. Priti Dhingra

      Hello Gary,

      Functionality to install Java system is now available in MP.  The new process supports following product versions:

      • SAP NETWEAVER 7.5
      • SAP NETWEAVER 7.4
      • SAP S/4HANA ON-PREMISE 1511
      • NW 7.5 FOR SAP S/4 HANA 1511

      Best Regards,


  2. Ajay Chirmade

    Dear Sir,

    we are planning to install the NW 7.5 maxdb based JAVA system w/ this option as of now and mostly we will use it for several installtions planned ahead .. can you please share in case any of the document you have ? we are not sure how the SUM will be called and do we need to do any preparations for it ?

    we can not find this information also in any of the posts or guides since generally SUM requires its own directories and setup generally.. so do we need to do that manually or SWPM does all of it ? this part is really not clear.

    please help if you can guide on this.

    thnx and regards,

    Ajay Chirmade

    1. Boris Zarske

      Dear Ajay,

      For the installation of AS Java systems, Software Provisioning Manager does not prepare/start SUM execution, so you have to perform those activities as described in the update guide. An overview of up-to-date installation offerings is available for example in the technical details presentation of Software Provisioning Manager on slide 12 (“Improvements offered by up-to-date installation” – covers both AS ABAP and AS Java).

      Best regards,


      1. Ajay Chirmade

        ok thank you  so much for the explanation and clearing out the doubt. So in fact for JAVA system it is really not of any use as such if SUM needs to be started manually later.

        Since earlier post mentioned that the JAVA is supported we were curious about it.

        i dont think it is really giving any benefit just by creating the stack file earlier then .. it will be good if these points are clarified in the document written above so amount of time spent in exploration and learning this option will not be needed for customers who can not benefit from this .

        Thnx and Regards,


        1. Boris Zarske

          Dear Ajay,

          Thanks for this honest feedback! First, the status described above by me is the situation as of today. We are open to further feedback (for which we are also right now offering a CEI) and the Java scenario might improve in the future (also based on your feedback provided today :-). Second, I still see a major benefit in case you would have different roles performing a) the planning and b) the execution. By consuming the stack XML file, a clear handover is defined from planning phase to actual execution, making sure that the right product version with the planned SAPSID is selected in Software Provisioning Manager.

          Best regards,


  3. Klaus Hesselmann

    Hi Arvind,

    very good description! Planner + Download + SWPM with stack file work very good!

    My actual situation is that I planned a new installation with Maintenance Planner of NW7.50 SP03 – 2 System Landscape – ABAP only – two weeks ago and start installation last monday with the first system. During execution phase I started planning the second system with Maintenance Planner. Actually SP04 is available since 22nd of July. The first system is at the point where SUM is started. Is it possible at this time to change the stack file from SP03 to SP04 to get the latest patches installed? Or to change the SAPSID in the stack file to the SID of the second system to get the same version as the first system has? Additional I tried to generate the stack file based on SP03 for my second system, but some components where calculated with different patches (Kernel two weeks ago PL100 now PL200,  SWPM PL2 > PL3, SUM PL3 > PL4,  SAP-NW Gateway Foundation SP3 > SP4).

    Thnx for any information,


    1. Arvind Sharma Post author

      Hello Mr. Klaus,

      Thanks for the comments!

      Can you please share your email id & contact details, so that i can connect you with development team to understand your scenario better.

      Best Regards,

  4. André Richter

    Hello Arvind,

    thanks for the very interesting guide!

    I am facing a similar problem like Klaus right now:

    I plan to install a new SAP NW 7.5 BW powered by SAP HANA system environment (3 systems: DEV, QAS, PRD) and I would like to perform three identical up-to-date installations.

    Although the whole concept seems to be very sophisticated, I can’t believe that it is not possible in Maintenance Planner to plan a whole new system environment with e.g. 3 different SIDs?!

    As I understand it right, limited by current functionality, I have to create three different transactions in Maintenance Planner (one for each new SID) and “hope” that the calculated stack.xml files are completely identical.

    At least a copy report like RPT_MOPZ_COPY_STACK_XML would be helpful to reduce the effort and risks.

    Best Regards


  5. Douglas Helm

    How do I plan a new NW 7.5 Java SLD system with the maintenance planner?

    There is no JAVA option & the only selections under NW 7.5 are:
    “Application Server ABAP”
    “BI Content Extension”
    “Business Intelligence”
    “Developer Workplace”
    “SAP BW/4HANA Starter”

    Confirm Selection is grayed out until you select one of these.

    Furthermore, there is no option to plan the JAVA stack of Solution manager 7.2 from what I can tell.  What am I missing here?

    Thanks in advance!!

    1. Boris Zarske

      Hi Douglas,

      You can switch system type by clicking on the left icon next to the SAPSID. This normally also shows up as pop-up at the beginning of a planning process for a new system.

      When you select JAVA, the corresponding options show up.

      Best regards,


Leave a Reply