All demos

Tool 09 · Live demo

Clean Core Scorer

SAP RISE readiness and Clean Core compliance score.

Tool intake · Clean Core Scorer

Upload artefacts (any format), paste free-text context, or rely on your Landscape Intelligence knowledge base. Clean Core Scorer will reason against whatever you provide and sap rise readiness and clean core compliance score.

Build Landscape KB first

0 chars

Drop files or browse

PDF · DOC/DOCX · PPT/PPTX · XLS/XLSX · CSV · TXT · JSON · PNG · JPG · WEBP · HEIC

The algorithm needs context to reason against. Either build the Landscape Intelligence KB, upload one or more artefacts, or describe the status quo in ≥ 20 characters of free text.

17-criteria rubric lifted directly from the A²AI Clean Core Scorer spec. Weights are the production weights; remediation patterns are condensed for the demo.

Clean Core Score

50/ 100

Significant remediation required

17 of 17 criteria below target

By category

Code50%
Extensibility50%
Data50%
Integration50%
UX50%
Security50%
ALM50%
Globalisation50%
Operations50%

17 criteria

Grouped by category — expand to score.

Code2 criteria
50%
  • Zero modifications to SAP standard objects

    weight 10

  • All extensions in customer namespace (Z*, Y*)

    weight 8

Extensibility3 criteria
50%
  • Side-by-side extensions on BTP, not in-stack

    weight 9

  • Use of released APIs only (no private interfaces)

    weight 9

  • Key User extensibility used where possible

    weight 6

Data2 criteria
50%
  • No direct DB access; CDS views for all reads

    weight 7

  • Master data governed via MDG / SAP MDF

    weight 5

Integration2 criteria
50%
  • Integration via SAP Integration Suite / events

    weight 7

  • No file-based or RFC point-to-point interfaces

    weight 6

UX1 criteria
50%
  • Fiori-first UX (no Dynpro / SAP GUI new build)

    weight 6

Security2 criteria
50%
  • Single sign-on via IAS / IdP, no local users

    weight 4

  • Roles via PFCG templates + business catalogs

    weight 4

ALM2 criteria
50%
  • Lifecycle managed via Cloud ALM / Solution Manager

    weight 5

  • Custom code scanned with ATC + Clean Core check

    weight 5

Globalisation1 criteria
50%
  • Localisation done via SAP standard, not custom

    weight 4

Operations2 criteria
50%
  • Output mgmt via BRF+ / Output Control framework

    weight 3

  • Reporting via Analytics Cloud / embedded analytics

    weight 2

Top remediations

Ordered by weighted impact. Tap to read the fix.

01

Zero modifications to SAP standard objects

+5

Replace modifications with implicit/explicit enhancements or BAdIs.

02

Side-by-side extensions on BTP, not in-stack

+4.5

Migrate in-stack extensions to BTP side-by-side runtimes (CAP, Kyma).

03

Use of released APIs only (no private interfaces)

+4.5

Audit usage of unreleased APIs; switch to released equivalents in API Hub.

04

All extensions in customer namespace (Z*, Y*)

+4

Refactor any non-namespaced custom objects into Z/Y namespace.

05

No direct DB access; CDS views for all reads

+3.5

Replace SELECTs with released CDS views (C1/C2 contracts).

06

Integration via SAP Integration Suite / events

+3.5

Route integrations through SAP Integration Suite (CI / API Mgmt / Events).