What Is the SAP BTP Cockpit? Navigation, Configuration, and Cost Management

The BTP Cockpit is where you manage everything on SAP Business Technology Platform: global accounts, subaccounts, entitlements, users, services, and costs. If you’re responsible for a BTP environment, this is where you spend most of your time. Getting comfortable with it early saves you a lot of headaches later. Trust me on this.

This guide walks through the cockpit’s structure, what each section does, and the configuration patterns that prevent the mistakes we see over and over.

TL;DR: BTP adoption reached 55% among ASUG members in 2025, with 73% using it for S/4HANA transformation (Precisely, 2026). The BTP Cockpit is the central admin interface for managing global accounts, subaccounts, entitlements, security, and costs. Key areas: Account Explorer for hierarchy management, Service Marketplace for provisioning, Security for role-based access, and Usage Analytics for cost control.

What Is the BTP Cockpit and How Is It Structured?

BTP adoption reached 55% among ASUG members, and 73% of BTP users deploy it specifically for S/4HANA transformation projects (Precisely, 2026). Every one of those deployments is managed through the cockpit.

The cockpit is organised in a four-level hierarchy. Get this right from the start. Nota bene: restructuring after the fact means migrating services, and nobody enjoys that.

Global Account. The top level, representing your SAP contract. You access it through a regional URL (e.g., cockpit.eu10.hana.ondemand.com for Europe). Everything else lives under this account.

Directories. Optional grouping layer for organising subaccounts by department, project, or region. Use directories when you have more than 5-6 subaccounts. Without them, the Account Explorer becomes a mess.

Subaccounts. The working unit. Each subaccount has its own region, runtime environment (Cloud Foundry, Kyma, or ABAP), entitlements, and user assignments. Most companies create separate subaccounts for dev, test, and production.

Spaces. Within Cloud Foundry subaccounts, spaces provide additional isolation. A typical pattern: one space per application or team within each subaccount.

How Do You Navigate the Account Explorer?

SAP’s total cloud revenue reached EUR 17.14 billion in FY 2024, up 25% year-over-year (SAP News, 2025). The Account Explorer is where you manage your share of that cloud infrastructure.

When you log into the cockpit, the Account Explorer is the first view. It shows your complete hierarchy: directories, subaccounts, and their status. From here you can:

• Create and delete subaccounts: assign region, environment type, and description
• Organise into directories: drag and drop or create new groupings
• View subaccount details: region, provider (AWS, Azure, GCP), subdomain, and tenant ID
• Monitor status: see which subaccounts are active, suspended, or being provisioned

The sidebar navigation changes depending on your context. At the global account level, you see Entitlements, Usage Analytics, and Security. Drill into a subaccount and you see Cloud Foundry or Kyma environment management, Service Marketplace, and subaccount-specific security settings.

One thing I’ll flag: the most common cockpit mistake we see is creating subaccounts without a naming convention. After 10+ subaccounts with names like “test”, “dev2”, and “project-x”, nobody knows what’s where. Use a convention like {project}-{env}-{region} from the start. You’ll thank yourself later.

How Do Entitlements and Service Marketplace Work?

Only 48% of digital initiatives meet their business outcome targets (Gartner, 2024). Misconfigured entitlements (services provisioned but not used, or needed services missing from subaccounts) contribute to that failure rate. Not glamorous work. But it matters.

Entitlements control which services are available in which subaccounts. Your global account has a pool of entitlements (based on your SAP contract), and you distribute them to subaccounts. Think of it as a budget: the global account holds the total, and each subaccount gets an allocation.

Key entitlement patterns:

• Service plans: each service has multiple plans (lite, standard, premium). Choose the right plan per environment. Lite for dev/test, standard or premium for production.
• Quotas: some services have numeric quotas (e.g., number of Cloud Foundry runtime instances). Monitor these to avoid hitting limits during deployment.
• Auto-assignment: configure directories to auto-assign entitlements to new subaccounts, saving manual setup for each new environment.

The Service Marketplace is the catalogue view within a subaccount. It shows all available services (based on your entitlements) and lets you create service instances. Common services: SAP HANA Cloud, Integration Suite, SAP Build, Destination Service, Connectivity Service, and XSUAA.

How Do You Manage Security and User Access?

The security model in BTP is one of the most misunderstood aspects. 69% of SAP BTP users use its integration capabilities, more than any other feature (Precisely, 2026). Integration requires proper security configuration, and that starts in the cockpit.

Security operates at two levels.

Trust Configuration. Connects your corporate identity provider (IdP) to BTP. SAP provides a default IdP (SAP ID Service), but production environments should use your corporate IdP (Azure AD, Okta, SAP IAS) for single sign-on and centralised user management.

Role Collections. Groups of roles assigned to users. BTP ships with predefined role collections (Subaccount Administrator, Space Developer, etc.), and you can create custom ones. The pattern: create role collections that match your team roles, not individual permissions.

Common security mistakes we see regularly:

• Giving everyone Subaccount Administrator instead of creating limited role collections. Lazy, and it’ll bite you.
• Using SAP ID Service (the default IdP) in production instead of your corporate IdP
• Not configuring trust at the subaccount level. Trust must be set up per subaccount, not just globally.

How Do You Monitor Costs in the Cockpit?

More than two-thirds of large-scale tech programmes miss time, budget, or scope targets (BCG, 2024). Cost visibility in the cockpit helps prevent BTP from contributing to that statistic.

The Usage Analytics section (global account level) shows:

• Credit consumption: how many cloud credits you’ve used vs. your contract allocation
• Per-service breakdown: which services consume the most credits
• Per-subaccount breakdown: which subaccounts drive the highest costs
• Trend data: consumption over time, updated every 24 hours

Practical cost management patterns:

1. Review monthly. Set a calendar reminder. The cockpit’s data updates daily, but a monthly review catches trends before they become problems.
2. Flag spikes. If any service’s cost increases 20%+ month-over-month, investigate immediately. Common causes: runaway test instances, oversized HANA Cloud, or forgotten dev environments that nobody bothered to shut down. You’d be surprised how often that last one comes up.
3. Right-size environments. Dev and test subaccounts don’t need production-grade service plans. Downgrade to lite plans where possible.
4. Clean up unused services. Service instances that nobody uses still consume entitlements and sometimes credits. Audit quarterly. You’d be surprised what you find.

What’s the Difference Between the Cockpit and the BTP CLI?

44% of SAP BTP users plan to expand into AI services (Precisely, 2026). As environments grow more complex, the choice between cockpit and CLI matters more.

The cockpit is the graphical web interface: good for visual exploration, one-off configuration, and cost monitoring. The BTP CLI (btp command) does the same things through the command line.

When to use each:

For most teams, it’s not either/or. Use the cockpit for visual monitoring and ad-hoc tasks, the CLI for automation and CI/CD. Once your environment grows beyond a few subaccounts, the CLI becomes your friend. We switched early and haven’t looked back.

FAQ

How do I access the SAP BTP Cockpit?

Log in through the regional URL for your data centre (e.g., cockpit.eu10.hana.ondemand.com for EU). You’ll see the Global Account Selection page listing all accounts you’re assigned to. Only users with explicit global account membership see this screen.

Can I manage multiple environments from one cockpit?

Yes. The cockpit supports Cloud Foundry, Kyma, and ABAP environments, all within the same subaccount or across different subaccounts. The sidebar navigation adapts to show environment-specific options when you select a subaccount.

How often does Usage Analytics update?

Usage data refreshes every 24 hours. It’s not real-time, so don’t rely on it for immediate cost checks during deployments. For real-time service instance status, check the subaccount’s Service Instances view instead.

What happens if I run out of entitlements?

You can’t create new service instances for that service in any subaccount until you either free up entitlements (by deleting unused instances) or purchase additional capacity from SAP. The cockpit shows warnings when entitlements are near their limit.

Should I use SAP ID Service or my own IdP?

Use SAP ID Service for initial setup and personal dev accounts. For anything beyond that (shared dev environments, test, staging, production) configure your corporate IdP (Azure AD, Okta, SAP IAS). This gives you centralised user lifecycle management and SSO. Don’t skip this step.