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

How can critical objects be defined broadly, and what happens when a developer tries to release a transport containing one?

With wildcard * generalization (object type/name).

When a developer tries to release a normal/urgent-change transport containing a critical object, the release aborts with an error → the change manager goes More → Process Critical Object → Approve Object before it can continue.

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?
Why can the default 'import project all' let unauthorized changes into production, and what fixes it?
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?