Mastering RISE with SAP: optimising systems and compliance in your SAP transformation

But just a quick recap for our session today. So our presenter here, Daniel Parker, he's got over twenty years experience in all things SAP. We consider him our resident SAP data expert. And so you'll be in great hands with today's session. For anyone that has any questions, we will try and save some time for the end of this session to answer those questions, so feel free to throw them into the chat. If we can't get them all answered before the end of the session, we will answer them by email. The session is being recorded, and we'll share their recording as well as the slide deck through to everyone who registered after the event as well. So feel free to share those on as you see fit. You'll also be able to reply to that email if you'd like to get in touch with us, either speaking directly to Daniel, on anything technical or myself, if you have any questions as well about, about the content. So what we're gonna be talking about today is that journey, to s four HANA through Rise. Daniel has a lot of experience in these sorts of projects. It is a massive shift for organizations, not just in technology, but in how you manage, secure, and optimize your SAP environment once you're in the cloud. Daniel's gonna use today to take us through some common challenges that we're hearing from clients during that journey, from getting systems ready and managing data compliance to closing operational gaps that may arise once you're running under the RISE model. So we're at two past nine. I will hand over to Daniel to get started, and, and I'll jump back on at the end to, to let Daniel know of any questions that have come up. Over to you, Dan. Cool. Thanks, Kat. And welcome, everyone. So, yeah, as mentioned, I'm Daniel Parker, so solution architect in the region here for EPI-USE Labs. I mean, I basically look after this style of work and helping design solutions and working with our sales teams to pick the appropriate way to help our customers with our EPI-USE Labs solutions. So if you're not aware of this, EPI-USE Labs, we're a software r and d development business predominantly based around SAP solutions, but not exclusively. So today, I'm talking specifically around SAP, obviously, in a rise context. But we, you know, basically create solutions that help people manage their SAP landscapes and their SAP data around the BAU and day to day of managing SAP landscapes. And we're part of a greater group of organizations we call Group Elephant. So there's other EPI-USE businesses and other businesses within that group. And then we have a program we call ERP, which is about giving back to elephants, rhinos, and people to help save animals and list people out of poverty in Africa. So they're some of their core values in terms of what we do as a business. So today, as mentioned, we're gonna be talking about RISE or sort of the future of SAP. So, you'll be very likely aware that, SAP are wanting everyone to move to S4HANA in some manner and potentially move to a rise or a cloud hosted solution as well. So we'll talk a bit about how, yeah, common challenges and three sort of main areas that we feel areas that people should focus on around decisions and moving to that endpoint. But the key point from SAP is that regardless of your start point, they're looking for a common path and a common endpoint, which is some form of cloud posting cloud hosting in terms of your SAP landscape or SAP direction. So the key points we're gonna cover today. So we're gonna start sort of on the left here. We're gonna look at cost saving around the landscape. We're gonna look at reducing risk and also managing the contract and managing effectively once you're live in a arrive rise private hosting or private cloud scenario. So these are key areas that we see come up in terms of getting into Rise or planning the spend and the contract to put you in a Rise private cloud edition as well as the ongoing support. So I'll talk a little bit about each of those three areas. And there's two other areas as well where we can help around this space. So one is around optimization of costs related to users and risk. So there's a concept called full user equivalent around licensing. So there's a session coming up next month where our partner, Satering, is gonna talk about the details around that. So if you're not aware of how user licensing will change under S4HANA and Arise style contracts, that's a good one to join to be aware of that because that can have an impact on your business case and your planning. And then lastly, next year, early next year, we're gonna talk about an another area that we work around selective transition. So today, I'm talking more general landscape management, risk management, managing once you're in RISE. This is a more targeted conversation in terms of how you might transform or reduce a system as you go from ECC into SAP HANA. So that's the session that's coming up. Next year if you're interested. But, for today, Let's focus on those three points on the left. So we'll start with the general cost savings around a transition to into S banner and into Rise. So if you've done any planning or if you've already moved around to HANA style infrastructure. Essentially, you go from the current legacy systems. So your ECC running on a traditional database, maybe a d b two or Oracle or something like that. When you convert to HANA based architecture, the cost of running that infrastructure will go up. So this is just a kind of a fact of life in terms of that technology change. So maybe you've already gone to HANA on some of your systems, may not have gone to s four, but you've got that underlying infrastructure, and you might be feeling some of those cost pressures related to that. So this is a key area where we can sort of help reduce cost as part of that price contract. So when you go into Rise private cloud, you'll pick size points or t shirt size points for your development, your test, and your production systems. So if we've got ways of reducing those size points, we can reduce the cost. So this is where we look at cost reduction around the non production systems. So making smaller development, smaller test systems, even rebuilding the development system to better align with your production system as part of that move. So the end goal is we have smaller footprint and smaller license or contract cost in terms of the hosting on the SAP Rise side. So the way we do that is with our product suite called Data Sync Manager. So there's a main component in that called Client Sync, which allows us to do reduced client copies so we can make a smaller test system, a smaller development system. So Data Sync Manager is a solution we've been developing for well over twenty five years, Supports a range of SAP systems, and it's supported for use in Rise environments as well as on your current on premise ECC or even on premise s four. So it gives us methods to reduce systems before we move or reduce systems after we move. So it's a key tool set that our teams would use to around this kind of this point or this pain point. So what does that look like kind of practically? So if we think of a basic S4HANA landscape, you might have a production system that sits around a terabyte. So that puts you at a one terabyte t shirt size from an SAP rise contract point of view. So if you're using a traditional full database refresh as part of your landscape management and your test data management. So you're taking a full copy of production, putting it to QA. You've got a like for like size. You're gonna need to have a contract point which sets you up for a one terabyte appliance size in the QA system. So that's your spend point or your price point. And then on the development system, if you've locked in at, say, a smaller, you know, five hundred or two fifty six gigabyte style t shirt size, then you don't really have space to restore the system to it. But as always happens, a production system will grow, which means we might break out into a larger t shirt size on the production side. So that's gonna happen. That's what production does. But that basically means if we want to do a full restore to QA. We're gonna need to increase the spend on the QA side for a larger T shirt size as well for the appliance that runs the database. So over time, not only do we grow our production costs, but we grow our QA costs. So with a solution like Data Sync Manager and Client Sync, we can take a slice of the data from the source system. Which is production into QA and sit at a smaller size. So we give a consistent working test client in QA at a fraction of the size of production so it still meets all the testing goals, but you can stay at a smaller t shirt or appliance side and not grow the QA spend or the non production spend over time for the life of the RISE contract. So how we do that sort of practically? So there's a concept of slicing the data. So as we extract data from the production system to refresh elsewhere, we do a time slice. So configuration and master data come in full for the client. We take a slice by time of the transactional data, and then there's dependencies brought in as you saw there. So if there's related data outside of the time slice, we'll make it part of the copy. So the end result is configuration, master data, and a subset of transactional data which is consistent in the testing system. You can also apply this as well to an enterprise or a company code, which is sometimes useful for different types of organizations. So we can time slice again, but by a particular company code or enterprise structure. Again, include the dependent records to make a consistent set of data. And then apply that across to the target system along with the subset of master data and all the client dependent configuration. So in both scenarios, we can create a reduced system size, be that QA or development with production like data without having to grow the size of the system. So if we think of that around what typically happens in a in an s four move, we see quite a few customers might just take copies of the production system. And use that to see their SPA HANA landscape. So they take a copy of production, convert it to s four, call that development. Take another copy, convert it to s four, call that QA, and then production is the final conversion. So the end result there is you have three systems which are production size, which have a larger cost point in terms of the contract. With something like Data Sync Manager and the concepts we're talking about, we can take an initial copy of production, convert it to s four, And then from that, we can seed out a small QA system and a smaller dev system. So there's ways of copying the systems, reducing the clients. So we have smaller Size point for QA and dev, but they're all still copy from production and aligned. And then, of course, in that kind of scenario, you might do a final move, which is the final cutover of production for your go live. So that cutover and that conversion is still run by standard SAP processes, standard upgrade and conversion processes that we're using Data Sync Manager to create the reduced dev and QA systems with a smaller footprint. So that is a key way we help with quite a few customers, and quite a lot of customers might compare the cost of the solution or cost of us helping to their potential contract cost with SAP for their non production system sizes. So that's a way people think about it from a budgeting point of view and a practical way that we get involved around that style of project to help reduce the cost. Alright. I'll move on to the second point we wanted to talk a bit about today, which is reducing risk. So this is another common area that we get involved and people need help in terms of managing or discussion around the cloud move in general and also the rise move. So this is essentially looking at security of the data or anonymization of the data. So if you're not aware, SAP made some adjustments to their data processing agreements a few years ago and then now call out in different ways and different methods that basically say that you shouldn't have personal data in non production environments. So these cloud hosting data processing agreements. This is the type of agreement you'll sign when you move into a rise hosting situation for your s four environment. So effectively, there's word in there saying that if you're copying a system or SAP or refreshing a system or using something like Client Sync, the expectation is that you won't have real personal data or identifiable data in the non production environments. So SAP don't really provide any tool sets to help for that from an s for HANA context, but they have at least to know something within the process and agreement for the system. So then the question is, what do you do about that? So if you've been running SAP for a long time and you're taking that ECC system, converting it to s four, you'll have a long history of data and a lot of personally identifiable information in the environment. So typically, when we start to talk to people about this, I think of employee as the obvious place where there's identifiable information. So it's real names, so my name, your name, address, family members, telephone numbers, bank details, pay details, that type of information. But in a S4HANA context or even in a standard ECC context, we might have a vendor record which is attached to the employee. So that's replication of that data. So just thinking about the employee isn't enough. We need to think about the vendor because I may exist as a vendor in the system for payback of expense claims and other things like that. And then in an s four context, we have customer vendor business partner integration. So these things will be connected by a business partner. So, again, we're replicating that basic identifiable information. So it's now located in three business object context across the system. And then lastly, there might be a customer as well depending on how you run things or what you do. Plus, you could have external customers. Vendors might be businesses or individuals that aren't employees as well. So there's a variety of ways you can have identifiable information sitting in the system. But this is a high level context. So this is at an object level, So the employee, the vendor, customer. Underneath that, we'll have a vast range of different tables and different styles of data. So it's not uncommon to, you know, have a conversation with people saying, I just want a scrambled bank account. But when you think about that, that could be, you know, tens, twenty, thirty tables and another sixty, seventy fields across those tables. So a very simple context in terms of I just want to scramble something turns into a large footprint of potential data that might exist in the system. And you potentially wanna keep these things aligned as well. So to identify these things is one thing. But if I wanna change my employee name, I've got a business partner and then a vendor, and I've also got address records. These things are all connected. So if I'm looking to de identify or anonymize this information, I'm gonna be very aware of how it links and how it aligns within the SAP system keep it consistent and keep it valid from a testing point of view. So we're looking to de identify the data, keep it consistent, but not break it from a testing or verification or a business verification point of view when they come to do testing processes. So that's essentially sort of the trick and kind of where we need to help people. So we in this space, we have what we call a data privacy suite. So, again, this is part of Greater Data Sync Manager suite of products, something we've been developing for twenty five odd years as well. But this is focused duly around scrambling or de identification of data in a system. And the way we can approach this is essentially around test data as well as production data. There's probably a little bit less need for the production data management, which is where we have disclosed, redact, and retain. So this is de identifying data in a production system where you no longer need to hold it. But today, we're more concerned in terms of this conversation around Data Secure. So scrambling or de identifying data in a test system. So this is where we can go through that employee, customer, vendor data, and, you know, change names, change addresses, change bank accounts to de identify it and reduce the risk around it. And in both of these things, we can provide workshops and analysis to help you identify where that data is and the potential ways to manage it in your systems. So what does this kinda mean practically? So if we look at a, you know, simple little illustration over here. So across a variety of systems and even objects within the same system, we have what we call business object definitions. So I've got that defined for customer, for business partner. That employee, vendor, so forth. And then those contain all the tables and fields which relate to that set of data in an SAP system. So if I'm working with customer, the object knows about all the tables, the relationships between them, and then we can define what we call an integrity map. So the integrity map is the thing we use to apply scrambling, and it can link the field to cross objects. So if I need to change a customer name, I know how that relates back to a business partner, potentially out to a b w system, but more likely, yeah, customer to business partner to vendor within the same SAP system. So with this object model context concept of the data and the integrity map linking fields, we can say, I will change a name and apply it consistently across those datasets. And this is extensible as well. So if I had zed fields that contain PII or if I've got zed tables that contain PII, I can extend the products in the same manner to work and keep those fields aligned as well. So the end result there is we either did in file scrambler systems as we help build them in s four or the customer has a solution where every time they do a refresh, they can run a scramble on a test system and to identify themselves in the future. So it's affecting it becomes a product that you can run as needed on test systems whenever you refresh or potentially part of the refresh process with something like client sync. And yeah. And it's all about helping with that concept from the data processing agreement in terms of you should not be storing or should try to avoid storing personal data in non production environments. So this is, how we help kinda derisk or solve that risk. Alright. I'll shift gears a little bit away from the data side and the data management, a bit more into the general landscape management and sort of managing the contract and the relationship a little bit around BAU with SAP. So effectively managing the day to day of the RISE contract once you're in RISE. So RISE private cloud is essentially SaaS with a choice. So you're going to a cloud platform. You get some choice on that. You might pick the particular hyperscale you wanna put it with. But at the end of the day, it's kind of a SaaS like solution. So it's your system. It's your data. You have most control over it. But at some point in the data model or in the data layer, it becomes SAP that are managing the lower layer of the SAP system, the database, the operating system, which basically means you end up with a map, a list of roles and responsibilities between yourself and SAP. And it's best to sort of understand upfront what that means from an operational support point of view. So the cloud services agreement with SAP breaks things down into five basic categories. So there's standard services. So things that will SAP will do as part of the rise hosting contract. There's optional services. So these things you can add over time or at sign up time. So they might do it or you might do it. There's additional services. So one offs where you might ask them to do a particular thing, package services that you add in the different capabilities. And then lastly, the excluded tasks. So this is where sometimes there's a little bit of surprise for people or they're not quite ready for the workload or the effort around those excluded tasks. So it's typical roles and responsibilities type model. You know, some of it's SAP, some of it's you, some of it SAP will optionally do, some of it they won't touch at all. So it's best to try to look try and understand that gap and what it means from a BAU perspective for you. So, yeah, so we got the roles and responsibilities model. There's a link to it there at the bottom if you wanna get more detail on it. But, basically, this will go into quite a lot of detail around specific tasks. So the little screenshot there, which is probably a little bit small, but that's specifically around system copy or system refreshes. So SAP will provide you refreshes. They won't provide any of the other topics I was just talking on. So things like, you know, data reduction for a smaller system size or data scrambling. So they're not part of the package services or standard services. So if you want that style of help in terms of refresh, that's where you need to work with a third party to provide that. The other thing they exclude is a lot of the prework and the postwork. So they'll do the heavy lifting around a refresh, but the finer points of maybe repointing Yeah. Connections, reporting, RFCs, your other post processing tasks. You may be dependent on your own teams or someone else to perform that. So that's kind of one example where they're taking care of a lot of the work, but there are gaps which are more specific to how you run the system, how you manage your system that you need to be aware of in terms of roles and responsibilities. But, yeah, if you're not aware of that, this when we send the slides out later, be able to grab that link and have a look at the context and the full detail of that model. So what we've put together from an EPI-USE Labs point of view to help around this is using our tech ops or managed services team, which is a global service line focused around SAP basis, SAP technical support of systems and landscape, be that on premise or rise, and then helping cover that gap or cover that area between the SAP contract and what you might need from a BAU point of view. So it's a mix of helping around the things like an actual refresh as well as helping around incident change management advisory services, other concepts like that. So it's helping fill the gap between yourself and in SAP. So some examples of that here. So the rise contractor at a high level, things like service request management, incidents, you know, support, very low level infrastructure management. That's all taken care of by SAP. But from a managed services bridge service point of view, we can help follow-up or log or drive the service requests and the incidents provide advisory services around infrastructure. So SAP are managing the infrastructure for you in a in a SaaS or an infrastructure as a service type context that you might need technical people or technical experience to help advise them on what to do or particularly how to manage new environments or help with performance issues or management and things like that. Backup recovery start up shutdown disaster recovery. So, yeah, things like that. There will be gaps around the Doctor event or Doctor test. And again, that's where the team can come in with technical expertise around infrastructure in SAP to help manage things. The down the bottom of the page there as well around monitoring daily checks. So, again, SAP will do technical monitoring and quite a fair bit around the solution. But if you want more active things in terms of specific functional business style checks, general landscape health, batch job monitoring, that style of stuff, that's where you might need a service or some capability to do so within your teams. Yeah. Performance as well. So digging deeper into performance issues and other areas around upgrades, system copies, refreshes. So SAP will do the bulk of the work, but you will still need to drive a project and do pre and post steps testing that style of work. So, again, this is where we can help in that space. Yeah. And then you might be in a hybrid situation as well, so maybe you're taking this an ECC system into S4HANA. Private cloud. But you've still got on premise, maybe some b w or some CRM or something like that you're looking to retire in time. So this is where the teams can help as well. So they're very experienced in landscape management, technical management of systems, so they might help you with the management of those systems until such time as you retire them or move the functionality to s four. But, yeah, these are just some ideas in terms of where people typically find a bit of a gap between the reality of the rise contract day to day and their capabilities internally and what they might be trying to do from your internal support team versus where you might call on a support partner to help cover the gap. Alright. So, yeah, that's just a quick introduction in terms of those three items on the left in terms of how we can help manage around the journeys to rise, so saving cost around the actual physical size of systems in terms of the spend within your hosting contract, reducing risk around scrambling of personal data within the environments as well, the testing systems. So helping align better with cloud hosting agreements as well as, you know, taking away the risk of production data, production personally identifiable data in test systems. And then lastly, just having better coverage in terms of the gaps and the management of the day to day practicalities of the RISE contract and your teams. And as mentioned as well, there's talks coming up on those last two items. But one thing to be aware of, for each of these, we have assessments to help kind of understand how we can practically help. So if you're either in the early stages of thinking about going to RISE, going to s four, or maybe you're already in RISE, and some of these concepts would be helpful to you. We have a range of assessments which based on analyzing the content of the SAP system to help us give you some advice on how we can help with cost reduction, risk, areas we can help in terms of the landscape management, and also these other concepts on the right. So what are they practically? So it's an analysis report. It comes in a transport that we would load into your SAP systems. We typically extract a range of data from a non production environment, so maybe a QA system that's a recent production copy. What we take out is essentially row counts and technical information about the system metadata, if you like. So there's no identifiable information, nothing business related, nothing actual real data related in the extract. But from that, it gives us a view of data for Variance potential PII fields and tables without seeing the actual PII. So that can help give you some understanding or some rough costing around how the solutions can help or how you might get a space saving or what the impact of a scrambling situation on your test system might be. So, yeah, you can grab that QR code if you're interested. That'll give you a bit more information about these reports and how we go about running them and how we use them. But it's a free process. So if you're interested in the concepts, reach out from that link, and we can take you through some specific examples and how we can help in your particular environment. And the little looping video on the right there, so that is the dashboard view of the data that you get access to as well. So we extract it. We put it into our secure support portal, and it's available for you to access and drill down and look at detail on, as well as for our consultants to give you advice on how we can help. Alright. So just starting to wind up a little bit. So as mentioned, one of the other concepts on is around users and full user equivalent. So if you're not aware of that, I do encourage you to grab that link or have a look on our website for a coming webinar on the sixth of November. So our partner, Ceterian, will be talking about changes to how you use a license and full user equivalent, how you manage, calculate, and pay for licensing under a rise in an S4HANA contract. It's different. And the potential pitfalls in terms of costs and benefits is face saving in that area. So if that's not something you've been aware of in the past, I do encourage you to listen into that one because it's quite insightful. It gives you an idea for how license measurement and user changes will impact you. And then lastly, in February next year, we're still narrowing in the date, but we'll send out some advertising on that when it comes. But we'll have a session around selected data transition. So today, I've spoken more about concepts to help you once you're in Rise or to prepare a traditional landscape to go into Rise as a brownfield conversion. This conversation or the selected data transition is more about transforming or streamlining or minimizing the production system as part of the move. It's a different style of conversations, a different style of transition to s four, but it's ways we can help cut a system down by, you know, just to active company codes or reduce some legacy data as part of the cut over to S4HANA. Yeah. So that will be coming up early in February. But again, if you jump on to our website, epuselabs dot com, you'll see some information there around what we call Prism and selective donor transition and the global service line that we have relay related specifically to that style of work for S4HANA systems. Alright. I will wind it up there and hand over if there's any questions, Kat. Yeah. Thank you so much, Dan. That was a great presentation as always. With those two additional upcoming webinars, I will send links to both to everyone that registered for this via email. So that second one, it doesn't have a date yet. We should be looking in a date in the next probably early next week. I already have a landing page up for it. I think it might have a placeholder date of, like, the first of Feb. So I'll just send it out as is, and then I'll confirm once that date has been finalized for anyone interested. But as Daniel mentioned, if you're on your way to RISE, they're both highly valuable sessions. With the Saturian one coming up on the sixth of November, I've seen that one as well. And I like, I'll just say, if you don't know how the licensing will change, you really do need to attend that session because it could make a phenomenal difference to your rise in negotiations. So I would definitely attend that one. There were a couple of questions then that came in. So one here was, where do you see customers struggle most with the gap between their capabilities and the Rise support scope? Yeah. Sure. So that's kind of around that bridge approach once we you're into b BAU. I think It Because SAP are picking up a lot of the infrastructure or the base level SAP support and management, People might think they have less need for technical resources, but you do sort of still need to manage and understand what SAP are doing and drive how they're managing the underlying layer. So that seems to be the biggest space where people get tripped up a little bit. So still understanding what it means to have a large SAP system, you know, how it's put together, how it's copied, how it connects into a network, how data flows, all that style of stuff, what it means to have the underlying operating system and database. Those concepts and knowledge of that is still needed, and that often that's a bit of a gap that people don't see coming, which is really what that service is about. So it's staying connected to technical resources that can help push and interpret what SAP need to do or what they're asking from you. So, yeah, very much. It's never really around the knowledge of your own business or your own functionality. It's more around that gray area between the base infrastructure and the SAP functional. So that traditional basis area is where people get a bit tripped up. Awesome. Thanks, Dan. Hope hopefully, that answers that question. Let us know if not, if you need any more details. And then there was another one here. Can you help scramble more than the SAP test systems? We have a range of other linked non SAP and cloud systems that should also be scrambled. Yeah. Sure. So that's common. There's a couple approaches to that. So again, this is where we'll usually workshop and design upfront with you in terms of what you're trying to achieve for scrambling. A lot of customers sometimes just scrambling in the Sfour system is enough because then they can just send interfaces out. So if you scramble Sfour, that might be the center of the data model, and then you push out one time interfaces to other feeder systems, and then they essentially become scrambled. So don't underestimate The Power of That, which is where our workshop and sort of understanding what's happening in the landscape comes in. But, of course, that doesn't always happen. So often you need to align scramble, say, in s four maybe a like a SuccessFactors style system or maybe something else, Workday, what have you or a Reba or something like that. So the approaches there is sometimes we work with another partner called Data Priv, and we can do a shared key relationship between the two products. So we scramble, share the key values, and then they align the scrambling or vice versa. At the same time as well, we're extending Data Secure to get into more and more cloud systems. So it has capabilities now for SuccessFactors and Employee Central data, and then we're doing work as well around I think it's a Rebo or Iris. I've got might have the wrong term, but we're doing more work around other solutions to extend there and work on those as well. But, yeah, It's part of the design and planning. It's either working with another solution, pushing interfaces, or predetermining constant values between the two. There's a very various ways to resolve it, but that's part of the implementation process. Yeah. Awesome. Thanks. There are just two last questions here. So one here is, is Data Sync Manager supported for the for use in s a in a s four Rise PC? Yes. It is. Yeah. So it has a I think the name's changed. It used to be a works with Rise, with SAP. I think it's more a stronger name now. It's like a large certification or something. But, yeah, it's certified for S4HANA and for deployment into RISE environments as well as for use on your non your on premise ECC system or what have you as the source side. So, yep, You should stay. Awesome. And then the last one I have here is, what does a refresh using Data Sync Manager provide that full system copy included with the RISE contract can't. Okay. That's a good one. Yeah. So, I mean, the first one is data reduction. So we can help provide a smaller size test system. That's probably the key one. That's where most people are interested. The other benefits that come along with it Much, a big I'll split it out. A big reduction in post processing. So a technical person who has refreshed the database of an SAP system will then go on and have to do a whole lot of manual post processing events or activities to make that system fitting with the test environment again. So Client Sync will basically either automate or remove the need to do a lot of that work. So from a refresh point of view, you get a smaller system and pretty much no post processing effort by the technical team at the end of the process. And probably the other benefit as well is that we can integrate it with scrambling solutions as well. So as you copy the data, it's smaller. There's no post processing that can already be scrambled. So they're kind of the key things that differentiate SAP's full refresh process. Awesome. Cool. That's all the questions that I have. Thank you again, Dan. There were really clear answers. I even I followed all of that, which is good. So, hopefully, that answered everyone's questions. If there was any unanswered questions, please just let me know in reply to that email I send out as a follow-up from today. So with the things that Daniel's talked about, there were two webinars that are upcoming. I definitely think you should have a look at those. They're both gonna help you with that RISE journey. And then those are set those free assessments he mentioned as well. If anyone was interested in, in any of those, I'll just send through, a link of how you can access those as well. And as I mentioned before, you can access myself or Dan, in applying to that follow-up email, and the session will be available on our website if there's anyone that missed it or that you'd like to share it with or would like to revisit it as well as the slides. So thank you so much for your time today, guys, and, hopefully, we'll see you on our next session on the sixth of November. Hey.