The first two parts of this series covered RISE with SAP as a transformation methodology and then went deep on one of clean core’s five principles: extensibility, the four-level model that classifies custom code. This third and final part covers the other four — business processes, data, integration, and operations — and the measurement framework SAP uses to score all five together.
Analysis | ~13 min read | By J. Torre
In brief
- SAP’s clean core strategy rests on five principles, not one: Business Processes, Extensibility, Data, Integration, and Operations. Part 2 of this series covered Extensibility in isolation; this piece covers the remaining four.
- All five report into a single structure SAP calls the Clean Core Measurement Framework, built on two parts — Governance & Maturity and KPIs — and made visible through the RISE with SAP Methodology dashboard in SAP Cloud ALM.
- Data got its own scoring model in February 2026: a Data Volume Efficiency practice with named KPIs (unused data, redundant indexes, outdated records, custom table footprint) rather than a single “clean or not” flag.
- Integration got an A-through-D classification system of its own in 2026, defined in SAP Note 3690029 — structurally the same idea as the extensibility levels from Part 2 (SAP Note 3578329), applied to interface technologies instead of ABAP objects.
- Business Processes is measured mainly through fit-to-standard adoption: the share of a customer’s processes that run on SAP Best Practice content without deviation.
- Operations is measured through a System Health Score and an Operations Index, both generated from the dashboard’s Operations View, covering connectivity, background job quality, and exception handling.
- SAP has published two customer figures for what following all five principles produces in practice: Hitachi High-Tech reported a 94% reduction in its customization footprint and 18x faster handling of solution updates; Accenture reported removing 21% of custom code from its core SAP applications within six months.
One framework, five principles
Part 1 of this series described RISE with SAP as a methodology built around three components, one of which was a governance structure meant to keep customers on a “clean core” as they move into the cloud. Part 2 went under the hood of exactly one piece of that governance structure: the four-level system (A through D) that classifies custom ABAP code by how safely it survives an upgrade.
Extensibility is the most visible of SAP’s clean core principles because it maps directly onto something developers already think about — code. But SAP’s own documentation is explicit that extensibility is one of five, not the whole strategy. The other four are Business Processes, Data, Integration, and Operations, and SAP treats them as equally scored, not as afterthoughts to the code question.
The clearest evidence of that equal treatment is a measurement structure SAP calls the Clean Core Measurement Framework, described in a company blog post published in September 2026. The framework has two parts that are meant to reinforce each other:
- Governance & Maturity covers the “how” — the tools, governance models, and expertise a customer needs to reach and hold a clean core. It is assessed through engagements with an assigned SAP Enterprise Architect and produces a roadmap with timelines and assigned responsibilities, feeding directly into the Quality Gates (Q-Gates) that already exist at each phase of a RISE with SAP project.
- KPIs are the quantitative side, pulled from system data collected across the project lifecycle. SAP groups them by principle: fit-to-standard adoption for Business Processes; the A-through-D distribution of custom objects (plus a Technical Debt Score) for Extensibility; data volume efficiency, unused data, redundant indexes, and outdated records for Data; integration stability, error rates, and standard-API adoption for Integration; and system health, connectivity, background job performance, and exception management for Operations.
Both halves surface in the same place: the RISE with SAP Methodology dashboard, hosted in SAP Cloud ALM — the same dashboard Part 1 referenced as part of RISE with SAP’s governance tooling. The dashboard has two main views. The System View tracks the software stack and the extensibility KPIs from Part 2. The Operations View, covered later in this piece, tracks day-to-day system health. SAP says it is adding views and automating a larger share of the KPI calculation with each quarterly release, so the dashboard’s coverage of all five principles is not static.
Business Processes: fit-to-standard as the default
Of the five principles, Business Processes is the least technical and the hardest to reduce to a single number, but SAP’s model for it follows the same logic as the others: define a standard, then measure distance from it.
The standard is SAP Best Practice process content — the pre-built process variants SAP ships for SAP S/4HANA Cloud. “Fit-to-standard” is the name SAP gives to the workshop methodology, run during SAP Activate implementation phases, where a customer’s process owners walk through this content and decide, process by process, whether to adopt it as-is or request a deviation. A clean core approach treats every deviation as something that has to be justified, documented, and tracked — the opposite of the older approach where custom process variants accumulated by default because nobody had to argue against them.
The KPI SAP attaches to this principle is the fit-to-standard adoption rate: the share of a customer’s business processes running on unmodified or lightly modified SAP Best Practice content, rather than custom variants. Business process governance — documenting process ownership, mapping deviations against a business process hierarchy, and reviewing that map on a fixed cadence rather than once at go-live — is what keeps the rate from drifting back down after the initial implementation.
This is also the principle most directly connected to what Part 1 called governance from the first workshop onward: fit-to-standard decisions made during implementation are exactly the discipline that a Business Processes KPI is designed to catch later if it erodes.
Data: what the dashboard actually measures
Data is the newest of the five principles to get a dedicated scoring model. SAP introduced a Data Principle on the RISE with SAP Methodology dashboard in February 2026, described in a company blog post as “the starting point of the data journey” rather than a finished feature — the initial release covers data volume specifically, with SAP saying further KPIs for other data practices are planned.
The data volume efficiency KPIs shipped in that release are:
- Data volume efficiency — an overall percentage score summarizing how efficiently a system stores and uses its data.
- Unused data — uncompressed data volume that has not been accessed in the last 30 days.
- Redundant data — the total volume of unused table indexes.
- Outdated data — data volume that has aged past the residence time defined in SAP Best Practice.
- Custom table footprint — the total volume held in custom (Z-table) objects, as distinct from standard SAP tables.
- HANA memory and HANA disk — direct visibility into how data volume translates into infrastructure consumption.
SAP frames the business case for tracking these in fairly concrete terms: unused, redundant, and outdated data drives up HANA memory consumption and infrastructure cost, slows system performance, and — the point most relevant to a clean core discussion — increases risk during upgrades and transformations, because every gigabyte of data a migration has to move or validate is a gigabyte that can go wrong. The dashboard is explicitly positioned to turn data cleanup from a one-time step bolted onto a migration project into a continuous, measured activity, the same shift in framing SAP applied to extensibility with the four-level model in Part 2.
Data quality in the broader sense — duplicate vendor records, inconsistent material classifications, harmonization across legacy cost center hierarchies — sits under the same principle but is not yet covered by a published dashboard KPI in the same way volume is; SAP’s own description of this release treats it as a later phase of the same “data journey.”
Integration: an A-through-D system of its own
The parallel to Part 2 is most direct here. In 2026, SAP published Note 3690029, which does for integration technologies what Note 3578329 (covered in Part 2) already did for ABAP extensibility: it classifies interface technologies, protocols, and patterns into a level-based system rather than leaving “integration” as a single undifferentiated category.
The note rates each integration technology against two criteria — Public Cloud readiness (whether it is supported in SAP S/4HANA Cloud, public edition) and alignment with modern integration standards (whether it follows established cloud and internet standards, event-driven architecture, and an API-managed approach) — and assigns a level from A to D on that basis. As with extensibility, Level A represents the strategic, cloud-ready choice; lower levels represent technologies that may still work today but carry more risk and less headroom for the future. As of a July 2026 update, the note’s scope was extended to cover data integration technologies specifically, alongside the SAP API Policy.
SAP’s Clean Core Integration White Paper, published in August 2026, builds on that classification to describe three architecture patterns a customer chooses among when designing an integration: central middleware, API-managed connectivity, and event-driven integration. It pairs those patterns with a governance layer — the SAP Integration Solution Advisory Methodology (ISA-M), an Integration Center of Excellence, and a Solution Standardization Board — and describes two separate paths for getting there: a “stay clean” path for new integrations built correctly from the start, and a “get clean” path for modernizing existing ones, including the RFC/BAPI-based interfaces that predate the current model.
That modernization path has a concrete, dated entry point: SAP’s Clean Core Modernization Recommendations for BAPIs, released in the third quarter of 2025, let architects automatically identify BAPIs still in use in older PI/PO interfaces and match them against modern equivalents published in the SAP Business Accelerator Hub — the same catalog of released APIs and events that Part 2 referenced in the context of extensibility.
The KPI framework SAP proposes for integration mirrors the structure used elsewhere: upgrade stability, operational risk, innovation adoption, and toolchain adoption, plus the more direct operational metrics named in the Clean Core Measurement Framework — integration stability, error rates, and the share of integrations built on standard, released APIs rather than point-to-point connections.
Operations: keeping it clean after go-live
Operations is the principle most explicitly about what happens after a transformation project ends rather than during it. SAP’s own description frames it as a cross-dimension discipline — embedding governance, people, process, and tooling practices that keep the other four principles from degrading once the initial project team has moved on.
The dashboard’s Operations View is where this becomes measurable. It reports daily on system health, connectivity, exception handling, background job quality, and performance across key business processes, and aggregates the results into two composite scores: a System Health Score and an Operations Index, intended to give both program teams and day-to-day operations teams a single view of run quality rather than a set of disconnected alerts.
The framing SAP uses for why this matters is direct: a system with a strong operations score absorbs security patches faster and adopts new capabilities — including the AI-related features SAP is building into SAP Cloud ERP Private Edition — without the months of regression testing a poorly governed landscape requires. That connects Operations back to the other three principles covered in this piece: fit-to-standard processes, a managed data footprint, and a governed integration layer are all inputs that make a high Operations score achievable, rather than something Operations produces on its own.
What the numbers show
SAP has published two customer figures specifically tied to following clean core principles across a RISE with SAP journey, both cited in the same September 2026 measurement framework post:
- Hitachi High-Tech reported a 94% reduction in its customization footprint and 18x faster handling of solution updates.
- Accenture reported removing 21% of the custom code from its core SAP applications within six months of adopting the strategy.
Both figures come from SAP’s own published materials rather than independent audits, and SAP has an obvious commercial interest in the strategy these customers are held up as validating — a competing interest worth stating plainly rather than leaving implicit. Neither figure specifies a comparison baseline in enough detail to independently verify the percentage calculation, and “customization footprint” is not a term with one fixed definition across SAP’s own documentation. Read as directional evidence that the five-principle model produces measurable change rather than as an audited benchmark, they are consistent with the mechanism the rest of this piece describes: once code, data, integrations, and processes are all scored against explicit standards instead of judged case by case, reduction becomes something a team can target and report, not just something they claim.
Closing the series
Across three parts, this series has covered RISE with SAP as it exists today: a methodology and governance framework, not a single hosting product, built to move customers into SAP Business Suite in the cloud while holding them to a clean core. Part 1 covered the methodology itself. Part 2 covered the first and most technical of clean core’s five principles, extensibility, in detail — the four-level classification, the on-stack versus side-by-side decision, and the KPIs tied to code. This piece covered the other four: fit-to-standard as the measure for business processes, a dashboard-based scoring model for data that is barely a year old, an A-through-D classification for integration technologies built on the same logic as extensibility’s, and an operations discipline meant to keep all of it clean after the project team disbands.
Taken together, the picture is less a single “clean core” checkbox than five separate, independently scored disciplines that happen to report into the same dashboard. That is arguably the more useful way to understand the strategy: a customer can be well ahead on extensibility and still behind on data, or fit-to-standard on paper while running integrations that haven’t been touched since a PI/PO migration a decade ago. The measurement framework exists specifically to make gaps like that visible rather than let a single average score hide them — which is also the most direct way to check any vendor’s claim that a given SAP landscape has “gone clean core.”
Sources
Getting to a Clean Core – The new maturity model of extensions into four distinct levels (A,B,C,D)
5 guiding principles of clean core — SAP
Introducing the Clean Core Integration White Paper — SAP Community, August 5, 2026
Modernizing RFC/BAPI-based Integrations for a Clean Core with SAP Integration Suite — SAP Community
Exploring How to Make Business Processes Clean Core Compliant — SAP Learning
