Give your SAP projects agility with on-demand test data

Hello, everyone, and welcome to our session on how partners can enable your clients to access exactly what they need independently, securely, and on demand. So we'll be talking about data copying. I'm Marielle from the global marketing team here at EPI- Labs, and we're really, really happy that you have allotted some of your time to see that, presentation that we have. And just a few reminders before we dive into our topic, this session is recorded, and we'll be sharing it to you via a follow-up email. If you have any questions, please feel free to send it. And you'll see on the left side of your screen, you can send those over there, and we'll be addressing them at the end as long as we do have enough time. And if we don't have enough time, we'll be answering them via email. Now I'm happy to introduce our esteemed speaker for today, Mubin Khan, our regional architect for Europe, Africa, and the Middle East here at Euse Labs. Over to you, Mubin. Thank you, Mariel. Good morning, good afternoon, good evening, wherever you are, in the world. I'm delighted, to welcome you, to this webinar where I'll be discussing, about specifically, about our object sync, solution, who I'm sure many of you are familiar with. I'm sure you have a lot of, clients, that you currently work with who are utilizing our solutions today. And in mind, you may feel, that they're utilizing our solutions very, very quickly, but there may be opportunities, for them also to look at the object sync solution specifically, particularly as we're seeing an uplift, of many clients moving to more of an agile way of working, which essentially means that they need their test data far, far quicker and far, far more efficiently, to service, the different types, of testing requirements. Well, I just wanna sort of introduce, everybody too, and I'm sure, that this is all very, very familiar to you. It's kinda really taking a step back. And one of the things that we've always seen, is that the SAP life cycle is very, very data thirsty. And I'm sure, as you're talking to many of your clients, having good test data is now becoming more and more of a challenge, and is also incredibly more paramount, than it has been today. And if we step through, each of these individual challenges right from the point of when you're implementing and you go live with SAP, obviously, the world changes significantly. And that also changes the landscapes and the dynamics, of your entire, SAP environment. So right to the extent of adhering to privacy laws, and we saw, several years ago, we saw the inclusion or the introduction of the GDPR legislation in Europe, and that also has manifested to similar legislations in some of the other regions, like the US, like the Middle East, like Asia, and also Africa. We're also seeing continuous challenges with the production system growing as well. So, again, as you're talking to many of your clients, they may be acquiring, new businesses. They're working at a very, very fast pace. And what that essentially means, that exacerbates and creates a significant growth, to your production environment. And that also then has inherent challenges to when you're thinking about doing, system refreshes. You've also got the continuous innovation. So you want to keep continuously to apply support packs or whether that's, in the guises of whether you're trying to take advantage of new features and new functionality or you're making sure you want to ensure that you're keeping your environments updated from a security patching perspective. And, obviously, as part of that process, you also need to ensure that you've got good test data so that you can do end to end testing correctly. You need to be creating training systems. Obviously, training is also getting more and more important for some of your key users. In order to do that, you need to have a very, very agile and very effective process in so far as how you can get good training data into your environment. You've got challenges around testing new developments. Often that requires, good test data because if you have data that is old, that is deprecated, that has implications in terms of how robust those need of adapt developments will be once they land into the new production environment. And you've got the ongoing challenges of new projects, mergers, and acquisitions. We're seeing lots certainly post the COVID era. We're seeing lots of challenges with, businesses getting acquired or businesses getting divested. And what that essentially means is that, again, it requires the need of having good test data and test data to test with to make sure that those projects can go live without minimal risk. You've also got the adoption of cloud. So cloud strategies come into the mix. So we're seeing a massive uplift of clients now starting to move, into hyperscale as well as moving into the cloud, whether that's Azure, whether that's AWS, whether that's GCP. And, again, as part of that migration, it also requires the ability, to also make sure, that you're able to refresh your environments consistently and effectively. Upgrade testing. Testing APIs, and s four eyes. In terms of upgrade testing, again, that sort of current size very much with when you're applying support packs. Obviously, when you're doing major upgrades, when you go into a new enhancement pack or you go into a new release of SAP, often that introduces, new features, new functionality, which also needs to be tested. But you may not want to test every single, but you may not want to do a full end to end test or to or to do a setup of all of the, or to do a testing of all of the environment. You may only want to target certain areas, and this is where the object sync solution can support with that. Or you may want to think about sunsetting your, ERP system. Now, obviously, sunsetting of the ERP system, is something very important to understand. It doesn't necessarily, align, to this, webinar that we're talking about today. But I think the point being from this particularly, from this particular slide insofar as we can see how data thirsty, the SAP, the SAP landscape is. In terms of our, in terms of our product suite, I'm sure this is, very, very familiar to all of you, but I think it's just, obviously, just to give you a refresher insofar as some of the recent changes that we've introduced. And, obviously, you know, the core components that you've probably seen are our system builder shell sync component, which is very much used to build what we call shell systems. So in a scenario where, you want to spin up a new environment, whether that's for, testing purposes or whether that's for project purposes, to service a new project engagement, and then you then supplement that system, or that shell system, sorry, with data, from client sync. And when we say data, from client sync, that usually tends to be your client dependent data. So that's taking, some of your client dependent customizing, taking all of your master data and a subset, of your transactional data, as well as the history. And, obviously, there is a semi there is semi automated capability which optimizes a lot of the post processing activities that typically, take a lot of time and effort and manual overhead. We also have the data secure solution, which is a solution which is used, utilized very much for doing data anonymization, data scrambling, or data masking. Notice that I've used those words or those phrases interchangeably, but essentially, that it means the same thing. And what we're doing here is that we're anonymizing sensitive PII data so to ensure that no, sensitive data is exposed during that data copy back process. And then the solution that we'll be focusing on in this webinar is really object sync. So it's really making sure that rather than doing the full client refresh, how could then I sub how can I then supplement my test environment to make sure that I only get the test data or the subset of data that I need to fulfill that specific scenario? So whether that's in the context of training, whether that's in the context of BAU. Yeah. The object extractor solution is something that we introduced very, very recently and is very much used in the context to support, data migration. So whether that's going from, ECC, to s four or whether that's also in the context of test automation where we can use the object extractor, to then orchestrate, your test automation scripts, whether that's through Worksop, or whether that's through TriTEST Tricentis. In this slide over here, again, this kind of just further details out what I, sort of, highlighted in the previous, slide is very much, an outline, of the core components. And, obviously, we've introduced object extractor, but I wanna really target object sync. And you'll see here on the left hand side where you've got, your ECC production environment, which is essentially, the makeup, of your client, independent data, which is your shell system, which is this over here. And then on top of that, you'll see sort of this block over here, which is sort of divided into three areas, which is really, a breakout of the client, independent data. So you'll see the red over here, which references your reput your client dependent data. You'll then have your, your, light blue here, which represents your master data. And then what you'll have here in dark blue, is your transactional data. And you'll see over here is that for objects synced specifically, your master data and subset, of your transactional data selectively, to then, effectively, copy that from a source environment into a target environment. So we can take subsets of that transactional data. We can take subsets of that master data, take it from a source environment, and load it into a target environment. And you'll see there that we have over one thousand objects which are applicable to ERP, CRM, BW, SRM, etcetera. The other thing to call out here, it's highly extensible, and we appreciate that as you've seen in many of your clients, that they will have very, very highly customized solutions. And what we can quite easily do with object sync is that we can integrate those customizations into the product itself to support those specific test cases or those dependencies. We've got then got the object extractor, which works in a slightly different way. But, again, what we are doing is that we are selectively taking areas of the master data, of the transactional data, and also the client dependent customizing to support those test data requirements, to support test data automation. So whether they're whether you might be using things like Worksoft scripts, to do specific, automated testing or whether using scripts through Tricentis, this is where we can use object extractor to bring that data back that you need to fulfill those specific test cases where you are using, Worksoft or Tricentis. Then you'll see that client sync and data secure, which I'm sure many of your clients are using today, where they're using client sync to do subsets, of data copying. So they'll be taking a very, very small subset of data and that they may take one years of data or two years of data or six months of data plus the history, and then they'll do a system or a client they'll do a client refresh. And when they do the client refresh, then they will then use the data secure solution to then do in place scrambling of sensitive data. And then in the final product suite we have, is that we have the system builder in shell sync. And as I said, we typically use that in scenarios where, you either need to build a new shell environment. So that could be used in the context of, that could be used in the context of, in a situation or in a scenario where you're building a project environment and you need to bring back a subset of data. You may want to only bring back, say, selectively, selective company code data, or you may only want to bring back, say, twelve months of data or two years of history. Object sync. Now, really, what I wanna tailor, this, this discussion on or this webinar on is object sync itself. And those are really the key bullet points. So if you think about a scenario where you'll have a client that's running, your client sync very, very, maturely today, they'll have a process where they might be doing, refreshes on a quarterly basis. They'll be taking a subset of data, and they're going through a repeated process, where they're doing these refreshes. But, obviously, they're doing that as, like, in certain cycles. And they might come across a situation, where they actually, they may come across a situation where they want to replicate a production issue, but they don't have the test data specifically to replicate that particular scenario. And this is really where object sync comes into the mix. It might come into a situation where, you might be doing an upgrade project. And, again, you might have some specific areas where you know where you know are going to be impacted by the upgrade. And, again, you may want to only bring back a small subset of data. So that could be bringing back maybe a couple of sales orders. It may be bringing back a couple of customers. It might be bringing back a couple of materials to test those specific test scenarios, and that's where object sync comes into the mix. And what you can see here that it's a it's really a method of where you can get real data in QA to test solutions properly so I can get the data essentially in real time. So it's also the ability, to, go to a faster correction process for production support. So in situations that have highlighted for BAU in the context of BAU where you may have where you're not able to replicate the production, where you're not able to replicate the scenario in your test environment. This is really where object sync will come into the list. On top of all of that, we're also fulfilling all the security requirements similar to how two clients are running client sync today, where they're doing client sync and running data secure in parallel, where they're doing anonymization. We are also doing the same thing with object sync where we can do in place masking. It's incredibly flexible. So we can selectively, copy specific transactions related to the master data from the multiple modules. So whether that's sales orders, whether that's deliveries, whether that's accounting documents, whether that's just customers, vendors, or business partners, We've built all of that logic, and all of the dependencies, to cater for those specific transactions or specific, areas of master payer. And most of all, it gives the end users the control and power to get the data that you need. So in this context here, really, we're talking about the functional users. So rather than the functional user having to rely on the technical teams to do it to be doing more frequent, client refreshes, functional teams and the test teams can actually use object sync to do those copy copybacks of data selectable. Really, the core valid value propositions for you as partners as you're talking to some of our clients are only sort of three areas. I think the first one is the most pertinent. It's really around fast test testing cycles. So as I said, you would use client sync and object sync, independently, and they work together. So client sync object sync essentially supplements client sync. So here, you could easily synchronize real production data quickly to accelerate defect resolution and testing. So rather than having to do a full client refresh to get the data that you need, rather than going through that manual effort in terms of recreating that test dates from the target environment, we can actually use object sync to synchronize specifically or selectively the data or the production data quickly to accelerate the defect resolution and testing. It also allows the ability to improve data privacy and compliance. And seeing it as though we are obviously bringing production data, it's highly likely there'll be p I the PII data in the production data that we are bringing into that target environment. And the fact that we can do that in place masking, it minimizes the risk of any sensitive data exposure. The final point is better quality in nonproduction environments, so it eliminates the task failures due to missing or inconsistent data. And, obviously, that's really, really important because, obviously, from a break fix payer perspective, you need to make sure that you can test that. You can get the data back into the test environment very, very quickly, very, very efficiently. You can do all the testing very, very quickly and very, very efficiently, and then you can then make sure that you can get that change into your corruption environment very, very quickly and very, very efficiently. And, obviously, that brings agility into your change management process as well because it limits the volume of transports that you have to create. It limits the volume of manual efforts like that you have to undergo in order to get that test data created. Some of the core business benefits of object sync. As I said, they're sort of, these are the kind of the key, the key areas, and I've already sort of highlighted those. But I think it's worthwhile just summarizing them just for you as partners as you're talking, to certainly some of your clients. I'm sure, they will have these types of challenges. And I think the first and foremost, as I've talked about, is production support issues. How many times do we come across situations where clients have done a refresh, but then very, very quickly a few weeks after that point? So it might be a situation, where they've gone light with a major project, and they've ended up in a situation where they've got an issue now in their production environment, and they need to now, be able to replicate that problem, in their test environment. And this is where they can use object syncs. Rather than having to go through the process of doing another client refresh, they can use object syncs. So it might be the case of where, you know, the client is having a particular issue in terms of creating a sales order or posting a delivery or posting an accounting document or creating a delivery document. Whatever it may be, they can use object sync to selectively copy that data back from the source, to the target. Testing specific development. So it might be the case where and it could be a scenario where you've got a large, organizations that were launched a specific brand. Certainly, previously, in my experience, there would always be situations where, particularly in the manufacturing business, where they're launching new brands and new markets all the time. And, again, that would require it would require configuration. And, again, this is a scenario where you could bring back the data selectively. So that could be a certain part of master data, not necessarily transactional data, but it could be master data that they want to bring back, certain customer data, vendor data that they could then use to then create the transactional data to support those to support that development. Training environment. Again, you know, it seems that we've seen many situations where I'm sure that your key users or your key clients will have situations where they'd have to do lots and lots of training. Obviously, you know, we're seeing requirements where certain processes are moving now, into different markets, into different regions, and that requires doing training more frequently. And in order for in order to do the training, it requires, having, the right data in order to do it. And often that data needs to be created manually. And what we can do with object sync is that we can reuse the data that gets created without having to manually, go through the process of creating that test data because we've got the ability to create a file, of the data that can be that can then be reimported. Support pack and upgrade testing. And we know the challenges here that, you know, go through that. The support pack, has to you have to apply support packs on an annual basis and you have to then do major upgrades, at certain points in time. And, obviously, now that is obviously in the context of pre s four, but certainly in the context of s four for so in certainly in the context of s four, whether that's doing, you know, support pack testing or whether that's doing feature pack testing. So when you're testing new features, again, rather than doing a client refresh, I can use object sync to do that. So I can look at the implications. So for instance, I might want to buy bring back a selectively a small subset of data from my source, ECC environment that might be on the HP seven to my target that's on the HP eight. And then I just wanna make sure that there's no implications of that process, of that business process when I do the upgrade. And that's another great thing with ObjectSync, but it's not dependent on the it's completely agnostic to the SAP version or the SAP software level. Working objects and kelp. And, again, this is very, very pertinent for your, for your clients as well. So as you're talking about, it's really about three key areas. About system refresh projects, so, obviously, there'll be situations or I'm pretty certain that all of your clients will have very, very robust, refresh cycles, whether that's in a biannual, whether that's just once a year, or whether that's doing it every quarterly. But object sync has the ability to rather than doing a full client refresh, you can then use object sync as a safe haven to do, very, very, to bring back small subsets of data to support individual scenarios. And that sort of feeds into point two and point three is to support your DevOps teams. And this is one of the great things about object sync is the fact that it allows you to provision the data on the demand. So whether that's to test a specific transport. So I talked about there might be certain projects, that, that are associated to a transport and you need to get the data to test those projects, that's where ObjectSync comes into the mist. Or it might be bug fixes or enhancements. And this is the other point that I called out, at the start of the presentation where we're seeing clients moving to more of an agile way of working. And rather than doing more fraud or free frequent client refreshes, I may only need to just use, object sync to bring back very, very small subset of data to support the DevOps, to support your DevOps teams. And the final thing is user acceptance testing. And, obviously, as you're going through and doing those testing, whether that's doing any bug fixes or whether that's doing any smaller projects or smaller enhancements or whether that's trying to do some support packet testing, it makes sure it ensures, that you've got good, accurate test data that's production like so that your testers and your business teams can be very, very confident that as those projects, as many projects or those changes land to a production environment, that they can be very, very confident that those changes can work, as expected. That kinda concludes, my presentation, and I'd like to sort of go into a demo, just to show you how intuitive, the object sync solution is. And you'll notice, that is very, very similar or exactly the same insofar as how we utilize, all of our solutions. And this will then hopefully engage, how we can or how you can then, you know, talk to your clients in so far as they're great. They're using client sync very, very effectively and very efficiently today. They're also using objects that are using data secure, sorry, to do the anonymization in tandem with their client sync refreshes. And now as I've spoke spoken about those areas around, you know, how can I get the test data, how can I get small subsets of test data without having to do a full refresh so that I can test, BAU fixes or where I can test a smaller project engagement? So I'm just gonna share my screen over here. So what I'm going to basically show you here is just a very, very simple example, on how we can take some master data, and some transactional data from a source environment and through to a target environment. And notice here that the object sync solution is very much designed, and, been designed and built to really support you, the functional colleagues, whereas what you're doing with client sync. Is very much your technical basis team, that are going through that process. With object sync, it's going to be your functional teams. So if I just click over here where it says create sync, you'll notice over here that it brings me back a breakdown of what we call of all of our business objects. And this is very, very similar to the SAP enterprise structure. And what I can do here is that we have a breakdown, and as I called out in my slide, is that we have very well over a thousand objects, which can be completely extensible, and customizable. But what I'm going to do here, is I'm going to take a very, very simple example, is I'm going to go to cross application components, and I'm going to go to master data, and I'm going to select a customer object. And in my customer object over here, what then this gives me, it gives me a nice selection screen. And on my left hand side over here, it gives me what we call an integration tree. And an integration tree, essentially, will contain all of my dependencies. So does my customer have a contact person associated to it? Does my customer have a business partner associated to it? Is my customer linked to an employee? So in certain situations, a customer record might have some associations to an employee record. Does my customer have a GL account? Now you'll see here that some of these options are completely customizable, so they can be selected, but we've gone with our default preselected options. On the right hand side over here, this is now where I'm going into my selection options where I can now input the value, of the customer that I want to select. And in here, I'm just going to select a customer number, but just to show you as an example. And this screen can be completely customizable. So in the context of your BAU, in talking to your clients, they may have some concerns, around opening this up, to everybody. So what we can do is that we can create these templates where we can effectively just customize the screen and lock out certain values. So for instance, I may only want my key users to select certain customers in a certain account group. And then we've also got the insert behavior down here. Now this is really, really important because of the way the object sync works. Client sync is very much doing everything at a client level, at a table level. Object sync is now very much doing, doing everything at an object level. Now in this situation here for a master data record, I've got the option to either replace complete object or I've got the ability to actually update the data, with selected data. So here, I'm going to replace the complete object. So what that will mean, it will take what I have on my source, and it will then replace it completely on the target environment. And if I go into my selection preview, what this will now do is that this will now trigger the SAP BAPI in the background, and it will now pull back, and it will show me the, the customer record, that's linked to three four five to three four seven six. If I scroll down over here, what this will also give me is that you'll see that this is all there's also a CRM system that links that's also associated to my ERP system, so it's pulling back the associated business partner. So, again, talking to your clients, they may have an integrated scenario where they've got an ERP system and they've got a CRM system. And, typically, this is something that we see a lot in ISU. So you'll have a customer, that's created in your ECC system that will be linked to a business partner, in your CRM system. And underneath all of these, it will then have all of the associated links to a business partner. So things like your address information, is something that we see all the time. And then I've got the ability to also anonymize the data as well as what I talked about in place masking. So in here, if there's concerns about PII data being exposed, so, again, things like employee data, things like customer data, things like bank information, that's, like, that's associate associated to a customer, things like address information that's associated to a customer, things like telephone number. Any PII data will also get bundled into that. And here, I can select, my data secure, a policy, that many of your clients have created for their own individual purposes. And then I'm gonna go into my execution options as you can see over here. And, again, this is very much your look and feel, so exactly what clients would see with client sync. So I'm going to do what I call here. I'm going to run it in background. I'm going to assign some parallel processes to it. And, again, it works in the same manner as it does with client thing to get better performance. And then when I do my execute, what this will now do is that it will now create a file for me at the file system. And if I just do a refresh like this, it brings me into my monitor desk. It runs very, very quickly. And then if I basically double click into here, it will now give me an overview, and a breakdown. And I can see in my object tree, I can see that all my associated records have been extracted. So I can see the business partner has been extracted. I can see that everything, is normal. And then similarly in here, I can go into my statistics, and I can see the same thing more or less. Although in my statistics, what it will show you, it will translate what that information means, in term in into the total records. It's going to numerical terms. And then what I will then do, is that I will then log into my target environment, and my target environment, is in here, and I will do exactly, the same thing. So if I go into my target environment that you can see on my screen over here, I will then repeat the same thing in my target environment, and I will go back and I will go back into here. And I will then do an import sync, like this and notice, but I'm using the file system approach here. We've also got the ability to do this via RFCs where I can just do it in real time where it will basically log me on to the target environment, and it will then prompt me to log on with my user ID and password, and it will perform the insert as well. But, typically, we like to use the file system approach. And if I go into the records or the syncs that we're on today, I'm going to select the top one. I can go into my selection preview, and my selection preview will give me the customer number. It will give me the sync number. And if I go into my execution options, then I can then go, and execute my sync. And if I do an execute now, what this will do is that this will now recreate the customer for me in my target environment. And you'll see over here that when I do a refresh like this, it's now come back as green, which is always good. And now what that's done is basically now created the customer record for me and the target environment. And you'll see over here if I go into my object tree, it will then just do give me a breakdown of all the records that have been inserted. So I see that my customer record has been inserted, But notice here that I do have some errors. Now those aren't necessarily errors. What that basically means if I go into my messages tab, it's highly likely, that I set those, that I set those objects to be overwrite disabled. Now that is not a problem, because in certain situations, there'll be certain objects that I don't want to overwrite, that I want to keep them as they are, on my target environment. And the only thing that I want to create or I want to change is my customer number, which I can see, over here. K. So this is a very, very simple, example, of a customer record. So this could be a situation where I just want to bring the customer data back into my target environment, and I wanna create some transactional data, on top of it. I'm now going to just show you a very, very simple example of some transactional data. Now, obviously, transactional data is very different, and that will cut I will show you what some of those differences are. So now what I'm going to do in this example is now I'm going to now show you how to copy back a sales order. Now if I now go into my logistics object over here and I go into sales and distribution, and I go into my transactional data, and now I'm going to select my sales document objects. Now when I go into my sales order, bearing in mind that there might be situations where you may have some specific customizations that are linked to your sales order process. So you might have some custom tables that are linked to your sales order process, or you might have standard SAP tables where you've also applied extensions. And you've if you have done all those things, again, we can also integrate those into our engine as well. And, typically, these are all things that we would flush out as part of the implementation. And it's key insofar as to the message to your, to your clients. Is any areas where there's been customizations, whether that's in the order to cash process or whether that's in the procure to pay process, those can be very, very quickly embedded and integrated into the engine itself. Now you'll see in the sales order process now, in the sales order object, sorry, is that there's far more options that are available. So you'll see now that in the integration tree that a noticeable change here is that I have my preceding documents. So, obviously, in a sales order for a sales order to be created, there needs to be proceeding documents that are created in advance of a sales order. So it might be a purchase order. It might be a purchase requisition. So it's key that those area those, documents are also included, as part of the sales order process, because we are using, the standard a the standard SAP buppies, the standard a the standard SAP APIs, and it's key that those preceding documents exist. And if they don't exist, then, there's a mechanism in place, to ensure that those get flagged. You see down here that, you know, there's obviously things that we've preselected by default, so things like internal orders, things like materials, things like profit centers, things like bombs. All of that is included by default. But, again, just like you saw in the customer example, those this this again is completely customizable, so there might be areas that you want to flag. I'm gonna select a very, very simple, sales order. So I'm just gonna select a simple number like this, called one zero nine six o. That's my sales order number. And as I called out before, you know, with this again, it's completely customizable. We can create what we call templates where we can customize the screen. So it might be the case that you only want to your end users to only select certain sales documents for certain, for, sorry, certain sales orders for certain, document types. And then if I scroll down over here, I've got my insert behavior. And, again, this is really, really important because this is where, the number ranges come into play. And, obviously, the number ranges between a source and a target environment are going to be very, very different because, obviously, your source environment is always gonna be moving on, but your target environment is may not move on as quick. And, obviously, if you create, a sales order that's in a specific number range, obviously, it's important that the sales order that gets created from the target environment also aligns to the number range as well. And that's exactly the way that object sync behaves because we're utilizing those what we call the standard SAP buffers in order to ensure that you preserve what we call that number range or retain the number range alignment. Advanced options. Again, these are really important areas, of the configuration that are important to understand because what we're able to do here is that we can depending on the scenario that we're trying to test, there might be certain things in the sales order that we create that we want to also preselect. So we might want to ensure that the delivery date is way into the future. So we may not want to create a delivery. We just want the delivery to be, created or to be requested at a different date. We might not be we may not want to include any sensitive information as things like payment card information. We may not want to include any of that. We might want to put a block, or sorry. We might want to, remove the block, that's on the delivery, or the billing document. So, again, there's various things that we can do in the advanced options depending how you want the state of the data to lock on the target. When I go to my sales preview, what I can see over here is I can now see that it picks up my sales order, and I can see that it picks up my sales order. And if I look at the object hierarchy within the sales order, what it will do now, it will then break up all of the objects that have been selected in the enterprise in the, in the integration tree. But, also, it gives me the enterprise structure as well of the sales order. So I can see here the company code that it's linked to, and it will then give me a breakdown of the company code, the sales order, the distribution channel, etcetera. And then if I go into the masking option, again, you know, if there's sensitive PII data, so if there's customer information that's linked to that, to that sales order, we can also include, the data anonymization or the data secure policy is what your clients would have called it. And then in my execution options, I'm going to do exactly the same thing. So you'll notice here that in the customer exam in the custom in the example of a customer, I didn't show you the RFC, but you'll see that there's two ways of doing an object sync. It's either through an RFC or it's either through a file export. I will show you the file export. You can use the RFC as well. Obviously, there's pros and cons to both. RFC is really used when you're just copying very, very small subs to date subsets to data, so it could be one or two records. And, obviously, if you're doing more than one or two records, we tend to, recommend, that you use the file export routes. And now I'm gonna do the same thing again, and now I'm going to do an execute sync. And now what it's done, it's now created a sync for me. And now what it will do, it will get all of that metadata, and it will now store it in the flat file. And I'm now ready to load that sales order, into my target environment. And if I now go into my target environment, I will now do an import sync, and I'm gonna do today's date, and I'm gonna do this, and I'm gonna do selection options. And this is my sales order, which I've selected. You'll notice that everything, has been has now been, grayed out, so I can't make any changes. I can make changes to any of the advanced options, but I'm not gonna do that at this point. It gives me my selection preview as well. If I've selected the data secure policy, it will show me that into here. And then now I'm gonna go into my execution options. And this is really where the power of object sync comes into the mix, and this is really why, one of many reasons why the engine or why the solution is so powerful. Because what I'm doing here now is I'm only targeting, my sales order. I'm only gonna be loading the sales order, into my target environment. So thinking about, you know, agile, thinking about impact onto the system. I've got my key users that can still continue to work as normal. I've got my key users that can still continue to do their test cases, and I don't need to request any sort of outage. So I can still create, this, sales order without, impacting any of the other activity that's happening in the system. And if I now do an execute, of the sync, you'll see now that it's now going to trigger the SAP buppies. It's now going to trigger the SAP APIs, and it's gonna reread the files, on the file system, and then it's gonna then perform, a series of it's gonna then perform a series of a it's gonna trigger a series of API. Sorry. And then it's gonna do a series it's then gonna trigger, the creation, of the record, in the actual system itself. And you'll see here that what it's now doing is in my overview, it's now just doing a run. It will just continue to run that. It will read all the files that have been created. And as it's doing all of that, it will continue to execute like this. I can monitor it. So again, from a, you know, from a monitoring perspective, my key users can see what it is doing. They can see that it's in progress. I can check my messages tab into here. I can confirm whether there's any errors or warnings, and I don't see anything just yet because it's still going through doing, the loading of the data. And if I go into overview again, you'll see over here, and it's still running. If we just give it a couple of minutes, it will continue to run like this, and then it's completed. And then if I go into my statistics, what it will do now, it will then give me a breakdown, of what, that translates to, in terms of, the number of records. And that really concludes, the demo, of object of the object sync solution. And if I just, scroll back, to my presentation, and what I'd just like to end with, is just to sort of summarize, the three key points. And as you're going out, talking to your, individual clients, as you're hearing about some of the challenges that they're having in so far as, you know, they're going through a process of where they need to there's requirements now with this pressure from those QA and Es in terms of doing more brain fixes or in terms of getting that data to support some of these smaller types of challenges that they have around testing of transport, testing of bug fixes, or smaller enhancements to have more of an agile way of working. That's an area where object sync can help. It's also a method to also use object sync. So if your clients are using object sync or using client sync, sorry, very effectively and very, very, very well today. This is also where object sync can also supplement client sync. So rather than doing multiple client sync execution, they can also have much faster testing cycles if they're able to use something like an object sync, which will then enables just them to selectively bring back that production data very, very quickly and very, very easily. And, obviously, data quality is important, and that facilitates accelerated user acceptance testing because I can, you know, test that change very, very quickly, very, very effectively. So I can get the data very, very quickly and very, very effectively. And then I can also test very quickly and very, very effectively because I'm just bringing back a very, very small, sets up to subset of data. So that concludes my session. I hope it's been beneficial. I hope it's been a beneficial session. If you have any more question, quickly, please back to the. Thank you very, very much for that. Moving now, we just have a couple of questions from the partners. I'll read them out to you. And to start it off, they're asking, how are you currently refreshing your QA or test systems? Yeah. So this is an interesting question, Marielle. So, various industries will have various, frequencies and periods where, they do, the annual they where they do their, client copies. So whether that's biannual, whether that's annual, whether that's monthly, obviously, going through a client copy process, it essentially means, that there has to be an outage, on the target environment. And, usually, that outage, that doesn't tend to be too disruptive, because it's typically done, over noncritical hours. But it just means, that, it requires additional planning. Now object sync, negates that from the process. So rather than having to go through doing a client refresh, planning the outage, going through that communication with your stakeholders, object sync, can be that stop gap, which would allow your functional teams and your QA teams to get the data very, very quickly and very, very efficiently, into their target environment. And what we're doing here is that we're not doing a full client refresh. We are targeting, selectively sorry. We're selectively copying the data that's needed for that particular scenario. So it sounds like we're doing really targeted surgery. Targeted surgery. Intelligently. Selecting the data that's required. Yep. And the next question would be, do your developers or testers often request specific data from production? Often, the common answer to that question is always yes. There's been and I hear challenges all the time from clients where a system copy or a system refresh has been done, and then soon very, very quickly up to that period, there's always demand, to get, more data or more production like data on the back of the copy back into those, nonproduction systems. And often that falls, onto the remit of the basis team. The basis team are continue continuously under pressure. They're continuous can continuously being chased. And the beauty about object sync, again, it negates that from it negates that process, from happening. So what object sync enables is really empowers teams to access the data, what they need very, very independently at a point in time. So it can allow them, to get the data when they want, how they want it, very, very quickly, and very, very efficiently without relying, on their Basis teams. And the last question that we have time for today would be what's your current system copy cycle? Yeah. And, again, as I said, this sort of piggybacks into my first question. It's kind of also been a theme really. I mean, the presentation itself is really around frequently. And as I quoted, that team of clients thinking on fixing can be run side by side. And often to me, I see them as solutions that complement, each other. So you might have you know, we have clients that run refreshes, every six months, and we have clients that run, refreshes, typically twice a year. And we have some clients that refresh once a year. And what object sync is what object sync significantly supports is that it can complement clients, your clients, or up are you absolutely. It can complement our clients' refresh strategy to have more what we call targeted updates. So, really, as you say, Marielle, really having that surgical approach rather than doing a full client refresh. You know, what is the data that I need, or what is the problem that I'm trying to resolve in my nonproduction environment, that would negate me or prevent me from doing a full time refresh. And this is really where object sync can support that process. So you've got client sync, you know, very much handling the client refresh. And then object sync is really to make sure that, you know, in those situations where, you need a specific data object, this is really where object sync can massively support that process. And you saw from my demo, but it's very quick. It's very intuitive. It's very, very easy to use. Mhmm. And that's all that we have for today. Thank you very much for all those wonderful questions from our partners, and we really do appreciate the active participation that you had during the q and a session. And that's all for today's webinar. All these full links will be included in the follow-up email. And, of course, if you want to know more about object sync, we are really, really happy to help you with that. And just send us an email or just reply to the follow-up email that we will be sending. That's it. Cheers. Goodbye. Take care. Thank you. Bye.