Difference between SAP S/4HANA :Public Vs Private edition : RISE with SAP
In this blog I wish to bring out the difference involved with implementing RISE with SAP S/4HANA,private edition against RISE with SAP S/4HANA cloud(essential edition)
This blog is intended for those who have basic understanding of RISE and wish to understand a detailed difference between the public and private edition while using SAP Activate methodology.
NOTE: The images present in this blog are taken from public source => https://learning.sap.com/learning-journey/planning-strategies-for-rise-with-sap/introducing-rise-with-sap
With the Roadmap Viewer , SAP helps us to easy navigate across the SAP Activate methodology that is available for various implementation => https://go.support.sap.com/roadmapviewer/#
From the link above (can be used by anonymous user or registered user), click on “Explore all roadmaps” and choose the required road map. For us, the first 2 below is of our interest.
SAP S/4HANA Cloud, Private edition Vs SAP S/4HANA Cloud(essential)
|#||SAP S/4HANA Cloud, private edition||SAP S/4HANA Cloud(Public edition / Essential edition)|
With the private cloud, services are maintained on a private network protected by a firewall
We can build a private cloud within our own data center or use one of the Iaas – AWS,Azure,GCP,Alibaba Cloud.Private clouds offer the most security and control.
Private editions are single tenant environment where the provider runs our services in a dedicated environment
RISE with SAP S/4HANA Cloud,Private Edition and SAP S/4HANA Cloud, extended edition is offered as private cloud solution.
NOTE:SAP S/4HANA Cloud, Extended Edition provides additional capabilities for customers that require specific functionality, broader extensions, and deeper configuration capabilities in a dedicated cloud environment
With the public cloud, services are delivered to customers over a network that is open for public usage.
Public clouds offer efficiency and affordability, and are often multi-tenant – meaning the provider runs your service in a shared environment.
|How to decide between public and private cloud edition under RISE program of SAP||
Existing SAP ERP customers who has the desire to move to the cloud , does not want a complete process redesign and who wants to retain their current investment made to their existing SAP ERP system.
New customers who wants a full, extensive, ERP functionality including partner add-ons with the ability to extend and enhance as required can opt for private edition
This is designed to provide innovation and cloud value while allowing the customers to retain their investments by converting their existing systems
Existing or new customers who has the desire to move to the cloud , who is ready to start fresh with a clean system by giving up on any existing investment made on any ERP solution and is open for a process redesign
This is a choice for companies who are ready to embrace the future of ERP with a new implementation and predefined process
|SaaS – Software as a Service||This is not a SaaS product from SAP||SAP S/4HANA Cloud is a complete modern SaaS ERP solution. Other example of SAP Saas solutions are :SAP SuccessFactors, SAP Fieldglass,SAP Concur,SAP Ariba|
RISE with SAP some Core components:
a.BPI(Business Process Intelligence)
c.SAP Business Network Starter pack
BPI: SAP Best practices Explorer and Digital Discovery Assessment,SAP Process insights Discovery Report(needs data from customer’s existing ERP system),Signavio Process Manager and Collaboration hub
Tools and services: SAP Learning hub and SAP Cloud ALM, SAP Launchpad service and mobile start app, SAP Readiness Check and Custom Code Migration, SAP Enable Now
SAP Business Network Starter pack: Ariba Network,Asset Intelligence Network,Logistics Business Network
BPI:SAP Best practices Explorer and Digital Discovery Assessment
Tools and services:SAP Learning hub,SAP Enable Now and SAP Cloud ALM
SAP Business Network Starter pack:Ariba Network,Asset Intelligence Network
|Type of implementation||Brown field, Selective Data transition and Green field||Green field only.Could be a component of selective data transition|
|LoB (Line Of Business) coverage||This covers all 25 industries like SAP S/4HANA on-premise||Highly standardized business processes covering selected LoB and industry scenarios,
and a comprehensive ERP scope.In-depth coverage for professional services and component manufacturing; more
industries on road map
Customers has the ability to customize(including structural changes) and also modify the SAP source code.
Customers has full visibility and control with access to the backend of the system through the SAP GUI
Customers have full access to the on premise extensibility framework, supporting in-app and side-by-side extensions in addition to code enhancement and modifications. Expert configuration is possible with full IMG access, and the operating expense model is subscription-based.
With the public cloud solution, customizations are made through SAP Fiori apps designed to facilitate the changes like Custom Fields and Logic, Custom Business Objects.
No access to backend GUI.
Can not modify SAP source code.
For complex customizations that cannot be done through the existing Fiori apps, the SAP Business Technology Platform extension suites are readily available and easily integrated to SAP S/4HANA Cloud.
No IMG access
|Lifecycle stability||It depends on the level and type of modification that has been deviated from standard best practices||Stable|
|TCO and ROI||Comparatively higher TCO||Lowest TCO and highest ROI|
|Infrastructure provider||S/4HANA is deployed on the infrastructure provider of customer’s choice||SAP is the default infrastructure provider for SaaS solution : SAP S/4HANA Cloud|
SAP Best Practices Explorer(This has clearly defined business processes with documentation based on SAP’s many years of experience with business software and our customers)
(The Digital Discovery Assessment is used in the sales cycle to assess a customer’s requirements and match them with the best SAP S/4HANA Cloud solution to fit their needs. This occurs in the Discover phase of the SAP Activate Methodology.)
To access Digital discovery assessment, navigate to Discovery phase of SAP Road map viewer and click on related links to subscribe for the same)
SAP Best Practices explorer processes are a valuable input to help customers design their new system and are optional to activate.
SAP Best Practices for SAP S/4HANA, private edition:(Note: The Best Practices for both on-premise is same as private edition )https://rapid.sap.com/bp/#/BP_OP_ENTPR
Customers can choose when to install the latest enhancements to SAP Best practices content, provided they stay within mainstream maintenance (5 years).
The business processes selected on the Digital Discovery Assessment in discover phase are the processes that will be delivered in the new SAP S/4HANA Cloud system.
SAP Best Practices for SAP S/4HANA Cloud https://rapid.sap.com/bp/#/BP_CLD_ENTPR
SAP Best Practices enhancements are automatically pushed out to customers that have the relevant processes already active in their quality and production systems.
SAP S/4HANA Cloud, private edition follows 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.
After an yearly base release Feature Pack Stacks (FPS) are released quarterly with new non-disruptive features until the next base release is launched. After a new release, the previous release version will receive Support Pack Stacks (SPS) each quarter with only corrections (no new functionality) until the end of mainstream maintenance.
The release reference consists of the last two digits of the year and the numerical month. For example, the first release of the year 2022 in February is release 2202. A continuous feature delivery is indicated by a suffix following the release. For example, the first continuous feature delivery after release 2202 is 2202.1, then 2202.2, etc
|Tools to configure and manage S/4HANA deployments||
SAP Solution Builder is used for deploying SAP Best Practices in the private cloud. (A solution contains a set of SAP Best Practices scenarios, which are predefined process flows for a particular line of business.)
Tools to Manage the Business Processes :
1.Signavio Process Manager and SAP Process Collaboration Hub by Signavio
2.SAP Solution Manager(Customer-specific content and supporting documentation is created and maintained in Solution Documentation)
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).
3.Use only the Implementation Guide (IMG) to configure your system.
|SAP Central Business Configuration supports the system provisioning and configuration of RISE with SAP S/4HANA Cloud (formerly SAP S/4HANA Cloud, essentials edition).|
|Tools to transport configuration and extension till production||
To assign extension items to software packages and transport requests:
“SAP Fiori Register Extensions for Transport app”: ”
To create software packages:
“Configure Software Packages app”, or in the backend in transactionObject Navigator (SE80) or in transaction Package Builder (SE21).
To create Transport requests and tasks: “Configure Software Packages app, or in the backend with transaction Transport Organizer (SE09). ”
Note:Content activation and/or customizing takes place in the development system, then transports are released to the quality system. After thorough testing in the quality system, transports are released to the production system.
To deploy configuration to QA and PROD: SAP Central Business Configuration
To transport extensions , business objects and business logic:“Export and Import Software Collection apps”.
To transport extensions:
Add the extensions to be transported to a package in the “Export Software Collection app”. The transport will run on a scheduled job that night by default, or can be pushed immediately.
In the production system, the “Import Software Collection app” is used to apply the extensions to the system.
|SAP PO integration||
SAP Process Orchestration integrations are defined with the Advanced Adapter Engine Extended (AEX) in SAP NetWeaver. AEX provides the connectivity capabilities of the Advanced Adapter Engine (AAE) in addition to design and configuration tools (ES Repository and the Integration Directory) to set up integration scenarios.
Not available because AEX is accessed via the SAP GUI.With public cloud we do not get access to GUI
Data Migration options for new implementation using “Migrate Your Data-Migration Cockpit”:
S/4HANA Migration cockpit supports customers in migrating their data to SAP S/4HANA.
-New Implementation: This tool is used to migrate all data from legacy system(s) to the target SAP S/4HANA system
-System conversion: SUM tool is used to migrate SAP ERP to S/4HANA. However there may be data in other legacy system(s) that needs to be migrated to the target SAP S/4HANA system. The Migration Cockpit is relevant in this scenario
Below are the ways to migrate legacy data to S/4HANA Cloud, private edition using migration cockpit
1.Migrate data using staging tables (divided into two approaches)
a.Transfer data using template files (Local SAP S/4HANA Database Schema connection)
b.Transfer data using separate HANA staging database (Remote SAP HANA Database Schema connection)
2.Migrate data directly from SAP system
|Below are the ways to migrate legacy data to S/4HANA Cloud using migration cockpit
1.Transfer data using template files (Local SAP S/4HANA Database Schema connection)2.Transfer data using separate HANA staging database (Remote SAP HANA Database Schema connection
|Available system landscapes for S/4HANA Deployment
Implementation landscapes consists of 2 system or 3 system landscape
1..EML(Enterprise management layer)
2.SAP S/4HANA Fully Activated Appliance
|Trail system:(Temporary system)
Implementation landscape on S/4HANA Cloud: :
1.SAP Cloud Identity Services: Runs on BTP and consists of 2 separate tenants:1.Identity authentication 2.Identity Provisioning
2.SAP Central Business Configuration: Separate tenant that runs on BTP and hels with provisioning Starter , QA and PROD system
3.Starter system: This has preconfigured business processes and master data and is useful for delivering “Fit-to-Standard” workshop to the customers. After consultants move onto configuring the Quality and Production systems, the Starter system can be decommissioned.
4.Quality:The Quality system provisioned and configured via CBC(Central business configuration) based on the data and requirements gathered during the Fit-to-Standard workshops. The implementation team should transport configurations to the quality system in weekly or bi-weekly sprints, followed by thorough testing of configured processes.
5.Production:The Production system is provisioned via CBC and kept in sync with the Quality system via weekly or bi-weekly transports. After configurations have been made in CBC, transported to quality and tested thoroughly, the configurations can be released to the production system via CBC.
|Responsibility and Governance|