Find what is actually used
Separate business-critical behaviour from code that survives only because nobody has challenged it.
SAP · UK & EUROPE
SAP Custom Code & Clean Core
SAP Custom Code & Clean Core focused on keeping SAP change useful without creating the next generation of technical debt.
REPRESENTATIVE CHALLENGE · NOT A CLIENT CLAIM
SITUATION
SAP Custom Code & Clean Core
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.
WHY IT BECOMES DIFFICULT
SAP Custom Code & Clean Core focused on keeping SAP change useful without creating the next generation of technical debt.
LIDITECH INTERVENTION
How we would take control of the difficult part.
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.
EVIDENCE TO COLLECT
What we would want to see.
- 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
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.