Skip to content
Atlas docs

Diff two SAP releases

Compare Studio is how Atlas shows what changed between two SAP releases. Pair ECC 6.0 with S/4HANA 2023, or S/4HANA 2022 with 2023, or the other way around.

Anatomy of a Compare pair RELEASE SCOPES ECC 6.0 EHP8 · source → S/4HANA 2023 · target filter: SD · MM · FI SOURCE BAPI_PO_CREATE1 BAPI · C1 · uses 12 times in corpus atlas:belongsToModule → MM TARGET · SUCCESSOR API_PURCHASEORDER_PROCESS_SRV OData service · C2 released atlas:validForRelease → 2023 CONFLICT GUIDANCE Migration path · priority: critical Replace the BAPI call with the OData service client. The parameter signature changes; see SI-4321 for the mapping between the two. Four affected callers in SD, eight in MM. VBAK Table · ECC row store I_SalesDocument CDS · C2 · replaces VBAK as the read surface Every pair renders its two artifacts above, with guidance below. Expand any row to see its sources.
Compare Studio — paired source/target rows with the conflict guidance underneath.

1 · Pick the release scopes

Section titled “1 · Pick the release scopes”

Click Compare in the left nav. The top strip has two dropdowns: source release and target release. Pick one on each side. If you are inside a case, the two scopes default to the case’s own.

2 · Read the paired diff

Section titled “2 · Read the paired diff”

The main panel pairs artifacts by identity. For each pair:

  • Left column — what exists in the source release (artifact name, type, stability contract)
  • Right column — its successor in the target: a replacement name, a “removed” marker, or unchanged
  • Conflict row below — high-priority migration guidance Atlas attached to the pair

Contract tiers show with traffic-light color: green C2, amber C1, red C0.

3 · Filter

Section titled “3 · Filter”

The filter strip above the pairs lets you narrow by:

  • Module — only SD, only MM, etc.
  • Change type — superseded / deprecated / removed / unchanged
  • Contract tier — show only pairs where one side is C0 or C1
  • Module coverage — pairs that touch an active case’s modules

Filters are client-side against the already-returned data. Toggling them is instant; changing the release scopes re-queries the backend.

4 · Read the conflict guidance

Section titled “4 · Read the conflict guidance”

Each pair expands to show the guidance rows Atlas attached to it: migration paths, deprecation notices, replacement recommendations. Every guidance row has its own evidence — expand further to see which catalog entries, help-portal pages, or released-CDS entries it came from.

This is the same guidance Atlas uses inside Investigate; the Compare view just flips the axis — one question from the graph’s side (what changed in this pair?) instead of the user’s side (what blocks me?).

When to use Compare instead of Investigate

Section titled “When to use Compare instead of Investigate”
  • You are scoping a conversion and want the full drift picture for a module.
  • You are writing the release notes for an internal upgrade.
  • You are auditing whether your custom code still makes sense against the new release’s VDM.

For ad-hoc questions, Investigate is quicker. For systematic coverage, Compare is the right tool.