This blog is summarized to have a basic understanding of RISE with SAP, and wish to have a difference between the public and private editions. This is not an elaborated version, shorten for a quick glance only, not all the differentiation is stated, you may reach out to me for more…
The SAP S/4HANA Cloud Private Edition can build in one of the Landscape As-A-Service (laas) like AWS, Azure, GCP, or similar our own cloud. The SAP S/4HANA Public Cloud is a multi-tenant (the cloud provider runs on your service in a shared environment) that provides the services over a network for a public usage
SAP S/4HANA Cloud, private edition – The existing customer want to keep their existing process, data and business as usual in the cloud, you may migrate the existing environment to the Private Cloud. SAP S/4HANA Public Cloud – The existing or new customers who have the desire to move to the cloud, and is ready to start fresh with a clean system. This is like Software-As-A-Service (SAAS)
SAP S/4HANA Cloud, private edition – Implementation can be Brownfield, Greenfield or Selective data transition possible. In SAP S/4HANA Public Cloud only Greenfield implementation
SAP S/4HANA Cloud, private edition – This covers all 25 industries like SAP S/4HANA on-premise. SAP S/4HANA Public Cloud edition – Standard Business process covering Line Of Business (LoB) and industry scenarios only. Professional services and component manufacturing are in place more will be coming soon.
SAP S/4HANA Cloud, private edition – Customer could customization, source code change, structural change and access through SAP GUI possible, similar to on-premises. SAP S/4HANA Public Cloud edition – Customizations via SAP Fiori apps designed to facilitate the changes like Custom Fields and Logic, Custom Business Objects. No access to backend GUI. Cannot modify SAP source code.
SAP S/4HANA Cloud, private edition – Higher TOC. SAP S/4HANA Public Cloud edition – Lowest TOC and Higher ROI
SAP S/4HANA Cloud, private edition – The Best Practices for both on-premise is the same as the private edition. SAP S/4HANA Public Cloud edition – The business processes selected on the Digital Discovery Assessment in the discovery phase are the processes that will be delivered in the new SAP S/4HANA Cloud system.
SAP S/4HANA Cloud, private edition – Release strategies follow the annual base release of SAP S/4HANA On-Premise, however, there is a requirement to install at least one upgrade every five years to stay within mainstream maintenance.
SAP S/4HANA Public Cloud edition – Release strategies follow Two major releases per year and Provide enhancements to existing functionality. Enhancements to a customer’s existing scope are automatically installed by SAP.
SAP S/4HANA Cloud, private edition – Different methods of Configuring SAP S/4HANA:
1. Use SAP Activate Methodology and SAP Best Practices content.
2. Use SAP Activate Methodology and SAP Best Practices content as templates for your system configuration, then make changes using the Implementation Guide (IMG)
Pic Source: SAP Site
3. Use only the Implementation Guide (IMG) to configure your system.
SAP S/4HANA Public Cloud edition – SAP Central Business Configuration supports the system provisioning and configuration of RISE with SAP S/4HANA Cloud
SAP S/4HANA Cloud, private edition – Tools to transport configuration and extension to QA ad Production similar method of using STMS concept.
SAP S/4HANA Public Cloud edition – To deploy the configuration to QA and PROD: SAP Central Business Configuration. To transport extensions, business objects and business logic:“Export and Import Software Collection apps”.
Sreenivas Kurup, CTO (TDI APJ Pte Ltd) is an SAP technical background, especially in SAP infrastructure Migrations. As a certified Migration Consultant having 25 yrs of experience in SAP technologies able to advise and enable your migration and requirements.
0 Comments