34. Myth - Rise vs On-premises ? How to generate Stack XML for RISE Private Cloud - Maintenance Planner?

We will usually get a query on which system type needs to be selected for Rise Private Cloud Installation/Updates/Upgrades. This tick clarifies the same.

Let's have an simplest explanation and clarify Myth before knowing which option to select.

Rise Private Cloud vs Public Cloud vs On-premises Systems (includes Cloud Azure/AWS/GCP)

(Baby Answers below)

1) Public Cloud (Grow) won't have GUI. We can login directly through Fiori Launchpad only as the only interface. Deployments is entirely different in which we need to go through usual SAP Learnings and Journeys. 100% - Compatible to do quick Client PoCs, Demo, Testing Best Practices, New Innovations. 50% - Not suitable for Production Projects.

2) On-premise Systems is deploying (installing) SAP systems in our Office Premises Data Centers. We can also say Cloud Environments - Azure/GCP/AWS System (but landscape responsibility under Customer) as On-premise systems. (Just to differentiate exactly with Rise Private Cloud systems)

3) Rise Private Cloud Infrastructure on the other hand, is as same as On-Premise System. It's an Major IT boom in recent years than Public Cloud (Grow). Assume, we have installed SAP System via usual SWPM. SAP GUI logins, Fiori launchpad, Business Clients, etc., possible as same as On-premises. 

In On-premises, Customer needs to take care of Landscape and Infrastructures - Say Azure/AWS/GCP/On-premises Datacenter, OS/SAP installation, Maintenance, LVM Configs, FS Permissions, Client 000 Administration, etc.,

However, In RISE, Assume it's an Bundled Pricing package which SAP will be hosting everything from their end. Model will be same but customers doesn't need to face/maintain these Infrastructure requirements and 50% Basis Administration things since SAP owns it (for deployment and maintenance). Of course, Client needs to discuss and confirm on all Infrastructure requirements for deployment (based on their billabilities).

  

We need to raise cases for our usual technical issues.

We need to raise Service Requests for Landscape actions - such as Network, Firewall, OS, FS, Client Administrations such as Client Copies, 200+ Catalogs/Services are available.

 

Anyone can raise SR now - by seeing template definitions even Developers/Functional/BTP Architects/Near by Java Colleagues.

  

But, Who are we? 

  

The ones who tried to did those 200+ by ourselves when system it's in On-premise - Fail - Learn - Try - Fail - Fight - Success

Rise will be the future But those who worked on On-premises will drive that future. Hence, Everyone who has an good hands-on on On-premises system will definitely match up Rise Projects as well.

Myth - Rise only for S/4HANA Systems?

As I said above, Rise is just an On-premise system which landscape infrastructure will be maintained by SAP (which can be Azure, etc.,) as per Client requirement. In simple, we can conclude that SAP Systems exist on their SAP landscape and full ownership owned by SAP only.

 We can have any SAP Systems which currently in maintenance and latest version sufficient enough with full compatibility in Rise. Say - NW - GRC on HANA, NW - SLT on Sybase, S/4HANA Systems 2023,2022, Solution Manager, etc., Any Migrations (compatible path) is possible - including Lift and Shift as well - without changing DB and SAP versions.

Now, Which Option to select in Maintenance Planner?

Rise environments boom happened from S/4HANA 2025 onwards only which SAP released exclusive "Plan an SAP S/4HANA Private Cloud Upgrade" option for S/4HANA 2025. Future releases will be added as well. You can see "S4HANA 2025 Private Cloud version" version.

It will just have an S/4HANA PCE Server - S4PEXT 109 as an additional product add on - S/4HANA 2025. All others are same as On-premise system type only.

For all other S/4HANA, Other Systems - Say S/4HANA 2023, NWs, etc.,

Just create an usual Stack XML file with the correct options as mentioned below based on your requirements 

"Plan an S/4HANA Upgrade"

"Plan a Maintenance"

 "Install an S/4HANA System" - New installation
"Plan a transition to Rise" - Just an Lift and Shift 

"Plan a conversion to S/4HANA - S/4HANA 2023"

There won't be any specific PCE Cloud version for lower versions. Say - S/4HANA 2023 Private Cloud version

1) Example - "Plan an S/4HANA Upgrade" - for S/4HANA 2023 Upgrade + Rise transition

2) Example - "Plan a transition to Rise" for NW - GRC Add on System. Assume it's just an Lift and Shift Method with/without minor change.

SAP ECS/Migration team will use the Stack XML for Migration. Same applicable for Installations and other categories as well. It's as same as On-premise Only. Just Landscape and 50% basis admin activities will be under SAP responsibility.

3) Example - "Installation of S/4HANA 2023" - For New Rise Environment

No option to select - as S/4HANA Private Cloud 2023.

Just use "Install an S/4HANA System"

Note 3649125 - Cannot find "S/4HANA Private Cloud 2023" option in MP when planning upgrades vers2

Hope you liked this tick !

Please visit gadgets link and support !