Brian Jacob Sanchez

Clean Core Transformation

Future-proof your S/4HANA landscape

Assess and remediate modifications, enhancements, and custom code to align with SAP's clean-core principles.

Service overview

Clean core technical assessment and remediation planning for brownfield S/4HANA landscapes, covering modifications, enhancements, custom objects and the extensibility model behind them.

The assessment classifies the existing custom estate against SAP clean core guidance and identifies where key-user extensibility, developer extensibility or side-by-side extensions on SAP BTP are the appropriate target.

The result is a scorecard and a staged roadmap that a team can actually execute alongside normal delivery, rather than a single large rewrite.

Problems this service addresses

  • Excessive custom modifications of SAP standard objects
  • Clean core compliance issues raised during audits or upgrades
  • No clear rule for when to extend in-stack versus side-by-side
  • Enhancements with no documented owner or business justification
  • Technical debt that grows with every release

Who this is for

  • SAP program managers
  • SAP technical leads
  • S/4HANA transformation teams
  • Organizations preparing for an upgrade

Scope and deliverables

Scope of work

  • Clean-core assessment
  • Side-by-side extension design
  • Key-user vs developer extensibility
  • ABAP Cloud readiness

Deliverables

  • Clean-core scorecard
  • Remediation roadmap
  • Reference implementation

Technologies and capabilities

  • SAP S/4HANA
  • ABAP Cloud
  • SAP Clean Core
  • RAP
  • CDS views
  • SAP BTP
  • ATC
  • Eclipse ADT
  • Released SAP APIs

Engagement approach

  1. 1

    Discovery and access review

    Short qualification call, confirmation of scope, systems, releases and the technical access required.

  2. 2

    Technical assessment

    Hands-on analysis in your system using ADT, ATC, trace and analysis tools relevant to the scope.

  3. 3

    Findings and prioritization

    Findings written up with severity, effort indication and a prioritized backlog agreed with your team.

  4. 4

    Implementation or remediation

    Agreed changes implemented in transports, with code review against your standards.

  5. 5

    Testing and knowledge transfer

    Testing evidence handed over plus a walkthrough session so your team can continue the work.

Expected outcomes

  • Supports upgrade readiness by shrinking the modified estate
  • Reduces unnecessary custom modifications over successive releases
  • Strengthens technical governance with documented extensibility rules
  • Improves maintainability of extensions

Outcomes depend on system landscape, code base and available access — no fixed results are guaranteed.

Related proof and reading

See more anonymized SAP engagement case studies, SAP technical articles on ABAP and S/4HANA, or read about Brian Jacob Sanchez's SAP experience.

Frequently asked questions

Book a technical assessment

Talk through your clean core transformation requirement with Brian Jacob Sanchez in a free 30-minute technical conversation.

Book a technical assessment