Bug fixes aren’t implemented as part of the development code line, but in a separate correction code line. In this manner, corrections can be delivered to consumers even while regular development is ongoing.
We recommend setting up a maintenance system landscape that runs in parallel to the development system landscape. This maintenance landscape consists of:
-
A correction system COR where corrections are developed. This system is provisioned in subaccount 01 Develop in the development space. Set parameter
is_development_allowed = true. -
A quality assurance system QAS for testing the corrections. This system is provisioned in subaccount 02 Test in the test space. Set parameter
is_development_allowed = false.
The required entitlements and system-related details are listed in the table below:
|
Global Account |
Subaccount |
Space |
Entitlements |
ABAP System |
|---|---|---|---|---|
|
Global Account for Development |
01 Develop |
Develop |
1x abap/standard abap/hana_compute_unit (standard: 2) abap/abap_compute_unit (standard: 1) |
COR |
|
02 Test |
Test |
1x abap/standard abap/hana_compute_unit (standard: 2) abap/abap_compute_unit (standard: 1) |
QAS |
The Manage System Hibernation app in the Landscape Portal allows you to shut down the maintenance systems when no corrections are being developed, significantly reducing the costs incurred. See Manage System Hibernation. For more information on working with two codelines, see Use Case 2: One Development and Correction Codeline in a 5-System Landscape.
It is not strictly necessary to set up a separate maintenance system landscape. You can also implement corrections in the existing development and test systems to further reduce costs. In this case, ongoing development must be stopped while the release branch is checked out and worked on. See Use Case 1: One Codeline in a 3-System Landscape.