Back to features
Released-API mapping

SAP Cloudification Catalog

Map legacy objects to their released S/4HANA successors using SAP’s official Cloudification Repository — the same source behind SAP ATC — plus curated field-level mappings.

Stage 1–2 — Analyze & Design

What it is

Every standard object your code touches is matched against SAP’s official Cloudification Repository — the public dataset that also backs SAP ABAP Test Cockpit (ATC) Clean Core checks — enriched with hand-curated field-level mappings to released APIs and CDS views.

The catalog is weekly auto-synced, versioned and audit-traceable, and is browsable as a public reference at /catalog.

What’s possible

  • Look up any SAP standard object’s Clean Core readiness and released successor
  • Direct table reads (e.g. VBAK, BSEG) mapped to released CDS views / OData APIs
  • Versioned & audit-traceable — every mapping is attributable to a catalog version

Honest scope & limitations

  • It is reference data to accelerate assessment — not a replacement for SAP ATC / ADT, which remain the authoritative checks.
  • Objects without a released successor are flagged, not invented; unreleased APIs must be confirmed with SAP before production use.

Related

Free · community-built · complementary to your SAP tooling

Try it on your own code.

Get free access