Are you looking for ERP-SAP tools to be in your Enterprise?
Please call us for the best process implementation and Solution optimized in Cloud and Digitalization toolkits (AI,ML, AWS, Quantum AI).
WAYS TO USE SAP IN THE RISE MODEL
Techniques for implementing cloud computing
Depending on the customer, there are two different cloud models available for RISE with SAP S/4HANA: public and private. The system maintenance model is not the only area where the system differs; there are differences in the user interface, configuration options, system development, system upgrades, and system management, among other areas. The trajectory of a SAP S/4HANA implementation project is also affected by it.
The RISE with SAP service is intended for three types of customers: those who are already using SAP ECC, those who have SAP S/4 HANA on-premises, and those who are interested in implementing SAP. There are two cloud-based deployment alternatives available to us. S/4HANA Public Edition is a public cloud, and RISE with SAP S/4HANA Cloud Private Edition is a private cloud. Let’s examine how these options differ from one another. Firstly, let me clarify that the SAP solution offered in the on-premises model and the private cloud model are actually quite similar; to put it another way, they are both similar systems that are either locally or on the cloud.
Cloud computing: public or private
Utilize the interface(UX):
The Fiori interface is the only one accessible on the public cloud. For carrying out daily operations, it is an extremely intuitive and user-friendly interface based on selection screens, sometimes known as tiles. Similar to the on-premise solution, there are two interface choices for the private cloud. Apart from Fiori, the SAP GUI—which is recognizable to those who have used earlier SAP versions—is still accessible.
The training and readiness of end users during the go-live phase are also impacted by the accessibility of user interfaces.
Configuration:
There are significant variations in this field. Pre-configured packages chosen from the list of recommended practices serve as the foundation for the system configuration in public clouds. SAP advises based the whole configuration on the packages that are available in this instance, severely restricting the modification options. This is a huge shift that, in highly standardized organizations, may cut the realization phase and the actual implementation period considerably, depending on expectations. However, migrating to the public cloud can be extremely difficult for highly customized systems. We can further configure the system with full access to configuration settings (including SPRO transactions) in SAP Private Cloud.
Development:
Access to and modification of the programming code are heavily restricted by the S/4 Public Cloud. Using SAP-certified apps (supplied by SAP or partners) that can be bought on the SAP Business Technology Platform—a marketplace that functions similarly to the Google or App Store—is essentially the only choice for system development. Since we have complete access to the source code on the private cloud, we may develop the system to meet the needs of our clients.
System upgrade:
The public edition automatically upgrades twice a year, notifying users approximately two weeks in advance, to maintain an up-to-date environment. Although there will be forced business interruptions along this road of rapid and frequent upgrades, the upgrades are easier and less expensive because the “core” of the applications is not altered. We will also need to upgrade the private cloud version every five years to continue supporting a certain product version. The customer sets the date for system updates, but they require planning and require extra work.
Administration:
Carried done in the public cloud exclusively by SAP. You have two options for managing the private cloud: either use your own IT staff or contract with a specific company that offers the service, like All for One. It might be required to offer extra services not included in the RISE contract in both scenarios.
SAP S4 HANA 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 based on SAP Activate methodology and supplemented with many years of experience in SAP system implementation projects and elements of the agile approach.
Our approach includes six stages of system implementation.
Discovery phase
This phase needs to be phase of identification of needs/requirements. 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 SAP BTP Solutions. The goal of this 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.
Project organization (PMO)
This phase 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.
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 the basis for the configuration of the prototype in the next phase of the project.
Realization
It is the phase of the project based on 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.
Deploy phase
This phase needs to be transferring the solution from the test environment to the production environment, and user training. The scope of training and transport management differs depending on the option chosen. The culmination of this phase is going live.
Run/Post Go-live Support
This is called the post-go live support. This is the management of the system in its life cycle, i.e., updates, ongoing administration, and upgrades. This phase of the project also includes optimization of work with the SAP system based on the observation of the production operation.