Before you start the extraction of data from your SAP system, you need to prepare the initial steps in the cloud, to receive the data.
In order to get started with a ‘Ready for SAP HANA’, you need to have an active Gekkobrain account and have access to this account as an Account Administrator. If you don’t have an account yet, then you can contact us at email@example.com or contact your Gekkobrain Partner. Then an account will be created, and you will receive the login details in an e-mail.
Before you can start doing an assessment you need to setup the first project in the Gekkobrain Cloud. A project in the Cloud is always linked to a System-ID (which should match your SAP System-ID) for which you will do the HANA Readiness inspections. You can define multiple systems and projects in Gekkobrain for the same account.
Go to the Menu ‘System List’ in the Menu - and you will see the newly created System-ID.
The system you have just created will get an API-key. You will need this API key when you send inspections to your Gekkobrain account.
After you have created a system, the next step is to create a new “HANA Ready” datasource. You will need to link the datasource to the System ID, you have just created in the previous step.
You have now created a new HANAREADY project in Gekkobrain. Go to the Menu ‘Project List’ in the Menu, where you will see the newly created Project.
The final step you need to go through before you can send the first inspections to Gekkobrain is to get the Account ID. You will need this Account ID, when you start the extraction report in SAP. See FAQ
When you have defined the SAP Systems and Datasource in the Gekkobrain cloud, then the next step is to install the Gekkobrain Extractor Framework and setup the scans to send data to the Gekkobrain Cloud.
When the Extractor in SAP has completed the transfer of inspections, you are now ready to get started with the assessment.
Log into Gekkobrain and see the first HANA assessment of your inspections.
Based on the latest scan of your Custom Code, the Project Cockpit will give you a detail insight into how you are impacted by HANAReadiness Issues. The cockpit consists of the following elements:
When the custom code is scanned by SAP for HANAReadiness Issues, then the result of this scan is divided into three different priorities:
The Gekkobrain Assessment tool contains an estimation template, which is used to calculate the expected effort for each of the different issues found.
We calculate an overall estimate per priority if the task were to be done manually, and we also consider which of the issues can be fixed automatically by either SAP Quick Fixes or Gekkobrain Codefixes.
Furthermore you can also subtract the effort for all the objects which are not used in the productive system. In order to do this, you need to upload usage data and mark the flag ‘Based on UPL’, then all Objects with no usage information will be taken out of the final estimate. These objects would typical be subject to decommissioning.
If you have added Usage data into the project, you can see the estimates based on Priority/Usage. This can be quite helpfull especially for Priority 2 which is related to potentiel performance issues. Addressing the issues in Objects which are excuted in the productive enviroment with High Usage, would minimize the risk of the performance issues related to HANAReadiness.
With the Objects Status you can easily track the progress on the HANAReadiness Custom Code changes. For each ABAP Object registered in the scan, the developers can report a status on the Readiness, whether they have started the analysis, is in progress fixing the issues or it has already be marked a completed or not relevant.
Objects which are maked as Competed or Not relevant (no usage) - is subtracted from the total effort estimation.
See how your Custom Code is impacted per Priority
You can use the DevClass overview to see how a particular DevClass is impacted by HANAReadiness Issues. Apart from calculation the overall effort, you can also see the split between Complexity and Impact of the issues per DevClass.
You can use the overall burndown chart to see the Estimated Effort left, if all issues should be fixed. In order to use the Burndown chart, you need to setup a daily HANAReadiness Scan of your custom code. Whenever the issues are fixed in an object then it will automatically impact the burndown. Objects which are marked as completed or not relevant is also impacting the burndown chart. If new issues are introduced in existing ABAP Objects or new Objects which issues are added, you will see the Actual Effort going up.
For each of the Priorites you can track the Estimated Effort left - and also monitor if new issues are introduced in the system
You can always download the HANAReadiness PDF Report - either for all objects and issues in the system, or you can select only the see the result of the assessment based on Usage data.
The PDF will include the Effort estimation and also details about the Issues found for each of the HANAReadiness priorities.