What usually goes wrong
The problems we get called about.
- Code that blocks your upgrade.Custom objects flagged in every readiness assessment, never remediated because nobody is confident enough to change them.
- Modifications where extensions would do.Core modified years ago for a reason nobody remembers, now a permanent upgrade tax.
- No standards, so no consistency.Five developers over eight years, five approaches, no review process, no naming convention anyone follows.
- Manual work that should have been automated.Processes still run by someone copying between transactions because automating it never reached the top of a backlog.
- Developer dependency.One person who understands the custom landscape, and everyone quietly aware of what happens if they leave.
What's included
Scope, in plain terms.
- New development.ABAP, RAP where the release supports it, CDS views, OData services, Fiori extensions.
- Remediation.Custom objects assessed and reworked to clean-core patterns ahead of an upgrade.
- Reusable components.Common patterns built once properly instead of five times badly.
- Process automation.Manual steps replaced with scheduled, monitored, logged jobs.
- Code review.Independent review of existing custom code, with a written register of findings by risk.
- Standards and enablement.Development standards documented and handed to your internal team.
Code is read far more often than it is written. Most SAP custom development is optimised for the wrong one of those.
Free, no obligation
Let's look at one problem properly.
One problem area, examined by an engineer. You get a written findings note and a fixed-price proposal. No charge, no obligation.
Book a 45-minute technical review →