1. SAP S/4HANA Maintenance with Focus on
Cloud Testing
Rajashekar Reddy , Senior Quality Specialist
SAP Labs India Private Limited

2. Abstract
This topic will deal with a new and unique maintenance concept designed and executed for SAP Strategic pursuit on Cloud as compared with maintenance process in On-Premise environment.
The objective is to introduce the audience to the following,
What is Hot fix, Why Hot fix should be Implemented in Cloud Infrastructure, Why not a Note?
Different stakeholders involved in Hot fix Creation.
Hot Fix Governance: End-to-End Hot fix Creation Process.
What are the Delivery Channels to Release Hot fix to Host in Cloud?
Best Practices in Cloud testing to ensure successful delivery of Hotfix Collection

3. SAP S/4HANA Maintenance
SAP S/4HANA is a hybrid solution with one development system for SAP S/4HANA Cloud and SAP S/4HANA On Premise
Out of the sINFINITY system we deliver every quarter a Cloud version
Out of the sINFINITY system we deliver every year an On-Premise version
The cloud system landscape is dynamic and the transport supply will change every 1-2 months due to quarterly Cloud Shipments.

4. About Hotfix Multi-Tenancy Compliant Mass Enabled Standardized
Multi-tenancy is an architecture in which a single instance of a software application serves multiple customers.
Each Customer is called as Tenant
Mass Enabled
In an on-demand environment, corrections are delivered to all the systems irrespective of whether all customers face the issue or not.
Standardized
Shall not Produce any Side effects
Shall be Quickly deployed without business downtime
Must not Damage Customer Business

5. Roles Developer MAO Test Engineer Hotfix Governance
Process Incidents & creates Corrections
MAO
Approves & Supervise Corrections
Guides Developers
Test Engineer
Tests Corrections to Ensure Quality
Hotfix Governance
Responsible for all processes till deployment

6. Hotfix Process Request created by developer To be approved by MAO
Ready for Delivery
Tested OK
Final Double Check by MAO
Implements Correction
Request approved by MAO
To be approved by MAO
Request created by developer
Hotfix Process

7. Delivery Channels Bi-Weekly Hotfix Collection Verification Patch
Once every two weeks, a new hotfix Collection is produced.
This Hotfix Collection will then be tested for a week.
Once a positive release decision is provided at the end of the week of testing, then the Hotfix Collection is released to hosting who will deploy this to customer systems.
Bi-Weekly Hotfix Collection
If a severe regression is reported during the week of testing, then a verification correction and subsequently verification patch is produced and imported into the testing system.
At the end of the week of testing, both the Hotfix Collection and the verification patches are released to hosting if a positive release decision is taken.
Verification Patch
If a single customer faces a Critical Issue, then emergency corrections and subsequently emergency patches are produced which can be deployed onto the specific customer systems.
Ad-hoc Emergency Patch

8. Best Practices in Cloud testing to ensure successful delivery of Hotfix Collection
Hotfix Collection Tests & Verification Patch Tests
Inbound Qualification Tests
Daily Regression Tests

9. Author Biography
Rajashekar Reddy working as Senior Quality specialist in SAP Labs India Private Limited Since August 2006 has 14 years of experience in testing SRM , Insurance, S4HANA & Procure Topics, worked as Test Engineer, Scrum Master, Core hotfix Governance team member

10. Thank You!!!