## 4.2.14.1.5.2.2  Set Up a Global Account for Development
As a SaaS solution operator, you have to configure the global account for development (used for development, testing, and demo purposes).
<!-- image -->
##  Recommendation
We recommend the following subaccount structure:
- In the 00 Landscape Portal subaccount, your subscription to the Landscape Portal is created. If required, the CI/CD service should also be subscribed in this subaccount. No Cloud Foundry environment is required.
- In the 01 Develop subaccount, add-on development is performed in a permanent development system. See Development in the ABAP Environment [page 745].
- In the 02 Test subaccount, the developed software components are tested after a successful import into a permanent test system.
- In the 03 Build/Assemble subaccount, the add-on package assembly is performed in a transient assembly system that is created and deleted automatically by the build pipeline.
- In the 04 Build/Test subaccount, the add-on product is installed and tested again.
- In the 05 Provide subaccount, the add-on product is provided as a SaaS solution for testing purposes in the development phase.
##  Note
You can use a booster (see Booster for Landscape Portal [page 1229]) to automatically perform the setup of subaccounts 00 Landscape Portal, 03 Build/Assemble and 04 Build/Test. This includes the assignment of entitlements, creation of subscriptions and trust setup as described below.
##  Note
If you use gCTS instead of add-ons for delivering software components to production systems, the setup and usage of the following subaccounts is redundant:
- 03 Build/Assemble (used for the add-on assembly)
- 04 Build/Test (used for add-on installation test)
Additionally, considering the availability of software components only in the same global accounts, you have to create the production systems as well as development and test systems in the same global account (only one global account is used).
In the provider subaccount, the entitlement for an ABAP instance of service plan type abap/ standard instead of abap/saas\_oem needs to be available.
See Delivery via Add-On or gCTS [page 1214].
You should configure a Cloud Foundry space in each subaccount. Dividing the development, testing, and assembling activities into different subaccounts allows for maximum flexibility. For instance, you may want to use different identity providers or consume different connectivity services during testing and development.
The ABAP systems that you use for development, testing, and add-on assembly are of type abap/standard and made available via entitlements. ABAP systems for add-on installation are of type abap/saas\_oem . These service entitlements must be assigned by an administrator to different subaccounts, according to the following structure:
| Global Account                   | Subaccount   | Space   | Services                                                                                   |
|----------------------------------|--------------|---------|--------------------------------------------------------------------------------------------|
| Global Account for Develop- ment | 01 Develop   | Develop | 1x abap/standard abap/hana_compute_unit (standard: 2) abap/abap_compute_unit (standard: 1) |
|                                  | 02 Test      | Test    | 1x abap/standard abap/hana_compute_unit (standard: 2) abap/abap_compute_unit (standard: 1) |
| Global Account   | Subaccount        | Space          | Services                                                                                                                                   |
|------------------|-------------------|----------------|--------------------------------------------------------------------------------------------------------------------------------------------|
|                  | 03 Build/Assemble | Build/Assemble | 1x abap/standard abap/hana_compute_unit (standard: 2) abap/abap_compute_unit (standard: 1)                                                 |
|                  | 04 Build/Test     | Build/Test     | 1x abap/saas_oem abap/hana_compute_unit (standard: 2) abap/abap_compute_unit (standard: 1)                                                 |
|                  | 05 Provide        | Provide        | 1x abap/saas_oem abap/hana_compute_unit (standard: 2) abap/abap_compute_unit (standard: 1) Application Runtime abap-solution saas-registry |
|                  |                   |                | xsuaa                                                                                                                                      |
Additionally, the following entitlements for SaaS application subscriptions are required:
- SAP Business Application Studio for UI development. See SAP Business Application Studio [page 243].
- Web access for ABAP for access to systems during development phase. See Subscribing to the Web Access for ABAP [page 190].
- Landscape Portal to manage systems and tenants in the provider subaccount. See Landscape Portal.
If you want to integrate an existing corporate identity provider in the subaccounts of the global account for development for authentication/authorization, see Trust and Federation with Identity Providers [page 2280]. To restrict access based on certain criteria such as the IP address, you need to use the SAP Cloud Identity Services - Identity Authentication.
##  Tip
For in-depth information about the system landscape/account model, check out System Landscape/ Account Model [page 1192].