Show TOC

Process documentationProcessing a Phase Cycle

 

You can use this process to create and use a phase cycle for normal changes, urgent changes, general changes, defect corrections, and administrative changes. You can edit phase cycles in the WebClient UI under Start of the navigation path Change Request Management Next navigation step Change Cycles End of the navigation path.

Process

  1. System administrators or technical project leads create a phase cycle to control all change activities in the solution landscape using Change Request Management.

  2. They switch the phase to “Scope”.

  3. The system displays the guided procedure for creating a task list. For more information, see Creating Task Lists.

    Note Note

    You can also use change cycles without task lists. For more information, see Using Change Cycles Without a Task List.

    End of the note.

  4. Once the task list is created, you create requests for change. The corresponding change documents are assigned to the phase cycle. The selected cycle in the Details assignment block defines which change cycle is assigned by the system.

    In the “Scope” phase, features can be developed and transport requests and tasks can be created but not exported.

    Note Note

    Do not use this phase in normal changes because developers will not be able to import changes into the test system, for example, the changes from the transport of copies.

    End of the note.

  5. When the change manager switches the phase of the phase cycle to “Build”, transport requests can be released from within a normal change.

    The administrator either uses the task list to import all released changes whose phase matches the import strategy of the cycle into the test systems, or triggers the import of a specific change document from the WebClient UI, using the preliminary import function.

    Note Note

    Transports of copies can be imported only from the task list.

    End of the note.

  6. The change manager sets the phase of the phase cycle to “Test”.

    Note Note

    In a phase cycle, the test phase applies to a real test phase or period (for example, acceptance tests or scenario tests). It does not apply to the phase of a change document.

    End of the note.

    If there are any normal changes whose phase has not been set to “Tested Successfully” when the phase is changed from “Build” to “Test”, the system issues an error. No changes can be excluded from the test; they either have to be withdrawn or released. Any errors that are found during the test phase are reported by testers and resolved with a defect correction.

  7. In the “Go Live” phase, the entire content of the buffer is imported into the production system.

  8. The project buffer is now empty, and there are no open transport requests. You close the phase cycle by setting the phase to “Being Completed”.

    Note Note

    This phase does not allow you to go back to the “Go Live” phase.

    End of the note.

  9. You set the phase to “Complete Phase Cycle” and you create a new cycle. Any changes that were not finished due to capacity or design issues are transferred to the next phase cycle.The task list used for the phase cycle is assigned to the next phase cycle.

    Note Note

    The system performs an additional check whether any change documents or requests for change that have an ITPPM project assigned are allowed to be reassigned to the next cycle. If the ITTPM project does not allow the transaction to be reassigned, the system displays an error message.

    End of the note.

    The new cycle is displayed on the WebClient UI and you can navigate to it.