Skip to content
Atlas docs

Track a migration as a case

A case is the persistent home for an Atlas investigation — the thing you open on Monday, come back to on Wednesday, and hand to a teammate on Friday. This tutorial walks the four tabs a case rotates through: Resolve, Corpus, Compare, Govern. About fifteen minutes end to end.

A case rotates through four tabs CASE Sales-order readiness on S/4HANA 2023 SD · MM · FI · clean-core TAB 1 Resolve run investigations Natural-language queriesanchored to the case.Pin findings to thetimeline. TAB 2 Corpus check freshness Per-source fetchtimestamps. Stalesources downgrade theconfidence of anythingthat cites them. TAB 3 Compare diff two releases Paired artifact diffbetween source andtarget. Conflictguidance attached toeach pair. TAB 4 Govern read the scorecard Compliance %, clean-corecoverage, deprecatedAPIs, top risks — thecase-level view of/control. Every tab is scoped to the case's modules and release pair. Switching tabs keeps the context.
Case tabs — one case, four surfaces, same context.

What you will build

Section titled “What you will build”

A case titled “Sales-order readiness on S/4HANA 2023” with one pinned deprecation, a corpus freshness snapshot, a diff between two releases, and a governance reading. By the end you will have used every section of Atlas a day-to-day conversion team relies on.

1 · Create the case

Section titled “1 · Create the case”

Click Cases in the left nav, then + New case. Fill the form:

  • Title — “Sales-order readiness on S/4HANA 2023”
  • Owner — yourself
  • Modules — SD, MM, FI
  • Posture — clean-core
  • Source → target — ECC 6.0 EHP8 → S/4HANA 2023

Submit. Atlas opens the case on the Resolve tab.

2 · Resolve — run an investigation anchored to the case

Section titled “2 · Resolve — run an investigation anchored to the case”

The Resolve tab is an Investigate view scoped to this case’s modules. Ask a question like “which SD BAPIs are deprecated in the target release?” and press Ask. Atlas returns the blockers with full evidence; click into one and Pin to case attaches it to the case’s timeline.

You can run Resolve queries as many times as you like. Every one becomes an evidence row on the case.

3 · Corpus — check what Atlas has read

Section titled “3 · Corpus — check what Atlas has read”

Switch to the Corpus tab. This is the freshness view: for each source Atlas ingests (Simplification Item Catalog, api.sap.com, released-CDS list, SAP help portal), you see when it was last fetched and how many documents in it touch your case’s modules.

4 · Compare — diff two releases

Section titled “4 · Compare — diff two releases”

Switch to the Compare tab. Atlas pre-fills the two release scopes from the case (ECC 6.0 EHP8 vs S/4HANA 2023). The main panel pairs artifacts side by side:

  • on the left, what exists in the source release
  • on the right, its successor (or “removed” marker) in the target
  • a conflict-guidance panel below pointing out the high-priority migrations

You can filter by module, artifact type, or stability contract (C0 / C1 / C2). Each row is a graph traversal that shows its sources when you expand it.

5 · Govern — read the scorecard

Section titled “5 · Govern — read the scorecard”

Switch to the Govern tab. The scorecard has four numbers and a top-risks list:

  • Compliance % — how much of the case uses released APIs versus private / deprecated bindings
  • Clean-core coverage — how much is on BTP vs modifying the core
  • Deprecated APIs in use — a direct count Atlas derives from the Resolve findings
  • Released coverage — how many modules have at least one A_ (C2) replacement candidate

Each module gets its own row; expand one to see why the number is what it is.

Where to go next

Section titled “Where to go next”