Show TOC

Process documentationProcessing a Maintenance Cycle


This process creates and uses a maintenance cycle for normal and urgent changes, defect corrections and administrative changes. You can edit maintenance cycles in the WebClient UI.

Note Note

Maintenance and project cycles can be called up in the WebClient UI under Start of the navigation path Change Request Management Next navigation step Change Cycles End of the navigation path.

End of the note.


  1. An administrator creates a maintenance cycle for a maintenance project.

  2. The administrator sets the status of the maintenance cycle to Development without Release. In this status, changes can be developed and transport requests and tasks can be created, but not exported (except urgent changes). Urgent changes are permitted in every phase except for Go Live.

  3. The administrator switches the status of the maintenance cycle from Development without Release to Development with Release. Transport requests can be released from within a normal change. The IT operator uses the task list to import all released changes into test systems.

  4. The administrator sets the status of the maintenance cycle to Test. If there are normal changes whose status has not yet been set to Tested Successfully when the maintenance cycle phase is changed from Development with Release to Test, the system issues a warning. These changes are then excluded from the integration test, and cannot be released.

  5. During the test phase, errors are detected in the test systems, and are reported to the developers by defect corrections. The developers correct these errors. If all error messages have been closed, the maintenance cycle can proceed to the go-live preparation phase.

  6. If changes still have to be made after the test phase has been completed, transport requests and tasks can be created and released, as part of the go-live preparation phase, but only by using the task list of the Schedule Manager.

  7. In the Go Live phase, the entire project buffer is imported into the production system. Neither transport requests nor urgent changes can be released during this phase.

  8. If there are still any open transport requests, return to the Development with Release phase and repeat the process, including the test phase, to ensure that any open requests can be released and transported.

  9. If there are no open transport requests, you can close the maintenance cycle, by setting the status to Being Completed, and then to Completed. You can then create a new maintenance cycle.

    Note Note

    Normal changes can be created in the test phase of a maintenance cycle, but the corresponding transport requests cannot be exported.

    End of the note.