The webinar discussed how Panaya helps manage risks when changing SAP systems. Panaya uploads a customer's code and runs analyses to discover what needs changing and what doesn't. Within 48 hours, Panaya provides a report on project scoping and testing rules. It then helps track changes in real time and accelerates testing. This reveals the secrets behind managing SAP changes more easily and at lower cost than traditional expensive and time-consuming testing of all changes.
OK, so let’s try something a bit different with this Webinar and start with a question…
How often do you release new functionality to your SAP ERP system?
Once/Twice a year
Every Quarter
Every Month
Bi-Weekly
Every Week
We will wait a few moments allow everyone to answer the question
And I am sure none of you will be surprised to hear the results – most of you are introducing change into your critical ERP system on a regular basis, and of course with that frequency of change, you are also introducing an element of risk with every transport to production. Now, in order to reduce this risk, the best thing you can do is make sure that you test, test and test again. In essence, whether you are involved in a major project like an EhP upgrade or a roll-out, or just those monthly updates based on business requirements, you will be constantly trying to identify areas for concern and testing ad nauseum.
In my role educating Panaya’s customers, I get exposed to some of the challenges that project managers, functional analysts and business testers face when they are dealing with these changes – and something that often appears at the top of the list is the big “unknown” – i.e. do I really know what is going to be impacted when I go live, and as a result what do I really need to test
In essence, organizations are constantly faced with the dilemma of where to start…
and it is here that Panaya’s magic can be of assistance. In today’s webinar I want to share with you some of the secrets of that magic and how you can benefit from it.
But before we carry on, let me ask you another question….
Which of the following changes are you planning in the next 12-18 months?
HANA and/or S/4HANA upgrade
Enhancement Pack Upgrade
Roll Out
Significant Functional Enhancement
Support Pack Stack Upgrade
Other ERP Project
We will wait a few moments allow everyone to answer the question
For those of you that are not familiar with the Panaya approach to ERP change management, here is the short answer - basically we take a technical magnifying glass, and evaluate your system, with all of its customized nuances, in order to assess what the impact will be, based on the proposed change. Of course, when you know what is going to break, it can focus you on what actually needs to be tested as well – and Panaya’s CloudQuality Suite provides all of this in a simple to use platform for both the required code remediation and testing.
So, There's magic with Panaya.
You spend 1 hour extracting meta data on your environment, upload and within 48 hours the magic happens. You get a full assessment on your environment and its fitness, and don’t forget, Panaya has already done this on over 25000 landscapes, so we also use our crowd insights to help you assess your system.
But that is just the short answer!
So, what do we actually do to get all of this vital information in our cloud based software platform? We start with SAP. Every time the vendor releases a new version, such as a support pack, Panaya gets a copy of it and runs it through a cloud based ERP smart learning engine. We have actually already analyzed over 9 billion lines of code and an even bigger number of screens.
From this process we come up with 2 types of rules:
Scoping rules, for example which user exits impact transactions or which tables became obsolete in the analyzed version, and Testing rules such as which dynamic values are generated for each transaction.
And from all of that, we create what we call the SAP ERP Baseline.
Then, we start to take a look at the customers.Every ERP system has its own unique environment, its own systems, customizations and business processes.Panaya needs to analyze all of that as well…so the customer uploads their custom code using our code box and their test scripts using our test box. We are not interested in your actual business data, just the custom code of your system and how much it is used.
As you can see, this is merely a matter of compiling the relevant data and loading it into the Panaya platform.
Over a mere 48 hours we analyze the customer specific baseline, assisted by the vendor ERP base line rules that we already have collected using our smart learning engine and come up with a detailed and very accurate plan of customer specific scoping rules and test rules which are now available for any type of change.
One of the other key benefits of analyzing all of this information is that the engine is continuously learning from everyone who uploads their data allowing us to continuously update the ERP Baseline rules with new patterns that we find, so that our customers can immediately leverage that in their next project.
We present all of this in an area of the application called My ERPs. The first report shows a snapshot of your ERP system including its relative size alongside object related information. Panaya displays all the information you need to compare your system with other ERPs out there. In the ERP Fitness State area we help you to understand and determine your system readiness for future changes by comparing your system with other similar systems in the market (based on over 5,000 ERP systems analyzed by Panaya).
Using all the parameters of your system plus the status of your custom code, Panaya can give you an ERP Fitness Score (indicating how well prepared your ERP is for future changes).
The Satellite Map provides a view of all satellite applications interfacing with your ERP system, and the change stream presents a time-line based view of all system changes, their nature and volume. In addition it provides meaningful insights for upcoming changes and the ability to leverage Panaya’s services.Now, let’s say you want to simulate a potential change – Panaya runs the change simulation query on your ERP base line and gets 2 things:
We generate a detailed Optimized scoping Plan for all fixes and Testing.
So you will not have to test too much and lose valuable time, or test too little and expose yourself to risks.
Then, after you know what to test, you can use our CloudQuality Suite to accelerate test runs of business processes and identify all defects. You will be able to complete your test cycles (Unit Tests, Integration Tests, UAT and regression tests) of IT & Business as fast as possible. Customers who accelerate their tests with Panaya meet their deadlines, on budgets without introducing critical defects after go live.
During each change we also provide real time reports to monitor and track the progress, identify who is holding up the project, how much work is yet to be done and ensure you meet you change project goals, KPIs and regulation reports.
The process is repetitive and will apply for any change that you introduce, and of course, all the assets from your previous use of Panaya can be used again and again, so changes will, by definition, get easier and easier allowing you to be more agile and efficient.
Would you like a Panaya representative to contact you to set up a free assessment?
We will wait a few moments allow everyone to answer the question…
Q1: How would I go about including my own CR data into the analysis tool?
A: For your regular Change request process, one would use the Change Simulation area to upload the content plan and then analyze the release accordingly. For these types of changes the biggest thing is knowing what to test, and the analysis can help you define a specific accelerated testing cycle for that change event.
Q2: Is there any way of knowing what we have uploaded to Panaya?
A: Yes, we keep track of all your uploads, whether it is code or tests – all can be found in the Code Box or the Test Box areas.
OK – so that’s all we have time for today, thank you for listening and being part of the magic.
Goodbye.