1

2
3
4
Responsibilities:
In principle, four roles can be identified in the process of using Quality Gate
Management:
A development lead is responsible for creating changes and transport requests,
assigning them to the developers and releasing them, when the development is
complete.
An IT Operator is responsible for importing the transport requests into the test
and production systems. He monitors the imports and fixes technical problems
during the import process.
The Quality Manager performs quality checks at certain project milestones. For
example he checks if project documentation and testcases are available in a
good quality. He also checks the result of automated quality checks like code
inspection analyses or completeness of transports in the test system.
The Quality Advisory Board is the steering committee for the implementation
project. It supervises the risks of an implementation project
5
6
7
8
3 different levels of control:
1 Level: Transport Tools STMS (CTS/CTS+)
2/3 Level: Central Transport Management in combination with SAP Process
Best Practice (Quality Gate Management)
9
The phases are separated by quality gates (Q-Gates). Using the Q-Gates, the
quality manager and quality advisory board can check and document the
progress being made in a project. A Q-Gate represents a milestone in a project
and includes a check on the results of the preceding phase. You can record the
necessary results and requirements placed on a given software development
project in SAP Best Practice checklists and documents.
10
11
Overview
A summary of important objects is provided in Change Management, sorted by
the business partner status and function:
Approval is needed for a Quality Gate
Change requests assigned to your business partner
Change documents assigned to your business partner, sorted by change
procedure type, for example, urgent correction
Product maintenance procedures you have created or changed, or to which
your business partner is assigned
Click a hyperlink to go to a view of a filtered list.
For example, as requester of your approved change requests, you go to the
Change Requests view with a list of your approved change requests.
The graphical view of your projects contains an overview of the deadlines, Q-
Gates and milestones in your project. You can prepare existing projects for
quality gate management, or change them, and manage document templates
for the project Q-Gates, with Maintain Project.
12
Implementation Project
Project to implement business processes in an SAP landscape.
Create a project structure from the business processes. You can either create a new
project structure, or base it on one of the following:
...
One or more user or partner templates
An existing project
Scenarios and configuration structures delivered by SAP
An existing production solution landscape
Upgrade Project
A project to upgrade existing systems.
In an upgrade project you can:
Upgrade customizing: Upgrade existing functions
and/or
Delta customizing: Copy additional functions
Optimization project
A project to optimize the flow of business processes, or the use of a software
solution.
Maintenance project
A project to maintain a solution
...
in Quality Gate Management. The project contains all maintenance activities and
urgent corrections of a solution.
13
Which fields are ready for input depends on the user. Quality managers and
members of the quality advisory board, for example, can release a Q-Gate in
one of the following ways:
Initial no status is set.
Partially passed some minor points are still open in this phase, but they
should not delay the project.
Passed the project can go to the next phase.
Not passed - the project cannot go to the next phase.
Re-open - the project can go to the next phase
14
15
16
The risks are collected automatically by the system. The quality manager can
decide before each phase or phase completion, whether all transports have run
correctly into the next system, or whether he must take measures to ensure
that they do so.
The view has two screen areas:
The top area contains the systems and the risk descriptions.
The lower area contains the change requests for your project which are
affected by these errors.
Risks can be, for example:
Open Transports
Transport error (return code 8)
Missing transport requests
Transports which did not run synchronously
The quality manager can react to critical situations appropriately, and asses the
project risk.
17
18
On the risk tab you can see the different Risks based on System and
transport level:
19
On the System Landscape Graphic tab you can see the different Risks based
on System and transport level visualized:
20
21
22
In this example, the Solution Manager Project comprises several SAP systems.
The systems have dependent transports. All transports for the whole solution
are bundled under the umbrella of the Solution Manager project. When the
project goes live all transport requests that belong to the same Solution
Manager project are imported at the same time. So all dependencies are
considered automatically.
23
24
25
26
27
28
29
30
31
32
33
34
35
36