Video: Demystifying SAP Data Migration & Management | Duration: 3608s | Summary: Demystifying SAP Data Migration & Management | Chapters: Welcome and Introductions (29.470001s), CXO's Complex Challenges (382.015s), SAP Modernization Challenges (582.01495s), Data Maturity Journey (806.265s), Data Migration Validation (1240.32s), Conclusion and Farewell (3108.74s)
Transcript for "Demystifying SAP Data Migration & Management": Good morning, good afternoon, good evening, and welcome to our session. Today, we're gonna be talking about de risking SAP modernization and how you can ensure data integrity in your SAP S4HANA system. I'm Andrew Hayden. I'm the Principal Product Marketing Manager for the Automate Products here at Precisely, and I will be your host today. And I have the distinct pleasure of being joined by Peter Griffiths from our wonderful partner in London, Calamir Point. Peter, do you want to take a moment, introduce yourself, and talk a little bit more about Calamere Point and what they have, what you have to offer for your clients and customers, and precisely customers as well? Sure, Andrew, thanks for the introduction. So my name is Peter Griffiths. I'm the founder and CEO of Callumere Point. We are a London based data analytics consultancy founded in 2009. We're leading experts in delivery of value to clients using Precisely's Data three sixty Analyze solution, having delivered hundreds of different use cases across multiple industry verticals. And we've been a precisely partner for a very long time and working with them to combine their automate suite of products with Data360's analyzed capabilities to bring value to clients. We'll show a little bit of that later in demonstration. So back over to you, Andrew. Thanks, Peter. As I said earlier, I am the principal product marketing manager for the Automate Products here at Precisely. And for those of you who don't know Precisely, in addition to automating SAP for over twenty years, we are the leader in data integrity, which means we provide the software data and service consulting services. Need to get the really high integrity, accurate and consistent and contextualized data. You need to make confident business decisions. And in a world where AI is becoming more important, having that really, really perfect, high quality, trustworthy data, it has never been more important. So if you're on that journey, and Peter's gonna talk to you a little bit about how you can get there as you go through your SAP modernization, Precisely is a really great place to start. So, let's get started. And one of the things I like talking about, I like to start a lot of presentations with this slide, which is a quote from Justin Trudeau, the former Prime Minister for Canada. And he made the quote in 2018, but it's never been more true. And the quote is, The pace of change has never been this fast, but it will never be this slow again. And it always feels like everything is constantly accelerating. And I think, you know, that is absolutely true. And again, as you add AI into the equation in your your organization, it just feels overwhelming at times. But I think what we're gonna talk about today is one way to look at how do you moderate or deal with this pace of change. How do you catch up with it? Because it will never be this slow again. It's going to constantly accelerate. So think about that as we go through the presentation today. Now, specifically as we go through, we did our introductions already, Peter talked about Calamir Point and I talked about Automate. But what we're going to talk about really is, I'm going to start talking about that CIO's dilemma and the challenges with SAP modernizations. What are the things that we see from you know, sources, multiple customers we talk to, and what is everybody dealing with as you modernize from and move from ECC to S4HANA, and as you modernize your overall IT infrastructure. Then I'm going to turn it back over to Peter. He's going to talk to you a little bit more about kind of that journey you go through with your data and give you some examples and show you some demonstrations of Data three sixty Analyze and what it can do for you in combination with Automate Studio. We're gonna do a wrap up and we'll do a little bit of Q and A at the end. So, really quickly, the Precisely Automate portfolio consists of these three core products: Automate Studio, Automate Studio Manager, and Automate Evolve. We're going to talk mostly about Automate Studio today, but a lot of what Peter's going to talk about in terms of with Automate Studio, you can accomplish with the other two as well. So, Automate Studio is the premier Excel to SAP automation tool. It really enables users across any SAP environment, whether it's ECC or S4HANA, whether you're working in the SAP GUI or whether you're working in Fiori or GUI for HTML, to create and manage SAP data in Excel. So you've got that consistent user interface throughout. It's a really powerful tool and it's great for mass data processes, where you're doing things like cleansing data or analyzing data, understanding what's happening in your data, or you're making changes to data in your SAP system. So a really great example of this is things like condition updates and condition changes, pricing updates, things of that nature, where you tend to have tens of thousands or hundreds of thousands of items within SAP and records within SAP you need to make the same change to. Studio Manager is a server based product that enables you to add some additional features to Studio, some server side features to Studio. So, it's things like job scheduling and license management and script management and centralized script distribution. So, it allows your teams to be able to use the same scripts across a global environment. And then Automate Evolve is our complete form and workflow business process automation platform. So your users, again, whether they're working in ECC or S4HANA, are working in business friendly forms. And it's really perfect for those complex data intensive SAP processes that often have lots and lots of data and lots and lots of people in your organization involved. So keep that in mind as we walk through though. Like I said, Peter's mostly gonna focus on Automate Studio and the power that Automate Studio gives you when you're going through a migration exercise. All right, CIO's dilemma. And it really is not just CIOs, it's CXOs who are dealing with a lot of complex challenges today that hit our entire organization on a macro scale. The business environment, highly disruptive business environment for many different reasons, whether it's geopolitical changes that you're not sure what's gonna, you know, what kind of mandates are gonna come down tomorrow. Currency is current currency is constantly fluctuating these days. You don't know what's gonna happen in supply chain. It can be anything from tariffs to a ship stuck sideways in the Suez Canal or a lock broken in the Panama Canal. Those kinds of disruptions are things which CXOs and IT environments just kind of drives them nuts because you need to be agile and flexible to adjust to them very quickly. AI has become this kind of new thing that everybody has we've known about it for a number of years, but over the last few years, it has become this imperative that is driving so much of our business strategy, so much of our data strategy. And yet, the results we've seen so far have been underwhelming, let's say. There was a study that came out of MIT last year, so in late twenty twenty five, that found that only 5% of the AI initiatives that have been undertaken have ever actually been put into production. So there's a lot of promise and a lot of hypothetical opportunity with AI, but so far, the return on investment the companies are seeing is fairly low. Now, the question is, is that real or is it just that we're so early in the cycle that we're not sure exactly how to derive value from it? So CIOs are dealing with that as well. And then layer on top of that SAP modernization, which tends to be the heart of a larger IT modernization effort. But the SAP modernization is highly, highly complex. It's resource intensive. There was a company named Horvath that did a research study that found that 60% of SAP modernization efforts are either over budget or over time. So they're either delayed or they're costing way more than was expected. And this is something that we hear over and over again. You've got this one massive thing that's just sucking up a huge amount of resources. And what a lot of this is leading to is this tension between today and tomorrow. Because today, despite all of the challenges we have in our business, with long IT lead times, manual processes, expensive on prem infrastructure, really poor quality data, you have to have business continuity. You've got to keep your business running today with the promise of where you're going to be tomorrow, with agile innovation within your IT organization, scalable automation with things like Automate, precisely Automate, which again, we've done this for a very long time. We see a really, really great future for automation. Cloud first IT infrastructure and that move to cloud that a lot of companies are seeing. And the need for, and the constant reinforcement for the need for high quality, high integrity data to not only feed AI, but also your reporting, your analytics, everything else, which are becoming more and more important to our businesses. So going back to that SAP modernization, we did a survey with ASUGS, the American SAP User Group, And in that, we found that one of the things holding up automation is the complexity of the business process. So 63% of our respondents found that that complexity is really keeping them from automating their SAP processes. SAP processes are complex. The data is complex. It really, it's a big challenge for a lot of people. However, there is more power every day in no code, low code platforms. And that's what we offer. And again, we've done this for a very long time. SAP migration and modernization efforts take a long time, up to six years according to ASUG's own research. The average is between a year and a half and two years. So, very long timeframes that we're talking about. And during those timeframes, you have a lot of disruption in your organization. I talked about the cost and the time that it's taking, and then this inefficiency that we run into as you're going through that modernization process, where you often have multiple user interfaces. So you are often running concurrently ECC and S4HANA systems, which means you've got SAP GUI, Fiori, and GUI for HTML, sorry. And what we find is workers tend to get very confused. So offering them an automation front end or a front end like Excel or like a business friendly form means that those workers don't have that disruption. So you're able to overcome some of those challenges in those mixed use environments. Now, when we dive deeper into this, we find a number of other challenges that people have going through their modernization. One is just persistent complexity. I was talking with a group last week, and one of the things I reminded them of is if you think about SAP ECC, and you think about something like a material record. On average, a material record in ECC has about 300 data elements, and it's got anywhere from six to eight or more steps or people within your organization who either need to contribute data, review data, approve data, have some effect in that process along the way. And that's in ECC. And when you move to S4HANA, guess what? It stays the same. So, that persistent complexity within SAP doesn't go away just because you've modernized the system. Talked about the concurrent, multiple concurrent user interfaces, custom transactions and Z transactions in ECC. You want to have fewer of them in S4HANA, but moving that data and figuring out a way to replicate those processes can be very challenging. So, what we see a lot of companies doing is they're using something like Evolve to replicate a custom process, but deliver standard SAP data and S4HANA. So you're able to maintain a clean core strategy. I talked about change management. We talked a little bit about AI. And then Peter's going to talk to you about the issues around data quality in ECC transferring to S4HANA and how do you avoid bad data in ECC becoming bad data in S4HANA. I was on a panel a year ago or so, and one of the panelists was a very large company. I think everybody would recognize the brand. And they said they had moved, done a lift and shift. They'd taken their data from ECC, put it into S4HANA, and the guy said that was a mistake because the data was so poor that now they were having to go back and figure out how to fix all that data in Sfour HANA where they could have fixed it in ECC much more easily as part of that migration effort. So I'm going to turn it over to Peter, and he's going to talk to you about how companies can really achieve those goals of high quality, high integrity data as they move from ECC to S4HANA. So Peter. Thanks very much, Andrew. Let me just pop over and share my screen. Okay. All So as I said at the beginning, Academy Point offers data analytics support for clients across multiple industry verticals and at different levels of maturity in their journey, of data maturity. So yeah, we described the organizational data maturity profile of our clients and looking at clients from, you know, the very early stages where in a sense they're going from, you know, the very simple profiling of their data all the way through to, you know, advanced analytics and AI clients are distributed across that. We see a lot of clients sort of, I guess in that space where they kind of understand what data they've got, but they're really trying to get a handle on the quality of the data they're looking at. And this area is a key area of focus for most of the clients we're speaking to on the SAP side. You know, they will have multiple, you know, errors in their data within the SAP environment. And the difficulty they have is, you know, how do you go in there and start to assess that and also to remediate it so that you can then go onto the things that kind of really add the value for your business. You know, the advanced data analytics, AI, you know, that expansion of value at that stage of the process requires you to do the legwork at the very beginning of this. And what we're gonna show in the demo in a few minutes is how Data360 Analyze can help you accelerate that process. How can it accelerate you down that from, you know, left to right in this diagram? How can you go from profiling data all the way through to some of the more advanced processes in the quickest possible time? Now, what do I mean by each of these steps? I mean, I'm gonna go through each of them. I mean, I've sort of framed them as a form of question, right? Data profiling is really what have we got? You know, some of the clients we're speaking to at the moment are literally at that phase. Their first thing is to really just understand what exactly they have in their SAP environments, right? They have historical data. They have data going back for decades in some cases, and they really need to get a handle on what they've actually have got in the system. So, you know, that's a very early stage process, but it's, you know, it's key for them to try and understand that so they can then shape what needs to happen next. The next thing they'll obviously then do is once they've got an idea of what data they have got is what quality is that data in? You know, what shape is it in? How is it looking? You know, are we finding that there are, you know, huge number of records that are missing key attributes in which case, you know, how do we quantify that? How do we assess that? And, you know, that leads into the next question is now that we know we've got a problem, how do we actually use something to actually remediate that data? As Andrew said, you know, the ability to automate feeds of data out of and back into SAP via the automate studio platform is great. But I guess the next question is how do you then build rules to improve that data once it's out of the system? How do you get it into the shape it needs to be so it could then be loaded back in as efficiently as possible? And this is where the interaction between Automated Studio product and also the Data three sixty Analyze Engine is so vital. So the next challenge a lot of clients are coming to us with is also data mastering and that mastering is across, you know, all sorts of things, product, it's, you know, materials, clients, customers, suppliers, you know, we're seeing issues of duplication in records. We're seeing issues where clients are basically, you know, have lost control of their supplier input, for example, and, you know, we'll have multiple versions, some supply data with missing key missing attributes, duplication of, you know, meaning that, you know, payments go awry or, you know, workflows take longer to actually implement because of the fact that the supplier is not correctly set up in the system. We had a case recently where a particular client of ours had an item in their material master, which was basically, you know, creating such a huge headache that they had to stand back up manufacturing processes that cost them thousands of dollars to establish. The next phase of this is integration. You know, it's all good and well, you know, having a lot of data within your SAP environment, but SAP is not the only, you know, is not the only source of data. The ambition, I guess, once data is kind of clean, normalized within your SAP environment is okay, what else can I combine it in to give me a better insight into my business? And, you know, we are working with a number of clients who SAP is just one of the systems they want to interact with. And that story of bringing that data together from SAP and the other repositories is really helping them to drive value in their organizations. The next phase of this is, you know, data visualization. This is kind of part and parcel. It appears at this point, but it is really in realistic terms, sort of feeds across the whole piece. You know, a lot of people trying to explain data to their businesses struggle to get it across. If it's just, you know, tables of ones and zeros, or, you know, it's lines of code. What we find is that, you know, installing data visualization and making it the data accessible to everyone across the business, no matter how level of, what level of technical capability they have is important because, you know, being able to tell the story with the data to, you know, to embed decision making from that data is a key attribute of this. So, you know, the Data three sixty platform is, you know, has highly high levels of connectivity with a lot of the data visualization platforms, which make the actual generation of visualization solutions extremely streamlined. Now we go into advanced data analytics and, you know, the Data three sixty Analyze platform is what we call sort of Swiss Army knife of solutions. You know, in a sense it allows us to profile data at the very simple end, but it also, because of its Python based code base enables us to build extremely complex and advanced analytics. You know, we have built solutions to clients in, you know, leveraging machine learning, very complex modeling, very complex algorithm generation. And so it has that capability under the hood as well, not just to cleanse data, normalize data, but actually to build some serious analytics and even embed AI into the platform as well. We'd recently did a piece of work for a client where we embedded connectivity to OpenAI's API so that we can integrate AI into these solutions for clients as well. So, you know, whatever stage of this profile you're on, whatever stage of priority is in your organization, the reality is Data three sixty can help you go all the way along the chain and help you accelerate your move up and, you know, up the level of complexity, and to drive more value into your business. So I'm gonna skip out of the presentation mode and I'm actually gonna go into show you what this tool actually looks like for those who haven't seen it. So if I go into Data360, so Data360 Analyze as obviously as it says there is a precisely analytics engine. It is Python based, as I mentioned at the beginning. So it sits on a sort of, I guess a Python code base and that enables, you know, data science teams and also, you know, anyone really with, you know, Python proficiency to start to build technical stuff. But a lot of what you're seeing on screen now, and I'll go through this in a little bit is pre canned logic. So it allows that business user to basically start to analyze their data. So before I go too deeply into it, I'm gonna explain a little bit about the functionality. So the section you see here, the white space in the middle with the various nodes on is what we call the canvas. And what that is, is the area where you actually build the process flow that you wanna build. So as you can see, the data goes from left to right and basically follows a set of logic through that process flow. But I'll go into that in a second. The first thing I actually really wanna concentrate on is this section on the left hand side here. So each of those little circular sort of buttons there is what we call a node. And each of those nodes contain a set of pre canned logic that exists in each of them. And those logic sets enable us to basically very, very quickly start to build data flows that require very little coding in the initial phases. And I'm gonna go through just a couple of the examples of this data, of what these nodes actually do. So the yellow nodes you see here, this whole clump of yellow, circles is what's called the input connectors. Now, the wonderful thing about Data360 is that it allows us to basically pull data from anywhere in your organization. So if you imagine at this point that you're operating in a world where for now all you wanna do is look at your SAP data and that SAP data is being pulled out of the system by the automate studio platform and being posted to an Excel file. We have the ability to immediately basically drop a node from here into the canvas, point out where the file is that you want to bring in and load the Excel file in. But in addition to that, as you can see by these, the myriad of buttons on the left hand side, there are a huge number of connectors here. So in theory, what I can do is really pull data from anywhere in your organization. And when I talked about the integration capabilities, this is crucial for that. So in other words, you're able to pull data from things like SharePoint, Salesforce, you're able to pull data from Excel files, you read in CSV files, you can connect to databases. So I've got the ability to link via JDBC or ODBC, you know, I can basically pull data from anywhere. And that ability means I can get this data from all over my organization without having to build, you know, complex processes that involve, you know, putting new platforms in, I can literally pull the data from anywhere. And that is one of the huge advantages of this system. It enables you to basically connect data from your organization seamlessly. Now, some of the other nodes that you see here contain other pre can functionality as well. And we'll go into a little bit of that as we go through the demo, but you know, each of these, you can sort of pull drag out of here and I'll put onto the canvas and then basically connect to the data source you wanna use. So it's almost extremely streamlined and extremely quick to be able to start developing stuff for yourself. So I'm just gonna delete that node off there. So in here also the ability to kind of bring data together. So these correlation nodes for anyone familiar with sort of, you know, using SQL, these are pretty common things, full merges, you know, fuzzy joins, fuzzy cross reference nodes, all of these functionalities exist. And what we'll do is we'll go through the view on the right hand side there, but I will talk through some of these other nodes as well. A lot of these, you know, getMetadata allows you to basically harvest metadata. We're able to change the metadata in a file in an automated way. So we just define what we wanna do. You know, there's huge amounts of capability in terms of actually just dealing with the meta side of the datasets. There's ability to profile and patterns. We'll go into the profiler in a minute. There's obviously some very complex logic down here involving sort of linear aggressions and quantile regressions, but again, pre CAN functionality that probably is more advanced, but you know, it's very helpful to have out of the box. The other thing to note about Data360 is no matter where you pull data from, you can always say write data back to it. So, as I said at the beginning, you know, let's say for example, you wanted to do some remediation of some data quality. So you test it, you build the logic, you then enrich the values within Data three sixty, and then you wanna post this back out to, automate studio for load. We have the ability to basically output to any of these places. And one of them is obviously an Excel template file. So we can basically write to Excel and in a form that basically needs, you know, can meet the requirements of automate studio. So in theory, just simply press, you know, load on the Automate Studio side and the data will appear in your SAP environment. Extremely seamless, extremely accessible. The other thing I mentioned is that Data360 also can connect to all sorts of different visualization tools. So you can see here Qlik Sense, Tableau. We do a lot of work where we write data for consumption by Power BI. So any of the major visualization solutions that people use in their organizations, we can pretty much write native data to them for them to be loaded. So it accelerates the ability to also put visualization in parallel with this as well. So I'm gonna stop there in terms of the so many nodes, I can't possibly go into all of them, but, you know, happy to, if anyone's in particular interested, then we can, you know, arrange something offline. So what am I doing here? So in this flow chart you're seeing on the screen, we're using dummied up data that we have recently, from a client exercise we recently did looking at assessing data quality for a particular client. Now this data is direct from SAP. It is supplier data. So LFA1 is a key supplier table. LFBK is the bank details, particular suppliers. And we're gonna use this example just to run through some of the functionality. So the first thing to notice about the Data360 is this is an Excel note. So we brought in an Excel file that we've put into a particular location as is defined here, down the bottom here, we literally just press run on that. And the thing about the Data360 platform is the data stays in the system. So in other words, at any point during this process flow, I can see the entire set of data. I can basically go down here. I can see all of the data that I wanna see. And so it helped me in discovering what my data actually looks like. The first thing in the, if I go back to the slide deck, you know, the first thing we talk about is data profiling, right? And so we've got 10,286 records in this file. And the first thing I want to do is see what this data actually is, right? Before I'd start doing anything with it, I wanna be able to profile it and I'll show you how that works. So if I remove that node, I select profiler, data profiler node, I drop it onto canvas. I basically link it to the data source I wanna pull the data from. So in this case, the initial set of records from the LFA one table, I press run and within a second or two, that will have produced the profile of this particular dataset. So here we go. I've got those. So there are 45 rows in that dataset, sorry, 45 columns in that dataset. And for each one of them, it's giving me some very valuable information without me having to encode anything. So if I look for example, at this country region key, which defines where the supplier is based, without me telling this, you know, Data three sixty anything or building any code, it's automatically been able to tell me specific things about the data. So in this case, it's looked at all the values of the data in that thing. And it's suggesting to me that this is a country ISO field, right? So it can see that actually by looking at the validation as in the format of the data within this, in this particular row, it can tell me some attributes about that data. Now that allows me to basically start to get a handle on my data very, very quickly. It, you know, it tells me also other very valuable things about my data. It tells me how many of these are actually nulls, right? So if a field in your SAP data came through and it said, okay, I've got a mixture of values in here. Some values are populated, some aren't, and it's a mandatory field, you know automatically there are issues with that data. Where this profiler node really comes into a zone is the acceleration also of data governance. A lot of our clients, as part of their data journey are trying to embed governance in their processes and having this profiler node run across your data almost gives you a recipe card of attributes that you can then put into your governance model. And also, you know, gives you those key metrics just to start the process with. So, you know, again, it's a huge accelerant for anyone doing data profiling, sorry, data governance. So that's great. We know a little bit about our data now. We were on the first step of the rung of the ladder in terms of that flow I showed earlier. The next stage is right. I wanna know a little bit about my data and I wanna be able to start cleaning that data. So what we're doing here is being suppliers, we have both suppliers that are natural persons and we have suppliers that are organizations. And as you can see here, if I go in here, the first thing I wanna do is I wanna start testing some of my data attributes. So for example, and just as a very simple example, as I brought in all these personal records, I wanna say, okay, anyone who is an active person, I wanna be able to see whether they have a date of birth field as part of their submission, right? So I go in here and I basically select the particular field I'm interested in this case, date of birth. And I go into there and I say, okay, I want this to make sure that, you know, there are no null values in here. And what it does is it will run and it will then highlight to me, okay, these are all the entities that have been highlighted as individuals that have no date of birth field in them. So I can then start to say, okay, someone either needs to populate that, or we need to source that data from somewhere else. But ultimately that, you know, that logic is there to be basically identify any gaps in the process. Again, we're not expecting anyone as a natural person to have a VAT number because it's a corporate instance, but you know, if anyone does have a VAT number, then obviously that's bad data as well. So you can start to build rules very quickly. And the thing about Data three sixty is anything you build now, as long as the data coming in remains consistent, will always generate the same outputs. So I can rerun this process as many times as I want, and it will always continually produce the same set of outputs that I'm getting. So for monitoring data quality, building the rules across this and the rules can be built very simply on single fields, or you can build extremely complex multi, multi field rules and multi, you know, and also logical rules that basically make sure that all that data is coherent and consistent. All of that is built and will be, you know, is fully repeatable in the process flow. So, you know, we showed some very simple data quality checks there. We also can build some fairly complex logic. This is an example of where we're showing how you actually look at the deduplication of some of your client, your supplier mastering data. So in this case, what we're saying is we take the client, the data on persons, for example, and we assess whether those particular records show any form of duplication. So you take the one population as your left input, one as your right, and you assess what the level of duplication is. In this case, I'm basically saying, can I find suppliers that are consistent, you know, are duplicated? And obviously here, what I'm doing is returning. So Alpine Property KFT finds a supplier reference of this, but it also finds the same supplier reference here. So it suggests to me on a very basic check that actually what we're seeing is duplicate suppliers in my population. We can go even more complex than that. And what we can do is we start to build fuzzy logic that allows us to basically assess not just whether, you know, the direct matching works, but also in this case, whether we've got clients that have, sorry, suppliers that have actual, you know, values that are basically similar, but not exactly the same. So in here, we're doing is we're running what's called a Levenshtein distance, which will assess whether for the change of one particular character in a name, whether we find the same pattern. So if I look in here, you'll see the green holdings SA, when we looked at the data, we've also found a record that has something called green holdings sorry, not SA, SL. So in other words, we're able to basically spot that there is duplicate in here, even though the name is variant by one particular letter. So, you know, it enables us to basically, so in here that is the other side of the field, and we can see there is one letter difference. SA has been converted to SL. So we can build these rules very, very quickly and start to assess that data and start to run the deduplication. In addition to that, you know, other thing is obviously one of the things we also wanna always be able to do is combine data sets. So in this case, we're assessing from the left hand side and right hand side, we're seeing if any of the suppliers are missing bank account details. So when we run this through, we simply link on the supplier number and then ultimately what we're able to do anything on the left orphan side suggests this is a client that doesn't have bank account details set up in that particular LBK table. So, you know, we are then able to basically go in there, flag that to anyone running the supplier data and get them to remediate that exercise. So, you know, there is huge amounts capability in here, or as I said, all of this is repeatable. So once you've established a set of rules, you can run them consistently. And a lot of what we do with clients is we will build a framework of data quality rules for them. We will then execute that for them, or they can execute it internally themselves. And what that will do is give them a way of tracking the evolution of the data over time. So it's no point in cleaning all your data, doing, going through that huge effort for only it to start sort of, worsen over time again. Okay, cool. So hopefully that gives you sort of, I guess we've covered there the data profiling, some of the data quality rule construction, some of the data mastering processes that can be run-in this, in the solution. What I also wanna talk a little bit about, and I'm gonna go back to my slides is a little bit about how this works when it comes to our migration exercise. Now data, as Andrew mentioned at the beginning, data migration often is a very high risk process for a lot of organizations, right? The ability to get it right first time, the ability to move the data from, you know, your old environments to your new SAP environment can often be a high risk moment for an organization and can often lead to, you know, overspend, failure of programs. And one of the key drivers of those failures of programs is, I guess, lack of visibility of the data that is being moved. And I think where Data360 Analyze has been used by our clients to support their migration exercise is the ability for you to basically create what we call prototypes. So if you imagine you're going from an ECC environment now where you've brought out data from a particular table and you need to move it into the new S4HANA environment, you may need to make some transformations to that data. And to do that in a live migration environment means, you know, you run the risk that those transformations aren't captured correctly or are, you know, are creating actually worse data than you had in the original system. So what we talk about here is the ability for Data360 Analyze to act as a prototyping source. So what that does is enables us to basically extract the data from your existing environment, construct the transformational logic in Data three sixty. And we'll go through an example of this in a minute, but that transformation logic can be built in Data three sixty. You can run that data through those transformational steps and create what we call a prototype. So in other words, what the data should look like when it goes into SAP. Now, what that gives you then is the ability to then reconcile that data. So once you are ready to migrate your data, let's say you've now done all that stage of basically prepping your data for the actual true migration. The ability to then take that data and compare it to the prototype data means that you're able to then validate that the data you're about to put into your SAP system is coherent based on what the transformational steps should have been. Now, this is extremely powerful because, and I'll show you how the process works in Dev360 in a minute, but by being able to test and, you know, validate the data before it's even loaded into your new SAP environment means you substantially de risk the migration exercise because you know, before you even load the data back into the new environment, that the data is coherent and consistent. And that three way reconciliation, the wonderful thing about Data360, can actually then tell you where those deltas exist. And those deltas can not just be at the record level. So does your count of rows make sense, but it looks at every single element and attribute of those particular records as well, and tells you any differences between the two. So that means that, you know, before anything happens, that your data is a 100% as you expect it to be once it's loaded into the data, into the SOR HANA environment. So I'm gonna just show another demo of that. So this is actually a real life exercise we've just done for a major UK financial service firm who were moving from a particular, not an SAP environment, but a Unisys environment into their SAP, into F4HANA for their customer data. So what we show here is that we've pulled out a 100,000 rows as a sample records. This is just for demonstration purposes, but the reality was that was many millions of rows of data. Now, what they were doing each of these stages here, and I'm not gonna go into every single bit of it is these are steps of significant transformation, right? Changing the format of data, changing the metadata in one system versus the other to make it compliant with what SAP is expecting, carrying out transformations. And I'll show you the type of transformation we were doing. So renaming particular fields, you know, so in here going from the original source to what the, you know, SAP field should be, we were going through different format changes in this case, some of them very basic. So again, going in here and changing date structures and each of these changes can be defined basically within this flow. So if you're having to create any sort of complexity of change that can be built very, very quickly in Data three sixty. So whatever transformation logic you're having to run, it can be constructed and tested and run through with the data that's necessary. So how does the actual process of then the validation work? So in a sense, have built ourselves a prototype. This 100,000 row dataset has been through the transformation stages that have been defined as part of the transformation logic that's being applied to the migration. And then what we're doing here is we've created, I suppose, the, the, the SAP version of the data that is about to be uploaded. So this is almost like the real case. This is the data that is gonna go into the system. And now what we're trying to do is make sure that what we've prototyped and what's actually going into SAP are consistent. Now, what we do here is use what's called the full merge node in Data360. And what that is doing, it allows you to tell multiple things. The first is very, very simply which records on the left hand side do not appear in the right hand side. So what data is in your prototype version versus what you're about to load into your SAP environment. And again, we see there are 700 records here where that data has been, you know, built in the prototype, but is not visible in what is about to go live in your SAP environment. So obviously that's something that would immediately flag a concern for people. The zero cases is where we have stuff that has completely failed. So, you know, this is where a record is found, but none of the values in it are consistent. On this node here, this right hand node, again, it's the opposite. It's where we have data that's now going live into our SAP environment that was not there in the prototype version of the data. And most interesting of all, I suppose, is this 658,000 rows here, which show me exactly per customer record and per field value changes that are not consistent. So as you can see here, this particular date format has been transformed inconsistently, right? So I was expecting a particular value on the left hand side per my prototype. And what I'm seeing in my SAP load is this different value here. Again, we have missing values again, that, you know, this GB is shown as the nationality of the client in the prototype version, but it's not found in our SAP environment. So again, you can start to assess at a very, very granular level where things are going wrong within your data field, data fixes. So in other words, can then, you know, as part of your migration, you would then stop at that point, look at what is causing that variation and basically try and rectify that before it's loaded into the system. Because once it's loaded into the system, obviously you have the hassle of trying to, you know, delete the data and start again. So the ambition here is that you're de risking your migration by prototyping using Data three sixty and then testing the viability of the two setups prototype versus real in the infrastructure itself. So the other thing to focus on, I mean, why is that important? I mean, I guess, you know, the benefits of doing this are, you know, the ability to build that logic within Data three sixty is extremely rapid. You know, those building transformational logic in Data three sixty is, you know, is a matter of hours. You can then build your prototype again, you know, we've done this for clients who are running billions of rows of data, right? So they're running transformations across a huge variety of records, a huge number of records. So very high volume, it's volume agnostic, you know, again, billions of records transformed. And by having the repeatable process, what we're able to do is as your data changes, you can reload that and recreate the prototype. So it's almost like a living vehicle, right? So in other words, as the data changes over time, you can create prototypes almost on a daily basis. And then you also have the ability to then test those against what you see as your live example of what's about to go into a newer SAP environment. And finally, again, as I touched upon earlier, the ability to connect this data to data visualization tooling seamlessly means that ultimately what we're able to do is actually give management visibility as to how the migration is going. So we can flag statistics that are important to people across the program to make sure that everybody is, you know, is getting a very simplified and very clear message of what the state of things are in this process. So again, this crucial benefit of having the ability to do these multiple stages is hugely powerful from the Day360 Analyzer perspective. Okay, I think that's the demo done. I'm gonna hand over back to Andrew. So Andrew, thanks for taking back control. Well, thanks Peter. That was fantastic. I think hopefully people have a much better idea now of what Data three sixty Analyze can do to help people going through this migration. And as you mentioned, you can actually extract that data from SAP using Automate Studio into an Excel file, and you can then use that with as your source file for Data three sixty Analyze, and then repost using Studio back into your new S4HANA system. So a lot of power in that. Hopefully you've got a much better sense of how to streamline that data migration process. Because one of the things that we've run into recently is a number of companies have a systems integrator, and all they're doing is the technical implementation of S4HANA. And the business is left to have to actually manage their own data migration. So, this is a very powerful tool and a powerful way for people to be able to manage their data. So, real quick on a wrap up, you know, think we've talked about some of the benefits, but, you know, getting that clean, accurate data in S4HANA and other systems using this combination can be a very powerful tool. Gives you faster, more efficient migration. Know, Peter talked about how you can get everything set up and running very, very quickly. Within a day, you might have your prototype developed and working properly. And then you can actually start that migration and get it into production quickly. Improved SAP performance and reporting. Obviously, the higher the quality data you've got in your SAP system, the better it's gonna run, the fewer recycles you're gonna have to do, and the better reporting and frankly, business decisions you're gonna get out of it. Ongoing capabilities across the SAP environment. So this isn't a one time just migration thing. You can continue to use this to maintain your high integrity data once you've gone live. Reduce compliance and security risks from not only understanding your data better, but having more compliant processes. And ultimately, it gives you better business agility and operational efficiency. So, what does that give you with Precisely Automate and the Data three sixty Analyze combination? Faster time to value, lower total cost of ownership because it is, you're not having to rely on an expensive external source to be able to do this, or you're able to work with very efficient partners like Calamir Point to help you. And then ultimately, again, we've talked about better business outcomes for you and for your business as you go through that migration and modernization process. Hopefully this has all been helpful for you to understand where the opportunities are for you. If you wanna learn more, you can go to precisely.com. We've got white papers, demos. You can find more about this in the SAP process automation section for your SAP modernization, as well as other Precisely products. So highly encourage you to go there and check that out. And finally, I just wanna thank everybody for being here. I know your time is valuable, and we definitely appreciate that you have chosen to spend that time with us. So, Peter, real quick. I know we're we're running short on time, but did wanna check with you. When you work with clients and customers who are doing that migration, what's their, I guess, entry pain point? How do they come to you and what is this? Try to think of the best way to put it, but what are they looking for? I suppose, I mean, you know, again, it depends slightly on their maturity as an organization, as we talked about, you know, lot of clients are using the migration sort of trigger point as a way of determining, you know, how they're gonna handle their data going forward, right? So a lot of them will have got to the point where, you know, they've lost control a little bit of what's in their SAP environments and they will start to, assess that where they are in that particular process. And I think what we find is a lot of clients are really concerned about their data quality prior to migration. A lot of them will maybe know what they've got in their systems, but they, again, may not completely understand how good it looks. And so are keen to make sure that the quality of data enhances before they move it from one system to another. And that I think is probably where we've seen the sort of the sweet spot for clients is people who have concerns about quality, concerns about sort of duplication of things in their mastering of data. And at that point, they're looking to fix those prior to them moving that data across to the new environment. So that really is the sweet spot for people at the moment. Okay. And I guess that also applies if you've got multiple SAP or ECC systems that you may have acquired a few of them and you've got transformations in order to get it all to be consistent. Yeah, exactly that. And, you know, and the ability to basically pull data from each of those ECC environments using Automate Studio and then loading them into Data three sixty means that you can start to pull that together much more quickly, right? In the old days, you know, if you're operating in, you know, you can pull it out of Automate Studio and then if you're operating in Excel, then obviously it's very easy to get lost. You know, I think that this it's much clearer. Yeah. All right. Wonderful. Well, again, I very much thank you for joining us. It is, I think, just terrific to see what this opportunity is for customers and clients. Any final thoughts from your end on kind of what you want people to take away? No, I mean, I think, you know, anyone who has challenges with their SAP data, whether it be in situ or in being migrated, I think, you know, the Data three sixty tooling offers you a real way of accelerating some of those good practices. And, you know, it'd be very happy to talk to any clients out there, visit CallumearPoint's website to hear more about some of the use cases we've done, but, you know, very, very grateful for the opportunity to talk to people today about this. Wonderful. Well, thank you very much. I appreciate you've been here and I hope everyone has a happy and healthy day. Bye. Perfect. Thanks. Bye.