Find what is actually used
Separate business-critical behaviour from code that survives only because nobody has challenged it.
LIDITECH INSIGHT
SAP Custom Code Clean Core Scorecard
SAP Custom Code Clean Core Scorecard focused on keeping SAP change useful without creating the next generation of technical debt.
WHY IT MATTERS
The decision behind the question
Extensions become a problem when every exception is treated as permanent. The important question is what genuinely differentiates the business, what standard SAP can now handle and where an extension should live.
PRACTICAL METHOD
How to work through it
Use the steps to move from assumption to evidence and then to a decision.
Choose the right home
Use standard, in-app or side-by-side extension patterns according to the requirement.
Control the boundary
Design APIs, events, identity and data ownership so extensions remain upgrade-friendly.
Measure the exception
Keep a reason, owner and review point for every deviation from the core.
WHAT WE EXAMINE
Evidence worth collecting
- Usage and business criticality of current extensions
- ATC findings, upgrade impact and technical dependencies
- Standardisation, retirement, refactoring and side-by-side options
- Security, support and ownership of the future extension model
WHAT YOU RECEIVE
Useful outputs, not shelfware.
We keep deliverables tied to decisions, delivery and ownership. The exact format changes with the workstream; these are the outputs we would expect to leave behind.
01
Custom-code decision register
02
Extension architecture and guardrails
03
Prioritised remediation backlog
WHERE WE FIT
We do not need to replace your existing team to be useful.
Bring us in when clean-core policy is becoming abstract, custom code is blocking migration or teams disagree about where new functionality should live.
TALK TO LIDITECH
Tell us what is getting in the way.
The current problem, the outcome you need and what cannot be disrupted are enough to start.