PackagePackagetypeA library you install and call yourself.See every one →What this type is →by SAPby SAPoriginPublished by SAP itself. A visible facet, never an input to a reading — a dormant official plugin reads exactly like a dormant independent one.See every one →

Project Kernseife

A custom ABAP Test Cockpit check that scores how custom code uses SAP objects against a classification the customer writes, as a measure of clean core technical debt.

An ATC check installed into an ABAP system beside SAP's own, built as an enhanced version of the standard "Usage of APIs" check from SAP Note 3565942, with the classification it scores against supplied as JSON instead of fixed. The sources come in with abapGit as an offline repository, usually into a local package; the category ZKNSF_CL_CI_CATEGORY and the check ZKNSF_CL_API_USAGE are then selected in Code Inspector and the "Kernseife: Usage of APIs" check activated in a check variant. The classification JSON is uploaded into the system with report ZKNSF_CLASSIFICATION_MANAGR; a default file ships with the project, built from the Cloudification Repository as of 2025-05-21 and described by the maintainers as a starting point for an installation. With the "Track Language Version" option set on the check variant, a run also records each custom object's ABAP language version, which is what the level concept needs, and the results leave the system through CDS view ZKNSF_I_EXPORT as CSV. It raises and scores findings; deciding what to do with the objects it flags stays with the developer.

Facts

Last pushLicenceApache-2.0

Where it sits

Lives in
Provides
Static analysisABAPStatic analysiscapabilityCatching problems in code before it runs: naming, obsolete statements, security findings, and compatibility with a target environment. Style linting, security scanning and cloud-readiness checks are often treated as one concern.ABAP Cloud readinessABAPABAP Cloud readinesscapabilityWhether code can run in ABAP Cloud — released APIs only, no direct table access, no obsolete statements — and what to do with the code that cannot.
Requires
SAP S/4HANASAP S/4HANAoutside the atlasThe system the check runs in: an ABAP Test Cockpit on SAP S/4HANA 2023 or higher, with the three SAP Notes behind the standard check implemented.abapGitabapGitartifactThe installation route the guide gives: the release zip is imported into an offline repository and pulled into the target package.

Who is behind it

SAPSAPOrganisationMaintains this
In the atlas: maintains 139, wrote 14
@SAP
maintainerAjinkya PatilPersonContributes to this
In the atlas: contributes to 113
@ajinkyapatil8190
andreasmuensterPersonContributes to this
In the atlas: contributes to 3
@andreasmuenster
Daniel HuserPersonContributes to this
In the atlas: contributes to 3
@daniel-huser
Fabian LehmannPersonContributes to this
In the atlas: contributes to 5
@fabianleh
Thomas KaltbeitzelPersonContributes to this
In the atlas: contributes to 1
@kalti-enbw
Thomas KaltbeitzelPersonContributes to this
In the atlas: contributes to 1
@kalti
Lik WeiPersonContributes to this
In the atlas: maintains 1, contributes to 5
@likweitan
Lukas BretschneiderPersonContributes to this
In the atlas: contributes to 2
@LukasBretschneider
MarkusPersonContributes to this
In the atlas: contributes to 4
@Markus1812
Markus KapferPersonContributes to this
In the atlas: contributes to 2
@mrkskpfr
10 contributors

Before choosing this

Conditions

PracticalFunctional boundary

It runs on an ABAP Test Cockpit on SAP S/4HANA 2023 or higher with SAP Notes 3565942, 3630552 and 3710789 implemented, so a system below that line or without those notes cannot carry it. The maintainers state they have no second S/4 system to test against older versions of the ATC note.

What it declares

Every artifact

Type
Package
Origin
By SAP

As a package

Where it runs
does not say
Distributed through
does not say

Parts and add-ons1

Parts 1

Apps1
Kernseife BTP Appby SAPThe BTP side of Project Kernseife: a CAP application with Fiori apps where the classification is maintained and the ATC findings exported from the system are read back per system.
ConsiderationFunctional boundaryThere is no hosted tenant: the application is built from the repository and deployed into a subaccount of your own, which needs Cloud Foundry runtime memory, a HANA Cloud instance for an HDI container, five bound services and a SAP Build Work Zone subscription on the Standard (Application) plan. The ATC check works without it, and the maintainers note that deviating from the ratings they supply switches off features such as the default classification logic.

Connections5

Project Kernseife connectionsProject KernseifePROVIDES→ provides2provides stated Scores the usage of SAP objects against a classification uploaded into the system as JSON, so clean core technical debt is measured on the customer's own ratings, and records each custom object's ABAP language version so the run can report its level. SAP/project-kernseife — README, About this project: https://github.com/sap/project-kernseife SAP/project-kernseife Wiki — Scoring & Development Object Guide: https://github.com/SAP/project-kernseife/wiki/Scoring-&-Development-Object-Guide SAP/project-kernseife Wiki — Scoring & Development Object Guide: https://github.com/SAP/project-kernseife/wiki/Scoring-&-Development-Object-GuideABAP Cloud readinessprovides stated Adds a check of its own to Code Inspector and the ABAP Test Cockpit — the category `ZKNSF_CL_CI_CATEGORY` and the check `ZKNSF_CL_API_USAGE` — which is activated in a check variant and raises findings on the SAP objects custom code uses. SAP/project-kernseife — README, About this project: https://github.com/sap/project-kernseife SAP/project-kernseife Wiki — ABAP Installation Guide, Enable Kernseife Check Variant for ATC: https://github.com/SAP/project-kernseife/wiki/ABAP-Installation-Guide SAP/project-kernseife Wiki — ABAP Installation Guide, Create Check Variant: https://github.com/SAP/project-kernseife/wiki/ABAP-Installation-GuideStatic analysisNEEDS→ needs2needs stated The installation route the guide gives: the release zip is imported into an offline repository and pulled into the target package. SAP/project-kernseife Wiki — ABAP Installation Guide, Import the Kernseife ATC Check into target system (using abapGit): https://github.com/SAP/project-kernseife/wiki/ABAP-Installation-GuideabapGitneeds stated The system the check runs in: an ABAP Test Cockpit on SAP S/4HANA 2023 or higher, with the three SAP Notes behind the standard check implemented. SAP/project-kernseife Wiki — ABAP Installation Guide, Prerequisits: https://github.com/SAP/project-kernseife/wiki/ABAP-Installation-GuideSAP S/4HANALINEAGE← has part1has part derived Through: inverted from its part_of edgeKernseife BTP App

Learn more1

Readings
  1. Taking Control of Clean Core: When to Use Project Kernseife in addition to Standard SAP ToolsLBretschneider, SAP Community

README

quoted from SAP/project-kernseife under Apache-2.0, read
SAP/project-kernseife/README.mdOn GitHub

REUSE status

🧼 Project Kernseife

Tip

In case of issues please check the FAQ. Feel free to open an issue in case there is no solution. Keep in mind: This is an open-source project.

Caution


Version 1.5.x is out with major authorization changes for the BTP App. Please checkout the Release Information for details.

📖 About this project

Project Kernseife is an open-source custom ABAP Test Cockpit (ATC) Check for ABAP systems that enables you to flexibly score the usage of SAP objects in your system, e.g. to score the technical debt regarding clean core based on a custom, adjustable classification. This check is an enhanced version of the "Usage of APIs" Check (see SAP Note 3565942), where you can introduce a custom classification in a JSON format. A description of the classification can be found in the Classification Guide. More details on the idea behind this tool can be found in two blog posts in SAP Community:

🚀 Requirements and Setup

Note: we migrated all the guides to the Github Wiki for easier maintenance.

🤲 Contributing

Please refer to our Contribution Guidelines.

🤝 Support & Feedback

This project is open to feature requests/suggestions, bug reports etc. via GitHub issues.

🔒 Security / Disclosure

If you find any bug that may be a security problem, please follow our instructions at in our security policy on how to report it. Please do not create GitHub issues for security-related doubts or problems.

📜 Code of Conduct

We as members, contributors, and leaders pledge to make participation in our community a harassment-free experience for everyone. By participating in this project, you agree to abide by its Code of Conduct at all times.

⚖️ Licensing

Copyright 2025 SAP SE or an SAP affiliate company and project-kernseife contributors. Please see our LICENSE for copyright and license information. Detailed information including third-party components and their licensing/copyright information is available via the REUSE tool.

Apache-2.0, read

Others providing26

Static analysis
  1. @abap2ui5/linterCommand-line checker for abap2UI5 app classes and their viewsfrom ABAP
  2. abap2UI5 PlaygroundIn-browser ABAP editor beside the abap2UI5 app it buildsfrom ABAP
  3. abapcdsgrammarANTLR4 grammar, lexer and parser for ABAP CDSfrom ABAP
  4. @abapify/acdsParser for ABAP CDS DDL source with a typed ASTfrom ABAP
  5. abaplint-sci-clientABAP client surfacing abaplint checks in Code Inspector and ATCfrom ABAP
  6. abaplintStatic analysis for ABAP source outside a systemfrom ABAP
  7. BellaEclipse plugin bringing Claude into ABAP Development Toolsfrom ABAP
  8. abapOpenChecksOpen-source rule pack for SAP Code Inspector and ATCfrom ABAP
  9. upDOWNciUploads and downloads Code Inspector check variants as XMLfrom ABAP
  10. abaplint-Ext-for-abapGitShows abaplint results inside abapGitfrom ABAP
  11. ABAP remote filesystemVS Code extension editing ABAP systems over ADT as a filesystemfrom ABAP
  12. code pal for ABAPATC and Code Inspector checks for Clean ABAPfrom ABAP
  13. Clean-Core.ioHosted workspace redrawing custom ABAP as BPMN and grading itfrom ABAP
  14. ACESAP GUI tool for static analysis of ABAP call flow and code metricsfrom ABAP
ABAP Cloud readiness
  1. abap-cloud-guiReport-style programming model for abap2UI5 on ABAP Cloudfrom ABAP
  2. codepagePolyfill for CL_ABAP_CODEPAGE under Clean Corefrom ABAP
  3. Modernization Agents for SAP on AWSAWS agents for ABAP, PI/PO and BW modernisation workfrom ABAP
  4. ROSAMCP server answering whether SAP objects are released for ABAP Cloudfrom ABAP
  5. SAP Table to CDS MapperRanked candidate CDS objects for a classic SAP table or fieldfrom ABAP
  6. Cloudification RepositorySAP's list of released APIs for SAP Cloud ERP with successorsfrom ABAP
  7. code pal for ABAP — Cloud EditionClean ABAP check set for ABAP Cloudfrom ABAP
  8. Kernseife BTP AppHolds the custom classification and reports imported ATC findingsfrom ABAP
  9. Clean-Core.ioHosted workspace redrawing custom ABAP as BPMN and grading itfrom ABAP
  10. Clean Core MeasurementReports Clean Core ATC results per system as Level A to D KPIsfrom ABAP
  11. ABAP Select ConverterConverts classic Open SQL SELECTs to released CDS entitiesfrom ABAP
  12. abap-system-fieldsInjectable wrapper for SY fields and date functions in ABAP Cloudfrom ABAP
  13. Cloudification Repository ViewerBrowser form over SAP's Cloudification Repository for ABAP Cloudfrom ABAP

Details

Sources3
GitHub APIdiscovered herechecked
github.com/SAP/project-kernseifetree, pushes, contributors, CIchecked
README.mdquoted, and what the entry declareschecked

Sources are graph entities: the same page may back several entries, and an unreachable source flags every row that rests on it.

Compatibility and provenance
discovered viaGitHub API
first seen in the atlas
ecosystem and domainabap, developer-experience
Contributors10
History in the atlas1
  1. First seen.
For your agent
Ref
artifact:sap-project-kernseife
JSON
/artifacts/sap-project-kernseife.json
MCP
Connecting an agent