Software Maintenance: Updates, SPAM & Add-ons

What determines whether an add-on component can be uninstalled?

What account does SUM run as, compared to SWPM, and which version applies to S/4HANA?

What do most add-ons require, and how is it generated?

What's the difference between an upgrade and an update in SAP maintenance, and what tool does both?

Why must you update Transaction SPAM before an update, and what's it always combined with?

What is the maintenance planner, and what critical file does it generate for SUM?

What's the only precondition for using the maintenance planner with a system not registered in SAP Solution Manager?

Why does SUM need the current certificate revocation list (CRL)?

What are the six sections of a SUM update, and which is the real downtime?

What are the SUM update strategies and their downtime/resource trade-offs?

Why should all systems in a landscape use the same update strategy?

What is an MCOD system, and what constraint does it impose on updates?

Why is skipping Transaction SPDD never an option?

Before entering the downtime part of an update, what must you back up and why?

What does SUM do to the SAP HANA tenant database's log mode at downtime, and what happens at the end?

During the Execution (downtime) section, who can log on, and what do other users see?

What are Type P errors during an update, and what must you do about Errors Requiring Revision?

What are the key manual activities after an update?

Until what point can a SUM reset be done, and what's the only way back afterward?

Why is SPAM entirely downtime, and when is it still a reasonable choice?

How does SPAM import a patch, and what final step must not be forgotten?

What's the difference between SPDD and SPAU in modification adjustment?

During an update, which directory grows substantially and why, and what space thresholds matter?

When would you use SPAM instead of SUM for patching?

What does creating a maintenance transaction in the maintenance planner do, and how do files reach the server?

How are SUM's connections managed differently from SWPM's sapinst?

How does SUM use a shadow repository and shadow instance to reduce downtime?

How are the shadow repository's schema and the new tables named during a SUM update?

Why can SUM disable database archiving during downtime, and why is that the recommended choice?

Why should you restart the system after an SGEN ABAP load generation?

What are add-ons, and how are they installed?