A multitenant application has some central sizing properties that dictate the scope and metric of your offering, or in other words, how many resources will be available for each consumer.
Tenant Limit: Before deploying your application, you must decide on a tenant limit. Once that number of consumer tenants is reached in a system, a new system will be provisioned for the next consumer. If you choose a limit of 1, you will be defining a single tenant offering with one consumer per system.
For in-depth information about multitenancy, see this section.
Additionally, you need to define the sizing of each provisioned ABAP system. The sizing is defined by the number of ABAP compute units (runtime) and HANA compute units (persistence) each system is assigned. These values are reflected by the parameters size_of_runtime and size_of_persistence. For more information, see Creating an ABAP System.
For multitenancy offerings, there’s no sizing/quota per customer. You must decide on an overall sizing depending on the expected load in a region. You can use the Technical Monitoring Cockpit to assist you in this.
If the quota for a system is exceeded, you can request a resizing of the ABAP runtime or persistency depending on the needs of the SaaS application.