SAP Solution Manager 7.2 · Quality Gate Management (QGM)

Why does using ToCs mean only one transport ever reaches production, no matter how many test rejections?

Each test rejection generates a new ToC (rejected 4 times = 1 original + 4 ToCs), and ToCs all die in QAS — never entering the production buffer.

Only the original transport (with the latest object versions) goes to PRD. This protects the production buffer, slashes go-live transport counts, and keeps repository objects locked in DEV to prevent conflicts. Even rejected 100 times, only one transport reaches production.

This is one card from the KnowCard library. The full way to learn it — spaced-repetition review, progress tracking, and AI explanations — lives in the KnowCard app. We’re in private beta now; iOS & Android are coming soon.

Join the private beta

Already a tester? Sign in →

More in Quality Gate Management (QGM)

How are milestones technically realized in QGM, and who oversees them?
For QAS to receive changes from DEV in QGM, what must happen at the Q-Gate, and how does that differ from a milestone?
What does the QGM task list handle, and how does it differ from ChaRM's task list?
What are QGM's four standard roles, and what's the benefit of splitting them this way?
What is the quality management process in QGM, and what should you do if building change management from scratch?
Which standard does QGM follow, and what options exist for how transports move?