Clean Core

Identify what should stay in the SAP core, what should move to BTP, and what should be retired.

The Clean Core Extension Assessment is a structured review of your custom SAP code — classifying every Z-object and modification against SAP's clean-core standard and producing a prioritized migration roadmap.

Assess your extensions See how it works
The Problem

Custom code is the number one blocker for SAP Cloud adoption.

Years of modifications, Z-programs, and custom enhancements accumulate silently — until the moment you try to upgrade or move to SAP Cloud, and everything stops.

  • Thousands of Z-objects with no documentation and unknown business owners
  • SAP upgrades blocked or heavily tested because of core modifications
  • Cloud migration scope overestimated because nobody knows what custom code is actually used
  • Annual maintenance costs inflated by code that no longer serves a business purpose
  • No roadmap for how to move from where you are to a clean-core architecture
The Outcome

A complete picture of your custom code — and a clear path to clean core.

  • Full inventory of custom objects with usage frequency and business criticality
  • Classification of every object: Retire / Keep / Migrate to BTP
  • BTP extension candidates with recommended approach for each
  • Realistic effort estimates and phased migration roadmap
  • Reduced cloud migration scope and cost baseline for vendor negotiations
Our Framework

Three verdicts. Every object gets one.

We classify your custom code using SAP's clean-core extensibility model combined with real usage data from your system — not just a theoretical framework.

Classification What it means Typical examples Next action
Retire Object has no active users, no business function, or duplicates standard SAP functionality Unused Z-reports, deprecated workarounds, replaced form outputs Decommission — reduce maintenance scope immediately
Keep Object uses standard SAP extensibility (BAdI, CDS View, RAP) — already clean-core compliant Enhancement implementations, standard BAdi exits, key-user extensibility Document and govern — no migration needed
Migrate to BTP Object modifies core tables or uses non-standard ABAP techniques — must move to BTP side-by-side Core-modifying user exits, Z-tables with business logic, custom reports on standard tables Design BTP extension and plan phased migration
The Process

How the assessment works.

Five structured phases. Minimal disruption to your team. Maximum clarity on your custom code landscape.

01

Object Extraction

We extract the full inventory of custom objects from your system using standard SAP tools — Z-programs, BAdi implementations, enhancements, modifications, and Z-tables.

Day 1–2
02

Usage Analysis

We analyze transaction usage logs to identify active vs. dormant objects — filtering out the code that nobody uses before spending time classifying it.

Days 2–3
03

Technical Classification

Senior ABAP architects review active objects against SAP's clean-core extensibility model and assign a classification: Retire, Keep, or Migrate to BTP.

Days 4–7
04

Business Validation

We run a short validation session with your key process owners to confirm business criticality and identify any objects flagged incorrectly by technical analysis alone.

Days 8–9
05

Roadmap & Report

We deliver the full classification report, phased migration roadmap, BTP extension candidates list, and a 90-minute readout with your team.

Day 10
What You Receive

A complete clean-core action plan.

  • Custom Code Inventory — full list of all Z-objects with usage frequency, technical type, and business process mapping
  • Classification Report — every object classified as Retire / Keep / Migrate with documented rationale
  • BTP Extension Candidates — prioritized list of Migrate objects with recommended BTP pattern (side-by-side app, iFlow, SAP Build workflow)
  • Phased Migration Roadmap — 3-horizon plan (quick wins / mid-term / long-term) with effort estimates per object group
  • Quick Win List — objects that can be retired immediately with zero risk, for fast scope reduction
  • Readout Session — 90-minute walkthrough with your IT leadership and key process owners to discuss findings and priorities

Use the results regardless of what comes next.

The assessment report is yours to use — for internal planning, SAP partner negotiations, board approval, or as a baseline for your cloud migration RFP. No lock-in.

Clients typically retire 40–60% of custom code immediately after receiving the quick win list.

Ideal For

This assessment is right for you if...

You are planning a migration to SAP S/4HANA Cloud and need to understand your custom code debt before committing to scope

You received a migration quote that seems too large — and you want an independent view on what can actually be retired or simplified

Your SAP upgrade cycles take too long because of the custom code regression testing required

You want to adopt clean-core principles gradually and need a prioritized roadmap to guide the work

You are an SAP partner who needs a clean-core baseline for a client engagement or presales proposal

You want to reduce your annual SAP maintenance costs by decommissioning unused custom objects

Why Frontino IT

Clean core is not a trend for us — it is how we build.

Every project we deliver starts with a clean-core lens. We know which objects to keep, which to retire, and which to move to BTP.

ABAP and BTP architects

Our senior architects understand both the legacy ABAP landscape and the BTP extensibility model — so classifications are technically accurate, not just theoretical.

SAP-aligned classification

We use SAP's official clean-core extensibility tiers as the classification standard — ensuring your roadmap is compatible with SAP's upgrade and cloud direction.

Business context included

Technical classification alone misses objects that are unused by the system but still required by the business. We validate with process owners before finalizing the report.

Actionable, not academic

The roadmap is built to be executed — with effort estimates, priorities, and BTP patterns you can hand to a delivery team or use to issue an RFP.

Common Questions

Frequently asked questions.

For a full assessment we use standard SAP transactions to extract the object inventory and usage statistics. This requires read-only access or a data export from your BASIS team. We provide a precise extraction guide so your team can prepare the files without giving us direct system access if that is preferred.
The standard assessment covers up to 2,000 active custom objects within the 5–10 business day timeline. For larger inventories (enterprise SAP landscapes with 5,000+ objects), we scope the assessment in phases — starting with the highest-impact process areas. We will advise on the right approach after reviewing your initial inventory.
Many clients use the assessment as the starting point for a BTP Integration Sprint or a broader clean-core migration engagement with Frontino IT. If you want to move directly from assessment to execution, we can design the follow-on scope based on the roadmap findings — no need to restart from scratch.
The assessment is designed for SAP ECC and S/4HANA on-premise environments — where custom code accumulates over years. It is most valuable as a preparation step for a move to SAP Cloud, but it also delivers immediate value for ECC environments where upgrade cycles are slowed by custom code regression testing.
We sign an NDA before receiving any data. The object inventory and system information are used solely for classification purposes and are not shared with any third parties. All deliverables are returned to you — we do not retain client system data after the engagement closes.
Start the Assessment

Tell us about your SAP landscape and we will confirm the scope.

A short intake call is all we need to confirm your custom code volume, agree on the assessment scope, and set a start date.

Timeline

5–10 business days from intake to report delivery.

Deliverable

Classification report, BTP extension candidates, phased roadmap, and readout session.