Archive legacy SAP data without the headaches or security concerns

Hello, everyone. We're going to get started with the webinar today. Thanks, everyone, for joining today's session. It's archive legacy SAP data without the headaches or security concerns. My name is Sarah Enders. I'm on the marketing team here at EPI-USE Labs. And I'm so happy you could all join us today. We are recording this webinar today, so we'll make sure to put it up on our website and send you a link if you want to replay it or share it with your colleagues. So I'd like to introduce today's speaker, Paul Hammersley. He's the head of application lifecycle management here at Effie's Labs. His portfolio includes, system landscape optimization, test data management, data security, and also, very skilled in the topic we're talk talking about today. So before I hand over the mic, to Paul, just a few house keeping things. We'll wait until the end of the session to answer any questions. It's just a thirty minute webinar, so we won't have a lot of time, but, we'll make sure to try and get through any questions we get. So just type those into the question box on the GoToWebinar panel. So I will go ahead and turn it over to you, Paul. Thank you very much, Sarah, and thank you to everyone for joining us today. As we go along, we will also have a couple of poll questions for you. So, stand by for those. So we're talking about, decommissioning of data, and there are a few reasons why people typically look to decommission data from SAP. Sometimes, it's because they are moving to a new implementation of SAP. So perhaps with the greenfield S4HANA project, you may, have a requirement to keep your legacy system, but you don't wish to keep the entire system as a display only system forever. It can be when certain processes are moving from SAP to somewhere else. So it could be your HCM processes are actually moving to SuccessFactors, and you don't wish to take legacy employees or leavers from the system. You want to have a better way of storing that data. Even if that data is currently in a ERP system that will continue to run, would you want to leave highly sensitive data in that ERP system as it goes off on its journey perhaps to S4HANA? We also have organizations who are leaving SAP, moving to other technologies who need a secure way to store their data efficiently. And we also see where there are mergers and acquisitions and divestitures, there's often a requirement for one party to have access to the historical data, but in a display only, manner going forwards. So those are the sorts of challenges that we're working with organizations on, with our latest offering, which is called Archive Central. And Archive Central is part of the solution that we're offering. The other part is actually the extraction of the data from SAP. So this is a relatively new offering, that we brought to market in the last two years, but it's built on two very mature technologies. So Archive Central shares a base with RxCentral, other products. So things like ClientCentral that you may be familiar with if you're already a client of ours. That's where we manage interaction with our existing customers, and it has over twenty thousand users. And in any given month, over five hundred logging on to the solution. So that stack is already pretty mature, and we're leveraging that capability for Archive Central, which is a software as a service solution. We then have the extraction side from SAP, which is based on our extractor that's part of the data sync manager suite. So we've been mapping the SAP data model for many years now, and we actually have definitions of thousands of different data types. So we can go into an SAP system and using our extractor, extract out the data for lots of different types of business data, but with the metadata as well. So the relationships between the different tables that make up that data model and also some of the metadata from the system. So where you have, a particular value in the database that is a number or a code, there may be a description behind that. We bring that description as well. So when we actually get that data into Archive Central and we begin to configure that data for the business users, we can give them the choice. Do you want to see the code, or do you want to see the description that goes with the code, or do you want to see both? So there's a bit of work that we would do during the project once we've ingested the data to actually make the layout match what the business users are used to in SAP. And we already have preconfigured setups for that we've used with other organizations. We then look at how we provision the role based access for Archive Central. So although we're talking today specifically about decommissioning SAP data, ArchiveCentral is a generic platform. You can actually store other systems in there as well for decommissioning. And, many of our existing clients are already doing so. But because we have role based permissions within ArchiveCentral, we can completely distinguish or delineate the different sets of users. So the team that are viewing data for SAP might not be aware that there's actually other users in ArchiveCentral looking at other technologies. Or even within the SAP area itself, you may want to have certain users that can see finance data. Other users can see warehouse management data. Maybe other users can then see HR data. But even within a particular collection, you can limit people to only see certain keys within that dataset. So an example of this is you might have vendors. And with those vendors, you could have a particular account group, which is used to store employee data. Maybe that it was used to pay expenses as a vendor. We can provide access so that people can see all of the other vendor account groups, but not the one that stores the employee data. So any of the fields that are part of the data model can be used in order to restrict access within ArchiveCentral. So it is simple to use. It is intuitive. The whole design for ArchiveCentral, similar to ClientCentral, is that we don't require training courses. Somebody doesn't need to have a big guide that tells them how to go and find data. Because, of course, with legacy data, you may be finding that you only go view that once a week initially. Maybe it becomes once a month, might become once every six months or even once a year for some users. When they need to access the data, they don't want to have to go back to a training guide or to watch a video. They want to be able to go into the URL and then search for their data and understand from what's in front of them where they may need to go within the technology to find the data that they're looking for. And that is the whole design principle with Archive Central. So before we take a quick look at Archive Central, I would like to start the first poll. So, Sarah, if you can get this poll running for me, please. Yep. Here we go. Okay. What's your main motivation for decommissioning your data? Greenfield, Sfour HANA, migrating HR processes to the cloud, leaping SAP, mergers, acquisitions, or divestitures, or no immediate plans? So let me just give everyone a few more seconds here to finish this, and everyone has responded. Alright. Make sure to get your votes in. People are still voting. And alright. I'll go ahead and close that out and share the responses with the group. Here we go. Can you see those, Paul? I can. So we've got twenty seven percent are, interested in greenfield S4HANA projects, another twenty seven percent leaving SAP, nine percent mergers, acquisitions, divestitures, and then the remainder with no immediate plans. So it's interesting there that split of, organizations looking at greenfield S4HANA as a driver for this. Obviously, there's probably many organizations going to S4HANA via a brownfield approach or planning that route, and then there are some organizations leaving SAP. But I think what's interesting is that, that journey to the cloud that SAP are encouraging their install base to actually take is not something specific to SAP. So we've seen this where organizations that have an SAP system to decommission, they also have perhaps a Microsoft AX system, or they might have an Inforce system or IFS system. All of those vendors are actually looking at their cloud version as the route that they wish to get people to, 00:09:44,080 --> 00:09:4n8lm3u4jyn,{""english_name"":""English""