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
Nothing for a starter example the first time you run it. Any other analysis spends one of your five transformations when it completes. 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 — "5 of 5 left" 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: One recommended example under "Start here", three more chosen for what they show, and the rest behind "More examples" — each card 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
Press Start on the card under "Start here" — Z_MM_PO_APPROVAL, the case the demo project is built on
One click creates the project and opens its workspace, and the start is the analysis: the deterministic engine reads the source and the result is sealed as a signed run. With the model on, the narrative is written into the same run while you watch; without it, the engine’s reading is signed alone. At 552 lines it is a real approval process — vendor block list, price tolerance, approval by department head or manager — and it shows the honest gaps too: two includes the code names but does not contain are marked Not determined, never guessed.
You should see: The first look, about 20 seconds in six steps — the code read, the process recognised, plain names, the rules hard-coded in the program, what could not be determined, and your process as numbered steps beside the map. Pause or skip it at any time.
This is the one step that costs a transformation — except the starter examples, which are free the first time you run each of them. Everything after it is included, and re-running the analysis on the same source is free; starting the same example a second time is an ordinary analysis, counted once it completes. - 4Workspace — Business view
Decide on the rules
The Business view opens with one next step — "Decide on n rules" — then the process as numbered steps in plain words, what it decides and what it changes. For each rule the program hard-codes, answer Keep, Change, Drop or Clarify; a Clarify names the question and who should answer it.
You should see: The business rules, unanswered first, and the next step moving on once every rule has an answer.
- 5Analyze
Open Analyze and read the findings
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 Clean Core Score, a worklist of findings, each with a severity, a location and a recommendation, and a recommended route: in-app ABAP Cloud (RAP) or side-by-side CAP on SAP BTP, part of the SAP Business AI Platform.
- 6Stages 2 to 7
Open the other tools from the workspace
Design drafts the target architecture against released APIs when it opens. Transformation generates the RAP or CAP implementation next to the original. Documentation writes a process description from the code when it opens, with BPMN 2.0 beside it. Testing generates test cases: on the CAP route it runs them against mocks, never in your system; on the ABAP Cloud route you record the ABAP Unit result from your own SAP system. Economics models the upgrade cost on assumptions you enter. Delivery hands you the package.
You should see: The tools bar of the workspace and of every tool, from Analyze through to Delivery — a check where a phase is done, its own mark where work has started, amber where something on record is out of date.
- 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 the project on the dashboard with the state of each phase, to 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.
File system access, which has no equivalent in ABAP Cloud at all.
Classic BAPI calls and their released OData successors.
A change SAP’s key-user tools cover as a whole — custom fields, custom logic, a configuration object and an analytical query, each with its limit — so no code is built.
Business rules hard-coded in the program — and what cannot be determined from the code alone: a dynamic function call and two includes that are not part of the upload.
A call to another system that makes a side-by-side extension on SAP BTP the recommended route — and the CAP package the engine builds for it.
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