Executive summary
Candent upgraded a real estate company’s SAP S/4HANA landscape from release 1610 to 2021, together with the SAP HANA database from 1.0 to 2.0. A mock upgrade on a copy of production came first, so the production upgrade ran to a tested plan and the company’s custom Fiori apps kept working.
Business context and problem
S/4HANA 1610 is an early S/4HANA release, and staying on it means missing years of functional improvements and moving further from SAP’s maintenance timelines. S/4HANA 2021 also needs SAP HANA 2.0 and a newer operating system, so the upgrade touched every layer of the stack.
Approach
- Three layers in order: operating system (SLES), then the SAP HANA database, then the S/4HANA application.
- A copy of production upgraded first as a mock, to find issues, adjust custom code and measure the downtime production would need.
- Development and quality upgraded next, followed by testing and a cut-over plan, then production.
- Custom ABAP objects adjusted in SPDD and SPAU; custom Fiori apps protected throughout.
- BASIS and ABAP delivered by Candent; the operating system upgrade by the client’s infrastructure partner.
Before and after
| Dimension | Before | After |
|---|---|---|
| Application | SAP S/4HANA 1610 | SAP S/4HANA 2021 |
| Database | SAP HANA 1.0 | SAP HANA 2.0 |
| Operating system | Older SLES release | SLES release supported for S/4HANA 2021 |
| Custom code | Written for 1610 | About 100 custom objects adjusted for 2021 |
Solution architecture
| Layer | Detail |
|---|---|
| Landscape | Two systems: development and quality on one SID, plus production |
| Rehearsal | Sandbox / mock system copied from production |
| Tools | Maintenance Planner, feasibility and simplification item checks, Software Update Manager (SUM) |
| Custom code | SPDD and SPAU modification adjustment |
| User interface | Custom Fiori apps retained |
End-to-end flow
- Copy production to a sandbox, run Maintenance Planner and the feasibility and simplification item checks.
- Upgrade the sandbox: SAP HANA 1.0 to 2.0, then SUM uptime and downtime phases, custom code adjustment and post-upgrade steps.
- Upgrade development and quality the same way, then system and user acceptance testing.
- Upgrade production to the rehearsed cut-over plan, with backups before each step.
- Post-upgrade BASIS and ABAP support for upgrade-related issues.
Delivery
Delivered offshore from Candent’s Pune office with a team of 8, followed by post-upgrade support.
