Skip to Content

Up-To-Date Installation


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>



 ./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

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


    got a problem while using the Stack XML.

    The latest SWPM (SP21 PL6) pops up with no Info.

    Somebody else got the same Problem?


    Starting the SWPM on Linux with 3 options:

    sp21_6/sapinst SAPINST_SLP_MODE=false SAPINST_STACK_XML=/int/workdir/download/MP_Stack_1000325023_20171026_.xml SAPINST_USE_HOSTNAME=<hostname>

    • I’ve found a solution/workaround.

      You need to run the SWPM >=SP21 in Browsermode.

      Example below:


  • I did not find that it very helpful. it may save a few minutes in staring sum tool by your self in case ABAP system installation but it did not save you any frustration in doing the update process involve all the sap notes that need to be applied first before continue the update process. for JAVA system it is the same. at first glance I expect it to perform the installation and update all the support packages provided in stack.xml in one step without go through the SUM process it a bit of disappointment.

  • Hello , I have a question.


    How technically can I include several languages installation in the up-to-date installation withowt use the SMLT transport after the SAP installation?


    Thank you in advance for your answer.

  • Hello,


    I followed this blog to generate Stack for new installation of Netweaver 7.5 system. But when I start sapinst with Stack.xml file it gives me error “sapinst XML parsing error. DETAILS: XML parser reports an error error, line 0 column 38 during parsing file /<path>//sapinst_instdir/<XML_File_Name>.xml (no DTD specified, can’t validate).3”

    Has anyone faced this error before?

    Thank you in advance for your answer.



    in my “Define Change” List within the “Plan a New System” there is no entry for the SAP Solution Manager 7.2. But this is exactly that SAP System I want to install first (until now we have installed no SAP System).

    What shall I do?

    Thanks in advance for your answer.

    • Most probably your problem is that you are using a wrong SWPM version. There are 2 kinds:

      SWPM for NetWeaver 7.0x and SWPM for newer systems. For Solman 7.2 you most probably need this so-called SWPM for newer systems (NetWeaver 7.3 and above).

      SWPM for NetWeaver 7.0x is used to install older Solmans.

  • Hello Priti,

    After the installation, in which client (000 or 001) is recommended to implement the notes for avoid SUM errors?


    Thanks in advance