SAP's platform for building alongside the core rather than inside it — and what that principle is worth.
SAP Business Technology Platform is SAP's cloud platform for extension, integration, data and analytics. Its purpose is to let you build what your business needs outside the ERP core, so the core stays standard and upgradeable. Integration Suite, Extension Suite, SAP HANA Cloud and SAP Analytics Cloud are all BTP services.
The argument for BTP is the clean core. Every extension written inside the ERP is a cost at every future upgrade, and an obstacle to adopting standard functionality later. Building on a platform alongside the core moves that cost out of the upgrade path. The argument against is that it is another platform to run, secure and pay for.
Cloud Integration, API Management and connectors. The successor to PI/PO for most new integration work.
Build Apps, CAP and the runtimes for custom applications that read SAP data through released APIs.
Managed HANA for data that belongs alongside, rather than inside, the ERP.
Planning and analytics over SAP and non-SAP sources.
Cloud Connector and identity services, which are how the platform reaches an on-premise system securely.
A business wants a supplier portal where vendors update their own details, upload certificates and see payment status. Built as custom ABAP inside the core, it becomes part of the system landscape: in scope for every upgrade regression test, constrained by the core's release cycle, and difficult to expose to the internet safely.
Built on BTP, the portal is a separate application reading and writing through defined APIs. It can be released on its own schedule, it can use current web tooling, internet exposure is handled where that is the intended design rather than bolted onto an internal system, and the core remains clean. The data stays in SAP; only the experience sits outside.
The trade is that you now operate two things rather than one, and the API contract between them becomes an artefact to version and maintain. For a small internal utility that overhead is not worth it and in-core is the right call. For anything user-facing, anything with its own release cadence, or anything you expect to change often, the overhead is repaid at the first upgrade.
| Term | What it means |
|---|---|
| Side-by-side extension | Custom functionality running on BTP rather than inside the SAP core, connected by API. |
| Cloud Foundry / Kyma | The runtime environments BTP offers for deploying applications. |
| Integration Suite | The integration tooling — cloud integration, API management, event mesh, open connectors. |
| CAP | The Cloud Application Programming model, SAP's framework for building BTP services. |
| Destination | Configured connectivity from a BTP application to a back-end system, including authentication. |
An extension that belongs in the core as configuration should stay there. BTP is for what genuinely does not fit.
It is consumption-priced and needs governance. Unmanaged, it becomes a surprise line item.
Extensions read SAP data through released APIs. Without a view of which APIs you depend on, upgrades become uncertain.
BTP is an umbrella over many services. Scope the specific services, not the brand.
| Metric | What it tells you | What distorts it |
|---|---|---|
| Extensions on BTP vs in-core | Whether the clean-core principle is actually being followed or merely stated. | |
| API call volume and latency | The health of the connection between extension and core, and the first thing to degrade under load. | |
| Consumption against commitment | BTP is consumption-priced; unmonitored services are the usual source of surprise invoices. | |
| Services enabled but unused | Subscriptions nobody turned off, which is the most common avoidable cost. |
We build and support the systems this page describes. Start with a free working proof of concept — no cost, no commitment.