Your first run
Seven clicks from signing in to a downloadable package. You do not need an SAP connection, you do not need credentials, and you do not need any code of your own — there are examples waiting on the dashboard.
What you need
An account. That is all — no approval to wait for, no system connection, no credentials, no data.
What it costs
One of your five transformations, spent at the analysis. The six stages after it are included.
How long
About fifteen minutes end to end, most of it spent reading the output rather than waiting.
- 1clean-core.io
Sign in with the account you registered
Use "Get Free Access" in the top right. Registering activates the account immediately — there is nothing to approve and no waiting list — and you land on the dashboard.
You should see: The dashboard, with your transformation balance shown in the header — "0 / 5 Transformations" on a fresh account.
- 2Dashboard
Scroll to "Try it with an example"
Below your projects there is a panel of ready-made legacy reports. They are fictional, but written the way grown enterprise ABAP actually looks — and they are the same objects the analysis engine is regression-tested against.
You should see: 7 example cards, each naming the object, its size, and the Clean Core problem it demonstrates.
This is the step that saves you the most time. Nothing has to be exported from an SAP system, and no customer code leaves anybody's estate.
- 3Dashboard
Click one card — Z_MATERIAL_STOCK_CALC is a good first pick
One click creates the project, stages the source, and takes you straight to stage 2. At 99 lines it is small enough to read in full, and it has the single most common Clean Core problem in it: direct reads on MARA, MARC and MARD where released SAP APIs exist.
You should see: The Analyze stage, with a green "Source Code Ready" panel confirming the source is staged.
- 4Stage 2 — Analyze
Start the analysis
The deterministic engine parses the source first — findings, database coupling, code inventory, complexity and criticality — and only then does the AI write the narrative around that evidence. Takes a minute or two.
You should see: A Clean Core Score, a findings list with line numbers, and a recommended route: in-app ABAP Cloud (RAP) or side-by-side BTP (CAP).
This is the one step that costs a transformation. Everything after it is included, and re-running the analysis on the same source is free.
- 5Stage 2 — Analyze
Read the findings before moving on
Each finding names the offending construct, where it sits, and what to do instead. This is the part worth judging the platform on — if the findings do not match what you know about the object, tell us.
You should see: A worklist of findings, each with a severity, a location and a recommendation.
- 6Stages 3 to 7
Walk the rest of the workflow with the stepper
Design drafts the target architecture against released APIs. Transformation generates the RAP or CAP implementation next to the original. Testing generates and runs ABAP Unit tests. Documentation produces BPMN 2.0 and the business-facing procedures. Delivery hands you the package.
You should see: The numbered stepper at the top of every stage, from Upload through to Delivery.
- 7Stage 7 — Delivery
Download the package
An abapGit-compatible ZIP with the generated sources and tests, plus the audit evidence pack — a signed record of what was analysed, by which engine and catalog version, and what it concluded. That signature is verifiable later, which is the point of it.
You should see: Your download, and a completed project on the dashboard you can return to at any time.
Which example should I pick?
Each one is built around a different Clean Core problem. Start small; the thousand-line report is the honest stress test, but it produces a lot to read.
Direct table access that has released SAP APIs available as replacements.
ABAP OO inheritance and awkward SQL joins — the harder end of the range.
File system access, which has no equivalent in ABAP Cloud at all.
Classic BAPI calls and their released OData successors.
Presentation logic welded to data access.
Business rules buried in code instead of configuration.
What a genuinely grown enterprise report looks like — 1,000 lines, many findings.
Something not working?
Write to us. Questions about the output, an object the engine handled badly, a stage that failed — all of it is useful, and a person answers.
info@clean-core.ioWant the background first?
The How-To Guide walks through the same workflow narrated, with the reasoning behind each stage and what the Clean Core paradigm is actually asking of you.
Open the How-To Guide