Support Packages, Add-ons & Enhancement Packages

You need to obtain support packages for a system based on SAP NetWeaver 7.0 or later. Why can't you just grab the individual files straight from the Support Portal and load them?

When you copy a support package to the SAP transport directory instead of the frontend, what extra step is required before SPAM can load it?

When you define a Support Package queue for several software components at once, what do you actually select, and what does SPAM compute from it?

A support package import through SPAM is failing partway. Besides the SPAM logs, where else can you look for the technical cause?

You must apply a large number of support packages to an ABAP system and the downtime window is tight. Beyond running SPAM inline, what option minimizes downtime?

A team wants to trial a business function on the development system before rolling it to production. Why is the dev system the wrong place to evaluate it?

For an SAP NetWeaver enhancement package, is there a separate business-function activation step like the one for an SAP ERP enhancement package?

When SAPehpi starts, what is the first program it launches, and what does that program do?

Before you can run SAPehpi to install an enhancement package, what landscape prerequisites must be in place?

Which two support-package component packages exist in every SAP system, and why does that matter when planning a stack?

A colleague calls the file they're importing a "hot package." Is that the same as a support package, and what exactly does it correct?

What makes a Support Package Stack different from just taking the newest support package for each component?

In a SAPehpi run, what does the stack configuration file control, and where does it come from?

After an upgrade or support-package import changes SAP's authorization defaults, which transaction reconciles your existing roles with the new SAP proposals?

Before you modify an SAP standard object, what registration is required, and how does that surface later during a support-package import?

In a SAPehpi run, why does optimizing the shadow-system build (Preprocessing) NOT shorten the part that actually causes user downtime?

While defining a Support Package queue, SPAM flags that one component is missing an intermediate package. Why can't you just proceed with what you have?

During a support-package import you're prompted to adjust modified objects. A teammate is adjusting changed Data Dictionary (DDIC) objects under SPAU. Right transaction?

A 2013-era runbook tells you to use SAPehpi/SAPup for an enhancement-package install and a separate tool for the release upgrade. On a modern system, what's wrong with that?

An admin wants to import a support package directly in the productive client so the fix lands where users work. Why is that the wrong client?

A request comes in to install an SAP industry solution / plug-in. Which tool — and what's the giveaway that it's NOT a support-package job?

After installing an enhancement package, where do you actually turn the new functions on — and why is this a scheduling decision, not just a final click?

A colleague says "we installed the enhancement package, so the new functionality is now system-wide like any patch." Why is that the wrong mental model?

During the SAPehpi Preprocessing step several things happen to the shadow system — which action affects transports in the original system?