Upgrade of S/4HANA Cloud, public edition (3-system landscape)
In my previous blog Release and Update Cycle of S/4HANA Cloud, I talked about the three different types of life cycle events for S/4HANA Cloud. Having a 3-system landscape (Dev, Test and Production) is the new default for S/4HANA Cloud, public edition. In the Activate roadmap for 3-system landscape, there is an Update and Release Cycle deliverable, described all the three different types of life cycle events on public cloud, hotfix, continuous feature delivery and release upgrade.
For the release upgrade scenario in 3-system landscape, there is an upgrade roadmap that provides structure and details with regard to this process. It is a separate roadmap dedicated to S/4HANA Cloud, public edition (3-system landscape) upgrade, covering the 2 weeks preparation related steps before software upgrade starts with Test System, describe the regression test that customer needs to be focusing on during the 3 weeks of upgrade period in Test System, and highlights the tasks to be completed right after the software upgrade of Dev and Production system, including the deployment of upgraded business configuration content, which is new with the introduction of 3-system landscape.
What is business configuration content? For those of us have worked in the old R/3 ERP world, we all know that the flexibility with R/3 ERP is all about the configuration or customizing that is maintained in IMG. Without any code changes, setting in configuration tables can lead to different ways how customers want to use the same SAP product. The decoupling of the business content managed via these configuration table vs. software or code updates are a natural progression with public cloud. This allows the software or code line continuously being updated in cloud without impacting how customer run their solution per current configuration setting for their business. Customers are given more time to make mandatory adoptions in their business process and implement new innovation per their own timeline.
From project planning point of view, as the green bar indicated here, there are quite a lot of design and configuration activities can be carried out throughout the 3 weeks software upgrade period. For example, customer can still scope and make organizational structure changes and access configuration activities via the SAP Central Business Configuration tool.
There are certainly some restrictions on S/4HANA side, as indicated with couple of short red bar, around the software upgrade weekends where transport related activities in the respective systems are impacted.
During the upgrade period, Test System should be used for Regression Testing to ensure functionality that worked before are not impacted by the upgrade. Although transports can still be moved across the landscape from Dev to Test to Production, it should be minimized in order to maintain a valid testing environment.
After the 1st week, if customer creates a new project in SAP Central Business Configuration, it will have the upgraded reference content, the new content version. Therefore, avoid deploying this new project to Dev system till after Dev system is software upgraded at a later point.
Here are the respective recommendations and limitations from the above diagram:
a) System getting prepared for Upgrade. No Import & Export of transports
b) Moving transport cross the landscape (D-T-P) is still possible. For urgent needs only to ensure valid regression testing environment for customer are live in P
c) Access Configuration Activity is possible until the respective S/4HANA Cloud systems (Development, Starter, Partner Demo) getting prepared for upgrade.
d) Organizational structure enhancements, adding new scope or country are possible until project in SAP Central Business Configuration is locked when upgraded business configuration content is uploaded. It is however, not recommended to activate new country during the 3 week period as it may delay the application of content upgrade in case of activation issues at the end of the 3-week period.
e) Avoid deploy a project created new after the 1st week in SAP Central Business Configuration. Applicable to both Evaluation and Implementation project
As a result of the previously mentioned decoupling, one key difference in 3-system-landscape upgrade is the deployment of upgraded business content from SAP Central Business Configuration to S/4HANA landscape. It is after the completion of 3-week software upgrade period.
In task Deploy Upgraded Business Content, it described the SAP Central Business Configuration behavior and the Transport Automation scheduled on S/4HANA side in two procedure steps and highlighted in the procedure note about the automatic consistency check and possibility of revising the default import schedule.
Inside SAP S/4HANA Podcast
As always, I would like to encourage you to subscribe to our new podcast “Inside SAP S/4HANA.” This podcast leverages the unique knowledge and expertise of SAP S/4HANA product experts, partners and customers to address your needs by sharing product insights and project best practice. There is no customer success without product success and project success; we help you get to the next level and make your SAP S/4HANA projects a success. Subscribe now and benefit from the shared knowledge.
openSAP Microlearnings for SAP S/4HANA
Just a couple of months ago, we launched openSAP microlearnings for SAP S/4HANA as an exciting new learning opportunity. What began with a small batch of 20 videos, has now become a channel with more than 50 microlearnings that have generated over 20,000 views since then. Today we cover multiple lines of business, like Finance and Manufacturing & Supply Chain, and key technology topics like Master Data Management, Extensibility, User Experience, and Upgrade Management. We are continuously adding new microlearnings to the SAP S/4HANA channel, so make sure you check them out.
Your Voice Matters!
If you want to learn more and actively engage with SAP subject matter experts on SAP S/4HANA Cloud, join our SAP S/4HANA Cloud Community. This community brings together SAP S/4HANA Cloud customers, partners and SAP experts and has a clear mission: deliver an interactive community to engage with one another about best practices and product solutions. We invite you to explore the new SAP S/4HANA Cloud Community ‘one-stop shop’ as the central place for all resources, tools, content questions, answers and connect with experts to guide you through your SAP S/4HANA Cloud journey.
Check out the Q&A section of our community for some frequently asked questions or raise your own.
Follow us via @SAP and #SAPS4HANAValueSeries