SAP Solution Manager 7.2 · Quality Gate Management (QGM)

QGM, ChaRM, and Release Management can each manage transports. What technical layer do all three actually sit on, and what follows from that shared foundation?

Answer locked. Get the free KnowCard app to reveal it — plus spaced-repetition review so it actually sticks.

This is one card from the KnowCard library — thousands more across SAP, Linux, Python and more. In the app you get the answer, AI explanations, and cards that come back right before you would forget them. Free to start on iOS, Android or the web.

More in Quality Gate Management (QGM)

A team assumes they must activate cCTS before QGM can move any transports. Is that correct, and what are their actual options for how transports flow?

After a ToC is released from DEV to QAS for testing, can the developer still keep working in the original transport request?

A change cycle is ending but some transports are still unfinished. What happens to them, and which Q-Gate makes carry-over to a new cycle safe?

At the end of the Deploy phase, QGM offers two Q-Gate options. When do you pick 'Deploy to scope' versus 'End of deployment'?

If a change is rejected in testing 100 times under QGM with ToCs, how many transports reach production, and what is the cost asymmetry that makes this matter?

For QAS to receive DEV changes in QGM, who must act at the Q-Gate — and why won't reaching a milestone alone move the transports?

Start learning today

Free to start — download the app or use it in your browser.