Logo

Table of Contents:

User Guide

Prerequisites needed in the Gekkobrain Cloud

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.

How to get an account

In order to get started with either a ‘Ready for SAP HANA’ or ‘S/4 Estimate’ project, 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 sales@gekkobrain.com or contact your Gekkobrain Partner. Then an account will be created, and you will receive the login details in an e-mail.

How to setup your first ‘HANAREADY’ project

Before you can start doing a HANA 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.

Create a new system in Gekkobrain

  1. In the menu choose ‘New System’
  2. Enter the following:
    1. System-ID for the SAP system you want to inspect
    2. Description for the system
    3. System Type should be set to ‘DEV’
    4. Choose ‘Add New’

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.

Create a new ‘HANAREADY’ datasource in Gekkobrain

After you have created a system, the next step is to create a new “HANAREADY” datasource. You will need to link the datasource to the System ID, you have just created in the previous step.

  1. In the menu choose ‘New Datasource’
  2. Enter the following
    1. Select the System-ID you just created in the drop-down
    2. Select ‘HANAREADY’ as template
  3. Choose ‘Add New’

You have now created a new HANAREADY datasource in Gekkobrain. Go to the Menu ‘Datasource List’ in the Menu, where you will see the newly created Datasource

How to setup your first ‘S/4ESTIMATE’ project

Before you can start doing a S/4 HANA 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 S/4 HANA Readiness inspections. You can define multiple systems and projects in Gekkobrain for the same account.

Create a new system in Gekkobrain

  1. In the menu choose ‘New System’
  2. Enter the following:
    1. System-ID for the SAP system you want to inspect
    2. Description for the system
    3. System Type should be set to ‘DEV’
    4. Choose ‘Add New’

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.

Create a new ‘S4ESTIMATE’ datasource in Gekkobrain

After you have created a system, the next step is to create a new “S4ESTIMATE” datasource. You will need to link the datasource to the System ID, you have just created in the previous step.

  1. In the menu choose ‘New Datasource’
  2. Enter the following
    1. Select the System-ID you just created in the drop-down
    2. Select ‘S4ESTIMATE’ as template
  3. Choose ‘Add New’

You have now created a new S4ESTIMATE datasource in Gekkobrain. Go to the Menu ‘Datasource List’ in the Menu, where you will see the newly created Datasource

Finding the account-id in Gekkobrain

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

Install Extractors and setup of the scans

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.

Use the Installation Guideline

Working with the S/4HANA Assessment

When the Extractor in SAP has completed the transfer of inspections, you are now ready to go. Log into Gekkobrain and see the first S/4HANA assessment of your inspections.

First select the project

  1. In the menu and choose ‘Dashboard’
  2. The choose the tab ‘Projects’ to navigate to the list of projects
  3. On the list of projects you can see when the latest inspections was received in the cloud
  4. Choose ‘Project Cockpit’ to navigate to the current project
  5. The navigation will lead you to the Project Cockpit

The Project Cockpit / Overview

The Project Cockpit consists of three different elements:

  1. Project Estimation - here you will find the overall t-shirt size estimation of all the simplification issues found in the system
  2. Issues by Application area - here you will be able to see how the different areas is affected by the Simplifications issues found and the Simplification Categories
  3. Number of Issues by Application Area - here you can drill down into each application area to see the details of the simplification issues for this area

Project Estimation

The Project Estimation will give you an overall t-shirt size estimation (in days) based on all the simplification issues found in the system. The assessment will group all the issues found into t-shirt size categories. In the estimation overview you will be able to see the overall amount of ABAP objects which are impacted and the total amount of issues found. The estimation is always based on the latest inspection, and you can exclude ABAP objects which has been defined as ‘Completed’ or ‘Not Relevant’ in the estimation, you do this by setting the tick mark (on the top/right of the screen).

Issues by Application area and Simplification Category

With this view, you will be able to see how a specific application area will be implacted by the simplification issues found. Furthermore you can see a grouping of the simplifation categories within each area as well. The simplification category can indicate how complex it will be to solve a simplification issue.

Meaning of the simplifation categories:

Number of Issues by Application area

With this view you can do a deep dive into an Application Area, and see in details how this area is impacted by Simplications (listed by the individual OSS Notes). You can also see the estimation (in days) for each of the OSS notes. Clicking on the OSS note will show you all Simplification details all the way to the impacted Custom Code.

The Issue List

If you want to know how your Custom Code is being impacted by an individual OSS note, you should use the Issue List. From the issue list its possible to navigate to the OSS note details or navigate to see all the Custom Code is being impacted by a specific Note. For each OSS note you can see the Simplification Category, the Total amount of issues and an estimate to fix these issues. The estimation is always based on the latest inspection, and you can exclude ABAP objects which has been defined as ‘Completed’ or ‘Not Relevant’ in the estimation, you do this by setting the tick mark (on the top/right of the screen).

The Note List

With the Note List you can see the underlying details of each SAP Simplification Note. Each SAP Simplification Note consists of several sub-elements which can impact you Custom Code in different ways. So the Gekkobrain estimation is not done at Note level, but based on all the individual sub-elements in the Note. From the note list its possible to navigate to the Custom Code which is being impacted by a specific sub-element.

For each sub-element in the OSS note you can see the Simplification Category, the sub-element Type/Name, the Total amount of issues and an estimate to fix these issues. The estimation is always based on the latest inspection, and you can exclude ABAP objects which has been defined as ‘Completed’ or ‘Not Relevant’ in the estimation, you do this by setting the tick mark (on the top/right of the screen).

The Object List

The Object List will show all the ABAP Objects found by Extractor in the underlying SAP System. When an ABAP Objects has been registered on the Object List it will remain there. If you conduct further scannings, then only the related Issues will be updated. So an ABAP Object which has been cleared for Simplification Issue will stay on the list, but with no issues reported.

For each ABAP Object you can navigate to the Object Details to see all Issues found, and update the Assignee and Status on the requested ABAp Object.

For each ABAP Object on the list you can see the Status, Assignee, Usage information, Sprint, Estimation and Solution Component. The estimation is always based on the latest inspection, and you can exclude ABAP objects which has been defined as ‘Completed’ or ‘Not Relevant’ in the estimation, you do this by setting the tick mark (on the top/right of the screen).

Based on the filter used, you can always see the total amount of ABAP Objects, Total amount of issues and the related Total Effort.

You can use the ‘Mass Change’ to change Assignee, Status or Solution Component on all the selected ABAP Objects.

The Object Details

On the Object Details page you can see all the Simplification Issues for the selected ABAP Object. The issues are listed with a reference to the underlying include and the linenumber in the Custom Code where the issue is found.

You can mark an Issue as completed if you have analyzed the code, and didn’t find any reason to do any code changes. Use the comments section e.g. to document the reason for status changes.

You can use the ‘Status’ field to indicate where you are in the process with the specific object. Two of the status-codes have a special meaning:

  1. Status ‘Completed’: Indicates that no further action is needed for this object. Any remaining open issues, will not be part of the estimates anymore
  2. Status ‘Not Relevant’: Indicates that this object is not relevant for any Custom Code changes. E.g. it could be that the object not used in production anymore and should be decommissioned, or it could be replaced by SAP std. functionality on S/4HANA. Any remaining open issues, will not be part of the estimates anymore

Use the ‘Assigned to’ to indicate who is responsible for make this object ready for S/4HANA.

Use the ‘Solution Component’ to add the object to selected Solution Component.

How to build a final S/4HANA Assessment Estimation

In order to compile a complete estimation for the Custom Code task, you will need the following input and considerations:

  1. If your current SAP system is running on a non-HANA database, then the first step is to do a HANAReady Assessment (see Gekkobrain HANA Assessment guide). This assessment will give you an estimate for all the mandatory Custom Code changes needed in order for your code to run on a HANA Database.
  2. Run the Gekkobrain S/4HANA Assessment, which will give you an estimate for all the Simplifications Issues found.
  3. If you haven’t done any Custom Code Decommissining, then you will most likely have a lot of Custom Code in your productive enviroment which is never used. Spending time on these objects will most likely be vasted. According to SAP, their analysis of Custom Code shows that is not uncommon to find approximately 50% unused code in productive systems. So there is a great saving in the estimation process, if you can lift this part out of the project. You can upload ‘Usage information’ into Gekkobrain to do the filtering there, and mark alll objects with no usage as ‘Not relevant’. See Gekkobrain UPL/SCMON Guide.
  4. Even after upload and filtering using Usage information or Code Decomissining, then you might consider not to bring all the remaining Custom Code to your new S/4HANA system. Some elements might be replaced by SAP standard functionality and other parts of the code base might not be relevant anymore due to Simplification in S/4HANA. You can use the Solution Components in Gekkobrain to group the Custom Code you plan to bring over to S/4HANA, and even also create a Solution Component for elements you plan to leave behind. All Solution Components will report their own estimate, which you can use in the overall estimate.
  5. Evaluated all ABAP Objects containing XL and L. They might need a possible refactoring.

Switching to Project execution mode

Apart from using Gekkobrain for the S/4HANA Assessment, you can also use it for Project Execution of the Custom Code changes. This means that you can use the tool to plan and monitor the progress of the changes.

In order to this you will need to setup a S4ESTIMATE project for the new S/4HANA Development System, Install the Gekkobrain Extractors on the new system and finally setup the scans to run on a daily basis, so you always work on an updated inspection.

Then navigate to the project details for the S4ESTIMATE project for the new S/4HANA Development System

Click ‘Execution program’ and the select the Assessment System in the drop down (the Assessment system/project is the one you used for the first scanning your SAP system before migration)

The benefit of linking the ‘Project system’ to the ‘Assessment system’ is to get a merged picture of the issues in the two project. If you only rely on the issues found in the Project system you will be blindspotted. SAP can only scan and report issue in Custom Code without any syntax issue. And when you start up in the Project system you will have quite some of these, and the estimated time to complete would be less than reality. When you link the systems together we will make sure to tap into the assessment system and get the issues from there if the custom code contains syntax errors.

The typical project timeline