BTP Fundamentals Part 1: What SAP BTP Is and How It Is Organized
SAP Business Technology Platform (BTP) is SAP's platform for building extensions, integrating systems, managing data and using AI. Learn its main capability areas, the account model (global account, directories, subaccounts), runtimes, services and entitlements, and commercial models — the map you need before touching any BTP service.
What this complete series covers
Learn BTP Fundamentals in a clear, practical sequence — from the basic idea to real project use, troubleshooting, and interview-ready understanding.
- Who it is for
- Best for SAP consultants, developers, and learners who want a practical understanding of BTP Fundamentals.
- Prerequisites
- A basic understanding of SAP BTP helps. Hands-on steps may require a BTP subaccount and access to the relevant Integration Suite or BTP service.
- Final outcome
- By the end, you should be able to explain BTP Fundamentals clearly, follow the main end-to-end flow, apply it in a project scenario, and troubleshoot the most common issues.
- Part 1: BTP Fundamentals Part 1: What SAP BTP Is and How It Is Organized
Understand the SAP BTP account hierarchy - global account, directories, subaccounts, and entitlements - and why this structure underpins every integration and extension deployment decision.
- Part 2: BTP Fundamentals Part 2: Runtime Environments and Connectivity
Compare the Cloud Foundry and Kyma runtime environments on BTP and understand how Cloud Connector and destinations enable secure connectivity between BTP and on-premise or external systems.
- Part 3: BTP Fundamentals Part 3: Destinations for On-Premise and Cloud Systems
Understand how destinations, the Connectivity service, and the Cloud Connector work together to let BTP applications and integration flows reach on-premise, private network, and ot
System and release assumptions: SAP BTP services evolve regularly. Capability names, screens, and setup steps can differ by region, entitlement, and tenant version; the core design principles remain the same.
Explanation
📌 KEY POINTS
✅ BTP groups services into application development & automation, integration, data & analytics, and AI.
✅ Account model: global account (contract) → directories (optional) → subaccounts (where you work, per region).
✅ Entitlements decide which services and plans a subaccount may use; quotas limit amounts.
✅ Runtimes: Cloud Foundry, Kyma (Kubernetes), ABAP environment — plus many SaaS services you subscribe to.
⚠️ Using BTP without a clear subaccount and entitlement design leads to cost surprises and security gaps.
━━━━━━━━━━━━━━━━━━━━
▶ WHAT THIS SERIES COVERS
Part 1: What BTP is and how it's organized
Part 2: Runtimes and connectivity
Part 3: Destinations to on-premise and cloud systems
━━━━━━━━━━━━━━━━━━━━
▶ 1. CAPABILITY AREAS
- Build (CAP, SAP Build), integrate (Integration Suite, Event Mesh), data (HANA Cloud, Datasphere), AI.
━━━━━━━━━━━━━━━━━━━━
▶ 2. ACCOUNT MODEL
- Global account, directories, subaccounts; regions and providers.
━━━━━━━━━━━━━━━━━━━━
▶ 3. ENTITLEMENTS AND QUOTAS
- Assign service plans to subaccounts.
━━━━━━━━━━━━━━━━━━━━
▶ 4. SERVICES
- Instances (for apps) vs subscriptions (SaaS apps).
━━━━━━━━━━━━━━━━━━━━
▶ 5. COMMERCIAL MODELS
- Consumption-based credits vs subscriptions — check your contract.
━━━━━━━━━━━━━━━━━━━━
▶ STEP BY STEP
- Open the BTP cockpit and explore the global account.
- Review entitlements of a subaccount.
- Create a service instance and a subscription in a trial/sandbox.
✅ CHECKPOINT: you can explain instance vs subscription and where entitlements are assigned.
Code example
===== ACCOUNT MODEL =====Global account (contract, entitlements pool) ├─ Directory "Finance extensions" │ ├─ Subaccount DEV (eu10, Cloud Foundry) │ ├─ Subaccount TEST │ └─ Subaccount PROD └─ Subaccount Integration (Integration Suite subscription) ===== TOOLS =====BTP cockpit | btp CLI (btp login, btp list accounts/subaccount) | cf CLI | kubectl (Kyma)Real project scenario
A mid-size manufacturer started with one subaccount for everything. Development tests consumed production quotas and developers had production access. Splitting into DEV/TEST/PROD subaccounts with separate entitlements and role collections fixed both issues.
Common mistakes
- One subaccount for all.
- Admin rights for everyone.
- Ignoring entitlements.
- Confusing instances and subscriptions.
- No cost monitoring.
Best practices
- Separate environments.
- Least-privilege roles.
- Plan entitlements.
- Understand service types.
- Monitor consumption.
Interview angle
Questions: "What is SAP BTP?", "Explain the account model", "Instance vs subscription?"
Strong answer: capability areas, account model, entitlements, runtimes/services, commercial models.
Practice this lesson
Quick check
1. In the SAP BTP account model, what is the primary purpose of entitlements assigned to a subaccount?
2. In SAP BTP, what is the primary purpose of creating a service key for a service instance?
3. How does a quota assigned to a subaccount differ from an entitlement in SAP BTP terminology?
Interview questions
1. Can you explain what SAP BTP is and name its five main functional pillars?
Answer it in your own words first, then compare.
2. How are Global Accounts, Subaccounts, and Directories structured within the BTP cockpit?
Answer it in your own words first, then compare.
Reference-verified: the steps are checked against official SAP documentation and tutorials, and object and field names in the sample code are checked for consistency. The code has not been compiled or run on an SAP system by ERPClimb. Syntax marked release-dependent varies by SAP release, so check it in your own system.