Show TOC

Component documentationQuality Gate Management


Quality gate management (QGM) provides an integrated and consistent quality process for managing changes and their deployment over all operational units across the various organizations of a company. This enables you to complete the following tasks:

  • Monitor all software change processes and obtain full transparency of these processes

  • Use a project-based or release-based approach to distribute software across systems and technology stacks

  • Gain an integrated and consistent overview of the implementation of changes to your SAP software solution

Quality gate management combines different software developments into one logical structure. These developments are, in turn, collected in “QGM scenarios”. You can organize and monitor how software is distributed according to individual scenarios or change cycles, as well as the changes made for them.

In this way, quality gate management ensures that all software change processes are fully transparent. It does so by centrally managing the software distribution in complex system landscapes across technology stacks and application components. Technically based on the Change and Transport System (CTS), quality gate management integrates the various development workbenches into one central transport and change control system. It also synchronizes the software distribution in the different software stacks.

Note Note

For each QGM scenario, you can also activate the central Change and Transport System (cCTS), which provides a technical infrastructure for the enhanced flexibility functions in Change Control Management. For more information, see Change Control Management Using Central Change and Transport System.

End of the note.

Quality gates quickly enable you to obtain an overview of each scenario or change cycle, as well as its status. Within the overview, the time schedule for the different scenarios or change cycles is displayed along with the ratings of any quality gates that have already been passed.

Note Note

Be aware that Quality Gate Management does not support an integration with Change Request Management.

End of the note.


Before you can use quality gate management for a scenario or change cycle, you must provide certain information such as the quality manager responsible, the quality advisory board member responsible, and the quality gate data.

You can access quality gate management from the SAP Fiori launchpad using the corresponding tile in the Change Management group.


Quality gate management controls the flow of software changes using quality gates (“Q-Gates”). A quality gate is a milestone that determines whether changes can be imported into follow-on systems. Only after a quality gate has received the status “passed” can the data be imported into other systems.

By using quality gates, quality gate management provides you with an overview of your scenarios and their statuses. Deadlines can be displayed either graphically or in list form.

Each QGM scenario comprises four phases: Scope, Build, Test, and Deploy. Each of these phases is separated by quality gates. The quality gates control whether data can be imported into the follow-on systems assigned to the gate. You can import data into a follow-on system only after a quality gate has been passed.

The quality manager and a member of the quality advisory board must approve a quality gate for its overall status to be Passed. Only specified users in a company are authorized to give quality gates the status Passed.

In addition to quality gates, you can specify milestones for your QGM scenario. Like a quality gate, a milestone is the end of a work step, but unlike a quality gate, a milestone does not control whether data can be imported into a follow-on system.