BTP - Global, Directories and Sub-Accounts

Global Account:

A Global Account is your contractual entity with SAP. it’s directly tied to your commercial agreement and license purchase. When your company signs an SAP BTP contract, SAP provisions a Global Account that contains:

• All purchased entitlements (service quotas you’ve bought)
• Commercial model assignment (consumption-based, subscription-based, or CPEA)
• Central user and security management
• Cross-subaccount governance capabilities

For example: A company buys 50 GB of SAP BTP resources. These entitlements are at the Global Account level, and you need to distribute them to subaccounts based on project needs. The Global Account is where CFOs and Procurement teams see what you’ve purchased. The SAP Architects decide how to allocate those resources based on business requirement.

Directory: Optional grouping of subaccounts

Eg: US-FINANCE-DIR

Subaccount:

Isolated administrative and deployment context

XX-DEV, XX-QA, XX-PROD

Please check the below diagram for better idea...based on your requirement you can create multiple sub-directories and sub-accounts

Account Explorer: 

Landscape Visualization

Account Explorer is your structural view into the entire BTP landscape. It renders your account hierarchy in a tree structure showing:

• Global Account (Root level)
• Directories (Optional organizational containers)
• Subaccounts (working environments)
• Multi-environment relationships

Account Explorer helps you navigate this structure quickly, check entitlement assignments, and jump into any subaccount’s cockpit. It’s particularly valuable when you have 100+ subaccounts and need to find a specific environment quickly.

Environment selection are available only at "Sub-Accounts" level.

Directories are optional.

Go to Entitlements and assign CloudFoundary and/or required services and then assign units(memory).

Boosters:

Boosters are orchestrated automation scripts that execute complex provisioning scenarios. Instead of creating manually.

Common Booster Examples..

Prepare an Account for Development: Provisions Cloud Foundry environment, creates spaces (dev/test/prod), assigns standard entitlements, and configures basic connectivity.

Set Up Your SAP Build Work Zone, Standard Edition: Creates subaccount, provisions Work Zone service, configures HTML5 repo, sets up required destinations, creates administrator role collection.

Enable SAP Document Management Service: Configures repository, sets up integration with S/4HANA, provisions necessary APIs.

Boosters encode tribal knowledge. They implement SAP’s recommended architecture patterns, so you’re not guessing at the right sequence of configuration steps.

Sources: help.sap.com

Thanks for reading :-)