SAP Solution Manager 7.2 · Transport Management (CTS/CTS+/cCTS)

Why can the default 'import project all' let unauthorized changes into production, and what fixes it?

Because import-project-all imports every transport in the queue/buffer together — regardless of ChaRM document status — so an unauthorized change can slip into production.

Fix: configure status-dependent import (IMG: Specify Transport Request Import Strategy) to control promotion by system role + change-document status.

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 Transport Management (CTS/CTS+/cCTS)

Why is TMS foundational to all of Solution Manager's CCM functionality?
Can cCTS be used on its own, and what extra abilities does it bring?
What does CTS+ add, and how does it relate to using the CCM tools?
How do you activate extended transport control for ChaRM/QGM, and what CTC values go where?
What conditions block reassigning a normal change to another cycle?
What is selective import, and why must you be careful using it under ChaRM?