Name: System Landscaping and Provisioning - SAP S/4HANA Deployment
Uploaded: 2021-2-23
Duration: 636 s
Description: SAP S/4HANA Cloud is provisioned to customers, through 3 distinct landscapes. In this video, the topology of these 3 systems, their line up along the SAP Activate phases and the quarterly upgrade process will all be explained. Understanding the upgrade process, in conjunction with the quarterly releases, is crucial in ensuring a smooth go-live process.

Share feedback

<p><u><strong>Planned maintenance of Practice Systems</strong></u></p>

Planned maintenance of Practice Systems

Why create an SAP account?

Enhance your learning experience

SAP Learning

Choose your subscription

Manage your subscription

Live Sessions

Hands-on Practice

Certification

My Learning

Ready to start learning?

<div>SAP S/4HANA Cloud is provisioned to customers, through 3 distinct       landscapes. In this video, the topology of these 3 systems, their line  up      along the SAP Activate phases and the quarterly upgrade process  will all      be explained. Understanding the upgrade process, in  conjunction with the      quarterly releases, is crucial in ensuring a  smooth go-live process.<br></div>

System Landscaping and Provisioning - SAP S/4HANA Deployment

Hi, my name is Jacob Moore and I come from the S4 HANA Cloud Delivery Group as an integration consultant with the SAP DBS organization. As a part of this video series, I will be talking to you about integration and side-by-side extensibility in the context of S4 HANA Cloud. I hope you find this information useful for your implementations. All right, so let's talk about this mindset change that we need to make from an on-premise mindset to more of a cloud mindset. And this really starts with moving from fit gap to fit to standard. So instead of filling gaps with customizations and whatnot, we really want to find a way to fit the processes to the standard set in cloud and what this allows for is number two which is continuous adoption as opposed to these big bang projects that take you know two years to complete instead we can do a quick go live in cloud and then continuously adopt as these upgrades come along which then leads to our our third point of moving away from these annual upgrades and going towards these quarterly upgrades that are mandatory to take. So working along those lines, you can get the latest innovations every quarter and really build off of those. Last and not so important to this video, but to keep in mind, is moving away from traditional licenses and moving towards more that subscription model for licensing. All right, so let's talk now about the S4HANA Cloud tenant topology, starting with the starter system, which is provisioned early on in the project in the prepare phase, and it comes with sample and demo data, so you can play around with the system and test around the system and learn how S4HANA Cloud works. It's also used during the fit to standard workshops to kind of show you what the standards are in cloud and try and fit your business processes to those. I will note that integration scenarios are limited in this system, and a very important note is that this system is temporary and is decommissioned 30 days after the quality and production systems are provisioned. Just take note of that when preparing anything in the starter system, it is only temporary. Next, we will talk about the quality system, which is provisioned right before the start of the realize phase. That's where it shifts over. This is really where you would build your integrations, do your configuration, all of that. This is your quality system, your queue system, which then is transported into production, which is the last system in the normal license that is provisioned really at the same time as the quality system. And there's really not much more to say about production. It is production. The last system over on the right here is the test system which is not included in a normal license, but you can think of it as a Q system that is not connected to any of the other systems. This is purely a test system. So it's not for productive use, but you can still use it as a queue system that doesn't transport anything to production. And as we'll talk about a little later, the upgrade cycle is timed with where the starter tenant is upgraded. All right, so now I'd like to talk about the S4 HANA Cloud systems in terms of the activate timeline. So right away in the discover phase, we have the trial system. We didn't really talk about this one. It's mainly just to understand the basics of what S4 HANA Cloud can do. It allows you to play around a little, but not too deep. Once you get to prepare and explore phases, we have the starter system where the initial setup and enablement takes place. But most importantly, those fit to standard workshops based on SAP best practices take place within the starter system. That allows us to understand what standard business processes we need to fit to in order to allow for a quick implementation, as well as the continuous adoption of new innovations that come every quarter as upgrades for S4HANA Cloud. As we move out of Explore into Realize, we provision the Q&P systems at the same time to keep the integrity between the two. And again, about the starter system, 30 days after you provision the queue system, the starter system does go away. It's a temporary system. Then you are just left with your Q&P systems moving through realize doing your configurations, migrating data, integrating other systems and doing your testing, and then moving on to go live in deploy for your QNNP systems and then continue to run your Q&P systems and accept those quarterly upgrades for S4 HANA Cloud. All right, so now I just want to outline some important pieces of the starter system. So specifically, three emails that you'll get from SAP that are super important to getting off the ground and using the starter system. So the first email includes the starter system URL and the initial user ID to log into the starter system for the first time. So this user ID is really just a technical administrator and allows you to create those business users with the administrator role that can then create more users for the starter system. It's not really required beyond that initial login, but it is a good idea to keep it safe. The second email is the password for that initial user. It's sent separately for security, but it contains that password, which you can reset if you want to. The third email is for SAP Cloud Identity, which gives you access to the Identity Authentication Service, or IAS. Really, the IT contact that is getting all these emails should be the owner of the system and maintain it. And IAS is really just the identity provider for S4 HANA Cloud. An important thing to note about the IT contact is that it may not be an actual IT person that is getting these emails. It may be someone just from the contract or the procurer responsible for S4HANA Cloud. You can change this by creating an incident with the component listed below and change that to an IT person. All right, so now let's talk about the upgrade process in S4HANA Cloud. Just to start, as a refresher, we have our quality system and our productive system, especially once the starter system has been decommissioned. Just as a point on the quality system, if you would think back to on-premise, you'd likely have a development system, a quality system and a productive system. In cloud though, we really combine that idea of development and quality systems morphed into one queue system. So when the upgrade comes through, at the beginning of the month, it goes to the quality system and their customers can test to make sure the upgrade went well, to make sure all the enhancements, hot fixes, and other innovations are working smoothly and to make sure that testing is complete before the upgrade moves on to the productive system at the end of the month. This ensures that we don't have any problems with upgrades going into productive systems. Now let's focus on the upgrade timing for S4 HANA Cloud Tenants. As I said in the last slide, the Q system is upgraded in the first weekend of the month, and the P system on the third weekend of the upgrade month. This gives you that two weeks of testing in the queue system to make sure that everything is correct and to correct any issues that may have come from that upgrade. As I said a few slides back, the starter system is upgraded on the second weekend of any given upgrade month. But if you have that test system, again, not part of the normal license, it would go in that starter system slot in the second weekend of the month. So as you can see below, there's just an example of how that's outlined for 2019 in the upgrade months of February, May, August, and November. All right, so when looking for your go-to source for information regarding system landscape and provisioning, you're really going to want to go to the activate methodology for S4HANA Cloud. You can sort specifically by technical landscapes, which should give you what you see here pictured, which sorts by the phase and gives you additional information on that starter system, initial access, queue system requesting, production system request, et cetera. All that information and some more helpful information is available in the SAP Activate Roadmap viewer.