SaaS Multitenant Consumer Tenant Setup
This concept is not sufficiently defined by the provided source snippets. The sources do not contain enough information to write a grounded, accurate definition.
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 CAP Multitenancy and SaaS Extensibility The concept name was not provided (marked as "undefined"), and the supplied sources do not contain enough grounded detail to produce an accurate, fully supported definition. Source [S1] references CDS modeling best practices on [SAP BTP](https://help.sap.com/docs/btp/sap-business-technology-platform/e4a7559baf9f4e4394302442745edcd9?locale=en-US&state=PRODUCTION&version=Cloud), and Source [S2] references multi-tenant application subscription, but without a clearly identified concept it is not possible to write a precise, grounded definition. Please provide the concept name so an accurate definition can be generated.
- Concept Tenant Host Pattern Routing The concept name was not provided (marked as "undefined"), and the single source snippet supplied covers only a troubleshooting topic — specifically undeploying multitenant applications via MTA on SAP BTP — without defining any distinct developer concept. There is insufficient information to write an accurate, grounded 2–4 sentence definition.
- Concept ABAP SaaS Add-on Product The concept provided is **undefined** — no valid concept name was supplied for this entry. A definition cannot be accurately written without a clearly identified concept to describe, and the available source snippets do not point to a single unambiguous term. Please provide a specific SAP developer concept name so a grounded, accurate definition can be produced.
- Concept Role and Role Collection Management The concept name is not defined in the provided sources, and no sufficient information is available to construct an accurate, grounded definition.
- Concept SAP BTP Account Model (Global Accounts, Subaccounts, Spaces) The concept name provided is "undefined," which does not correspond to a identifiable SAP developer concept. Based on the available sources — which cover topics such as global account administration, subaccount creation, the Cloud Foundry environment, and SAP BTP account management — there is insufficient information to produce a grounded definition for a concept labeled "undefined." Please provide a valid SAP concept name so an accurate and source-grounded definition can be written.
- Concept Approuter Application for Multitenancy The concept provided is "undefined," and the supplied sources do not contain a definition or description of a concept named "undefined." Based on the available source snippets, the closest identifiable concept is the **Approuter Application**, which is used to authenticate business users of a multitenant application at runtime. Developers use it to handle tenant-aware routing and security in applications built on [SAP BTP](https://help.sap.com/docs/btp/sap-business-technology-platform/44dbd0ae4d4b4d9c9c8371d711c22bfe?locale=en-US&state=PRODUCTION&version=Cloud), often in combination with the SAP Authorization and Trust Management Service (XSUAA) to secure multitenant solutions.
- Concept Cloud Foundry Domain and Route Configuration The concept name was not provided and the supplied sources do not contain enough grounded detail to produce a reliable definition — the source snippets are either untitled, inaccessible, or too brief to extract specific, verifiable claims. Please provide a valid concept name and complete source content so an accurate definition can be written.
- Concept SaaS multitenancy patterns on Cloud Foundry The concept name is missing from the submission and cannot be determined from the provided sources, which cover resilience patterns and SaaS application development on SAP BTP, ABAP Environment but do not define a single named concept. A meaningful definition cannot be written without knowing the specific concept to define.
- Concept Kyma Runtime deployment The concept name is undefined and cannot be determined from the provided source snippets. The sources reference SAP BTP Kyma runtime, Docker containers, and related deployment tutorials, but do not define a specific named concept that can be documented. A meaningful definition cannot be written without a valid concept name grounded in the sources.