Skip to content

ABAP Installation Guide

Jump to bottom
Daniel Huser edited this page Feb 4, 2026 · 5 revisions

How to install the Kernseife ATC Check

Caution

As this check is based on the "Usage of APIs" Check, it is necessary to have SAP Note 3565942 >implemented in your system.
As we don't have multiple Development/Test S/4 Systems, we are unfortunatly not able to check if this Version of Kernseife works with older versions of the ATC Note and without some other Notes. In case you find any dependencies or incompatibilities, please open an issue and we will help you figure things out.
As we revamped the Upload Report, SAP Note 3630552 is now also mandatory.
Due to breaking changes, SAP Note 3710789 is now also mandatory.

In general SAP has released a new SAP Note 3627152 which helps you identify SAP Notes which are related to Clean Core and should be implemented in your system in case you want to actually start your Clean Core Journey.

Prerequisits

  • ABAP Test Cockpit (ATC) on a system with SAP S/4HANA 2023 (or higher)

  • Note 3565942 implemented

  • Note 3630552 implemented

  • Note 3710789 implemented

  • Kernseife Classification JSON File

  • Authorizations

All which is included in the Standard Role: SAP_SATC_QE Additionally: SYCM_API

image

  • A Workbench Transport Request (to activate the Check, Kernseife itself can be installed into a local Package)

  • Latest release from the Release Page (Download the latest here)

Import the Kernseife ATC Check into target system (using abapGit)

Run the standalone version of abapGit using transaction:

ZABAPGIT

or executing the report (run transaction SE38) in:

ZABAPGIT_STANDALONE

image You can find the lastest version of the standalone report here: https://raw.githubusercontent.com/abapGit/build/main/zabapgit_standalone.prog.abap

In abapGit click on "New Offline" to add a new repository. Enter the repo name KERNSEIFE and create a new package $KERNSEIFE and click on "Create Offline Repository". image image

In the new offline repository click on "Import zip" and upload the file you downloaded here

image

After the .zip was imported you need to press "Pull". This opens a dialog where you have to confirm the objects to be imported. If you used the Package name starting with $, it will be a Local Package and no transport is needed. Otherwise you need a Workbench Transport Request. As we normally don't want to run code-checks in Quality or Production, we recommend using a Local Package.

Enable Kernseife Check Variant for ATC

After importing the the repository and creating the configuration files, the ATC check must be imported in ABAP Code inspector. Open Transaction SCI (Code Inspector) and click in the top bar on Utilities => "Import Check Variants" image

After that you can confirm the succesfull import by clicking on "Code Inspector => Management of => Checks".

image

The checks for Kernseife should now appear in this list. First you need to select the Category (ZKNSF_CL_CI_CATEGORY) and save. Afterwards you can select the Check (ZKNSF_CL_API_USAGE) and save. This requires a Workbench Request which can be deleted afterwards, in case you don't want to transport the Checks downstream.

Upload Classification Json

Execute Report:

ZKNSF_CLASSIFICATION_MANAGR

image

Click on "Upload Classic API File". Select the Classification Json File.

As the main purpose is to create a custom classification, we encourage you to leverage the CAP application to create a classification JSON file according to your needs. Still, we offer a default classification file. Remark: This file is purely based on the Cloudification Repository as of 2025-05-21. It is not the "best" or "right" classification, but a starting point that you can begin your Kernseife installation.

Create Check Variant

Go to Transaction SCI and create a new check variant. We recommend to copy the standard variant ABAP_CLOUD_DEVELOPMENT_3TIER as a base. Make sure the new Variant is a public one and not a personal one.

image

Note

If you used ABAP_CLOUD_DEVELOPMENT_3TIER as a template, you should:
Disable the "Usage of Released APIs" Check.
Enable the "Check for Enhancement Technology".

In every case you need to activate the "Kernseife: Usage of APIs" Check.

image

You can also just create a new Check Variant and only enable the "Kernseife: Usage of APIs" check. This is useful if you want to use the BTP App with Scoring & Development Objects.

Congratulations, you are now able to use the Kernseife ATC Check.

Clone this wiki locally