Show TOC

Procedure documentationSetting Up Quality Gates and Assigning Phases

 

You use quality gates (“Q-Gates”) to indicate the end of a phase in quality gate management and to release the next phase of your scenario. Quality gates ensure that transport requests cannot be imported into the system assigned to the quality gate until the quality gate immediately preceding the system has been successfully passed.

Prerequisites

  • You have connected your managed systems to SAP Solution Manager.

  • You have defined a logical component group that contains the transport landscape, and you have defined a change control landscape and branch. For more information, see Managing System Landscape Information.

Procedure

  1. Open the Quality Gate Management tile from the SAP Fiori launchpad.

  2. To create a new scenario, click the New Scenario button or to change an existing scenario, choose Start of the navigation path Actions Next navigation step Set Up Scenario End of the navigation path.

    In both cases, a guided procedure appears.

    Note Note

    You can view additional help documentation by clicking the question mark icon (?). You can then expand or collapse the help by clicking the tray.

    End of the note.
  3. In the header data, enter a name and description for your scenario along with the business partners of the quality manager and the member of the quality advisory board.

    If you are making changes to an existing scenario, you can click the Change Log button to view any changes that have been made to either of the manager fields.

  4. In the Define Milestones area, specify the quality gate and milestone data for the scenario.

    • Enter the planned deadlines for all quality gates and milestones. The deadlines for each quality gate must be in the correct sequence.

    • To create your own milestones as quality gates, choose Add Milestone, enter a name and a date for the milestone, and select the Quality Gate checkbox.

    • You can upload template documents for each quality gate. Select the row containing the quality gate and click Upload Template.

      Note Note

      The system administrator uploads templates to the system. These documents can be used by team members, who can download and upload them from the Open Q-Gate window.

      End of the note.
  5. In the Define System Landscape step, enter the change control landscape and branch that were previously defined for the system landscape (in transaction SLAN). The system uses these to calculate the transport track.

    You can also change the order of your system roles here.

    Recommendation Recommendation

    If you use multiple transport tracks, you must ensure that your quality gates are correctly assigned to your system roles. To get the best use from your entire scenario, we recommend that you use different system roles even if the systems have a similar purpose. For example, if your system role is the development system, use the system roles “DEV1”, “DEV2”, and so on. For more information, see Landscape View.

    End of the recommendation.
  6. In the Preview Transport Track step, you can see the transport track that is generated by the system. You can remove individual systems from the transport track by deselecting the checkbox. Depending on your transport track, other systems may then be deselected automatically.

    If inconsistencies are found in the transport landscape, the system displays the relevant messages at this point.

  7. In the Assign Retrofit Systems (Advanced) step, you define the relationship between the retrofit systems and the source systems. If you first select the source system, the possible values for the retrofit system are calculated dynamically and vice versa.

  8. In the Assign cCTS Cluster (Advanced) step, you can view the transport track that is assigned to your scenario.

    The corresponding system information (system, client, and system role) is displayed in the lower section. If you activate the central change and transport system infrastructure, the system searches for appropriate default clusters and assigns them. The clusters are displayed in the Systems table. If the system does not find appropriate clusters, it issues a message saying that no cluster can be found for all of the systems in your transport track. In this case, you must assign the cluster to the system manually.

    Note Note

    If a scenario includes transport requests, the cluster assignment cannot be changed.

    If your system landscape changes, the cluster assignment is automatically recovered from historical transport tracks and this assignment cannot be changed. You can assign new clusters only to newly added systems.

    End of the note.

    For more information about system clusters, see System Cluster.

  9. In the Assign Quality Gates to System Roles step, you specify which quality gate is to be passed for which system. When you specified the branch and landscape in the previous step, each system was assigned to a system role. By connecting system roles to quality gates, you define which quality gate has to be passed before transports into the respective systems are allowed. The corresponding QGM phases are displayed as they are related to the quality gates in the Phase column.

    Select the Enable the Transport of Copies Import in Build Phase checkbox as required:

    • If the quality gate assigned to the system role of the target system is passed, the system ignores the Enable the Transport of Copies Import in Build Phase setting because both the transport request and the transport of copies are imported in any case.

    • If the quality gate assigned to the system role of the target system is not passed, you can import a transport of copies provided that the project is in the “Build” phase, you have selected the Enable the Transport of Copies Import in Build Phase checkbox, and the target system is in the “Test” phase. If any of these conditions are not met, you cannot import a transport request or a transport of copies into the target system.

    Note Note

    This option is relevant only for systems that are assigned as the “Test” phase. It does not affect systems in any other phase (such as “Build” or “Deploy”).

    End of the note.

    Select the Disable Transport Release in Scope Phase checkbox if you want to prevent users from releasing transport requests when the scenario is in the scope phase. This checkbox is selected by default when you set up a new scenario.

  10. In the Confirm Data step, you can check that your data is correct. If it is, choose Finish to create the scenario. Otherwise, choose Back to correct your data.

Result

Your scenario is now activated and ready for use in quality gate management.

Example

You have a four-tier system landscape that includes a development, quality, preproduction, and production system. You have the following options:

  • To put the preproduction system in the test phase, assign the Test to Deploy quality gate to the Production System role.

  • To put the preproduction system in the deploy phase, assign the Test to Deploy quality gate to the Preproduction System role.

Caution Caution

You assign quality gates by entering them sequentially for each system. The sequence is based on the dates of the quality gates, from the earliest date to the latest date.

End of the caution.