SAP SPS Upgrade: A Complete Guide with Steps, Images, FAQs & Interview Q&A
Meta Title:
SAP SPS Upgrade Step-by-Step Guide with SUM | Real-Time Issues & Interview Questions
Meta Description:
Master the SAP Support Package Stack (SPS) Upgrade process with detailed steps, images, troubleshooting tips, and top SAP BASIS interview questions. Ensure compliance, security, and optimal performance.
What is SPS in SAP?
SPS (Support Package Stack) is a consolidated release of support packages provided by SAP for software components like SAP_BASIS, SAP_ABA, and others. Performing an SPS upgrade ensures your system stays updated, secure, and SAP-supported.
Why Perform an SPS Upgrade?
- Fix Security Vulnerabilities
- Resolve Known Bugs & Performance Issues
- Enable New Functionalities
- Ensure SAP Support Eligibility
- Prepare System for Future Enhancements (EHPs/S/4HANA)
Who is Involved in the Upgrade?
| Role | Key Responsibility |
|---|---|
| SAP BASIS Consultant | Plan, execute upgrade, and monitor SUM process |
| ABAP Developer | Adjust SPDD/SPAU objects |
| Functional Consultant | Perform module testing |
| Project Manager | Manage schedule, approvals, communication |
| Security Consultant | Check and fix authorization objects |
When Should You Upgrade?
- Every 6–12 months as per SAP’s release schedule
- Before OS/DB Migration or Unicode Conversion
- If a critical SAP Note recommends an urgent update
- As part of security audit compliance
SPS Upgrade: Pre-requisites Checklist
- Generate Stack XML using Maintenance Planner
- Download Support Packages and Kernel files
- Verify system backups (full DB + OS)
- Check for locked transport requests and clear SM13/SM12
- Download and unpack the latest SUM (Software Update Manager) tool
SPS Upgrade Process – Step-by-Step Using SUM
Step 1: Maintenance Planner
Plan the upgrade, select target SPS level, and download Stack XML.
Step 2: Download Required Files
Use SAP Download Manager to fetch stack files. Match filenames with stack.xml.
Step 3: Prepare SUM Tool
Unpack SUM into /usr/sap/<SID>/SUM. Run SUM UI using:
http://<hostname>:1128/lmsl/sum.html
Step 4: Execute SUM Phases
- Extraction – Prepare package content
- Configuration – Upload stack.xml
- Checks – Validate system environment
- Preprocessing – Handle SPDD adjustments
- Execution – Apply SPS updates
- Postprocessing – Handle SPAU adjustments
Step 5: Handle SPDD and SPAU
- Use SPDD for Data Dictionary objects
- Use SPAU for Repository programs
- Document each adjustment and take ABAP team support if needed
Step 6: Post-Upgrade Activities
- Run SGEN to generate ABAP loads
- Verify system using:
- ST22 – ABAP Dumps
- SM21 – System Logs
- ST03N – Workload Analysis
- SICK – System Consistency Check
Common Issues During SPS Upgrade & Solutions
| Problem | Likely Cause | Solution |
|---|---|---|
| SUM does not launch | Port or Java issue | Check logs & use correct JRE version |
| SPDD objects not editable | Modifications in custom tables | Reset changes, reapply if needed |
| SPAU inconsistencies | Unadjusted custom enhancements | Use SPAU_ENH, coordinate with ABAP team |
| Authorization failures | Incomplete roles for user | Temporarily assign SAP_ALL |
| Buffer errors on import | Pending transport issues | Clear import buffer, requeue requests |
Real Project Experience Snapshot
“During a production upgrade from SAP_BASIS 752 SP05 to SP16 using SUM 2.0 SP25, SPDD handling required 3 hours due to complex ZTABLES. Post-upgrade SPAU_ENH consumed 1.5 hours. We used offline SGEN post-process to reduce downtime.”
Top 10 SAP BASIS Interview Q&A on SPS Upgrade
1. What is SPS in SAP?
A Support Package Stack (SPS) is a set of patches for SAP software components bundled together.
2. What tool is used for SPS upgrades?
SUM (Software Update Manager) – a comprehensive tool for upgrades, patches, and conversions.
3. What is stack.xml and why is it important?
It defines the upgrade target, dependencies, and required software levels.
4. What are SPAM and SAINT?
- SPAM: Tool for applying support packages.
- SAINT: Used to install add-ons.
5. What are SPDD and SPAU?
- SPDD: Adjustment of modified dictionary objects.
- SPAU: Adjustment of repository (programs, reports) objects.
6. Why is SGEN executed post-upgrade?
To compile ABAP programs and avoid performance lags on first usage.
7. Can you combine SPS and kernel upgrades?
Yes, but take kernel backup beforehand and upgrade it separately using SAPCAR.
8. What backup strategy do you follow before upgrade?
- Offline DB backup
- OS-level filesystem snapshot
- SUM directory backup
9. What transactions to check post-upgrade?
- ST22, SM21, ST03N, SICK, SE01, SPAM
10. How do you adjust SPAU_ENH?
Use SPAU_ENH to identify custom enhancements and work with ABAP team for merging code.
- SAP SPS upgrade steps
- Support Package Stack upgrade tutorial
- SAP BASIS upgrade real-time issues
- SUM upgrade best practices
- SPDD SPAU explained
- SAP stack.xml usage
- SAP SGEN after upgrade
- Post SPS checks in SAP
- SAP kernel upgrade and SPS
- SAP upgrade plan and checklist
Final Thoughts
Performing an SPS upgrade is a critical responsibility of SAP BASIS teams. It strengthens the security, enhances performance, and keeps systems aligned with SAP support policy. With careful planning, collaboration, and validation, upgrades can be seamless and efficient.
