SAP Solution Manager 7.2 · Change Request Management (ChaRM)

How does ChaRM control the release of the original transport request?

Developers only release at task level in the managed system (same as before ChaRM).

The original transport request is auto-released by ChaRM when the normal change is set to successfully tested. If a user tries to release a transport directly in the dev system, ChaRM systematically blocks it (controlled by the admin cockpit's CTS status switch).

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 Change Request Management (ChaRM)

How do email notifications work in ChaRM, and what are they used for?
What must be done before configuring ChaRM?
What can you do in a ChaRM Attachments block, and what does the Advanced button add?
How do you triage which ChaRM transaction type to use for a given change?
What is the Release cycle (SMRE) used for?
How does ChaRM's Approval Management reduce unauthorized-change risk, and where is it available out of the box?