Logo

Table of Contents:

User Guide

Codefixer Transactions

After a successful import of the Codefixer Package – you will have the following elements available in your system (all kept in the /GEKKOBR/ namespace):

  1. Transaction /GEKKOBR/UPLOAD_FILE to import the fix file from Gekkobrain (zip file)
  2. Transaction /GEKKOBR/CODEFIX to start fixing ABAP Code
  3. Tables containing the fixes and the related status

How to upload the fixes

Gekkobrain will generate the Code Fixes in a zip file. The zip file will be in the ‘File transfer’ area in the Gekkobrain Cloud (Go to the selected system/project and choose ‘Upload Data’, and scroll to the file transfer section, select the Code Fix file and download it. Next step is to upload the zip file to your SAP Development system where the fixes should be implemented. When you upload the fixes, then the data are stored in the Code Fix tables (no source code is fixed yet) – in the following steps you will then be able select individual/multiple fixes from the tables for Automatic Code fixing. In order to upload the Code Fixes:

  1. Start transaction /GEKKOBR/UPLOAD_FILE
  2. Locate the zip file and the upload will start

The Gekkobrain Codefixer

Selecting the fixes to process

In order to see the ABAP Code Fixes available in your system – you need to start transaction /GEKKOBR/CODEFIX. Requirements to use this transaction:

The transaction will display the fixes available. You can use the selection to filter the Fixes you want to work with:

The Code Fix Overview screen

After executing the transaction, the report will display the fixes available in the system:

The overview screen is divided into 4 areas:

  1. The list of fixes and the related status of the fix (top – left)
  2. The fix details of a selected fix (bottom – left)
  3. The current source code (top – right)
  4. The recommended code fix (bottom – right)

Selecting a fix – get the details

In order to see all relevant details of a fix – you need to do the following:

  1. Find the relevant fix in the list of fixes
  2. Press ‘Display Fixes’ in the menu
  3. The transaction will show the fix details below the list
  4. Mark the fix details and press ‘Display Source’ The transaction will show the current source code of the select object (include name) and the recommended code fix in the two editor windows on the right side of the screen.

How to fix the sourcecode

There are two ways you can choose to update the ABAP Source code:

  1. Individual processing
  2. Mass processing (Batch Job) We always recommend to start with individual processing of smaller sets, to verify and review the generated fixes, before you switch to mass processing mode.

Individual processing

You can decide just to process individual fixes for selected objects if needed.

  1. Find the relevant fix in the list of fixes
  2. Press ‘Display Fixes’ in the menu
  3. The transaction will show the fix details below the list
  4. Mark the fix details and press ‘Display Source’
  5. Press ‘Update Source’ if you want to use the Code fix proposal
  6. The object will be changed and activated

Be aware you can only change the object with the Code fix proposal if:

Mass processing

If you want to mass process the code fixes, the changes will take place in a batch job. Do not schedule parallel jobs for the mass processing, you should ONLY have one job running.

  1. Find and mark all the relevant fixes in the list of fixes you want to process
  2. Press ‘Update Fixes in Batch’ in the menu
  3. The transaction will schedule and run the batch job automatically
  4. Press ‘Refresh’ to see the progress of the batch job
  5. The objects will be changed and activated one at a time

Be aware you can only change an object with the Code fix proposal if:

Fix Types

The Code fixer generates multiple kinds of fix types, which can be implemented in different ways:

Special processing functions

The Code Fixer tool has some additional functions available – to help you in the processing of fixes:

Fix Status Description

The fix status describes the state for each of the Code Fixes available in your system. This list describes the background for each status code:

The Application log & batch jobs

All processing, both when upload the fixes and when you implement them, will be tracked in both the application log and batch job log. Use the object ‘/GEKKOBR/’ in transaction SLG1 if you want to track the update of the source code and fixes. Batch jobs for mass processing with generate job names called: “GEKKOBRAIN_CODEFIXER”. The state of the batch processing can be found in the spool.