SAP BTP Fundamentals: Accounts, Environments and Services

Keep this: job aid

BTP landscape starter checklist

• One global account per contract; it administers, it does not host apps.
• Separate subaccounts for development, test and production, plus a sandbox.
• Directories and labels for owner, cost center and stage once more than one team is involved.
• Choose each subaccount's region deliberately: users, latency, data residency.
• Entitle test with the same service plans as production; size production quota for peak.
• No free tier plans in production.
• Pick the environment by skills and workload: Cloud Foundry, Kyma or ABAP.
• Pair each BTP stage with the matching ERP stage through destinations; check before testing.
• Shared tools (transport, alerting) in their own subaccount; production changes only by transport.