Manufacturing groupECC to S/4HANA conversion
Sole owner of custom code remediation on a live conversion: ATC and simplification-item analysis, SPDD and SPAU, CDS and OData for Fiori.
Custom code remediation
S/4HANA custom code remediation, done by senior ABAP engineers.
Your custom code is usually the largest single risk in an ECC to S/4HANA conversion. Some of it will break, some of it will run slowly on HANA, and a good part of it nobody uses any more. Our remediation team works out which is which, fixes what has to change, and hands back code that has been tested and documented.
Talk to an ABAP remediation leadWhat we remediate
What gets fixed.
The work that decides whether custom code survives the move to S/4HANA.
01
ATC findings
Findings from the S/4HANA readiness checks, fixed at scale and consistently.
02
Simplification items
Changed data models, replaced tables and removed transactions that touch your objects.
03
SPDD and SPAU
Dictionary and repository adjustments during the upgrade, handled cleanly.
04
Performance on HANA
Slow selects and nested loops fixed, with code pushed down to CDS or AMDP where it pays.
05
Unused code
Identified early, so you do not pay to fix what you can retire.
How it runs
Four steps from analysis to handover.
You see the plan and approve it before any code is changed.
01
Analyse
We run ATC and usage analysis on your system and size the work by object, finding and complexity.
02
Triage
Every object lands in one of three buckets: retire, fix or rebuild. You approve the list before fixing starts.
03
Fix
Engineers work through the backlog in batches, with a named remediation lead reviewing the quality of every fix.
04
Test and hand over
Changes are unit tested and supported through your integration and user testing. You receive documentation of what changed and why.
What you get
What you receive.
Outcomes you can check, not effort you have to trust.
A prioritised backlog
Retire, fix and rebuild decisions for every object in scope.
Clean custom code
Code that runs on S/4HANA, with tested and documented changes.
A team that can stay
The same engineers can carry on into build, cutover and support, so the people who know the code remain on it.
Experience
Remediation our engineers have already done.
Clients are described by type.
Medical-device manufacturerRegulated upgrade and migration
ECC to S/4HANA migration with more than 20 BAPIs for a shop-floor system interface and 400+ test defects resolved, under FDA compliance.
Who this is for
Enterprises and SAP partners.
Enterprises converting from ECC that need remediation capacity they can rely on, and SAP partners and system integrators that need senior remediation engineers inside their own programme. See the page for SAP partners ↗
Questions
Common questions.
Scope, time, cost and how we work with your team.
How long does S/4HANA custom code remediation take?
It depends on how many custom objects are in scope, how many of them are actually used, how old the code is and how heavily it touches the areas SAP has simplified. That is why we start with an analysis: you get an effort estimate based on your own system rather than a generic figure.
How much does custom code remediation for S/4HANA cost?
It depends on the scope of the work. We agree the scope with you first, based on an analysis of your own system, and the commercial terms follow from that.
Do you retire unused code or fix everything?
We identify unused code first and recommend retiring it. Fixing code nobody runs is the most common way remediation budgets get wasted. You approve the retire list.
What is the difference between remediation and rebuilding?
Remediation adapts existing code to S/4HANA. Rebuild replaces an object with a modern equivalent, such as CDS, RAP or a Fiori-ready service, when adapting it would cost more than it is worth. Our triage step decides which applies to each object.
Can you work on our system remotely?
Yes. The team works through your remote access and your change process, and reports through a named delivery lead. We can provide the time zone overlap your project needs; the requirement should be clear while we scope the work.
Do you only remediate, or can you do the full conversion?
Both. Remediation can be a standalone engagement, or part of the full conversion pod covering build, Basis, cutover and L2 and L3 support.
Do you work with SAP partners and system integrators?
Yes. Many remediation engagements run inside a partner programme. See the page for SAP partners.
Let’s talk
Tell us about the conversion you are planning.
A short note is enough. We reply within one working day with the questions that matter and a view on how a pod would work for your landscape.
Thank you. We have your request and will reply within one working day.