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

What is the Critical Object Check, and why would you need approval at the object level rather than the RfC level?

Approvals are usually at RfC level, but some core business objects need approval at the workbench/customizing object level.

The Critical Object Check blacklists these objects: a developer changing a flagged object gets a warning and must go through a separate approval before it can import. Scope: ABAP only, workbench + customizing objects of SolMan-controlled transports (transports built outside ChaRM don't count); no pre-delivered critical objects — each org defines its own.

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?