Depending on which version/EHP/SP level you are on and going to, you can probably use SPAM to apply your support packages, but I would recommend you use SUM. Here are some of its advantages:
Kernel: As somebody else already mentioned, SUM does everything, including kernel, sapjvm, igs, SPAM/SAINT update, etc., so you don't have to do those separately. It even unpacks everything for you.
Time: While the overall run time is longer when using SUM vs SPAM, the time during which your users are affected, i.e. down time, is considerably shorter. It will probably only really matter for production, but the process should be "tested" in dev and qa first.
Recoverability: Up until just before the down time, you can still back out of it without any restores being necessary. SUM prompts you to make backups before and after the down time, so recover time, if you do need to restore is much shorter as well.
Future: I suspect there will be more and more cases where SPAM cannot be used, so you might as well start getting some experience with it. If you have done upgrades before, it will look very familiar; if not, you will gain some experience for future upgrades.
What Juan mentioned is the Maintenance Optimizer functionality of the Solution Manager system.
You need to connect the ERP system to the Solution Manager and run the MOPZ to create a stack file and download all the files which are mentioned in the stack file.
The note mentioned by Shkëlzen suggests what should be used to patch the SAP systems.
If this is small scale patching then SPAM/SAINT should be fine.
Using SUM would be the appropriate one as it appears to me you want to patch all the components to the latest level.
If you are planning to update the EHP level of the system then SUM tool is the one to be used.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.