SAP BTP
Multi-cloud subaccountsCloud FoundryKymaSAP BuildBTP CockpitTrust 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.
What we do
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.
Module coverage
What's in scope.
Integration
Cloud Integration (CPI)API ManagementEvent MeshOpen ConnectorsPI/PO (legacy)IDoc / OData / REST
Extensions & Development
ABAP RESTful (RAP)CAP (Cloud Application Programming)SAPUI5 / FioriSAP Build AppsSteampunk (ABAP Environment)
Experience (UX)
Fiori LaunchpadFiori ElementsWork ZoneMobile StartPersonalisationAccessibility
Identity & Security
SAP Cloud IdentitySSOSCIM provisioningOAuthGRC integration
DevOps
Transport ManagementgCTSPiper / JenkinsCI/CD for CAP + RAP
Business outcomes
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.
How Phoenix delivers
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.
What you get
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
Customer stories
Customers on this journey.
Real Phoenix engagements — measured outcomes at MEA scale.
Pharmaceutical distribution·Egypt
Pharmaoverseas Group
Egypt's largest pharma distributor moves SAP to the cloud.
2,500 Users digitalized50% Uptime improvement
Manufacturing (Plumbing)·Egypt · Germany
EGIC Group
Plumbing market-leader upgrades SAP to RISE on AWS in a month.
80% Uptime improvement100% Hardware cost reduction
Real Estate·Egypt · MENA
Arab Developers Holding
Real-estate group refactors SAP to HANA — with GenAI on top.
90% Backup time reduction11×9s Data durability (S3)
More SAP capabilities
The wider SAP practice.
FAQ
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.
Talk to us
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.