SAP BTP
The extension platform, governed from day one.
- Multi-cloud subaccounts
- Cloud Foundry
- Kyma
- SAP Build
- BTP Cockpit
- Trust configuration
SAP · Technology, Integration & Experience
The platform layer: clean core, evolvable core.
Clean core on S/4HANA. Extensions on SAP BTP. Integrations through CPI and API Management. Fiori-first UX. The platform layer that keeps SAP evolvable.
Every SAP customer eventually inherits ten years of custom ABAP in the core. Phoenix designs the technology, integration and experience layer to prevent that: extensions on SAP BTP, integrations through CPI + API Management, Fiori-first UX on top of a clean S/4HANA core.
Clean core isn't a slogan; it's the choice that decides whether the next upgrade takes a weekend or a quarter. Everything below is designed around that choice.
What's in scope.
Integration
One observable hub instead of point-to-point spaghetti.
- Cloud Integration (CPI)
- API Management
- Event Mesh
- Open Connectors
- PI/PO (legacy)
- IDoc / OData / REST
Extensions & Development
Modern stacks that attract modern developers.
- ABAP RESTful (RAP)
- CAP (Cloud Application Programming)
- SAPUI5 / Fiori
- SAP Build Apps
- Steampunk (ABAP Environment)
Experience (UX)
A single, mobile-friendly surface for end users.
- Fiori Launchpad
- Fiori Elements
- Work Zone
- Mobile Start
- Personalisation
- Accessibility
Identity & Security
SSO and provisioning wired into the platform.
- SAP Cloud Identity
- SSO
- SCIM provisioning
- OAuth
- GRC integration
DevOps
Standard git workflows and CI/CD for SAP artefacts.
- Transport Management
- gCTS
- Piper / Jenkins
- CI/CD for CAP + RAP
What actually moves.
Upgrades that don't break Q4
Clean core means the next S/4HANA release lands as a technical upgrade, not a re-implementation. Extensions on BTP stay untouched.
One integration hub
CPI + API Management + Event Mesh replace point-to-point spaghetti. Every integration observable, retryable, versioned.
Modern extensions, modern developers
CAP + Fiori + Node.js/Java attracts the talent that Netweaver-only stacks lose. Standard git workflows, standard CI/CD.
UX users don't fight
Fiori Launchpad + Fiori Elements + Work Zone give end users a single, mobile-friendly surface instead of SAP GUI plus five bolt-ons.
The approach.
-
01
Assess
Custom-code inventory, clean-core scorecard, integration-landscape audit, UX debt inventory.
-
02
Land BTP
BTP landing zone: subaccounts, entitlements, trust, transport management, DevOps toolchain.
-
03
Extend & integrate
Custom code migrated off the core to BTP; integrations rebuilt on CPI + API Management; Fiori surface designed.
-
04
Govern
Extension registry, API catalog, DevOps guardrails, upgrade-readiness checklist owned by the platform team.
Named deliverables.
Every engagement lands specific artefacts, not slides.
- BTP landing zone: subaccounts, entitlements, trust, transport management
- Custom-code inventory + clean-core migration plan sequenced by workload
- Integration hub on CPI + API Management with reusable adapters + monitoring
- Event Mesh setup for async integrations where volumes warrant it
- Fiori Launchpad + Fiori Elements catalog on top of the core scope
- SSO + identity provisioning through Cloud Identity, SCIM automation
- DevOps pipeline for CAP + RAP with git + CI/CD + gCTS
- Extension registry + API catalog: living documentation, not a wiki page
The wider SAP practice.
Finance & Controlling
One source of financial truth: statutory, management and consolidation on S/4HANA.
Supply Chain & Operations
Plan, procure, produce, deliver, maintain: one integrated backbone on S/4HANA.
Analytics & Planning
Real-time analytics on the SAP transaction layer plus integrated planning.
Frequently asked
What does 'clean core' actually mean in practice?
Zero custom modifications to standard SAP objects in the S/4HANA core. All extensions live on SAP BTP (Cloud Foundry, Kyma, or ABAP Environment) and integrate via released APIs and events. Practically it means the next S/4HANA upgrade is a technical patch, not a re-implementation, because nothing you built modified what SAP shipped.
SAP BTP: Cloud Foundry, Kyma or ABAP Environment?
Depends on the extension. CAP on Cloud Foundry is the default for new Node.js / Java extensions. Kyma when Kubernetes-native or event-driven microservices patterns are the fit. ABAP Environment (Steampunk) when the extension team is ABAP-native and the extension has to move quickly with S/4 data models.
CPI vs API Management vs Event Mesh: when does each apply?
CPI (Cloud Integration) for orchestrated point-to-point and hub-and-spoke integrations. API Management for exposing APIs to consumers (internal or external) with rate-limiting, auth, developer portal. Event Mesh for async event-driven decoupling. Most real customers use all three, each for the pattern it fits.
Do you still deliver on PI/PO for on-prem customers?
Yes. PI/PO stays in scope for customers who haven't yet moved to CPI. Phoenix delivers new integrations on PI/PO where the estate is on-prem and cloud migration isn't imminent. Migration path to CPI is planned as a discrete workstream when the customer is ready.
Fiori: Elements, Freestyle, or SAP Build?
Fiori Elements for CRUD-style transactional apps (fastest to build, standard patterns, low maintenance). Freestyle SAPUI5 when the UX has to be genuinely custom. SAP Build Apps (low-code) for citizen-developer scenarios where speed to prototype matters more than deep custom logic. Mixed portfolios per customer.
The earliest conversations are usually the most useful.
Whether you're scoping an SAP move to cloud, restarting a stalled programme, or just trying to figure out where data and AI fit, start with a conversation.
