Multitenant Subscription Management
The concept name was not provided (marked as "undefined"), and the supplied source snippets cover distinct topics — the Maintain Solution App, the btp CLI for multitenant applications, and the Subscription Management Dashboard — without a shared concept that can be reliably identified and defined. A precise, source-grounded definition cannot be written without knowing which concept is intended.
Docs explaining this concept
Prerequisites
- Concept Provider and Consumer Subaccount Model The concept name was not provided, so a precise definition cannot be written. Based on the available sources, the closest identifiable concept is **Multitenancy on SAP BTP**, which defines the capability to host different customers (tenants) on a single application instance while keeping their data isolated. Developers use it to design and deploy multitenant applications on SAP Business Technology Platform, choosing from [multiple tenant models](https://architecture.learning.sap.com/docs/ref-arch/RA0007/3-mt-models/readme) depending on their isolation and sharing requirements. In the [ABAP Environment](https://help.sap.com/docs/btp/sap-business-technology-platform/633cc61560734a8fb8dba64b4dd904a9?locale=en-US&state=PRODUCTION&version=Cloud), multitenancy allows a single ABAP system to serve multiple consumer tenants, enabling efficient resource utilization across customers.
- Concept SAP BTP Service Marketplace The concept provided is **undefined**, and the supplied sources do not contain sufficient information to construct a grounded, accurate reference definition for any clearly identified SAP developer concept. The sources reference topics such as [subscribing to SAP Business Application Studio](https://help.sap.com/docs/btp/sap-business-technology-platform/0a9b42e8795d4f7b8fc196a6fde0b3f2?locale=en-US&state=PRODUCTION&version=Cloud) and [creating an ABAP system](https://help.sap.com/docs/btp/sap-business-technology-platform/50b32f144e184154987a06e4b55ce447?locale=en-US&state=PRODUCTION&version=Cloud), but without a named concept to define, no accurate prose definition can be produced. Please provide a specific concept name to generate a valid definition.
- Concept BTP Subaccount Creation The concept name was not provided and could not be determined from the available source snippets, which cover unrelated topics such as deleting users, navigating the SAP BTP Cockpit, setting up trial accounts, and configuring entitlements. A meaningful, source-grounded definition cannot be written without a valid concept name or relevant supporting sources.
- Concept SAP BTP Cockpit The concept name was not provided and the supplied source snippets do not define or describe a single, identifiable SAP developer concept — they cover a range of unrelated SAP BTP topics such as Kyma environment setup, Cloud Foundry org deletion, subaccount management, and service instances. A focused definition cannot be grounded solely in these sources without a clearly stated concept to define.
- Concept Multitenancy Roles (Provider and Consumer) The concept name was not provided and cannot be determined from the available source snippets, which reference multitenancy topics in SAP BTP but do not define a specific named concept. A meaningful definition cannot be written without knowing the target concept.