# SAP S/4HANA On-Premise Release Upgrade Checklist > Source: https://netray.co/tools/sap-s4hana-on-premise-release-upgrade-checklist > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: Free Tools ## Short answer Planning, custom code, technical prep, SUM execution and post steps for upgrading one S/4HANA release to a newer one. ## Category sap ## Erp SAP S/4HANA (on-premise) ## Audience - SAP Basis administrator - ABAP developer - SAP technical architect - SAP project manager ## Tool **Kind:** checklist **Groups:** #### 1. Planning **Items:** **Text:** Read the Upgrade Guide (Upgrade and Conversion Guide) for the target release and its release information note **Critical:** true Review the Simplification List for the target release; only items new since your current release apply Run SAP Readiness Check for the upgrade if your release path supports it **Text:** Build the target stack in Maintenance Planner including add-ons, and generate the stack.xml **Critical:** true Check front-end server (SAP Fiori) compatibility and plan the FES upgrade order for hub or embedded deployment **Text:** Check the minimum SAP HANA revision for the target release and upgrade HANA first if needed **Critical:** true Check OS, database and kernel support in the Product Availability Matrix Confirm every add-on, including industry and partner add-ons, is released for the target or must be uninstalled #### 2. Custom code **Items:** **Text:** Run ATC with the S/4HANA readiness check variant for the target release (for example S4HANA_READINESS_2023) **Critical:** true Use usage data (SCMON or UPL) to skip fixing code nobody runs Plan SPDD (dictionary) and SPAU / SPAU_ENH (repository and enhancements) adjustments with developers named Agree a development and transport freeze window Plan the dual maintenance approach for urgent fixes during the project #### 3. Technical preparation **Items:** **Text:** Download the latest SUM 2.0 SP and read its note **Critical:** true **Text:** Run the simplification item check (report /SDF/RC_START_CHECK, SAP Note 2399707) for the target release and clear errors **Critical:** true Take and test a full backup (database and file system) before uptime processing Clear open update requests in SM13 Empty qRFC and tRFC queues (SMQ1, SMQ2, SM58) and process pending IDocs Suspend background jobs with report BTCTRNS1 before downtime Release or clear locks (SM12) and check no transports are pending import Run a full trial upgrade on a copy of production and record phase runtimes #### 4. Execution with SUM **Items:** **Text:** Uptime phases: extraction, configuration, checks, preprocessing on the shadow system **Critical:** true SPDD adjustment in the shadow system when SUM stops for it Decide on the downtime approach: standard, or the Zero Downtime Option where your release path and licence support it Downtime: lock users, run execution phases, monitor logs Keep the SUM directory and logs until the upgrade is signed off #### 5. Post-upgrade **Items:** **Text:** SPAU and SPAU_ENH adjustments transported to QA and production **Critical:** true **Text:** Resume background jobs with report BTCTRNS2 **Critical:** true Run SGEN to regenerate ABAP loads Perform the follow-up activities listed in the Upgrade Guide for the target release Update Fiori content: new catalogs, spaces and pages, and clear caches Run regression tests for core processes and interfaces Upgrade the front-end server in the agreed order if it is a separate hub **Scoring Note:** This is a release upgrade within S/4HANA, not an ECC conversion. Check names of check variants and SAP Notes for your target release; release specific details are published in the Upgrade Guide on help.sap.com. ## Content **Intro:** This checklist covers upgrading SAP S/4HANA on-premise from one release to a newer one, for example 2021 to 2023, using Maintenance Planner and the Software Update Manager. It is not a conversion from ECC; it focuses on the delta between your current and target release. **Sections:** #### How to use it **Body:** Start planning a few months ahead: the Simplification List, add-on compatibility and HANA revision can each force earlier work. Work through planning and custom code in parallel, run at least one full trial on a production copy, then schedule the production run with the measured downtime. Export the checklist per system so DEV, QA and production each have a signed record. The critical items are the ones that most often stop or delay a SUM run. #### Where this lives in the system **Body:** Maintenance Planner on the SAP Support Portal builds the stack and stack.xml. The simplification item check runs as report /SDF/RC_START_CHECK in SE38 on the source system and lists items for the chosen target release. ATC (transaction ATC, often run centrally) uses the S4HANA_READINESS check variant for the target. SUM is run via its browser UI on the primary application server. SPDD, SPAU and SPAU_ENH are standard modification adjustment transactions; BTCTRNS1 and BTCTRNS2 are reports that suspend and release background jobs. **Bullets:** - /SDF/RC_START_CHECK: simplification item check. - ATC: custom code readiness. - SUM: the upgrade itself. #### Worked example **Body:** An S/4HANA 2021 system with a hub Fiori front-end server is upgraded to 2023. Maintenance Planner flags one partner add-on that is not released, so the vendor ships a new version first. The simplification check reports two relevant items for the delta. ATC with the 2023 readiness variant finds 140 findings, but usage data shows only 30 are in code that runs. The trial run on a production copy gives a downtime of about one weekend, and the team schedules the production run accordingly. #### Common mistakes **Body:** Forgetting the HANA revision prerequisite, discovering an unreleased add-on late, leaving jobs running into downtime, and skipping SPAU follow up in QA. Another frequent issue is the Fiori front-end server: an upgraded backend with an old FES can break apps, so plan the order with the compatibility information for your release. **Cta:** If you want your Basis and development team to ask questions about upgrade logs, ATC findings and simplification items in plain English on your own servers, we can set that up. **Faq:** #### What are the steps for an SAP S/4HANA upgrade? **Answer:** Plan with the Upgrade Guide and Simplification List, build the stack in Maintenance Planner, check custom code with ATC, run /SDF/RC_START_CHECK, prepare the system (backups, queues, jobs), run SUM including SPDD, then do SPAU, post steps, Fiori updates and regression tests. #### Where is the upgrade guide for SAP S/4HANA 2023? **Answer:** On help.sap.com under SAP S/4HANA for the 2023 release, in the Upgrade and Conversion Guide documentation, together with the release information note. Use the guide for your exact target feature pack stack. #### Do I need the simplification item check for a release upgrade? **Answer:** Yes. Simplification items can be introduced between S/4HANA releases, and the check must pass before SUM continues. Run /SDF/RC_START_CHECK with the target release selected and fix errors before the trial run. #### How long does an S/4HANA release upgrade take? **Answer:** Projects often run a few months including testing, while technical downtime depends on database size, add-ons and the SUM options used. Measure downtime in a trial on a production copy rather than relying on estimates. ## Search terms sap s/4 hana upgrade steps, upgrade guide for sap s/4hana 2023, sap s4 hana upgrade, sap s/4 hana upgrade guide, sap upgrade guide s 4hana 2025, s4hana 2021 to 2023 upgrade, sap s4hana upgrade checklist --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json