BTP & Integrationbeginner

BTP Global Accounts Part 1: Global Accounts, Subaccounts and Entitlements

Key takeaway

Understand the BTP account model in depth: global account as the contract level, subaccounts as workspaces bound to a region and environment, entitlements and quotas, service plans, and the difference between service instances and subscriptions.

What this complete series covers

Learn Global Accounts and Subaccounts 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 Global Accounts and Subaccounts.
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 Global Accounts and Subaccounts clearly, follow the main end-to-end flow, apply it in a project scenario, and troubleshoot the most common issues.

Part 1: BTP Global Accounts Part 1: Global Accounts, Subaccounts and Entitlements
Introduces the core SAP BTP tenant model - what a global account is, how directories organize subaccounts, and why subaccounts are the actual unit of work for deploying integration
Part 2: BTP Global Accounts Part 2: Designing Subaccount Structures for Environments
Explains how to design a practical subaccount layout for integration landscapes, covering entitlement assignment, quota planning, environment separation, and the trade-offs consult
Part 3: BTP Global Accounts Part 3: Directory Hierarchies and Governance
Learn how to use directories to organize subaccounts by environment, business unit, or region, and how directory-level entitlements, features, and authorization group assignments s

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
✅ The global account holds the contract and total entitlements; admins distribute them.
✅ Subaccounts are bound to a region/provider and host environments (Cloud Foundry org, Kyma cluster).
✅ Entitlements assign service plans (and quotas) to subaccounts; without them services can't be used.
✅ Service instances serve applications; subscriptions give users access to SaaS apps.
⚠️ Subaccount region can't be changed later — choose it with data residency and latency in mind.

━━━━━━━━━━━━━━━━━━━━
▶ WHAT THIS SERIES COVERS
Part 1: Account model basics
Part 2: Subaccount structure design
Part 3: Directory hierarchies

━━━━━━━━━━━━━━━━━━━━
▶ 1. GLOBAL ACCOUNT

Contract, admins, entitlement pool.

━━━━━━━━━━━━━━━━━━━━
▶ 2. SUBACCOUNTS

Region, provider, environments, users.

━━━━━━━━━━━━━━━━━━━━
▶ 3. ENTITLEMENTS & QUOTAS

Service plans; limits per subaccount.

━━━━━━━━━━━━━━━━━━━━
▶ 4. INSTANCES VS SUBSCRIPTIONS

Apps vs SaaS.

━━━━━━━━━━━━━━━━━━━━
▶ 5. ADMINISTRATION

Global vs subaccount admins; role collections.

━━━━━━━━━━━━━━━━━━━━
▶ STEP BY STEP

Create a subaccount in the chosen region.
Assign entitlements.
Enable Cloud Foundry and create a service instance.

✅ CHECKPOINT: subaccount has only needed entitlements.

Code example

ABAP Code

===== CLI =====btp loginbtp create accounts/subaccount --display-name DEV --region eu10 --subdomain acme-devbtp assign accounts/entitlement --to-subaccount <id> --for-service xsuaa --plan applicationbtp list accounts/subaccount ===== CONCEPTS =====Instance: app uses a service (e.g. XSUAA, destination) | Subscription: users open a SaaS app (e.g. SAP Build Work Zone)

Real project scenario

A retail company created subaccounts in three regions by accident; destinations and Cloud Connectors had to be duplicated. Consolidating new projects in one region per data residency need reduced effort.

Common mistakes

Random regions.
Too many global admins.
Missing entitlements.
Confusing service types.
No naming convention.

Best practices

Region by residency.
Few global admins.
Plan entitlements.
Understand instances/subscriptions.
Naming conventions.

Interview angle

Questions: "Global account vs subaccount?", "What are entitlements?", "Instance vs subscription?"
Strong answer: account levels, regions/environments, entitlements, service types, admin roles.

Practice this lesson

Quick check

1. What is the global account in SAP BTP?

2. Interviewers commonly ask candidates to explain the BTP account hierarchy and why subaccounts are the deployment unit rather than the global account. In the Global Accounts and Subaccounts context, which answer shows the strongest practical judgment?

3. A team proposes creating subaccounts in whichever region is fastest to set up. Why is this a problem?

Interview questions

1. What are the core concepts of Global Accounts and Subaccounts, and how would you explain them clearly in an SAP interview?

Answer it in your own words first, then compare.

2. A retail company's BTP subaccounts were created ad hoc in different regions. Explain the account model and how you'd correct the setup.