SAP Solution Manager 7.2 · Change Request Management (ChaRM)

What happens when a tester clicks 'Confirm Successful Test' on a normal change, and when can it reach production?

The original transport + the latest ToC version are merged, released, and queued for QAS (fully automatic).

It can only import to production once the cycle advances to go-live — deployment is done for all the cycle's normal changes together. Each document is set to production status, the RfC auto-moves to 'if implemented', and the change manager confirms to lock it.

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 does ChaRM control the release of the original transport request?
How do you triage which ChaRM transaction type to use for a given change?
What is the Release cycle (SMRE) used for?