Show TOC

Process documentationCreating Task Lists

 

You can create task lists in the WebClient UI using a guided procedure. Task lists are linked to change cycles. Depending on the cycle type, the following applies:

  • Continual cycle: Each continual cycle has its own task list. You create each task list in the WebClient UI.

  • Phase cycle: If you have created the cycle in the WebClient UI, it has its own task list. If the cycle is created as a successor cycle, the task list is continued and you do not have to create a new one.

  • Release cycle: For all release cycles that have the same change control landscape and branch, the same task list is used. When you put a release cycle in the “Hypercare” phase , the following release cycle takes over all unfinished change documents and continues the task list.

    You have to create a task list in the WebClient UI only if one does not already exist for any predecessor or successor release cycle with the same combination of change control landscape and branch.

Prerequisites

You have created a change cycle. Depending on the cycle type, the system starts the guided procedure automatically when the following status is set:

  • Phase cycle: Set the phase to “Scope”

  • Continual cycle: Set the phase to “Active”

  • Release cycle: Set the phase to “Scope”

    Note Note

    The guided procedure for creating a task list for a release cycle is displayed only if a task list has not yet been created for any successor or predecessor release cycle with the same combination of branch and change control landscape as the current one.

    If such a task list already exists, the system links it automatically to the current release cycle and does not display a guided procedure.

    End of the note.

Process

  1. The system checks whether the prerequisites for creating a task list are fulfilled. It checks for errors, for the RFC connection, for number ranges, and for transport management settings. The system behavior is as follows:

    • If the status is green for all lines, the system has not found any errors. You can continue to the next step.

    • If the status is yellow, the system has found errors but they do not interfere with the task list generation. For example, an RFC error has occurred or the system is not relevant for the transport track. You can continue to the next step.

    • If the status is red, the system has found errors that interfere with the task list generation. You have to resolve the errors before you can continue to the next step.

  2. The Define Scope step contains general information about the cycle. If required, you can add a retrofit system and enable the central Change and Transport System (central CTS). When switching to this step, you can display detailed information on the transport tracks overview. In the transport track overview you can select the desired managed landscape for your cycle. Choose the long text of the displayed message.

    Note Note

    If your system landscape has changed and you recreate your task list, the system does not allow you to remove the central CTS enablement flag if transport requests have been created already. This means that tasks lists that were enabled for central CTS before, have to remain enabled. If it was not enabled, you are not allowed to enable it.

    Any clusters that were already assigned to the existing systems cannot be changed. However, you can assign additional systems or remove existing system to existing clusters.

    End of the note.

    In this step, you choose a task list variant that determines the import strategy of the task list. For more information, see Task List Variants.

  3. The Check Cluster Assignment step is relevant only for central CTS-related cycles. It is skipped automatically for other cycles.

    The system first tries to automatically assign a suitable cluster, based on the transport track. If there is no cluster that covers all systems in the transport track, you have to manually assign the cluster to the systems in the transport track, starting from the source system. The clusters are grouped by transport track header, represented by the full name of the source system, and systems in the transport track. You can reset the cluster pre-assignment and select another cluster. You can also restore the default assignment.

  4. When you choose the Complete step, the task list is created and all information is displayed, including the cluster assignment overview.

  5. From the Related Transactions assignment block, you can navigate to the task list administration in administration cockpit. Here you can perform any required administrative tasks for the task list. For more information, see Task Lists Tab Page.

  6. Depending on the change cycle to which the task list is linked, the following steps are carried out:

    • Continual cycle: The system closes the task list once the related change cycle is closed.

    • Phase cycle: The task list is reused by the successor cycle when the predecessor cycle is closed and you have open change documents or open transport requests. If you do not create a successor cycle, the task list is closed. However, if there are open change documents or open transport requests, there is no option to close the task list.

    • Release cycle: The task list remains active so that you can plan new releases and reuse the task list for the release cycle.

More Information

Change Cycle

Task List

Redefining a Landscape