Services · 02
SAP architecture & clean core
Target architecture, extension strategy on SAP BTP and integration design from a single source.
Fact sheet
- Duration
- 4–12 weeks
- Format
- Architecture mandate, also as a second opinion
- Deliverables
- 5 deliverables
Decades of custom development make every upgrade expensive and every decision risky.
Many SAP landscapes have grown over decades: thousands of Z objects, point-to-point interfaces and modifications nobody fully understands any more. Every upgrade becomes a major project.
A clear target architecture with binding clean-core rules ensures that S/4HANA does not become as heavy as the old system within a few years.
Deliverables
- S/4HANA target architecture including surrounding systems
- Clean-core guidelines with a decision tree for extensions
- Custom-code assessment with a reduction plan
- Integration strategy (APIs, events, middleware)
- Architecture board process for ongoing decisions
Approach
- Step 01
Current architecture
Capture and assess systems, interfaces and custom developments.
- Step 02
Principles
Agree clean-core rules and extension strategy with IT and the business.
- Step 03
Target picture
Design the target architecture and integration patterns and test them against use cases.
- Step 04
Embed
Set up an architecture board so the rules hold in everyday project work.
Frequently asked questions
Does clean core mean “no custom development”?
No. It means building extensions so that they do not block upgrades — via released interfaces, key-user extensibility or side-by-side on SAP BTP.
Do we need SAP BTP for this?
Not necessarily. The platform decision is part of the architecture work and depends on your integration and operating requirements.