![]() | After Michael logged into his subaccount as an administrator and ensured that ABAP entitlements are configured, he enabled cloud foundry and created space for adding users. He is now ready to create an ABAP instance. |
Watch the video about how to create an ABAP instance.
Steps to Create an ABAP Instance |
---|
|
For more information about additional instance parameters required for the configuration, refer to the following table.
Parameters | Description |
---|---|
Admin Email Address | Use the Admin Email Address to create the initial administrator for the ABAP Instance automatically, including the assignment of the administrator role to this user. You can access the ABAP environment system only with this specified user. By default, the email address is used as subject name identifier. Using email addresses as the subject name identifier might not be possible if the email addresses are ambiguous across users, or the trusted identity provider configured for authentication in the ABAP Environment instance’s subaccount is already configured with subject name identifier Login Name. You can then change login_attribute to user_name via the parameter and in addition also provide the user name for the initial user in parameter Admin User Name. |
ABAP System Description | The ABAP System Description is optional. |
Development System | The Development System checkbox is selected by default. By using this setting, you can control the changeability of development objects in the system. If you want to protect all your customer-related software components and ABAP namespaces against manual changes via ABAP Development Tools, clear the checkbox. This setting is used for test and productive systems, where changes must be imported only. For information about which business catalogs are available in development systems only. |
ABAP System ID | The ABAP System ID must consist of exactly three alphanumeric characters. Only uppercase letters are allowed. The first character must be a letter (not a digit). The ID does not have to be technically unique. |
ABAP Runtime Size | The ABAP Runtime Size (parameter size_of_runtime) refers to the size of the ABAP runtime. It is part of the quota plan abap_compute_unit, with one ABAP compute unit representing 16 GB. The supported number of abap_compute_unit is 1, 2, 4, 6, 8, 16, or 24. |
HANA Memory Size | The HANA Memory Size (parameter size_of_persistence) refers to the size of SAP HANA memory. It's part of the quota plan hana_compute_unit, with one HANA compute unit representing the suitable block size for the underlying SAP HANA Cloud instance (15 GB on AWS or 16 GB on Microsoft Azure). The supported number of hana_compute_unit per HANA instance is 2, 4, 8, 16, 32, or 64. |
Size of Persistence Disk | The Size of Persistence Disk (parameter size_of_persistence_disk) refers to the size of the SAP HANA Cloud storage in GB. If the parameter is set to auto, the SAP HANA Cloud storage size is set to the minimal value 40 * size_of_persistence + 40. The maximum allowed value is 120 * size_of_persistence + 40. If you set a higher value, it will consume 0.002 HANA compute units (HCU) for any GB exceeding the minimal default size of the persistence disk. Therefore, the HCU ratio of additional storage disk to RAM is 1 : 33.33 per GB on AWS (as 1 HCU = 15 GB) and 1 : 31.25 per GB on Microsoft Azure (as 1 HCU = 16 GB). |