Software Maintenance: Support Packages & Add-ons

What is the difference between a Support Package Stack (SPS) and a Feature Package Stack (FPS) in SAP S/4HANA?

How is SUM's server-side process started, and how does that differ from SWPM?

What is the relationship between S/4HANA's Feature Package Stack (FPS) and Support Package Stack (SPS)?

What two sources can you upload a patch package into the SPAM patch queue from?

What is SUM (Software Update Manager), and which version does S/4HANA use?

Before starting a SUM update, why should you first update transaction SPAM to its highest version?

Why is it recommended that all systems in a landscape use the same update strategy?

When planning an add-on installation in the maintenance planner, what is the key difference from planning a normal update?

How feasible is uninstalling an add-on?

When <sid>adm can only log on via sudo and its password is unavailable, how does SUM set up an alternative authentication user (unlike SWPM)?

Which program puts back the background jobs suspended before the update, and what should you watch out for?

What is a type P error during an update?

Which is SUM's default update strategy, and what do the first three strategies essentially trade off?

Why is database archiving disabled by default during the update's downtime phase?

When patching S/4HANA, how should you choose between SUM and transaction SPAM?

What is the shadow system (shadow instance) in an update?

What are SAP's patch delivery units SP, SPS, and FPS?

Where is transaction SPDD executed, and why can't you skip it?

What are the characteristics and limitations of SUM's Single System update strategy?

How does the shadow repository reduce update downtime?

What is an add-on?

Before entering downtime, how does SUM change the HANA tenant database's log mode, and why?

What does running SGEN after an update do, how does it affect system load, and how do you reduce it?

What is the main cost of using a shadow system?

Among SUM update sections, which are in uptime and which is the real downtime?

Which two transactions are used for the update's modification adjustment, and how is the work divided?

Which SAP S/4HANA versions offer extended maintenance, and until when?

What must the backup before update downtime include, and why include the SUM directory?

What six main sections does a SUM update consist of?

After patching with transaction SPAM, what final action must you perform?

Why is the SUM directory's disk space requirement large (how much is recommended), and how are you warned about low space?

What is the relationship between SUM and the SAP Host Agent, and what must therefore be done before updating?

What is the CRL you download before an update, and what does SUM use it for?

How long does mainstream maintenance last for SAP S/4HANA 2022 and earlier versions?

What is the maintenance planner for, and where does its system information come from?

What extra file does an update/upgrade need compared with a new installation, and what generates it?

What GUI-connection feature does SUM have that SWPM does not?

What is the situation with Enhancement Packages (EHP) in SAP S/4HANA?

What is the difference between an update and an upgrade as SAP distinguishes them?

What time limitation does SUM's reset (full rollback to redo) have?

What scenario is SUM's Downtime Optimized strategy for, and what two options does it further split into?

At the start of the Preprocessing phase of a SUM upgrade, what does the system lock, and what is the impact?

After the maintenance planner generates the stack XML, how do you download the files to be installed to the server?

What two tools install an add-on, and how do you choose?

How is the database schema name for the shadow repository derived?

During the update's Execution section (downtime), what happens when an ordinary user logs on?

For a system not yet configured into Solution Manager, can you use the maintenance planner, and what is the prerequisite?

Which OS user does SUM run as, and how does that differ from SWPM?

How do you handle open repairs (unreleased repairs) during an update?