Skip to content
Atlas docs

What Atlas does

Atlas is a planner for SAP S/4HANA system conversions. You hand it a sentence describing what you want; it hands back an annotated CDS bundle that reflects the best conversion path it can find given your system’s shape, constraints, and history. It picks the objects, the order, and the trade-offs before handoff. Every decision is backed by evidence so you can check it. The transport itself belongs to the customer’s landscape; Atlas records the release when CTS confirms it.

Atlas at a glance

Section titled “Atlas at a glance”
3
audiences
architect · developer · integrator
6
pipeline stages
task → classify → plan → generate → validate → transport
4
evidence tiers
every claim carries one
1
knowledge graph
every fact linked to its source

What you see when you use it

Section titled “What you see when you use it”
The Studio pipeline Task one-sentence description Classify analytics · RAP extension · migration Plan dependency graph + gates Generate CDS · ABAP metadata Validate gate passes tests Transport TR + deploy Six stages. Every transition is a gate. No gate is bypassable.
Studio pipeline — Atlas turns a task description into a transported CDS view through six gated stages.

Six stages separate a sentence from a transport. Atlas runs each of them on every plan, because each one produces an artifact the next one consumes and reviews. Skipping a stage would break the evidence trail the architect is told to rely on.

Between every pair of stages there is a gate — a testable condition Atlas checks before letting the plan advance. Gates can be resolved or overridden with a stated reason; they cannot be skipped. See Gates are non-bypassable for the rule and Resolve a gate for the procedure.

How Atlas decides what to emit

Section titled “How Atlas decides what to emit”
Evidence tiers and the emit threshold 0.98 confidence Tier 1 — first-party structured Simplification Item Catalog, released-CDS list, customer extract. 0.70 confidence Tier 2 — first-party textual api.sap.com entries, SAP help portal official pages. 0.55 confidence Tier 3 — inferred Ontology reasoning over tier-1 / tier-2 facts. 0.40 confidence Tier 4 — snippet / community Never emitted. Ranks manual review only. emit threshold · 0.60 Above the dashed line, Atlas emits without asking. Below, it pauses for human confirmation.
Evidence tiers — four bands, one threshold Atlas never quietly crosses.

Every fact Atlas stores carries a confidence tier. Atlas emits artifacts built on tier-1 and tier-2 evidence; tier-3 and below stop at a proposal until you confirm. The emit threshold is 0.60 — above it Atlas ships, below it Atlas asks. Full treatment: Evidence and confidence.

Who Atlas is for

Section titled “Who Atlas is for”
Technical architect
Deciding whether Atlas belongs in a conversion program. Needs to verify that Atlas understands SAP.
ABAP developer or consultant
Working a specific task on a specific engagement. Needs exact answers anchored to evidence.
Platform integrator
Wiring Atlas into the team's tooling — CI, ATC, Datasphere. Needs contracts and endpoints.

Business stakeholders are served by the naburis.cloud site, not by these docs.

Where to start

Section titled “Where to start”
Run your first investigation
Ten minutes from opening Atlas to reading an evidence-grounded answer about a conversion.
Track a migration as a case
The four-tab workflow Atlas is built around — Resolve, Corpus, Compare, Govern.
Build a pattern in Studio
Classify a task, render its plan graph, emit scaffolds, inspect validation — the full pipeline, hands on.

How to read these docs

Section titled “How to read these docs”

The site follows Diátaxis: four modes, strictly separated.

  • To learn Atlas, start with the tutorials.
  • To solve a specific problem, use the how-to guides.
  • To look something up, use the reference.
  • To understand why Atlas made a call, keep reading the explanation pages.