Show TOC

 Creating a Project Cycle for a Project

Use

  • Maintenance projects

    You want to make changes in systems as part of your planned maintenance period, and import all these changes simultaneously into production systems at the end of the maintenance period. For this purpose, you want to create a maintenance cycle, which is represented as a change transaction and by a task list in the Schedule Manager.

    A maintenance cycle is the period of time in which you:

    • Make changes in maintenance systems

    • Include these changes in new transport requests

    • Import these requests into follow-on systems for testing

    At the end of a maintenance cycle, all transport requests are imported simultaneously into all production systems in the project system landscape in the same sequence as the exports. Subsequently, you can either manually close the maintenance cycle, or set its status to In Development. You can generate new change transactions during the test and go-live phases of the project only in maintenance project cycles.

  • Implementation, template, and upgrade projects

    You want to make changes in systems as part of your project, and import all these changes simultaneously into production systems at the end of the project. For this purpose, you want to create a project cycle.

    With the help of this task list you:

    • Make changes in development systems

    • Include these changes in new transport requests

    • Import these requests into follow-on systems for testing

    At the end of a project, all transport requests are imported into the production systems at the same time.

    For implementation, upgrade, and template projects, you can only create change requests in the development phase.

Note Note

If you want to create an urgent change in Change Request Management, first you have to create a maintenance cycle. New urgent changes always have to be assigned to an open maintenance cycle.

If the system landscape of an SAP Solution Manager project is changed incompatibly (if a system is added to a route, for example), you can ignore the checking rules of the task list and continue to use the task list, or you can close the current task list. Subsequently, you can add new systems, or remove systems that no longer apply.

End of the note.

Prerequisites

  • You have created at least one SAP Solution Manager project of the type Maintenance,Implementation, Template, or Upgrade, and specified which systems you want to use for this project.

  • You have created transport routes between the systems that you specified in SAP Solution Manager (in Customizing for SAP Solution Manager→Capabilities (Optional)→Change Control Management →Transport Management System→ Define Transport Routes for System Landscape).

  • You have provided Change Request Management with your configuration data (transaction SOLAR_PROJECT_ADMIN →System Landscape → Change Management→Refresh).

Procedure

  1. Call transaction SOLAR_PROJECT_ADMIN.

  2. Select a project and choose Change Project

  3. Select the System Landscape tab page.

  4. Select the Change Management tab page.

  5. Choose Change Request Management.

    Note Note

    One maintenance project can have multiple development or maintenance systems assigned to it, including the corresponding transport routes (one logical system for Workbench requests and one logical system for Customizing requests, for example). A Schedule Manager task list belongs to exactly one SAP Solution Manager project.

    End of the note.

  6. Select the project for which you want to generate a task list.

  7. Choose Create Task List.

  8. In the dialog box that appears, enter a short description for the new task list (maintenance cycle for project ABC, month 12, for example). This text helps you to find the task list later.

    The system generates a change transaction and task list for managing the operational part of the project.

  9. In the dialog box that appears, choose Task List to navigate to the task list.

  10. On the task list screen, choose Status.

  11. Select Activate.

    The system changes the status of the task list from Created to Development Without Export. Alternatively, you can choose Phase to set the status of the task list as Active. In the dialog box that appears, choose Next Phase.

  12. Choose Phase.

    The system displays the current phase, and allows you to switch from this phase to the previous one or to the next one. In the same way, you can switch between the phases of the service transaction.

  13. Click the General Tasks node with the secondary mouse button.

  14. Choose Lock/Unlock Group/Subsequent Groups.

    The system unlocks the tasks in the task list.

  15. Repeat steps 11 and 12 for the Track of Project <n> and General Final Tasks nodes.

Result

  • The system displays your new, activated task list in the Schedule Manager.

  • The status of the change transaction is Created.

    Note Note

    You cannot create the ID of the task list yourself; the system generates the ID automatically. The name consists of the prefix M (for maintenance), I (for implementation),T (for template), or U (for upgrade), and a consecutive number, which is taken from the number range object /TMWFLOW/M. You defined a number range for this object when you installed Change Request Management.

    End of the note.

All systems that are part of your project landscape including the tasks that have to be executed are displayed in the task list. The sequence in which the systems and tasks (task groups) are displayed depends on the transport track and the types of system roles. In addition, the header contains general tasks and the footer contains general final tasks that automatically appear in every task list that is generated.

The task groups of the task list are displayed in the Schedule Manager as follows:

  • At the highest hierarchy level of the task groups you see the transport tracks that originate from exactly one maintenance system. If you defined <n> maintenance systems in the Solution Manager project, you see <n> task groups for them at the highest hierarchy level.

  • Above the transport tracks, you see a task group for the general header tasks.

  • Below the transport tracks, you see a task group that contains systems without a transport connection (if there are any). These systems are either postprocessing systems or single systems. However, if you have included systems of other types in your maintenance project, but have not defined transport routes in TMS for them, they also appear here.

  • At the bottom of the task list, you see a task group with the general final footer tasks.

  • Each task group for a transport track contains three additional groups, which correspond to the types of system roles. Three groups are always displayed (Source Systems, Target Systems, and Production Systems), even if there is no system for a role type in your Solution Manager project whose role is assigned to this type. The additional group for the systems without a transport connection (Postprocessing Systems and Single Systems, for example) appears if systems have been defined for these groups.

  • The next hierarchy level contains the system roles that are assigned to the role type (but only if there are systems in the roles).

  • The lowest hierarchy level of the task groups contains the logical system (system name and client) of the role.

  • For each system you see the tasks that are planned for a system of this type.

You can now proceed to execute tasks for your projects. If you created a maintenance cycle, you can create urgent changes.

See also:

Changing the Status of Task Lists

Status Administration of Task Lists for Projects