Now accepting guest editorial from SAP, Oracle, Workday and ServiceNow practitioners.Pitch a guide
The Sign-Off Table

Lesson 3 of 5

Maintenance Planner

10 min

Listen to this lesson

0:00 / 5:46

Maintenance Planner is SAP's cloud-based planning tool for system maintenance. It calculates which support packages, feature packages, add-on versions and other files a system needs to reach a target stack, and it creates the stack configuration file (often called the stack XML) that SPAM and the Software Update Manager use. It also plans release upgrades and conversions to SAP S/4HANA, and offers related checks such as side-effect reports and security notes.

  1. System dataThe system's installed software is known to SAP (for example via the system landscape directory and LMDB data sent to the SAP Support Portal)
  2. PlanIn Maintenance Planner, choose the system and the target: an SPS, an FPS, a release, add-ons
  3. CalculateThe tool calculates the required packages, dependencies and conflicts across components
  4. Confirm and downloadFiles are pushed to the download basket; the stack configuration file is generated
  5. ApplySPAM or SUM reads the stack file and imports the queue in CMD first
From system data to an applied stack. The same plan is then repeated for CMQ and CMP.
The Sign-Off Table · thesignofftable.com/academy/sap-bas-203

Prerequisites

  • Accurate system data. If the installed software information is wrong or out of date, the calculation is wrong. Maintenance Planner can also correct recorded system information.
  • A valid maintenance certificate. SAP training notes it is part of the license file, is needed for patching and upgrades, and is valid for three months (it can be renewed automatically).
  • The latest tools. Update SPAM/SAINT with the SPAM/SAINT update before importing support packages, and download the current version of SUM.
  • Enough space and time. Downloaded archives, the shadow system used by SUM, and backups before the event.

SPAM or SUM?

AspectSPAM (Support Package Manager)SUM (Software Update Manager)
Typical useSupport packages and stacks in simpler situationsStacks in downtime-critical landscapes, release upgrades, conversions
DowntimeSystem largely unavailable during import (a downtime-minimized mode helps)Shadow system technique reduces downtime significantly when configured well
ComplexitySimpler to useMore complex, more options
Decision ruleSAP Note 1803986 lists the rules for choosingSUM 2.0 covers ABAP systems on SAP_BASIS 7.50 and higher
Choosing the import tool, per SAP training and the SUM product page.
The Sign-Off Table · thesignofftable.com/academy/sap-bas-203

Rehearse the import

SPAM offers a test scenario that checks the queue for conflicts and required modification adjustments without importing anything; afterwards the queue must be defined again for the real (standard) import. The standard scenario imports the full queue, and errors must be fixed before it can finish. While an import runs, no other imports or manual repository changes are allowed. After a successful import, confirm the queue in SPAM: until you do, further support package imports and SNOTE activities are blocked. A short rehearsal in CMD avoids surprises in the CMQ and CMP windows.

A SPAM import in CMD: rehearse with the test scenario, redefine the queue, import for real, adjust, then confirm so further imports and SNOTE are unblocked.
The Sign-Off Table · thesignofftable.com/academy/sap-bas-203

Modification adjustment: SPDD and SPAU

If you have modified SAP objects or implemented notes, importing new SAP versions raises a question for each affected object: keep your change, or return to SAP standard? SPDD handles dictionary objects and must be completed during the import, because tables may otherwise lose custom fields. SPAU handles programs and other repository objects, including implemented notes, after the import. Adjustments made in development are collected in transports that must be included when the stack is applied in CMQ and CMP; SAP training notes they are not forwarded automatically.

Adjustments are made once in CMD and travel as transports; they must be added to the queue for CMQ and CMP because they are not forwarded automatically.
The Sign-Off Table · thesignofftable.com/academy/sap-bas-203
Few modifications, tight windowPrefer SUM with downtime-optimizing options; rehearse in CMQ
Many modifications, tight windowSUM, early SPDD/SPAU in CMD, adjustment transports, full rehearsal
Few modifications, generous windowSPAM is often enough; keep it simple
Many modifications, generous windowEither tool; invest effort in SPAU and regression rather than downtime tuning
A rough guide to where effort goes in a maintenance event.
The Sign-Off Table · thesignofftable.com/academy/sap-bas-203

What would you do?

Maintenance Planner proposes a stack for CMQ that differs from the one Sam applied to CMD last week, because CMQ's recorded system data shows an older add-on version. What should Sam do?

Key points
  • Maintenance Planner calculates target stacks and creates the stack configuration file for SPAM and SUM.
  • Prerequisites: accurate system data, a valid maintenance certificate, current SPAM/SAINT and SUM versions.
  • SPAM is simpler; SUM reduces downtime and handles upgrades and conversions.
  • SPDD and SPAU adjust modifications; include adjustment transports in later systems' imports.

Check your understanding · not graded

Lesson check

  1. 1. What file does Maintenance Planner generate for SPAM and SUM?

  2. 2. Which adjustment must be completed during the import to protect custom table fields?

  3. 3. What should be updated before importing support packages?

  4. 4. How long is a maintenance certificate valid, per SAP training?