Dear Reader,

Wish you have had a wonderful year with full of learning and excitements. As this year’s (2023) clock is ticketing towards the end, thought of creating this blogpost series, which will take you through the simplified steps you need to perform while onboarding S/4HANA Cloud 3 System Landscape and initial system set-ups. Hope this series will help you in some extent while you are back from vacation in coming year.

Pre-requisites : Before starting, I’m assuming that you are already familiar with S/4HANA Cloud 3SL system landscape and components. There are multiple blogposts, learning materials are available one click away, my advice would be to go through them before reading the blogpost series. If you are looking for a bit elaborated synopsis, I highly recommend to go through this learning content : Onboarding with SAP Activate for SAP S/4HANA Cloud, Public Edition | SAP Learning

Contents : Like other SAP implementations, SAP S/4HANA Cloud 3SL implementation also follows SAP Activate methodology. Hence, you will have specific project phases, where these onboarding and system set-ups should be done. I’ll not focus more into the SAP Activate phases here, rather I’ll delve deeper into the technical steps which is supposed to be followed. If you need to know about “when” then you may take a look into SAP Roadmap Viewer and liaise with your project phases Roadmap Viewer (ondemand.com).

SAP S/4HANA Cloud 3Sl primarily contains 9 different tenants/SAAS components to start with , i.e.:

1. SAP for Me : SAP for Me portal is SAP’s one-stop shop for commercial, administrative, and technical information about SAP solutions. From provisioning the tenants to getting support, it’s a customer & partner enabler.
2. SAP Central Business Configuration : SAP’s one-stop central solution which enables you to scope, configure and implement end-to-end business processes for SAP S/4HANA Cloud.
3. SAP Cloud ALM (Optional) : It enables to test, validate and demonstrate the implementation and operation functionalities provided to support the application lifecycle management. However, it’s optional for 3SL implementation and left to customers’ choices.
4. SAP Cloud Identity Services (Non-Prod) : It is a productive instance of SAP CIS which creates and manages users to all these tenants. SAP CBC, SAP S/4HANA Cloud Starter, Dev & Test tenants will be tied up with this SAP CIS tenants, that’s why we are now categorizing it as SAP CIS Non-Prod.
5. SAP S/4HANA Cloud Starter System : The sandbox system with loaded master data and best practices, which will help your exploring capabilities for Fit-to-Standard workshop.
6. SAP S/4HANA Cloud Development System : Your productive development system.
7. SAP S/4HANA Cloud Test System : Your productive test system.
8. SAP Cloud Identity Services (Prod) : SAP CIS, tied to S/4HANA Cloud Production system and the Cloud ALM.
9. SAP S/4HANA Cloud Production System : Your production system.

The overall system landscape looks this this (image source : help-sap)

Now, we can categorize the onboarding and initial config steps into following sequence :

1. Receive order confirmation mail and set-up SAP for Me.
2. Provisioning SAP Cloud ALM and do the initial set-ups on user onboarding.
3. Provisioning SAP CBC and do the initial set-ups on user onboarding.
4. Provisioning SAP S/4HANA Cloud Starter System and complete the initial set-ups on user onboarding.
5. Provisioning SAP S/4HANA Cloud Development System and complete the initial set-ups on user onboarding.
6. Provisioning SAP S/4HANA Cloud Test System and complete the initial set-ups on user onboarding.
7. Provisioning SAP S/4HANA Cloud Production System and complete the initial set-ups on user onboarding.

For 1, 2  & 3 I will create separate blogposts very soon. For 4-7 , mostly it will have similar initial set-ups, hence for it I’ll create a single blogpost mentioning the minute difference steps for all the systems if any.

(image source : help-sap)

I’ll see you with the aforementioned blogposts one after another.

Wishing you a happy holiday season till then. Cheers. 🙂