Product Information
Six Steps to Deploy SAP S/4HANA Cloud with SAP Activate
Happy New Year to all of our customers, partners and colleagues.
In this post I want to share an update about the recently recorded demo videos providing overview of the key capabilities in SAP Activate powered by SAP Cloud ALM application of Implementation Portal. It shows how the combination of prescriptive guidance, rich business process content and powerful tools work together to guide customers in deployment of SAP S/4HANA Cloud.
Few notes before we dive into the details:
- The demo is showing example on one scope item (J60 – Finance: Account Payable) for simplicity. In real deployment project customer project team would execute these steps on number of scope items and backlog items that reflect the scope of their project.
- Demo refers to different personas like Project Lead, Configurator, etc. to distinguish between the different roles participating in the project.
- The videos are shortened to provide an overview of the key capabilities, they are not intended to be full click-though and show of all the tool capabilities.
The demo script follows closely the phases of SAP Activate and focuses on key steps in the deployment of SAP S/4HANA Cloud. The overview videoprovides introduction into the demo that then follows the six steps shown in the image below.
Now let’s briefly discuss the key activities that are shown in each of the six steps:
(Step 1) Setup and Enablement – this demo shows the steps project lead takes to setup the project, define key milestones, set the initial project scope and invite the team members into the project using Implementation Portal for SAP S/4HANA Cloud (that is part of SAP Cloud ALM).
(Step 2) Fit-to-Standard Analysis – in this video you will see how the configuration expert (or alternatively business process expert) sets the detailed scope for specific business area and company by selecting scope items to be in/out of scope for the deployment project. The demo then continues with the explanation of capabilities for reviewing the rich business process content, including displaying the business process models and documentation of the pre-delivered business processes. At the end of the demo, the team captures a requirement into the backlog using the “notes” functionality in the Implementation Portal.
While the demo shows this process in a straight sequence, in reality the project teams will iterate on various scope items and will refine the scope based on the results of the fit-to-standard workshop. Proper execution of fit-to-standard workshops is critical for projects to finalize the business scope, define the configuration values, define the scope of integrations, define output management and analytics needs and more. I do recommend you to take a look at the fit-to-standard guide accelerator we provide in SAP Activate that guides you through all the steps in detail.
(Step 3) System Provisioning – in this step, the team takes the results of the fit-to-standard workshops to set the scope for provisioning, maintain key values like chart of accounts and then trigged the Q-system provisioning process. The Q-system is provisioned with customer specific scope activated and the team can start configuration activities.
(Step 4) Configuration – in this step the project team takes the backlog and uses iterative agile approach to configure the solution. The demo shows how the backlog item gets implemented into a configuration in the system. It shows the configuration expert navigating to the Manage Your SolutionApp and then using Self-Service Configuration UIs to record the desired configuration values in the Q-system.
(Step 5) Testing – in this step the configuration expert runs the pre-delivered test script with appropriate values to confirm that the configuration in the system works as desired. The pre-delivered test scripts are useful not only during the initial configuration, but also and more importantly play critical role during the regression testing after each release upgrade. SAP S/4HANA Cloud comes pre-delivered with test scripts covering the scope of the solution, which is a significant saving of effort and cost.
(Step 6) Data Migration – the last demo shows the activities project team executes to load data into the new system. The data load tool simulates the load into the system, user can check the results, make adjustments if needed, and then complete the load activities. This process is tested in Q-system and then repeated in the production environment prior to the production cutover.
I hope that this blog provides you with better understanding of the available capabilities in SAP Activate and show you how SAP Cloud ALM supports the project team in execution of the project following the SAP Activate guidance.
If you have questions or want to engage with the SAP Activate team, please post your comment either directly on this blog post or join us in the SAP Activate Jam Group where you can find more information about SAP Activate.
Reference links
To save you time, in case you wanted to keep list of these videos, below are direct links to each step of the demo:
- Overview – https://youtu.be/MHwXuFAcSAM
- Setup and Enablement – https://youtu.be/zbCbzNCI_6k
- Fit-to-Standard Analysis – https://youtu.be/9rd-jPBkuIc
- System Provisioning – https://youtu.be/q-PYZXzd0UE
- Configuration – https://youtu.be/j9oAqdNAlG4
- Testing – https://youtu.be/MEwyiKrAi7k
- Data Migration – https://youtu.be/Dr7niaS4-mI
- Recap – https://youtu.be/dOR3Ow7OBVY
Direct link to the playlist: https://www.youtube.com/playlist?list=PLWV533hWWvDkApJ2f14X6EkPN0p98tKXP
Hello Jan,
Thanks for the detailed explanation, it was very very useful to understand the process in detail.
I had a small query, we from our organisation we are planning to create a template in the S/4 public cloud system by executing the sap best practice scope items from all the line of business. So as of now we have ordered the starter system in which we can see all the master data is available which are required to execute the best practice scope items. Now we are still yet to order the quality system, but we are trying to work on the data migration part as we are not aware whether this same master will be available in the Quality system. So we are working on data migration, i.e. extracting the master data from starter system and filling the master data details in the Migration cock pit templates available.
So just wanted to confirm whether we have these basic master data which are required to execute the best practice scope items, are these master data by default present in the Quality and Production system as well?
Thank you very much!
With Kind Regards,
Raaj
Raaj,
the Q-system request is raised at the end of Explore phase and the details are listed here
After the Q-system is provisioned it is in inactive state that allows you to pre-set specific settings that influence the activation process. I recommend to review this deliverable and tasks that provide details of all these steps.
The Q-system is then activated with your selected scope items which also brings in relevant data, but the org setup and CoA will reflect your settings applied in the config activities and setup activities you do before activation.
I also recommend to look at additional configuration activities you can find here and here.
Hope this gives you a better overview of the process and steps that are involved during the provisioning and configuration of your Q-system. Note that configuration gets transported to your P-system when it you receive it and then on regular 1-2 weeks cycle.
Thanks for your detailed response Jan, it is much helpful to understand it in a better way now
You are welcome. Glad I can help.