Clean-Core.io How-to
How custom ABAP moves through the phases of Clean-Core.io, from the analysis of the source to the handover of what is on record, on the in-app RAP track or the side-by-side CAP track on SAP BTP, part of the SAP Business AI Platform.
Walkthrough
The phases of a project, in the order the product shows them
Analyze
Stage an ABAP source (your own file or a starter example), choose the target deployment and run the analysis. A deterministic engine reads the code before any model does, and the result is recorded as a signed run.
- The engine reports each finding with its line in the source, computes the Clean Core Score and recommends an extensibility route: in-app ABAP Cloud (RAP) or side-by-side on SAP BTP (CAP).
- You can switch the route, and the later phases follow the route on the project.
- If a model is available, it adds a narrative report; without one, the run is signed over the evidence alone.
- Every later phase opens only once a signed run exists.
Questions
Which files can I upload?
Files ending in .abap or .txt, up to 1 MB. The text has to look like ABAP, and it is scanned for script or shell injection payloads and plaintext secrets before the analysis starts.
Does the analysis need a model?
No. The findings, the extensibility route and the Clean Core Score are computed without a model, and a run without a model is signed like any other.
What does the signed run record?
Which account analysed which source, when, with which engine and catalog version, and what the engine found. It records the analysis; it does not approve the recommendation.