SAP Business Technology Platform
BTP is where SAP wants your extensions, integrations, and custom UX to live. The architecture to get there needs to fit your landscape — not just SAP's roadmap.
The situation you're in
SAP says BTP. Your landscape says it's complicated.
Clean core changes where custom logic lives
Side-by-side on BTP, in-app extension, key user config — the options exist, but the right split depends on your landscape.
PI/PO is going away — but the successor isn't obvious
Integration Suite is the default answer. Whether it's the right one depends on what else BTP does in your architecture.
The user entry point is moving to BTP
Work Zone replaces the on-premises launchpad. Custom apps run on BTP. Your UX architecture needs to account for both worlds during transition.
Identity spans more systems than before
Cloud Identity Services, your corporate IdP, SAP user management — BTP adds another trust layer that needs to work end-to-end.
Architecture that connects BTP to your reality
We design the BTP architecture together with your SAP and infrastructure teams — not on a whiteboard in isolation.
Define what BTP is responsible for
Extension runtime, integration layer, UX platform, identity broker — or a combination. Scoped to what your landscape actually needs.
A transition path that keeps things running
On-premises and BTP coexist for years. The architecture needs to handle both — not just the target state.
Connect the dots to existing consulting areas
BTP decisions affect your cloud architecture, your integration patterns, and your identity setup. We work across those boundaries.
Let's talk about your BTP architecture
Tell us where you are with BTP — we'll follow up with concrete next steps.
We care about your privacy. Read our privacy policy.
Architecture by domain
Four areas where BTP decisions shape your landscape — each with its own architectural challenges.
Clean core is an extension strategy, not a cleanup project
SAP's clean core model defines where custom logic can live — in-app via released extension points, side-by-side on BTP, or as key user configuration. The challenge isn't understanding the options. It's mapping your existing customizations to the right target and sequencing the migration alongside your S/4HANA timeline.
- Custom code disposition and target mapping
- Side-by-side extension architecture on BTP
- Key user extensibility setup and governance
- Extension migration sequencing
Integration Suite replaces PI/PO — but the architecture is new
PI/PO is approaching end of maintenance. Integration Suite is the strategic successor — but the migration isn't a 1:1 move. The architecture depends on whether BTP serves as your central integration layer or just handles specific hybrid scenarios. That decision shapes Cloud Connector topology, API strategy, and how event-driven patterns fit alongside existing interfaces.
- PI/PO to Integration Suite transition
- Event-driven patterns with Event Mesh
- Cloud Connector topology and connectivity
- API design for hybrid consumers
Work Zone changes how users reach SAP
SAP Build Work Zone is becoming the standard entry point — replacing on-premises Fiori launchpad and bringing custom BTP applications, standard Fiori apps, and third-party content into one place. The architecture decision isn't just 'use Work Zone' — it's how to handle the transition while both on-premises and BTP UX coexist.
Identity propagation across the full chain
BTP introduces SAP Cloud Identity Services as an identity broker between your corporate IdP and SAP systems. Principal propagation, token exchange, and trust configuration need to work from the browser through BTP into your on-premises backend — across every integration path, not just the happy path.
- Cloud Identity Services configuration
- Corporate IdP federation (Entra ID, ADFS)
- Principal propagation to on-premises backends
- Authorization concept across BTP and S/4HANA
Connected consulting areas
BTP architecture ties into decisions we cover in depth on dedicated pages.
Figuring out where BTP fits?
Whether it's clean core, PI/PO replacement, or a Work Zone rollout — let's work through the architecture.