The RISE with SAP offering is dedicated to existing SAP ECC customers, to customers who already have SAP S/4 HANA but in the on-premise version, and to new customers interested in implementing SAP. We have two implementation options to choose from – both cloud-based. One is a private cloud, i.e. RISE with SAP S/4HANA Cloud Private Edition, and the other is a public cloud – S/4HANA Public Edition.

Let’s take a look at the differences between these options. To begin with, let’s point out that the solution proposed by SAP in the Private Cloud model and the on-premise approach are in fact very similar – in simple terms, in both cases it is a similar system, located either in the cloud or locally.

Public or private cloud

Use interface. In the public cloud, only the Fiori interface is available. Based on selection screens, so called tiles, it is a very intuitive, user-friendly environment for performing daily tasks. In the private cloud, as in the on-premise solution, we have two interface options available. In addition to Fiori, the SAP GUI (well known to users from previous SAP versions) is still available.

The availability of user interfaces also affects training and preparation of end users in the preparation for go live phase.

Configuration. The differences in this area are considerable. In the public cloud, the system configuration starts with pre-configured packages selected from the list of best practices. In this case, SAP quite strongly limits the customization options and suggests basing the entire configuration on the available packages. This is a very big change and, depending on expectations, in enterprises with high standardization, it can significantly shorten the duration of the realization phase and the implementation itself, however for systems with a high level of customization, adapting to the public cloud can be a real challenge.

In SAP Private Cloud, we have full access to configuration options (access to SPRO transactions), which allows us to better customize the system.

Development. S/4 Public Cloud severely restricts access to the programming code and the ability to modify it. Virtually the only option for system development it to use SAP-certified applications (provided by SAP or partners), which can be purchased on the SAP Business Technology Platform (which works similar to the Google Store or App Store). In the private cloud, we have full access to the source code, which allows us to develop the system according to customer requirements.

System upgrade. In the public version, to keep the environment up-to-date, upgrades are made twice a year automatically, and customers are notified about two weeks in advance. This path of fast and frequent upgrades will mean business interruptions at an imposed time, but due to the lack of modifications to the “core" of applications, upgrades are simpler and cheaper.

In the private cloud version, we will also be obliged to perform an upgrade to maintain support for a specific product version (every 5 years). It is the customer who decides on the date of system updates, however they require preparations and take more effort.

Administration. Carried out entirely by SAP in the public cloud. In the private cloud – you can rely on your own IT or outsource the administration to a selected provider of such a service, e.g. All for One. In both approaches, it may be necessary to provide additional services not covered by the RISE contract.

System implementation

For the private cloud offering, SAP published a version of the SAP Activate methodology adapted to the implementation of a private cloud.

All For One carries out implementations on the basis of SAP Activate methodology and supplemented with many years’ experience in SAP system implementation projects and elements of the agile approach.

Our approach includes six stages of system implementation.

  1. Discovery phase – identification of needs. At this stage, the implementation strategies, scope, schedule and budget of the project are defined. Meetings are held to determine the functional requirements for the system. In the case of migration to S/4HANA from a previous SAP version, it is necessary to analyze the current configuration and extensions. We use tools offered by SAP, such as Readiness Check, Custom Code Analyzer and SNP CrystalBridge. The goal of the phase is to better understand the current system and identify necessary changes. One of the decisions to be made is whether to choose a public or private cloud.
  2. Project organization is a phase in which, regardless of the model chosen, the target organizational structure of the project is established and the division of roles is defined. Regulations and other project plans and standards are developed. Activities in this phase engage primarily project managers on the part of the customer and All for One.
  3. Explore phase, i.e. conceptual design. An “Implementation Concept” is developed, describing the organizational structure and how it is modeled in the SAP system, data structures, real business functions and processes, interfaces, reports, forms and other extensions of the standard functionality. A description of the required technical infrastructure is created and a test and development system is prepared. It is a basis for the configuration of the prototype in the next phase of the project.
  4. Realization, i.e. on the basis of the prepared concept, the so-called system prototype is built and then tested in the test environment – the course of this phase depends on the configuration and development capabilities available in the private or public cloud. The phase ends with the approval of the system prototype.
  5. Deploy phase, i.e. transferring the solution from the test environment to the production environment, and user training. The scope of training and transport management differ depending on the option chosen. The culmination of this phase is go live.
  6. Run, i.e. post-go live support. Generally speaking, this is the management of the system in its life cycle, i.e. updates, ongoing administration, upgrades. This phase of the project also includes optimization of work with the SAP system based on the observation of the production operation.

SAP Best Practices

To make S/4 implementation easier and faster, the software manufacturer is investing in SAP Best Practices. Available to customers and partners, the Fully Activated Appliance platform allows them to check what the system looks like and how it works. It provides pre-configured business processes, users and initial test scenarios.

To make S/4 implementation easier and faster, the software manufacturer is investing in SAP Best Practices. Available to customers and partners, SAP’s Fully Activated Appliance test platform enables them to log on to the platform to see what process execution in the system can look like.

The platform includes all modules, as well as content for all 43 countries where SAP is available. Unfortunately, the test scenarios for Poland were prepared only in English.

When choosing a system, a company’s well identified business needs, its development plans, the level of advancement and adjustment of the previously used solution should come first. An experienced implementation partner will not only guide the company through the project of implementing and launching the system, but can also help in the process of identifying needs, choosing the optimal solution and its maintenance model.

The decision on whether to choose a public or private cloud (or perhaps still an on-premise model) has far-reaching consequences for the business, and should be based on well-thought-out arguments.